Use first seed when batching images instead of last seed.

[Gecktendo]

When I run aiyabot in batches larger than 1, the last seed is grabbed when I make edits to the prompt instead of the first seed. The result is that I'm not editing the same x seeds, I have to subtract x number of images to get back to the first seed in the image.

[wizz13150]

Hey,
for this you can just comment the line 515 in stablecog.py. It will do the job and keep the first seed.

aiyabot/core/stablecog.py

Line 515 in 8ee436d

batch_seed[10] += 1

Cheers ! 🥂

[Gecktendo]

Wait, so that line was intentional? What purpose did it serve? I thought it was a bug.

[wizz13150]

Same lol.
Not sure ((:

[Gecktendo]

I have another little bug. When I set seed to 0 and I try to pull up the edit, it doesn't preserve the 0 and thus ends up randomizing the seed. I get that this is a silly edge case but I think it should return 0, not "".

[wizz13150]

Hey, @Gecktendo, sorry for the delay !

Hum, indeed, this is a sneaky one !

I won't mention that using 0 as seed is probably not part of best practice with SD lol, you obviously knows it.
My fix for this would be to simply disallow 0 as seed, ahah.

jk jk

Here is what you're looking for, this will allow 0 as value.
Just edit line 77 in viewhandler.py :

aiyabot/core/viewhandler.py

Line 77 in 05840c2

value=input_tuple[10],

to
value=str(input_tuple[10]),

This will do the job.

Screen :

Cheers ! 🥂

[Kilvoctu]

Wait, so that line was intentional? What purpose did it serve? I thought it was a bug.

Looks like leftover code which no longer behaved properly ever since PR #170 was merged. I'd call it a bug.

Thanks for the fix @wizz13150 . I really don't like touching the batch stuff code. If it was up to me, I'd just remove the feature altogether; bad past experiences.