https://civitai.com/models/788550/realflux-10b?modelVersionId=915279

I'm working on a commercial product that currently makes use of SD 1.5, and some of its capabilities that are made possible by its open source nature & community ecosystem - e.g. controlnets, finetunes, LoRAs, etc. SD 1.5 is no longer state of the art though, and we're due an upgrade.

FLUX seems to be the model family of choice in the community at the moment, and playing with [dev] for personal projects, it seems to be at the point where it can achieve all of the features we'd need, with better results than we can currently get from SD 1.5.

FLUX.1-dev seems to be the goldilocks model in this family - [schnell] is a bit more limited, and hasn't gained much traction in the community as everyone is focussing efforts on dev. While [pro] is a bigger, more capable model, that can produce better quality images - in many ways it's even more limited than [schnell], as it's only available through an API that offers very limited control over the generation.

It seems like [dev] would be the ideal model for our purposes, but obviously the non-commercial license keeps us from just jumping right in to using it. However, Black Forest Labs do say that you can get in touch to discuss commercial licensing. We haven't started the ball rolling on that yet - partially because we're still in the model evaluation phase, but also because in my experience, when the licensing / pricing model is "contact us", that usually means we'll be tying up some legal/financial people in a negotiation, as well as developer time in documenting requirements, volume, etc.

The terms state:

you must request a license from Company, which Company may grant to you in Company’s sole discretion and which additional use may be subject to a fee, royalty or other revenue share.

Which doesn't give much clarity on what a commercial agreement might look like, or how likely they are to issue one. I guess this probably varies case-by-case, so it makes sense for them to keep the terms vague to cover different types of agreements they might make under different scenarios. It seems plausible that we might get in touch, just to find out that they only intend on issuing a handful of licenses and we don't qualify - or that the pricing model wouldn't make sense for us. For example, a revenue sharing model probably wouldn't be viable for us, as generative imagery is a relatively minor aspect of our platform, which is sold with enterprise pricing. A royalty model likely wouldn't work for us either, as the outputs are something our customers would be using commercially, and our existing contracts allow unrestricted use of outputs (and I don't see any new customers being willing to sign without that provision).

So, before I recommend kicking off a discovery process that drags a bunch of people into negotiations:

Has anyone here successfully obtained a commercial license for FLUX.1-dev? If so, what did that process look like, and how long did it go on for? Are there any broad indications of the pricing model you're able to share?

I want to learn how everything I use actually works, down to the nitty-gritty details. I'm interested in understanding the mechanics of an upscaler, how a sampler functions, what a VAE is, what masking entails, and what a detailer does. I want to grasp how these concepts work.

I'm also curious about why Flux is a U-Net model while others like DreamMaker are checkpoints, even though they both generate images. I want to learn all of this, but I can't seem to find any comprehensive text guides. I strongly prefer reading to watching videos, and I only tolerate videos from experts or founders in the field, like Andrej Karpathy for LLMs.

Is there a similar authoritative figure for image generation? Alternatively, is there a well-written, end-to-end text guide that teaches image generation concepts thoroughly?

ComfyUI format from Kijai (probably should work with SwarmUI as well) : https://huggingface.co/Kijai/OpenFLUX-comfy/blob/main/OpenFlux-fp8_e4m3fn.safetensors

The below text quoted from resource : https://huggingface.co/ostris/OpenFLUX.1

Beta Version v0.1.0

After numerous iterations and spending way too much of my own money on compute to train this, I think it is finally at the point I am happy to consider it a beta. I am still going to continue to train it, but the distillation has been mostly trained out of it at this point. So phase 1 is complete. Feel free to use it and fine tune it, but be aware that I will likely continue to update it.

What is this?

This is a fine tune of the FLUX.1-schnell model that has had the distillation trained out of it. Flux Schnell is licensed Apache 2.0, but it is a distilled model, meaning you cannot fine-tune it. However, it is an amazing model that can generate amazing images in 1-4 steps. This is an attempt to remove the distillation to create an open source, permissivle licensed model that can be fine tuned.

How to Use

Since the distillation has been fine tuned out of the model, it uses classic CFG. Since it requires CFG, it will require a different pipeline than the original FLUX.1 schnell and dev models. This pipeline can be found in open_flux_pipeline.py in this repo. I will be adding example code in the next few days, but for now, a cfg of 3.5 seems to work well.

Hello everyone.

I've been seraching for ways to up my prompting and overall picture quality using PonyDiffusion V6. On civitai.com I've looked through a lot of pictures, really nice looking ones, and came to see that most of them seem to use the EasyNegative embedding.

Now, I know that EasyNegative is ment for 1.5 and not SDXL, however, these folks seem to make it work. I've downloaded the EasyNegative safetensors and the pt files, but none of them seem to work.

So, my question is, is there anyone willing to help a noob out and tell me how I can manage to use EasyNegative with PonyDiffusion v6?