GitHub: https://github.com/deep-floyd/IF Colab Notebook for running the model based on the diffusers library: https://colab.research.google.com/github/huggingface/noteboo... Hugging Face Space for testing the model: https://huggingface.co/spaces/DeepFloyd/IF Note that the model is substantially more compute-intensive than Stable Diffusion, so it may be slower even though that space is running on an A100.
I tried the HF Space and it generates images of 64x64 resolution, which are basically useless.
DeepFloyd IF: open-source text-to-image model
211–220 of 237 posts
Re: DeepFloyd IF: open-source text-to-image model
#212Seeing a lot of text-to-image out there recently. Does anyone know what the current state of the art is on image-to-text? Thinking something similar to Midjourney's /describe command that they added in v5
This is text + image -> text but pretty cool and still might be of interest to you: https://llava-vl.github.io
Re: DeepFloyd IF: open-source text-to-image model
#213Tried using right now, and it's way better than Stable Diffusion (be it 1.5, 2.1 or SDXL). But is harder to get a good picture. This fine tuned with a good RLHF will be amazing.
Re: DeepFloyd IF: open-source text-to-image model
#214Tried using right now, and it's way better than Stable Diffusion (be it 1.5, 2.1 or SDXL). But is harder to get a good picture. This fine tuned with a good RLHF will be amazing.
What does this mean? Isn't the quality of a model determined by how easy it is to get a good picture?
I've been trying to get a good portrait picture with "neon lights" on Stable Diffusion and it is almost impossible. Meanwhile with the new Dall-e, that was possible. The picture specially with SDXL is good, but it doesn't really have neon lights...
I tried now similar prompt on deepfloyd and managed to get there!
Re: DeepFloyd IF: open-source text-to-image model
#215Is this intended to replace Stable Diffusion? Somebody want to give the eli5?
This does outperform Stable Diffusion 2.1, but uses a different architecture and requires more memory and compute. Stable Diffusion runs its denoising process in a compressed "latent space" which is how it was able to be so compute-efficient compared to other diffusion models. It also uses the (relatively) small text encoder from OpenAI's CLIP model to encode user prompts. Both of these optimizations meant that it co…
Re: DeepFloyd IF: open-source text-to-image model
#216Earlier quoted context omitted.
This does outperform Stable Diffusion 2.1, but uses a different architecture and requires more memory and compute. Stable Diffusion runs its denoising process in a compressed "latent space" which is how it was able to be so compute-efficient compared to other diffusion models. It also uses the (relatively) small text encoder from OpenAI's CLIP model to encode user prompts. Both of these optimizations meant that it co…
Does the increased memory footprint mean it can't be run on a normal desktop like SD?
But there are consumer cards with 14GB+ VRAM, so its not, even before optimization, out of reach of consumer hardware.
Re: DeepFloyd IF: open-source text-to-image model
#217Re: DeepFloyd IF: open-source text-to-image model
#218Re: DeepFloyd IF: open-source text-to-image model
#219I think this model will result in a massive new wave of meme culture. AI's already seen success in memes up to this point, but the ability for readable text to be incorporated into images totally changes the game. Going to be an interesting next few months on the interwebz, that's for sure. Exciting times!
Re: DeepFloyd IF: open-source text-to-image model
#220Earlier quoted context omitted.
This does outperform Stable Diffusion 2.1, but uses a different architecture and requires more memory and compute. Stable Diffusion runs its denoising process in a compressed "latent space" which is how it was able to be so compute-efficient compared to other diffusion models. It also uses the (relatively) small text encoder from OpenAI's CLIP model to encode user prompts. Both of these optimizations meant that it co…
thanks for the explanation! denoising in latent space certainly seems like the "correct" path. My (amateur) thinking is, the more you can do in latent space, the better.
The former seems likely to be lower compute-for-resolution, but that’s not the only consideration for “better”...