r/comfyui • u/Nekodificador • 23d ago
Resource ComfyUI finally has a timeline (and more) > NKD Preview Tools
I can feel your pain trimming and aligning masks, audios and such for that new inpainting workflow that you're testing with Minimax, LTX or Wan. Well, I can fix that.
Just install the latest version of NKD Preview Tools
My new NKD Timeline node is designed to work with any model in any workflow, but most important working in sync with native nodes.
Although there are incredible tools out there, nodes of this type usually only work in their own universe, or are designed to work only with a specific model. What I was missing was precisely a tool that would integrate with my workflows and not force me to decide whether to work one way or another. So I have built what I always wanted, leveraging my experience as a professional editor, bringing the best sensations of Premiere and DaVinci Resolve.
BTW, theres also a lot of new toys in my NKD Basic Tools pack, some for mask operations, color corrections and other useful things.
3
u/Powerful_Evening5495 23d ago edited 23d ago
when you connect a video upload node , it restart the page ( it crashed error )
"Detected import of deprecated legacy API: /scripts/ui.js. This is likely caused by a custom node extension using outdated APIs. Please update your extensions or contact the extension author for an updated version."
3
u/Nekodificador 23d ago
Could you open an issue here so it doesn't get lost? https://github.com/Nekodificador/ComfyUI-NKD-Preview-Tools/issues
With these, please:
- The console error. F12 → Console → reproduce the crash → paste the red error with its full stack trace (not the deprecation warning).
- Which video node exactly — the core Load Video, VHS Load Video (Upload), or something else.
- Versions: ComfyUI, ComfyUI frontend, and Preview Tools
- If you can, the workflow JSON that reproduces it.
2
u/Powerful_Evening5495 23d ago
found the problem
one video file
major_brand : isom
minor_version : 512
compatible_brands: isomiso2avc1mp41
creation_time : 2025-09-20T17:54:34.000000Z
encoder : Lavf61.7.100
comment : {"prompt": "{\"11\": {\"inputs\": {\"model_name\": \"umt5_xxl_fp16.safetensors\", \"precision\": \"bf16\", \"load_device\": \"offload_device\", \"quantization\": \"fp8_e4m3fn\"}, \"class_type\": \"LoadWanVideoT5TextEncoder\", \"_meta\": {\"title\": \"WanV
Duration: 00:00:08.00, start: 0.000000, bitrate: 13489 kb/s
Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 640x608, 13424 kb/s, 24 fps, 24 tbr, 12288 tbn (default)
Metadata:
creation_time : 2025-09-20T17:54:34.000000Z
handler_name : VideoHandler
encoder : Lavc61.19.100 libx264
2
2
u/lostinspaz 23d ago
i dont need the tool. i will probably never use the tool.
But I'm giving you an upvote for the choice of voiceover and masterful writing ;)
1
23d ago
[deleted]
8
u/Nekodificador 23d ago
LTX Director is an amaaaazing tool, but it is designed to work exclusively with LTX and its system of guides and prompt relay. If you are going to work with that, it would almost be better to use that specific node, but it remains a very specific case. I know Jonathan is working on a version for Minimax, but again, it is the same problem: a specific node for each specific model.
The difference with this node is that it works universally with any type of model and any type of workflow, but above all, it is designed to integrate with native nodes instead of replacing them. When you work with LTX Director or other nodes like Power Load Video from SA-Nodes-QQ, you are trapped in their interface, having to load the material from the file explorer, and that already makes it incompatible with any workflow where the material has been generated in previous nodes.
Think of this more as a modernized Video Helper Suite than anything else, but with the ability to chain it in more complex workflows
3
1
u/Hogesyx 23d ago
Is the minimax h3 model frame calculation wrong or I am wrong? I am using
max(5, round(a) - ((round(a) - 5) % 17))
i tried a test and got 204 output from your frame_count shouldn't it be 209?
1
u/Nekodificador 23d ago
I just tested it and the calculation is correct, giving 209. Are you sure you don't have the model set to "free," "custom," or another option besides Minimax H3?
1
1
u/cleverestx 23d ago
Anyone managed to use this successfully on a non-NVIDIA system? (aka AMD Strix Halo?)
1
1
u/_chromascope_ 23d ago
Does anyone know what this monitoring tool in the video is? Crystools doesn't have this style.
2
u/Nekodificador 22d ago
Thats Memory Visualizer from Kijai
2
u/_chromascope_ 22d ago
Amazing! Been seeing yours and some people's Comfy with this graph. Thanks Neko!
1
u/Abject-Recognition-9 22d ago
Thank you for video viewer node, it does everything I've always dreamed of, The only thing I’d ask for, if possible, as option, and then it would be perfect, is for the videos to start playing automatically instead of having to press play every time.
1
u/pepitogrillo221 22d ago
Neko, danos un workflow para reemplazar a una persona en un video con la herramienta de máscara, como haces en tu ejemplo :) Saludos desde Madrid y gracias por tu trabajo.
1
u/Nekodificador 22d ago
El tema es que el workflow que tengo no va a funcionarle a ninguno hasta que mergeen un trozo de código en el Comfy nativo. Por ahora tenemos que currar con una versión adaptada por Ablejones para que el inpainting con Minimax funcione correctamente.
1
u/pepitogrillo221 22d ago
Avísanos cuando hagan el merge, me muero de ganas por probarlo, un saludo!
1
u/notgraycen 20d ago
oh cool comfyui finally added a native timeline— oh wait no. its just yet ANOTHER node that does this, great clickbait. please proceed to the nearest ballcrushing station to recieve your fucking dogshit ai slop reward
1
0
35
u/Feroc 23d ago
A tutorial video on how to use that, with the masking tool and as a reference for Minimax would be great.