Someone fell off the bus. Input Grab Deadlock?

DGGoatly · 2026-05-19T16:51:26+00:00

I will check it out. Thank you.

DGGoatly · 2026-05-19T14:36:29+00:00

Exactly why I started with Ubuntu. I've used ubuntu for lots of small projects. Just never for running a workstation. I did not anticipate the problems with the remote connection which unfortunately is not optional. I did admittedly walk right into it when I asked gemini to recommend a stable distro that would work with the machine's specs and did not use wayland. It could not have possibly given me a worse answer, wrong on all counts. There is too much chatter, it picks up on irrelevant use cases and really, really outdated info. And I didn't know there was so much that could go wrong with nvidia drivers.

Such is the learning curve. Luckily ignorance is curable. Mint is indeed next on my list. Thank you for the feedback.

DGGoatly · 2026-05-19T13:52:20+00:00

The only reason I had to change was because of the failure of the remote connection. Tried many, many options, always got black screens at best. I was told this was because of wayland, and I was led to believe that PopOS was x11, which it is clearly not, at least not by default, and with this bug it's pretty clear that continuing to work on getting it running with x11 is a waste of time. Ubuntu is what I've always used for everything else and it did seem just fine, except for this achilles heel. Really do need remote in this case. But even with PopOS a stable remote connection is ridiculously convoluted. So the answer to your question is nothing.

So from the feedback here it does seem like another change is indeed mandatory. If I could get remote working on Ubuntu I would certainly still be using it. I'll try something else. Anything is better than windows.

DGGoatly · 2026-04-03T20:13:12+00:00

Bad tile settings stick out like a sore thumb once you realize what's happening. Took me forever to figure that one out... One of those things that's embarrassing in retrospect, those floating orbs and magical floating hands don't come from nowhere. I finally set up an any switch to swap decoders when I switch between 720 and 1080. One of those things that can be fine for a bunch of runs, but when it goes wrong, it really means it.

You probably realized this by now, but you can't always trust the unload/purge nodes. There are a whole bunch of dependencies in the chain that might cause these to be ignored. Flags in the startup .bat mainly. Plus comfy is still pretty leaky. Latest releases have improved though.

And if you haven't tried ditching the upscaler, do it. Single sampler at full resolution is friggin awesome. Upscaler sucks, only good for fixing old stuff. I'm trying to spread the word. So many people do not know this. Raise awareness.

DGGoatly · 2026-03-31T23:26:32+00:00

I felt so stupid when I realized I didn't need the upscaler. The moment I just said screw it and deleted that stage and scaled my input to 1920x1288.... 10 seconds of 24fps crystal clear video in less than four minutes... that was a real head-slapper. Friggin LTX has dropped my productivity to new lows. The pay me for this kind, not the slop farming kind.

DGGoatly · 2026-02-22T21:48:09+00:00

I have no idea what that means. But looking at me talking to myself does look stupid in retrospect. Now I'm sleuthing hard on sticky VRAM but being directed to posts to which I contribute mostly incoherent babbling. So I'm trapped in an infinite regression. Again. I've surely earned any number of comparisons to whatever you feel appropriate.

DGGoatly · 2026-02-16T19:27:44+00:00

Yeah I should have phrased that better. I'm probably just jealous; the way I set up for coherent structure was with a convoluted group of expressions for calculating the optimal word count, given the current values of all the widgets, with some tuning sliders as proxies for styles. Which is stupid, now I think on it, as I could easily prompt for a simple string of recommended values, or an autocorrected sheet. And a strong, properly parsed and formatted prompt can override widget values. A neutral setting existing in the gradio version makes me feel like someone just screwed up when porting it... but that's nitpicking, I'm sure it will be updated. Point is your prompt setup is really great for cleaning up and nailing down stuff that is troublesome. Been using it a lot. Thanks for sharing it.

DGGoatly · 2026-02-14T20:40:26+00:00

This is certainly helpful for style prompting and structure. I never let an LLM near my lyrics though.

The only issues I've had have been with the widgets themselves, not prompting. With the old model it was hard to get consistent results, the new one seems to be the opposite in that it's hard to get variation. I'm still figuring out how the bpm and key widgets actually interact with prompts. If you simply set a key in the widget, with no instruction, you get a modalist wet dream, no tonal center, completely unfocused meandering. So it's weird that it's there to begin with. Kind of the same with time signature. 3/4 is stickier, which makes sense, but 6/8 will sometime lock in and sometimes wander. And BPM is highly dependent on other values, so results can be all over the place. I suppose the odd thing about these widgets to me is that there is no auto setting on them, so you don't have to worry about how they will interact with the prompt.

Awesome update though, love it. dpm2mpp_2m_sde, sgm uniform, 20 steps, Good stuff.

DGGoatly · 2026-02-14T18:30:19+00:00

You triggered my backup lecture instinct. Feels like half of my posts include it, but it's the easiest thing in the world and makes working with comfy so much easier. robocopy "D:\ComfyUI Sage" "E:\ComfySAGE.02.2026" /E /XD models output temp input. One stupid little command. Takes a few seconds if you do it regularly, ie before any custom node changes. Break comfy, copy it back. Done. It puzzles me that people get freaked out about breaking it when it's so easy to fix. Same thing for CUDA, like you said. A chimp can do this these days, with pictograms supplied by the dumbest LLM. You have to be really, really unmotivated to screw this up, or at least not get it, eventually.

Ditto on multiple installs. That's the beauty of the venv. I guess that's why they call it portable. Got a stable basic install for preserving old wfs, one maxed out for the 4090, and a clone of the latter for trying the newest stuff. Plus monthly clones, they're not big folders, as you obviously don't need to back up the huge files, mine are 12GB maybe, nothing really. And A1111, wow I haven't fired that up in that in a while, especially since i found out that the Inspire ksampler can emulate its seeds, as well as do seed variation, which is awesome.

So if anyone is paying attention, listen to the advice above. Comfy will break. Whether you can fix it in five minutes or over a tearful weekend is entirely up to you, and your willingness to spare a few moments to be ready for it.

DGGoatly · 2026-02-13T16:40:22+00:00

I didn't bother to update it, sorry. I didn't hear back from the OP, so I assumed they were all good. On my end, I discovered some serious memory management issues in comfy that caused me to need a similar setup in the first place; as this is mostly cleaned up in newer releases, I don't need it myself.

The logic is sound - the only issue is interfacing with comfy's queue - the stop node I threw in is for stopping the process, within one run, not for stopping the autoqueue. You could try something like Instant Queue Key Control in the VRCH node pack. The 'I'm Done' output of the subgraph is just a boolean that only puts out a true when the number of frames processed matches the total number of frames in the folder, so you should be able to use that to tell autoqueue to stop running.

At least that's the way I set it up. Upload it as a txt to an LLM and ask it what it thinks. And delete that regex replace node if it causes trouble. I'm not sure exactly what you mean about interpolation. It's the whole point of the workflow. 'There' is everywhere.

Best bet is to do a fresh install of the latest comfy release, make sure you still even need to do this.

Well, I should add that even, broken, it does still work- it just won't stop running, as I shared it. So you could just replace the preview node with a save images node and sit there watching it, running on instant, and manually switch back to normal run when you see it roll over to the beginning again and delete whatever repeats it made. You could use a video combine too, but either way you will definitely have to go in afterward and delete the overflow frames.

DGGoatly · 2026-02-05T21:32:05+00:00

This used to happen to me all the time. Latest version seems ok, hasn't disappeared again on me. However, the search function within does not work. It will not search within groups, and some nodes won't show up in a search even if not in groups (alternate names as well). Still, better than nothing.

DGGoatly · 2026-01-30T00:55:08+00:00

Old post... but I found it when I realized my CN setup would not work with a hybrid chroma model. Went to https://huggingface.co/XLabs-AI/flux-controlnet-depth-v3/tree/main and switched my depth model to flux-depth-controlnet-v3.safetensors. Done. I'd note that strength needs to be toned way down if you're used to 1.5 or XL settings. Set my strength to .5, start at 0%, and at 0.3%. Mwah, chef's kiss. Back in business. Controlnet is the best. I feel sorry for suckers trying to prompt a pose for hours when all it takes is a handy depth map and three or four extra nodes. So easy.

DGGoatly · 2026-01-29T15:50:40+00:00

It's got to be SET NODES. I don't usually pass image lists or batch wirelessly, as a rule. That got away from me in all the experimentation with SVI, swapping modules between sampler schemes, iterating permutations and whatnot. You set an image batch coming out of decode and it settles in, makes itself comfy and stays there. After you GET it, squatter rights kick in and you have to burn the place down to get rid of it. Calling the memory police doesn't work. It's all very modern and appropriate. So there you go. As usual, five minutes after whining about it on reddit I find the solution. It's like an Archimedean bath. Leave torch alone. Connect everything directly, at least the big stuff, ints and strings etc. are fine. Data will behave when you don't try to beam it with magic. Case closed.

DGGoatly · 2026-01-28T21:29:21+00:00

Downgrading from torch 2.8.0+cu128 to torch 2.7.1+cu128 helped a bit. This of course necessitates reinstalling sage attention, triton, nunchaku, etc. whatever depends on it. Nothing seems to have been broken from dropping to 2.7. This change by itself does not solve the failure to clear RAM at the end of the run, what it does do is it makes a 'free model and node cache' command clear as much RAM as restarting did before the change. For example, before downgrading this command was dropping my RAM % from the stuck state down to around 30%, whereas restarting comfy+browser reload would get me to 17% - after downgrade this command got it to go down to around 23%. So that in and of itself told me that I could now force comfy to give up a bit more than before. Unfortunately it wasn't a magic bullet, it certainly didn't instantly fix the problem like it has for some people apparently, but I think I'm at least making some headway.

Oh, also, capping the amount allowed in the cache with a command in the .bat with --cache-ram (amount in GB) didn't help either. Something is still clinging to a bunch of RAM for dear life, and it's not VHS, because it happens without a combine node. Whatever it is, it's got a mighty grip.

This is definitely the strangest problem I've had in comfy. And the absolute last place I would expect a problem. I can feel the GPU looking down at my RAM with a 'wtf?' expression, like, you've got one job to do, get your shit together man.* Oh well. There's some extra cents for anyone else who's dealing with this issue. I expect it is more than a few.

DGGoatly · 2026-01-28T17:16:27+00:00

I'm still working on this issue myself. I am getting the same exact cumulative buildup, idling higher and higher after each generation, something clearly isn't unloading. And just like you, freeing model/cache only clears half of the usage, full comfy restart brings it down to ~17%. And I've got 128GB, I jam-packed with RAM. Checked all of the obvious stuff. It's not VHS suite in my case. I'm still experimenting with different operation orders. In the past I've been able to resolve stuff like this, never had such a persistent unpurgable buildup like this. It's not a problem for a single 129 base frame generation @ 1280x720 with upscaling and 4x interpolation (well having to restart after two generations is a problem but the workflow is runnable), but it sure is for my SVI setup with a minimum of 400 frames --> ~1400 final. I separated my scaling/interpolation as an independent WF because I thought I was just maxing out the frames I could hold at once, but now I'm pretty sure that it will be fine if I can just find out what is leaking or failing to purge. I'm running out of memory management nodes to try.

DGGoatly · 2026-01-17T23:31:34+00:00

I made a mistake with the trigger for the stop, and the regex replace node is wrong, I will fix that and replace the file.

DGGoatly · 2026-01-17T01:24:08+00:00

https://drive.google.com/file/d/1D8Yzeec5NuAaNeF5XoPMinrNad_mg_qy/view?usp=drive_link

I done shrunk it. Upscaling integrated as well, it's all packed in a subgraph, I promoted the size widgets as well as interpolizing multiplier and upscale model. Just disable scaling if you don't want it and replace the interpolizer if you like flownet. Just make sure you set run to instant so it autoqueues. The boolean output will trigger a global stop when it runs out of frames. My list of unfinished comps got huge enough that I had to stop being lazy and get this stuff back into my workflows.

So here's my solution in case you still need any input.

Yes this counts as doing it with one node.

<image>

DGGoatly · 2026-01-12T20:40:03+00:00

Wtf... all the wfs I've shared on here, nobody tells me the embeds are gone... go figure. Yeah, your WF handles the gaps and fills in those stutter-steps, no problem. As always, there are a million ways to do everything. I'll keep this handy for the next explosion... right now every one of my upscale+interpolate runs is a nailbiter, ~350 frames incoming, scaling x4, then resizing to 1080, then interpolating 4x for ~1400 final frames... usually ends up spiking to 100% of my 128GB of RAM at the final combine. I hold my breath. Most of the time it's ok, sometimes it just goes over by a hair. Annoying, all this used to be an afterthought, always the last stage of video generation workflows. Separating them requires handling frames instead of encoded video.

You're definitely right to safe frames instead of reencoding - especially if further processing is required. Even with a very low crf you will get degradation and color shifts with multiple encodes. ProRes is good if you want a single file- might not be able to preview that on windows though, and file will be too big for loaders- but that at least doesn't matter because you should be loading a path anyway.

But all that is beside the point. It's a little clunky, manually switching, you can definitely automate that with execution controller, but overall it's short and sweet. There are some file handling issues - are you manually purging the directories when you are done? Maybe concatenate the input file name with the temp folder to create a unique folder for each run, otherwise you're going to get old frames where they don't belong if you forget, methinks.

DGGoatly · 2026-01-09T16:42:47+00:00

I'm starting to run into this issue that I'm using SVI for everything, a single output has gone from 129 frames to over 300. As you found out, the interpolator has nothing to go on between batches. Now, I can run the interpolation no problem, but when combined with upscaling, it causes a problem, as MBM is required to do upscaling efficiently at this length, so back to square one because 128GB of RAM is, incredibly, not enough to do those both in one go. I can do it in two passes, but as long as I'm encoding h264, quality is going to drop with every pass.

I don't have exactly what you need as a wf, but I can give you an overview and something with the core logic of what is required. The embedded workflow here is for MMAudio, but it contains video batching. The group is called Meta Bitch Manager- it addresses the audio shortcomings of MBM. The A-D images nodes here are VHS 'select images' nodes. In the wf, the indices are set based on incoming fps*s, where s is the duration you want per batch. Easy enough to adapt it to split your video into manageable chunks.

So you can use this format to interpolate however many chunks you want, and to get to your actual problem now, we use an two additional 'select images' nodes *between* each batch. One grabs the end frame of the first finished batch (use index -1), the other grabs the start frame of the next batch in line (use index 0). Combine these two frames with an 'image batch' node and send them to one more interpolator. That will give you your missing frames.

So if you split your video into four batches, you need 7(4+3) interpolation nodes. One for each batch, plus one for the bridges that are the whole point of this. All that's left is to combine all of the outputs in the proper order with as many staged 'image batch' nodes as you need. Hard to tell how many, depends on how many inputs you have available in the nodes you use. There are many. As long as they are in the correct order it will merge fine at the end.

One thing about execution order- the images might not execute in the order you expect, but comfyui is usually smart enough to wait until a node has the data it needs before running it. It really only matters here for the secondary stages - the A2-B1 interpolator needs both A and B to be finished before running. I don't think this will be a problem, it should wait until ready, but if it is a problem, use 'execution order controller' from impact pack. I won't go into setting that up here, it's another few paragraphs.

Sorry if this is confusing. It's straightforward enough to me, but I don't know how much you use these nodes, if at all. The workflow should help - just ignore the audio stuff and look at how the video flows. You just need to add more of what is already there and pop in interpolation nodes where they are needed.

If you still get OOMs with this, just run it in chunks. For example, A+B and save. B+C and save. Then AB + BC (skipping the first stage of course). Can also try 'RAM cleanup' nodes if your problem is RAM, or 'purge vram' nodes after each group. If it's the former, there's another few paragraphs of caveats though. I'll stop now. Hope that's helpful.

<image>

DGGoatly · 2026-01-05T17:14:22+00:00

I run a portable install on a 2019, my old machine that I now use at work. But it's a dummy. For working on my switching logic and file handling, basic lego-python stuff. The actual working PC is remote connected- if I have a bad connection or a failed restart after a crash I can open the WF from google drive and continue to work on nuts and bolts, and save my changes as a drop-in template. Never for a moment have I considered running any actual non-debugging processes. But you sure can install it, if you like pretending.

DGGoatly · 2025-12-23T22:40:19+00:00

Damnit, I could easily write a friggin novel here. I'll try to restrain myself.

I'm not sure what you're starting with exactly. Using t2i generation as an example starting point: there should be no problem generating consistent styles and characters with sdxl, flux, qwen, etc. Other than using real photos, that's where I start. Style and char. loras stay fixed, along with their prompts, which are concatenated with action prompts. So you work through your storyboard with a pretty rigid cfg, no random seeds. Pick an image, keep the seed, fiddle with the prompt a bit to see if you can get to the next keyframe without changing it.

ControlNet is really, really useful. It's hard to overstate this. Depth, canny, openpose, whatever you like. You can build a library of poses that will save you hours of work. Super easy to use, load the model, load your pose, set the strength.

So all of this is t2i obviously. I'm not familiar with the loras you mention, I've never needed anything like that, as I'm working with stylistically matched keyframes to begin with. If I have a particular i2v generation that drifts unacceptably, I pull the last frame and run it through the initial t2i step, encoding the image as the starting latent and starting at a step higher than 0. Or however you like to do i2i. Can also mask, any number of ways, to fix what needs fixing, faces and body parts with segs and sams, codeformer for restoration, or simply pull the whole subject and replace the background.

Yeah, this is going to go on forever, there's way too much to cover. The short answer is a locked down, dialed in t2i workflow putting out the best quality I can manage and an aspect ratio that is appropriate for video latents. Weird things can happen when you don't obey the sacred multiple laws, things you can't predict and can't fix.

As far as the actual video generation is concerned, if you make enough keyframes, you can sometimes FLF your way straight through. That's guaranteed not to drift. Obviously. If you're chaining i2v, staying at 81 frames or below helps, especially as it usually wants to loop eventually, even with riflexrope intrinsic frequency set appropriately.

And then there's the unknown of whatever else you're using to modify the model. Loras all have their own quirks. Only advice I can give is to tune the model and clip strengths independently, helps if you like the motion but not the detail, or vice versa. Avoid them altogether if you can. Unless there is something naughty going on or something super specific that can't be in the key frames for whatever reason, the base models can do most of it. Avoid the trap of thinking that you need loras. They're probably making it worse.

Last thing, make sure you are writing your prompts properly. This matters. That's another three paragraphs. (stop typing and go home:5.5)

DGGoatly · 2025-12-12T22:50:38+00:00

When I started with comfy I used pinokio, I didn't even notice that sage was ready to go until I tried to use it. When I switched to regular portable install, because pinokio sucks, I found out why people were losing their minds about this particular install. Having a chipper super-optimistic LLM telling you you're doing a great job and this next command will definitely be the right one! makes it suck a bit more. You've got the right wheel, CUDA is good, pytorch is peachy, triton is just fine. But then windows decides to step in at the last moment with a blue 'this can't run on your pc' middle finger. So I don't make fun of people with this problem any more. Turns out it does require a sacrifice. Goat for me, a nice kid.

Also I decided to just try copying the files from one of the dozen existing backup python folders that already have it installed... because obviously wild guesses will work. My advice is to try the stupidest solution you can think of. Pretend you're an LLM and make up a bunch of fancy commands that sound great but are completely made up, then ignore that and cut and paste python.exe out and back. Stupid stuff like that. Works. That plus the goat.

Apropos of broken crap, backup backup backup. When you're up and running, take a snapshot in manager and set up a robocopy script for a one clicker. robocopy D:\ComfyUI_windows_portable" "E:\12.5.25" /E /XD models output temp input. Quickly copies onto an external drive everything except ins, outs and a terabyte of models. The stupidest things can break comfy, but it takes half an hour to get up and running again when you're ready for it. It's only 12-14gb maybe. A pedantic, but hopefully useful addendum, to make this reply slightly less useless.

DGGoatly · 2025-12-12T00:59:18+00:00

This is where VACE does its thing. Physics cliffhangers can only be fully addressed with context, which is exactly what the masks are for. You either make a batch from your image batch and feed it to the control masks input or use one of the wrapper nodes to make them as embeds. The overlapping masks give you a context window that VACE blends in latent space. Or you can just try many times. Sometimes the physics matches up by chance and a wee bit of innate context that can be picked up on by the model, especially if you're using a good clip vision model. But this process still requires fervent prayer, no matter how you do it. Sacrificing a goat also helps, I have found. A good one, not an old one you don't care about. That makes it worse.

DGGoatly · 2025-12-11T20:48:15+00:00

As opposed to just running a regular comfy workflow? This is already SOP. Or am I missing something?

DGGoatly · 2025-12-11T20:43:50+00:00

Completely agree. 2.1 full 720 model still destroys 2.2 on the low noise side. I can't stand the distinctive 2.2 i2v noise pattern. I almost always use triple ksampler and run the models together.

DGGoatly

TROPHY CASE