You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Stable Diffusion can reproducibly generate image resources, I was thinking it might be nice to have some standard protocol for accessing or referencing its output that can be easily exchanged or embedded in web pages, copy/pasted between GUIs, etc.
The idea would be to have a short text snippet "link" that gives you everything you'd need to reproduce an image. These would perhaps be used to save transmission bandwidth of the actual image(s) or to easily save or share links as an educational tool or what-have-you. Also a history, such as in a SD "browser" could be retained to easily locate any previously generated experiments. You could easily compile collections of related images, include them along with images in a tweet (if the prompt fits), put them in QR codes, etc.
Any parameters/arguments skipped would use the default for that model. Obviously this is incomplete and would need a more rigorously-defined standard.
These URIs can be easily copy/pasted, parsed into json, xml etc., displayed in a SD front end form, etc.
If SD as a scope is to narrow, maybe the path could look more like genimage://stablediffusion/releaseversion... OR maybe keep the transport protocol undefined/open? I'm not an expert with creating URIs formats clearly.
Is this a dumb idea or not the best way to do it? Does this already exist? Add any thoughts, and if it's a good idea, I may implement it in the GUI I've been contributing to.
ft
The text was updated successfully, but these errors were encountered:
Since Stable Diffusion can reproducibly generate image resources, I was thinking it might be nice to have some standard protocol for accessing or referencing its output that can be easily exchanged or embedded in web pages, copy/pasted between GUIs, etc.
The idea would be to have a short text snippet "link" that gives you everything you'd need to reproduce an image. These would perhaps be used to save transmission bandwidth of the actual image(s) or to easily save or share links as an educational tool or what-have-you. Also a history, such as in a SD "browser" could be retained to easily locate any previously generated experiments. You could easily compile collections of related images, include them along with images in a tweet (if the prompt fits), put them in QR codes, etc.
I'm imagining something along the lines of:
stablediffusion://releaseversion/imagename.jpg?modelversion=1.5&seed=234322322&type=txt2img&size=512x512&count=1&ddimsteps=50&prompt=an%20astronaut%20rides%20a%20horse
Any parameters/arguments skipped would use the default for that model. Obviously this is incomplete and would need a more rigorously-defined standard.
These URIs can be easily copy/pasted, parsed into json, xml etc., displayed in a SD front end form, etc.
If SD as a scope is to narrow, maybe the path could look more like
genimage://stablediffusion/releaseversion...
OR maybe keep the transport protocol undefined/open? I'm not an expert with creating URIs formats clearly.Is this a dumb idea or not the best way to do it? Does this already exist? Add any thoughts, and if it's a good idea, I may implement it in the GUI I've been contributing to.
ft
The text was updated successfully, but these errors were encountered: