Add a new parameter that creates a unique and increasing value assigned to each batch for each client that can be used in paths

[brendanhoar]

Feature Idea

While there are parts of the date/time that can be used, as can the seed, sometimes either SwarmUI or Comfy (not sure which) will reorder generation within a batch starting on a fixed seed. This leads to a larger seed being generated before a smaller seed.

Utilizing the date parts, the seed and the batch id does not seem to leave me with a way to sort multiple batches alphabetically and have the seeds presented in order if the backend reordered the seeds.

Perhaps something based on combined or separate items such as [client_ID] and [API_call_count], where the latter would an integer that always increases over time, even between restarts. If the between restarts part is too complex, perhaps adding a [date_time_of_backend_start]?

I dunno, just an idea to work around the unexpected reordering of generations in a multi-image batch. Maybe there's something better?

B

Other

No response

[mcmonkey4eva]

the time for outpath format is now the time that the request was made, rather than the time the image is saving at
Added [millisecond] and [request_time_inc] to better distinguish fine differences. Notably request_time_inc is an arbitrary incrementer at a sub-minute level, so [hour][minute][request_time_inc] is reliably linear. Also [hour][minute][second][batch_id] is almost always orderly as well