We need more ControlNet experimentation
I have always hated the phrase "What's the use case?" As a reason not to do things. Especially with relation to implementing functionality that is designed to interact with other functionality. The possibilities are endless and often not obvious until discovered.
The recent explosion of images using QR Monster demonstrates the possibilities of using a tool for what it fundamentally does as opposed to what it was designed to do.
There are lot of people out there prepared to dedicate a great deal of GPU time to training Checkpoints and LoRas.
I'd like to call upon people to think up some new and strange Control Nets that might be used for things even if you don't don't yourself know what they would be good for.
Post below any ideas you might have.
Here's some starter ideas.
Perspective lines ControlNet. This would let you have a degree of control over image perspective without explicit lines appearing in the generated image as you would get with using canny (like on building edges).
Pixel variance ControlNet. A little had to describe this, but I imagined a preprocessor that firstly generates a difference map (let's call it QImage) of an image where each value is set to abs(max(thispixel - neighbour)) then a map of the radius around each pixel where the sum of all values in QImage crosses some threshold. In areas of high frequency information the radius would be small. In areas of low frequency information the radius would be large. A ControlNet trained on images using this preprocessor would be able to provide information of where image detail should be, but would not impose any particular orientation on that detail.
Posted Sep 23, 2023, 9:28 PM UTC
The main problem is that most of the datasets for ControlNets are really big.
A) It's daunting to put together a CN if it's not something I readily need and hoping at least someone finds some use
B) Getting the data is a challenge in itself. The QR Monster CNet you see is on the 2nd or 3rd generation where the current training set is like 100,000 or 1,000,000 assets ( I know adding a 0 is a huge difference I just can't recall the exact # from the tweet )
Another issue is that current training sets and process are mostly private. There IS documentation on training but it would be really nice to see 'this is the set of data, this is how it was created, these are the parameters we used for training, etc' for all Cnets being made. Feels very gate kept. When I wanted to learn more about the QR Monster CNet, I reached out to the crew who made it and was ignored ( and this was before the CNet went big ).
[removed]