Live data from Hacker News

FLUX is fast and it's open source

replicate.com

91–100 of 127 posts

Re: FLUX is fast and it's open source

#92
post #39

Earlier quoted context omitted.

They almost certainly did DPO it, so that would have an effect. It was also probably just trained more on professional photography than cell phone pics. I’ve found it odd how there’s a segment of the population that hates a shallow depth of field now, as they’re so used to their phone pictures. I got in an argument on Reddit (sigh) with someone who insisted that the somewhat shallow depth of field that SDXL liked to…

As a DoF "hater", my problem with it is that DoF is just the result of a sensor limitation (when not used artistically etc.), not some requirement of generating images. If I can get around that limitation, there's very little motivation to maintain that flaw. In the real world, if I see a person at the beach, I can look at the person and see them in perfect focus, I can then look at the ocean behind them and it is al…

While you could look at DoF as a sensor limitation, most photographers use it as an artistic choice. Sure, I could take a pic at f/16 and have everything within the frame in focus, but maybe the background is distracting and takes away from the subject. I can choose how much background separation I want; maybe just a touch at f/8, maybe full on blue at f/1.2

Re: FLUX is fast and it's open source

#94
Every time there's a thread about models from Meta, there's a flood of comments clarifying that they aren't really open source.

So let's also set the record straight for FLUX: only one of the models released is open source -- FLUX schnell -- it's a distillation from the proprietary model that's much harder to work with.

Meta's Llama models have ironically much more permissive license for all practical intents and purposes and they are also incredibly easy to fine tune (using Meta's own open source framework, or several third party ones), while FLUX schnell isn't.

I think the open source community should rally behind OpenFLUX or a similar project, which tries to fix the artificial limitations of Schnell: https://huggingface.co/ostris/OpenFLUX.1

Re: FLUX is fast and it's open source

#95
post #39
post #31

Earlier quoted context omitted.

I guess it's optimized for artsy images?

They almost certainly did DPO it, so that would have an effect. It was also probably just trained more on professional photography than cell phone pics. I’ve found it odd how there’s a segment of the population that hates a shallow depth of field now, as they’re so used to their phone pictures. I got in an argument on Reddit (sigh) with someone who insisted that the somewhat shallow depth of field that SDXL liked to…

That's pretty funny. It reminds me of if you grew up watching movies with the standard 24 fps - trying to watch films at 60fps later felt unnatural and fake.

I'll say I'm okay with DOF - it just feels (subjectively to me) like its incredibly exaggerated in Flux. The workarounds have mostly been prompt based adding everything from "gopro capture" to "on flickr in 2007" but this approach feels like borderline alchemy in terms of how reliable it is.

Re: FLUX is fast and it's open source

#96
post #68

Earlier quoted context omitted.

However, the blogs or newspapers or print outlets that used to hire them hired them because you couldn’t- it was a differentiator. That differentiator is gone, and as such won’t pay for it anymore. They’ll just use the same AI as you. This destroys the existing market of the artist. To be clear, my comment isn’t meant as a judgment, just as market analysis.

I think it does not take into consideration how much thought and expertise goes into design work. Have a look at the recent controversy about the live-action shooter "concord" that failed spectacularly mainly due to bad character design. Here are two videos that explain that well. I don't think I would ever be capable of designing with that degree of purpose given a generative AI tool. [1] https://www.youtube.com/wat…

Thanks for the links Im glad there are people who are experts at character design. For my untrained eyes it just looks like all of the characters are muddy coloured ( washed out greens brown etc ) AND they are pretty much all incredibly ugly. I think I saw one that atleast looked fashionable, the black sniper female.

The older I get the more concerned I get that the larger the team that makes decisions the worse the decisions are, whats the word for this? Is there any escape? Teamfortress 2, took years and teams to build, but it was just perfect.

I heard they had a flat structure which is even more confusing as to how they attained such an excellent product.

Re: FLUX is fast and it's open source

#97
post #48

Does someone know what FLUX 1.1 has been trained on? I generated almost hundred images on the pro model using "camera filename + simple word" two word prompts, and it all looks like photos from someones phone. Like, unless it has text I would not even stop to consider any of these images AI. They sometimes look cropped. A lot of food pictures, messy tables and appartments etc. Did they scrape public facebook posts? S…

I highly doubt it’s a product of the raw training dataset because I had the opposite problem. The token for “background” introduced intense blur on the whole image almost regardless of how it was used in the prompt, which is interesting because their prompt interpretation is much better.

It seems likely that they did heavy calibration of text as well as a lot of tuning efforts to make the model prefer images that are “flux-y”.

Whatever process they’re following, they’ve inadvertently made the model overly sensitive to certain terms to the point at which their mere inclusion is stronger than a Lora.

The photos you’re showing aren’t especially noteworthy in the scheme of things. It doesn’t take a lot of effort to “escape” the basic image formatting and get something hyper realistic. Personally I don’t think they’re trying to hide the hyper realism so much as trying to default to imagery that people want.

Re: FLUX is fast and it's open source

#98
post #57

Earlier quoted context omitted.

It's not just flux, you can do the same with other models including Stable Diffusion. These two reddit threads [1][2] explore this convention a bit. DSC_0001-9999.JPG - Nikon Default DSCF0001-9999.JPG - Fujifilm Default IMG_0001-9999.JPG - Generic Image P0001-9999.JPG - Panasonic Default CIMG0001-9999.JPG - Casio Default PICT0001-9999.JPG - Sony Default Photo_0001-9999.JPG - Android Photo VID_0001-9999.mp4 - Generic…

wow this is wild! https://i.postimg.cc/vT6SV7pq/replicate-prediction-6ap8z1jv5... https://i.postimg.cc/vZzMTM71/replicate-prediction-7r4b4p6sj... https://i.postimg.cc/rs6wM5LJ/replicate-prediction-d8s4c93v5... I DEMAND TO KNOW HOW RUN LOCAL SAAR

I’m not sure what saar means here but these images are fairly standard and a drop in the bucket compared to the hideous number of porn fine tunes published daily on civit ai if that’s what you’re looking for

Re: FLUX is fast and it's open source

#99
post #96
post #68

Earlier quoted context omitted.

I think it does not take into consideration how much thought and expertise goes into design work. Have a look at the recent controversy about the live-action shooter "concord" that failed spectacularly mainly due to bad character design. Here are two videos that explain that well. I don't think I would ever be capable of designing with that degree of purpose given a generative AI tool. [1] https://www.youtube.com/wat…

Thanks for the links Im glad there are people who are experts at character design. For my untrained eyes it just looks like all of the characters are muddy coloured ( washed out greens brown etc ) AND they are pretty much all incredibly ugly. I think I saw one that atleast looked fashionable, the black sniper female. The older I get the more concerned I get that the larger the team that makes decisions the worse the…

Bureaucracy and hierarchy are much more damaging to good products than a large team. The flat structure and long timelines are how they overcame the limitations of a large team.

Re: FLUX is fast and it's open source

#100

Earlier quoted context omitted.

This is Sutton's Bitter Lesson : https://www.cs.utexas.edu/~eunsol/courses/data/bitter_lesson...

If I would take the Lesson literally, we should not even study text to image. We should study how a machine with limitless cpu cycles would make our eyes see something we are currently thinking of. My point being, optimization or splitting up int subs, before handing over the problem to the machine, makes sense.

I think the bitter lesson implies that if we could study/implement "how a machine with limitless cpu cycles would make our eyes see something we are currently thinking of" then it would likely lead to a better result than us using hominid heuristics to split things into sub-problems that we hand over to the machine.
Post reply on HN