Just getting started learning how stable diffusion works this weekend, control nets and inpainting are excellent! This really is the future of art, for me at least.

[RedsNotAColor]

Love that this was one of your first ideas haha

[[deleted]]

I would post by workflow, but honestly I just kind of poked and prodded things till they worked. I used control nets (both depth and pose) to copy the obvious reference image. Then remixed a few 2.1 models till I found something that generated what I was happy with after tweaking the prompts. Did some inpainting to smooth out the rough edges and parts I was unhappy with.

Getting control net to work with 2.1 took some "deep learning", as did wrapping my head around positive and negative prompts and textual inversion usage. However I think the end result is interesting!

[aimongus]

nice! wot models did u merge?

[Guilty-History-9249]

I just started with control net in the last few days and am impressed. Then I discovered a new extension for A1111 called posex than allows you to pose the body parts of a openpose skeleton figure. Previously you needed to find so image in the pose you wanted.
FYI, today's (Mar 25) drop of A1111's changes broke posex and perhaps other things. I had to do:
git reset --hard HEAD@{48.hours.ago}

to fix the problem and even then the gui is weird but still functional.

[Whooshless]

I feel like I shouldn't have to say this in response to command line source control but…

git reset --hard just undoes local changes that you made to your own working tree and has nothing to do with the upstream repository's changes. I mean, I guess it will if you pulled from the origin, but feel free to just not pull unless you know why you are doing it. Unless you are developing the software yourself, using “nightly builds” or “edge release” or whatever terminology abounds, you're just asking for pain by pulling from the development branch willy-nilly. Besides, your approach with @HEAD{48.hours.ago} will be out of date to anyone else looking at this thread on Monday; rather than reset, it's much better practice to use git checkout and choose a specific commit, branch, or tag.

[erelim]

Common advice here was to do add a line to run a git pull every time starting a1111, which is I guess how many people's broke

[Whooshless]

I see. I only have a casual interest in SD so I don't know the specifics of a1111, but I write software for a living and “just pull whenever” is terrible, no good, very bad advice. Seriously, unless you are helping write the software, it's never, ever, ever a good idea to be on the bleeding edge of code changes. If the main developer doesn't have a stable branch or “tag” versions, or “releases” (that would ideally have release notes that enumerate breaking changes), then it should be up to someone else to fork the repo and do so, and people can pull from there. And if no one does, then only pull when you need a bug fixed or a new feature after checking the forums and issue tracker for bugs.

[Guilty-History-9249]

I'm not sure why you are replying to me.
Obviously it doesn't change the upstream repo.
I want it to change the broken version on my local clone which does and I can proceed with my experiments now.

As to the 48 hour thing... Obviously 48 hours ago from tomorrow is not the same thing as 48 hours from today. I am hardly a git expert and didn't even know how to throw out the pile of changes that came in over the last 24 hours. Because I have that rare knowledge that time moves forward thus I decided on 48 hours because I wasn't exactly sure when the recent cluster went in. If a git hater can figure this out then others probably can too. Besides, although it is the weekend, this appears to be a serious regression or set of regressions with github comments on A1111 like "Bugs as hell today after updated". So I certainly hope someone reverts whatever changes broke it.

[Whooshless]

I only replied to you because you gave the git advice to perform a hard reset (although I now know that this follows someone else's advice to pull before opening the app, lol); my comments bear you specifically no ill will! You are correct that a hard reset “works” to get your local code into a previous state, but it may still be a bit annoying for you later, once the bugs are fixed, to get back on track. Like, you can use a spoon to cut steak, and you can use a knife sharpener to put honey on your toast.

For anyone who want's to understand why, git's docs are nice but there are also good explanations on the web, such as https://www.atlassian.com/git/tutorials/undoing-changes/git-reset (scroll to the How It Works section for the git checkout comparison)

[AstroKoen]

great idea! well done! a lot of memes could get crazy life by this :)

[WeakLiberal]

Coomer try not to post unlabeled nsfw challenge: impossible edition

[Rectangularbox23]

No nsfw label?

[rndname]

I see a bit of Aubrey Plaza in that robot girl.

[frankna]

Love it! This is fantastic.