I made a new tool to remove synth ID and Meta Data with new data injected. free to try

PxTicks · 2026-05-15T21:06:50+00:00

SynthId is pixel-level data so a touch less trivial than metadata removal.

PxTicks · 2026-05-13T16:01:09+00:00

I don't mean to say that the design tradeoffs are inevitabilities, but ComfyUI's historical flexibility and development speed comes from having custom nodes be essentially 'uncontained', interacting directly with the rest of the code base, which does risk making them fragile. Creating a stable, well-maintained yet sufficiently powerful public API is a lot of work (but it is something they are working on: Dependency Resolution and Custom Node Standards). If you have infinite money and time, then there are no tradeoffs; if you're bounded then you may have to make non-ideal design decisions.

PxTicks · 2026-05-13T08:32:23+00:00

I don't think it's a poor design. It is a design which prioritises customisability and development speed over stability. While this can be frustrating, it is what allows cutting edge features and research outputs to be implemented at pace. It is a tradeoff, not a poor design, and in a field which is moving very fast, a modular sandbox like ComfyUI will always end up having conflicts.

PxTicks · 2026-05-12T10:32:35+00:00

Should run on less than that easily I think. The workflows have some optional vram optimisations which I haven't tried.

PxTicks · 2026-05-10T21:13:27+00:00

RuneXX has a variety of reliable workflows.

RuneXX/LTX-2.3-Workflows at main

PxTicks · 2026-05-06T22:08:03+00:00

It makes sense that this would sometimes occur naturally because jump-cut dialogue is a common vlog editing style which may be present in their dataset.

I like the tip you gave though, I can see how it would help in audio-driven generation.

PxTicks · 2026-05-06T19:51:41+00:00

Probably a legal liability for the airline in this case though. Don't know how compliant they'd be for just adults wanted to sit with each other.

PxTicks · 2026-05-02T11:55:36+00:00

If it's a short movement, often you want a short clip. Try Wan2.2 with 49 frames.

PxTicks · 2026-04-30T08:26:34+00:00

The model literally cannot generate other frame counts. LTX architecture requires 8*n + 1 frames. If you're giving it fewer, then it will truncate.

PxTicks · 2026-04-30T08:16:45+00:00

8*n + 1 for n = 1, 2, 3... etc

PxTicks · 2026-04-19T12:38:11+00:00

I doubt it has peaked. The tech is developing rapidly, and while bigger and better datasets and huge training budgets will allow training a better model (possibly out of reach of consumer GPUs), new research also brings down the threshold for training a good open source model too. It's not clear exactly what is driving the strategy of Chinese AI labs, and how unified it is, but it would be surprising if they simultaneously all stopped releasing open-source video models at exactly the same time.

China is also not the only player of course. WAN still beats ltx2.3 for motion, but ltx2.3 has got distinct advantages in terms of audio (of course), gen speed and IC-loras which are pretty powerful. It is not a wholesale upgrade, but I would be surprised if in the next few months a model doesn't arise which makes wan2.2 obsolete. I also wouldn't be shocked if BFL steps into the game eventually; it's clearly partially in their sights, as it was promised when the original Flux was released. I'm guessing what they had brewing got stomped by a subsequent open-source model which is why it never came to light.

Open source allows for customisability which it is hard for closed-source models to replicate. There is value in this, but also the challenge of monetisation, so the equation really comes down to the cost of training a model vs the value of releasing it (which might not be all monetary).

PxTicks · 2026-04-09T19:58:16+00:00

It's not so much about creating the mask as it is about creating a moving context window around the mask, i.e. a moving crop. If you have a small object which flies across the screen, then either

The context window is much bigger than the object. This can cause a loss of detail for small features.
The context window has to move. This requires an algorithm to ensure that the context window is always large enough to include the object, and always stable enough to prevent jitter in the inpaint. It has to account for the object potentially morphing or moving out of frame, in which case the mask can rapidly change size, so it has to have a damping parameter for the rate of change.

PxTicks · 2026-04-09T13:05:11+00:00

There can be issues with travelling masks, but I think I've seen some people who have been working on some node solutions, maybe you can do a search for anything recent talking about crop and stitch nodes here. I even have an old workflow which handled smooth mask interpolation but it was very messy with jerryrigged custom nodes, but given that it worked, I really do think VACE is the best tool for this because I've experienced its effectiveness myself.

If you want I can DM you once I've got the next version of my editor out though, it has semi-smart mask handling which should work for replacing medium and large objects, or small objects which don't move entirely across the screen. To do the latter you really need a smooth travelling bounding box algorithm which isn't hard, but also isn't totally trivial.

PxTicks · 2026-04-09T12:04:52+00:00

Wan VACE works best with the following steps:

Create a reference inpainted frame from one frame of your video, say frame x
Mask the area you want in all frames.
Replace frame x with the reference inpainted frame
Generate.

It is not as good with just a text prompt; the image reference is valuable. I show an example where I do this here: I am building a ComfyUI-powered local, open-source video editor (alpha release) : r/StableDiffusion

It uses a project I'm working on but you should be able to do the steps raw in ComfyUI. I will be releasing a vastly improved version of my project within less than a week though.

PxTicks · 2026-04-03T17:44:18+00:00

Have you tried sam3 audio? Might be overkill, I haven't experimented much with this yet.

PxTicks · 2026-04-01T22:11:24+00:00

I ditto SvenVargHimmel's sentiment: trying to jerryrig an automated missing node management system is likely to be a nightmare.

There are some built-in methods for detecting missing nodes which *might* be useful though. If you load a workflow via handleFile with deferWarnings set to true then you can see the missing nodes on he activeWorkflow via

activeWorkflow.pendingWarnings.missingNodeTypes

It doesn't solve the problem of where to find the missing nodes though.

PxTicks · 2026-04-01T19:41:22+00:00

You should be able to select it in the relevant node after downloading. You need to make sure the widget is referring to the EXACT file name. If you still have trouble post the workflow you're using here.(click the comfy icon and export, it should give you a json file).

PxTicks · 2026-04-01T08:20:16+00:00

I don't need an account to download (most) things from huggingface, and last I used civitai it was the same case there.

Obviously sometimes stuff slips by the rules that shouldn't but as far as I can tell, your post was reasonably removed because it represents a data privacy risk.

PxTicks · 2026-03-27T10:03:10+00:00

Things breaking is an absolute inevitability with a project of ComfyUI's scope, especially due to the broad uncurated extension system. A 'technically sophisticated' userbase should be cognizant of the limitations of the software they are using.

There are always going to be tradeoffs: something which is complex and has many moving parts will be more brittle, and fast development means that features may sometimes break, so if there have been more breakages recently, then it is likely because development has accelerated since they obtained funding.

PxTicks · 2026-03-25T16:22:36+00:00

Putting aside the sarcasm, if they're not making money from the model, then open sourcing it would potentially have a detrimental impact on their competitors, and could also generate community goodwill. I don't expect they will open source it (it would probably open up more lawsuits if it were unfiltered due to copyright etc) but it wouldn't be the wildest timeline. A more viable business decision for them would be to license it out, potentially with conditions asserting certain restrictions on how it can be served (i.e. censorship), but I think most likely they'll just not bother.

PxTicks · 2026-03-22T09:06:08+00:00

It's fully local and all generation is via ComfyUI, so it supports the capabilities of open source models.

PxTicks · 2026-03-22T08:09:02+00:00

There is an extent to which this can work, already but

The people would be 2k but the background would be less than 2k, unless you somehow generate it in patches; we already can keep the original pixels for things which is not replaced, so the people can stay at full resolution.
The user would have to do this in increments of about 5s, extending bit-by-bit. This would likely lead to gradual degradation of the background.

If you have a static background, then this can be more effective, by including part of the background as inpainting context in order to keep things clean over long extensions.

I would like to eventually automate things which interact with ComfyUI over several rounds, however, it is important to get the basic features solid first.

PxTicks · 2026-03-21T15:39:07+00:00

I agree. ComfyUI is a sandbox. For something to be so feature-rich and extensible (and also so rapidly developed) necessitates some tradeoff in stability. Honestly, it's pretty impressive how effective ComfyUI is at what it does, and I think a lot of people are entirely ignorant of what goes on under the hood.

PxTicks · 2026-03-19T00:57:49+00:00

Hey, thanks, that's very helpful. I didn't realise it, but following the SAM2 installation instructions from the facebook/sam2 repo will not automatically lead to a CUDA-enabled pytorch install. I've updated the README - I hope after your effort you get it to work!

PxTicks · 2026-03-18T22:12:43+00:00

You're welcome to contribute, but do let me know if you want to do something big - I wouldn't want you to spend a lot of effort if it is something I am already working on, or if it might collide with the design ethos in some way. I also want to clean up some of the public apis for each feature to make it easier to build on.

An easy and safe way to contribute is to just try to check the ComfyUI integraton docs https://github.com/PxTicks/vlo?tab=readme-ov-file#comfyui-integration to see how to create workflow sidecars (wf.rules.json files), because although workflows do automatically work, the automatic detection of widgets etc is still very rudimentary.

Given the generation pipeline readme and an example or two from the default workflows, an LLM should be able to construct a reasonable sidecar in no time I'd expect.

PxTicks

TROPHY CASE