You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the recent update (December 30th), workflows utilizing regional conditioning with masks and Hook LoRA are no longer functioning as expected. Specifically, the crash occurs when using the Cond Set Default Combine node in combination with regional conditioning.
The issue seems to be tied to recent changes in how sigmas are managed, as workflows without regional conditioning (or masks) work correctly.
Steps to Reproduce:
Use the hook-test.json workflow (attached below).
This workflow works correctly after the update.
Modify the workflow to use Flux with masks and add the Cond Set Default Combine node.
Image example:
Run the workflow.
Expected Behavior
The workflow should execute successfully, with the Cond Set Default Combine node handling unmasked areas without issues.
Actual Behavior
The workflow crashes when using Flux with masks and the Cond Set Default Combine node.
An error related to model options is displayed.
Additionally, the workflow takes significantly longer to process compared to previous versions.
When replacing Cond Set Default Combine with Cond Set Props Combine, the workflow executes without crashing.
However, this alternative significantly increases processing time, taking approximately 30 minutes to complete, compared to the 60 seconds it previously took before the update.
The text was updated successfully, but these errors were encountered:
Thanks for the report, once that PR is merged the default conds issue will be fixed.
As for the performance difference, it's unrelated to any code changes, just bad luck with other memory usage on the system. Using default conds vs manually adding a cond with a mask has no difference in memory usage. I will be working on adding code to automatically determine when it will be better to not bother with caching weights that have to be offloaded vs. calculating them on the fly (slowdown in either way, but one should be faster than the other).
Thanks for the report, once that PR is merged the default conds issue will be fixed.
As for the performance difference, it's unrelated to any code changes, just bad luck with other memory usage on the system. Using default conds vs manually adding a cond with a mask has no difference in memory usage. I will be working on adding code to automatically determine when it will be better to not bother with caching weights that have to be offloaded vs. calculating them on the fly (slowdown in either way, but one should be faster than the other).
Thank you! I saw your change, and it's working now!
Your question
After the recent update (December 30th), workflows utilizing regional conditioning with masks and Hook LoRA are no longer functioning as expected. Specifically, the crash occurs when using the Cond Set Default Combine node in combination with regional conditioning.
The issue seems to be tied to recent changes in how sigmas are managed, as workflows without regional conditioning (or masks) work correctly.
Steps to Reproduce:
Expected Behavior
The workflow should execute successfully, with the Cond Set Default Combine node handling unmasked areas without issues.
Actual Behavior
@Kosinkadink
#6273
Logs
Other
Additional Notes
When replacing Cond Set Default Combine with Cond Set Props Combine, the workflow executes without crashing.
However, this alternative significantly increases processing time, taking approximately 30 minutes to complete, compared to the 60 seconds it previously took before the update.
The text was updated successfully, but these errors were encountered: