Closed CaptainGrock closed 6 months ago
I'm travelling at the moment but I'll take a look when I'm home next week. Does the error occur if you don't use the efficient ksampler?
Hi - sorry for the delay. I tried on the normal KSampler and it was the same error message. Thanks for taking a look/fixing (looking forward to feature this in an upcoming video).
Jeff
On Fri, Jan 12, 2024 at 7:37 AM chrisgoringe @.***> wrote:
I'm travelling at the moment but I'll take a look when I'm home next week. Does the error occur if you don't use the efficient ksampler?
— Reply to this email directly, view it on GitHub https://github.com/chrisgoringe/cg-image-picker/issues/72#issuecomment-1889075052, or unsubscribe https://github.com/notifications/unsubscribe-auth/BB7RBRSB6V7UTG7PMDHICWTYOEU7LAVCNFSM6AAAAABBXQGZWWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBZGA3TKMBVGI . You are receiving this because you authored the thread.Message ID: @.***>
Hi - this is a very innovative custom node! I am getting consistent errors though right now. I've included the WF but very basically, creating a batch of 3 in efficient KSampler. Routing to Image Chooser, routing the image to VAE Encode and then to a second KSampler. If I choose any image other than the first one (even with the correct index count provided), I get an index out of bounds error. Can you take a look please?
SampleImageChooser_BUG.json