Closed tholonia closed 7 months ago
yes I am rewriting the readme now and putting most of it into an organized github wiki you can download. For the regular prompt schedule, you need to make sure the max_frames
are matching for both schedules (I normally just use a prim connected to max_frames
converted to an input. For the prompt weight variables (ie: pw_a
), it needs to have backticks as that is what is being parsed by regex. I'll do some testing to see if things are working properly after I have the README.md
sorted. Let me know if you have any other questions with what I have here or anything else you came across. Cheers!
Thank you the prompt reply. I look forward to the updated docs.
I applied your suggestion of using prims for the max_frames, and I removed all refs to the Value_Schedules from the prompt, and I still get the same error. I have attached the smallest possible test case I could make, in case
you want to replicate the problem. anitest.json
I've fixed the issue with the latest commit. you should be able to schedule now. I used your test workflow and altered so you can see the changes better fixed anitest.json. I'll be making example workflows too for documentation. Thanks for your patence I had technical difficulties setting up a new rig in Japan.
I read that you planned on releasing a full workflow for the example in the
README.md
. Is that coming soon? The partial example you do show does not work when I add the missing pieces, or at least when I am guessing are the missing pieces. I just get aPromptScheduler
error no matter what I put in theValue_Schedule
. I have tried a single entry of0:(0.95)
and 120 entries from Keyframe string generator.In your examples, you use both 'pw_a' and `pw_a` (single quote vs backtick). What is the correct usage, or does it even matter?
The error begins around line 161 in
BatchFuncs.py
, but the value ofprompt_weight_1[i]
is being correctly read, so the problem is insidePromotSchedule
, or so it appears.