41–50 of 59 posts
For those who don't know, ControlNet is often used in conjunction with Stable Diffusion. It lets you add extra conditions to guide what is being generated. There are extensions for Automatic1111's stable diffusion webui that can make use of ControlNet. Some examples I've seen are copying the pose of a person/animal in an image and outputting a different person with the same pose (and extending to videos). Also taking…
Interesting, and I look forward to using it, but I wish the distribution had kept the folder-name conventions of AUTOMATIC1111, so that we could more easily have used symbolic links for folders of LoRAs and checkpoints etc. that we'd rather not duplicate.
Can't you symlink individual files? More effort but only a quick bit of scripting away. (I've occasionally used a duplicate file eliminator that finds dups over a certain size and replaces them with symlinks. You can run it on an entire subtree or drive)
"Native refiner swap inside one single k-sampler. The advantage is that now the refiner model can reuse the base model's momentum (or ODE's history parameters) collected from k-sampling to achieve more coherent sampling. In Automatic1111's high-res fix and ComfyUI's node system, the base model and refiner use two independent k-samplers, which means the momentum is largely wasted, and the sampling continuity is broken…
As a frontend developer, this reads to me as technobabble you'd find in entertainment media. In general, I learn about things not directly related to my sphere of interests by osmosis, but this is on another level. Reminds me of the time when I started my computing journey. I wonder if I'll be able to understand this eventually just by reading a relevant comment or blog here and there.
But anyway, it's the same here except that of course AI and machine learning is a far vaster topic than React so there's going to be more than twenty terms to learn.
For those who don't know, ControlNet is often used in conjunction with Stable Diffusion. It lets you add extra conditions to guide what is being generated. There are extensions for Automatic1111's stable diffusion webui that can make use of ControlNet. Some examples I've seen are copying the pose of a person/animal in an image and outputting a different person with the same pose (and extending to videos). Also taking…
Not to forget crazy creative QR codes that still scan! https://stable-diffusion-art.com/qr-code/
Earlier quoted context omitted.
Not to forget crazy creative QR codes that still scan! https://stable-diffusion-art.com/qr-code/
I've been playing with that. It's really hard to get right. My end goal is to have a nice picture I can frame and put on the wall in my home, but then if anyone asks for the wifi password I tell them to take a photo of it with they phone.
Earlier quoted context omitted.
Tbh I’m (loosely) following commit message best practices in all of my projects out of irrational fear of being viewed as unprofessional. But never needed that effing prose in my workflow. Maybe a keyword from time to time. I’m using code, not messages to navigate history, and in a rare occasion. If all my messages turned into “i” I’d lose nothing, because all rationales and essentials are in code comments. I’d bette…
The commit contents can tell you what changed, but it can never tell you why it was changed, what the authors thoughts were, what corner cases they took into account, whether it was a temporary workaround for something that's no longer a problem... (unless of course the author is a stickler for inline comments, which I also approve of)
Earlier quoted context omitted.
I've been playing with that. It's really hard to get right. My end goal is to have a nice picture I can frame and put on the wall in my home, but then if anyone asks for the wifi password I tell them to take a photo of it with they phone.
What a great idea, I'm going to do that too!
Right now though the process I have is to make 16 at a time with various settings and seeds and then run my phone over them all and see which ones the camera can read as QR codes. Finding one that is both nice to look at and reads reliably is rare.
Earlier quoted context omitted.
Commit comments are how you find code diffs. Focus on what/why in your commit messages. If you can’t articulate that in your commit messages, I can almost guarantee you’re thinking deeply enough about your code changes.
I appreciate advices, but I believe this one is not on point I expressed, as it only reiterates on a premise that I follow already but find mostly useless irl.
Your style of commit message is a crime against the future. It makes it impossible for a future developer to understand why you did something or what you were thinking.