prompt editing timeline has separate range for first pass and hires-fix pass

[rubberbaron]

Description

• allows a single prompt to be used to express different prompt editing behaviors for the first SD pass and for the hi-res pass
  • for relative times, the first pass is 0.0-1.0 (as before), the hires-fix uses 1.0-2.0.
  • for absolute times, the first pass is 1..steps, the second pass begins at steps and goes hires steps further, e.g. 40 regular steps and 20 hires steps, the timeline ranges are 0..40 and 40..60.
  • the syntax for prompt editing times is different, although 99% of the time the end result should be unchanged
    • if the number has a decimal point, it's relative; if it has no decimal point, it's absolute
    • main observable difference is that [foo:1] means the same thing, but the meaning of [foo:1.0] has changed from absolute (the same as [foo:1]) to relative (about the same as [foo:0.999999])
• code changes
  • capture the number of first-pass steps for use in hires pass
  • hires pass passes both first-pass steps and hires-steps through to prompt_parser.py
  • scheduled visitor chooses abs/relative differently
  • scheduled visitor computes hires pass times by offsetting by the first pass end times
  • plumb everything through
  • add back-compatibliity option
• issues:
  • addresses A patch to stop prompt editing in hires fix, so that it uses the prompt as it is at the final step of the initial render #9281
  • supersedes provide an option so hires fix uses the final step (sort of) of the prompt schedule #12350,

Screenshots/videos:

todo

Checklist:

• I have read contributing wiki page
• I have performed a self-review of my own code
• My code follows the style guidelines
• My code passes tests

[AUTOMATIC1111]

Can you make hires_steps an optional argument so that external code using those functions needs no changes, and remove use_old_scheduling, instead sending hires_steps as None when the option is enabled?

[rubberbaron]

Currently hires_steps is optional in the leaf function but not the higher level ones, so sure, that's not a problem to change.

But current use is that steps=first_pass_steps, hires_steps=None means the first pass but using the new syntax. So I'm not sure what you're imagining for removing use_old_scheduling, because we have to communciate 3 cases to the code: new first pass, new hires pass, old compatibliity mode.

I could do something like hires_steps = 0 or None have different meanings, but I don't really see the value in hacking that over passing around the flag (which can also get a default value)

[AUTOMATIC1111]

has anyone played around with this?

[catboxanon]

No issues I've noticed thus far, granted it's only been a couple days using this.

[selim-yildirim]

has anyone played around with this?

Hello Master,

I tried different plugins. There was some conflict and it affected system files.
When I reloaded, I was able to connect in chrome before. But when I click generate later, text2image and image2image do not produce images.
I tried it in Microsoft Edge and it started to produce patterns.
Then, when I installed kohya_ss, the same problems happened in Edge this time.
now i open mozilla and it works.

Believe me, I'm afraid to try something new.

Any experience and solution for this?