deforum-stable-diffusion VS automatic

This looks a fine-tune of the classic zero123 (https://github.com/cvlab-columbia/zero123) I’m excited to check out the quality improvements.

Though 3d model synthesis is one use case, I found the less advertised base reprojection model to be more useful for gamedev at the moment. You can generate a multiview spritesheet from an image, and it’s fast enough for synthesis during a gameplay session. I couldn’t get a good quality/time balance to do the same with the 3d models, and the lack of mesh rigging or animation combined with imperfections in a fully 3d model tends to break the suspension of disbelief compared to what players are used to. I’m this will change as the tech develops and we layer more AI on top (automatic animation synthesis is an active research area).

If you’re interested in this you might also want to check out deforum (https://github.com/deforum-art/deforum-stable-diffusion) which provides even more powerful camera controls on top of stable diffusion designed for full scenes rather than single objects.

2/Deforum – Open source and good at developing trippy videos – I have not used this too much (https://github.com/deforum-art/deforum-stable-diffusion)

Why is StabilityAI releasing what seems to be a clone of Deforum ?

might be deforum (project) (webui extension) or img2img loopback wave (webui extension). it's definitely something with img2img though. that's clear from how it's warping.

Sorry, I missed it, thanks to Deforum: https://github.com/deforum-art/deforum-stable-diffusion

Have you seen Deforum? Kinda sounds like you're about to reinvent it. :)

I'm talking about it https://github.com/deforum-art/deforum-stable-diffusion It is not possible to put in a separate environment.

> it won't ever be a viable option

For production workloads, I generally agree. It's an unsupported hack with a questionable future, I wouldn't do anything money-making with it.

However, for tinkering and consumer workloads, it already works pretty well. Enough of cuDNN and cuBLAS work to run PyTorch and in turn, Stable Diffusion with https://github.com/lshqqytiger/ZLUDA - there's even a fairly user-friendly setup process already in https://github.com/vladmandic/automatic .

I was able to get a personal non-ML related project working on my AMD card in just a few minutes, which saved me a lot of development time before I then deployed the production workload on NV hardware (this is probably why AMD pulled the plug on the project - it's almost more of a boost to NV than anything else, AMD really need people to be writing code on ROCm to deploy on AMD datacenter hardware).

While I currently use SD.Next[1], I have tested ComfyUI locally with my AMD card. The UI can be daunting, but you learn quite a great deal about how a Stable Diffusion pipeline works. In addition some innovations and advances find their way into ComfyUI first.

[1] https://github.com/vladmandic/automatic

I used SD.NEXT ( https://github.com/vladmandic/automatic ) and https://civitai.com/models/82098/add-more-details-detail-enhancer-tweaker-lora and epicphotogasm_lastUnicorn

I found this thread on GitHub talking about how this was fixed in the latest version with an optional setting. I tried enabling it, as they mentioned, but it just resulted in an immediate CUDA out of memory error when starting generation. So it seems I'm actually needing the shared memory, which I assume is my issue.

As always, do check out our more detailed changelog, give us a quick install from our Repo, and stop by our Discord Server for any questions or help you may need.

SD.Next

Today I finally wanted to give SDXL a chance, so I set everythin up according to Vladmandic's Wiki https://github.com/vladmandic/automatic/wiki/SD-XL

I'm trying to get SDXL working on Vlad's SDNext, but I keep getting the error in the title when trying to run basic operations. I'm not sure what's going on, I followed his guide for it to a T.

We used an inference container based on SDNext, along with a custom worker written in Typescript that implemented the job processing pipeline. The worker used HTTP to communicate with both the SDNext container and with our batch framework.