Node unresponsive after editing canvas again

[sky958958]

hi~ Encountering a very strange problem, the first queue was successful, But when I am not satisfied with the composition, I adjust the canvas and move the zoom, but the nodes cannot run again, the borders are red, and there is no response operation

[erosDiffusion]

it might have to do with an older node definition as v2 introduced some regressions but workarounds are possible (i'm rewriting the node again to fix the regressions)

• can u try deleting the node and get a new config and a new compositor ? then run again ? maybe have it paused the first time and hit capture once satisfied then re-run without pause.
• to retrigger the run make play with the paused setting or any other configuration setting

if that does not works and

• if the border of the node (not inside the composition is red it means the output is not there usually, try hitting the capture button once images are loaded. eventually reload with the reload button and re-run.

i'm talking of v2 a screenshot and developer tools open (F12 and show the console tab) might help understand what's going wrong

[sky958958]

Hello, if you move the position again, the queue will not work properly

[erosDiffusion]

so, i see some nulls in plugins and that index.js line 381 as red

• this could indicate that i'm not considering store tranform is false and then trying do do something with it. so: make sure you have the latest code pulled, (from the custom node node directory you can "git fetch" and "git pull")
• restart comfy, reload the flow, replace the nodes, set storetransforms and capture on queue to true and re-execute (i mean this should not be necessary but in case node is stuck with missing transforms...)

if that does not help:

• I would disable the three plugins that are mentioned here (mixlab, impact pack and use everywhere) as maybe one of them is incompatible. (I have all and see no issue)

let me know how it goes ;)

if you know how to debug, maybe click on that index.js 281 red line and show me it has anything to do with compositor. you can also give me the flow but i see it's pretty simple.

[erosDiffusion]

@sky958958 so I did a quick check it seems impact pack is searching for something in my custom node events -> output.aux

function progressExecuteHandler(event) {
    if(event.detail.output.aux){
        const id = event.detail.node;
        if(input_tracking.hasOwnProperty(id)) {
            if(input_tracking.hasOwnProperty(id) && input_tracking[id][0] != event.detail.output.aux[0]) {
                input_dirty[id] = true;
            }
            else{

            }
        }

        input_tracking[id] = event.detail.output.aux;
    }
}

[sky958958]

The first queue was successful, but there was no response after only moving the canvas and queuing again workflow - 2024-09-13T211729.070.json

[erosDiffusion]

@sky958958

• disable impact pack
• restart comfy
• leave capture on queue and transform on
• the first time you execute it will block you as there is no reference so it assumes you want to change the composition.
• make your compo
• rerun
• it should now work as intended -> please confirm me if this solve your issue

note: in this version there is actually a bug that if the image does not change it will still re-render, I'm rewriting the plugin so that it does not happen. the new vesion is in pr #37 but not ready for releasing

[sky958958]

Looking forward to your update~Your node is really cool and convenient. Keep me away from those troublesome numerical settings

[erosDiffusion]

did it not work by disabling impact pack ?

to recap, I've also had some wierd behavior when you get a red line, re enqueue again until it goes :) it fixed it for me.

in short, re-enqueue after it breaks until it goes , second or third time it gets it :D

[sky958958]

Even if the impact package is disabled, the same problem will still occur. Now, the storetranorms button must be triggered back and forth to queue

[erosDiffusion]

I see, leave defaults on there should be no need to change them, when you get the red line, just push the enqueue button multiple times.

i hope this helps, sorry for the bad quality https://github.com/user-attachments/assets/d0bb351c-6fa8-4dcb-8f4c-9aeae949d53a

[sky958958]

I don't understand technology, but I have an idea. For example, after adjusting the canvas, there is a control button below that can be clicked to directly trigger the subsequent workflow

[sky958958]

You have done an excellent job, it just takes time to maintain it. This node is the most anticipated one I have ever used

[erosDiffusion]

I don't understand technology, but I have an idea. For example, after adjusting the canvas, there is a control button below that can be clicked to directly trigger the subsequent workflow

in the new version it will come a button like "continue", that does what you ask. I'm working on a wait function that's controlled by pause.

so when you pause the capture will read "continue" (technology wise continue is making the waiting thread move) while enqueue is re-submitting a slightly changed flow that's being stopped (old nodes dont' execute as they are cached)

pr #37 is a rewrite to solve the issues with inconsistent behaviur regarding execution. i'm almost finished but i will not be able to work on it in the weekend :D

[sky958958]

Thank you for your video demonstration. Looking forward to your follow-up updates~Have a nice weekend~

[erosDiffusion]

should be fixed with v3 in pr #46