The diff that apparently does the RAM optimisation, quite simple and something to learn form:
https://github.com/basujindal/stable-diffusion/commit/47f878...
Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM
111–120 of 151 posts
Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM
#112How much VRAM was previously required?
512x706 on rtx 2060s with 8gb vram
Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM
#113Earlier quoted context omitted.
But anyone with enough time to learn (or money) can do it anyways without much effort. (I'm trying to understand the exact difference here.) So it boils down to democratization? That anyone can do it regardless of skills acquired?
It boils down to who's doing it. An artist in photoshop the artist is responsible. An AI asked to do it likely the people that made the AI is responsible (until AI can think for itself). Take it out of drawing. If you write a program to control elevators and it breaks the elevators aren't you, the person that wrote the program, responsible? Why would Adobe be responsible for something someone else draws? Or let's tak…
Perhaps it's the use of the AI moniker but this thing is a computer program under the control of a human, who is the person responsible. It takes time and effort to use and is very much not like automated elevator control. In order of difficulty:
1) figuring out how to rejig the prompt to get what you'd like, adjusting seeds and tuning configuration options. The more control you want, the more complex and manual the pipeline of backing software will be. All it does is amplify everyone's innate artistic talent.
2) Coming up with a good prompt. This relies on the person's imagination, facility with words and familiarity of limitations of the image generating software and its training datasets.
3) Selection. This can be a frustrating experience that tries one's patience.
> made a very pornographic image. Who would get the blame?
You would, it's not like the software automatically distributes all its generations. The vast majority of images these software generate are not good enough to be shared and aren't. You made the conscious decision to share it.
Even if it were an AGI, you would be responsible. It's very much possible to commission a ninja from a human artist and get something very pornographic on a famous celebrity and you would be held responsible for choosing to share it, you had the choice not to.
Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM
#114Earlier quoted context omitted.
Perhaps, but there comes a point where the technology is out there whether we like it or not. We should criminalize bad uses, not engage in some futile attempt to try to stuff the proverbial cat back in the bag
Don't let perfection be the enemy of good. Anyone with a basic machine shop can modify an AR15 for fully automatic fire, and a bump stock can be fabricated even easier. That doesn't mean we should just give up and make these things legal and easily accessible to everyone.
An automatic rifle has almost no positive use to it. This software is not like that and more like something that makes everyone better at a skill, uniformly raising the artistic talent floor. The large majority benefit but some would use their new earned skill for bad. It would be like denying literacy and the printing press because there will always be some people who use it to write very bad distressing things, manipulate more easily en masse and spread misinformation.
Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM
#115For everyone about to comment on the garbage in the commit: It looks like the committer made their changes in the top commit, then merged the updated CompViz StableDiffusion change set on top of it for some reason. That's where the license change, rick astley image, etc come from. And yes, StableDiffusion from the original repo will rick roll you if you try to generate something that triggers its NSFW filter. Here's…
> And yes, StableDiffusion from the original repo will rick roll you if you try to generate something that triggers its NSFW filter. It goes without saying that the authors of a piece of software have the right to make the software do whatever they want, but that shouldn't stop us from recognizing that AI engineers are starting to act like megalomaniac overseers who consider it part of their mission to steer humanity…
> Who exactly do these people think they are?
Software engineers who took the time to think about the ways that their work could be used.
How many times have we seen on HN people pleading with developers to think about the ethical dimensions of their work?
Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM
#116Earlier quoted context omitted.
Nah it’s just basic due diligence for releasing an open source app of this nature. Turning it off is a simple one line change, because everything is obviously named. This is not some high wall to scale. As someone that manages nsfw open source projects, this move seems fine to me. And actually kinda hilarious.
If what StableDiffusion did was ask the user something like "The prompt you entered may result in the generation of content some people find objectionable. Are you sure you want to proceed?", then I would buy your argument. As currently implemented (and the implementation took more work than a confirmation prompt would have!), it's an obvious attempt to control, rather than protect, users. They try their best to dres…
What would the average 11 year old answer?
Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM
#117Earlier quoted context omitted.
Yes, the megalomania of someone who makes their code and models freely available.
StableDiffusion isn't freely available, in the "Free Software" sense. They use the highly uncommon "CreativeML Open RAIL-M License" which is a wall of text composed of weasel words describing how the software is so incredibly advanced and dangerous that despite the authors' earnest wish to do so, they cannot in good conscience make it genuinely Free Software. These people wrote a bunch of Python code that pipes image…
You may be right in the larger sense, but the word you're looking for is conceited, maybe.
Megalomania: obsession with the exercise of power, especially in the domination of others
Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM
#118Earlier quoted context omitted.
This applies just as much if not more in a closed team setting. Personally I blame juniors that insist on using the git CLI instead of a million visual GUIs to git. They get told just do a git commit, have no idea what they changed so can't produce a meaningful commit message, and because it's the command line good luck getting a visual representation of what you're committing.
> and because it's the command line good luck getting a visual representation of what you're committing I don't get the point here. I've never met a developer who knew about `git commit` but didn't know about `git diff` (sometimes I pointed out `git diff --cached`). I don't think you can blame the CLI on this. It's about the lack of proofreading, in my opinion.
I'm exaggerating a bit of course, but the point still stands. Git diff and git status even with color are practically impossible to read and understand past a couple changes, and if it's across multiple files and code being re-arranged it's hell. And getting a junior to wire up a GUI diff tool to display and show those items? Impossible. Also, getting juniors to commit parts of a file or only a subset of them? Again, impossible.
Maybe you work with a higher/better caliber of juniors than I do. At this point, I'm seriously contemplating being a mean dictator and forbidding commits outside of a dedicated GUI until they can prove their adeptness at using the CLI, which they should learn on their own time.
Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM
#119For everyone about to comment on the garbage in the commit: It looks like the committer made their changes in the top commit, then merged the updated CompViz StableDiffusion change set on top of it for some reason. That's where the license change, rick astley image, etc come from. And yes, StableDiffusion from the original repo will rick roll you if you try to generate something that triggers its NSFW filter. Here's…
> And yes, StableDiffusion from the original repo will rick roll you if you try to generate something that triggers its NSFW filter. It goes without saying that the authors of a piece of software have the right to make the software do whatever they want, but that shouldn't stop us from recognizing that AI engineers are starting to act like megalomaniac overseers who consider it part of their mission to steer humanity…
Read the tweets of the Stability AI, company behind Stable Diffusion, founder. He agrees with you. The image is purely to protect themselves against criticism, takedowns, possible legal action, stuff like that.
Re: Stable Diffusion PR optimizes VRAM, generate 576x1280 images with 6 GB VRAM
#120I've been using the HuggingFace diffuses repo[1] with 6GB of VRAM fine. It's well engineered, maintainable and with decent installation process. The branch in this PR[2] adds M1 Mac support with a one line patch and it runs faster than the CompVis version (1.5 iterations/sec vs 1.4 for CompVis on a 32 Gb M1 Max, I highly recommend people switching to that version for the improved flexibility. [1] https://github.com/h…
I wouldn’t recommend using that as-is. MPS doesn’t give deterministic random number generation, which means that seeds become meaningless and you won’t ever be able to reproduce something. You can work around it by generating random numbers on the CPU and then moving them to MPS, but that probably requires a fix in PyTorch. The MPS support issue for diffusers is here: https://github.com/huggingface/diffusers/issues/2…
That's really annoying, even though I hadn't noticed it until now. I can confirm this is an issue.
But the situation seems to be the same on the CompVis derived repos, right?
So this is no worse off, but with better engineered and faster code.