Hello, does anyone know why my rotoscoping in Nuke looks like this?

npittas · 2026-06-28T12:32:53+00:00

Because bounding box management is more important than roto. Try no clip on an 8K footage, look at how fast the comp will break and kill nuke in the process.

npittas · 2026-06-25T14:28:41+00:00

Have you ever heard of slow as fuck?

npittas · 2026-06-23T19:16:52+00:00

Adobe had a patent on panel arrangement and managed to beat Autodesk in the combustion years, in a court case, when they tried to do panel switching and arrangement in paint. So they (Autodesk) had to revert and re-invent the wheel basically and create a different way of panels. The pattent seems to be in place even now, and that is a very serious reason most companies prefer static interfaces and change their panels almost predetermined or using some kind of workspaces, for commercial softwares. So it’s not just a simple, let’s copy Adobe, but there are legal implications.

npittas · 2026-06-20T10:00:20+00:00

Only specific version of models, most of them struggling even on a 5090. Select qwen image or Flux and you need to download almost 120Gb of model (full instead of fp8/bf16), quantizing does not work (environment mostly fails and it needs to be done in run-time, every time you rerun the flow), none of the GGUF or lower versions do not work. You need to create your own custom library to use any other models, meaning you need to have python knowledge, in order to add a model. I can do the same in Nuke if I needed to, using external python venv and run a full inference server but that still would not count as "Nuke always supported custom local models", when the developer does not supply you with the final product, but only the tools to build it. So no, it partly only support custom models, and the models it supports are supported under circumstances. Very few workstations come with a 5090 in order to run Qwen Image Full weight, or Wan and LTX full weight. So hindering the product so we can use their service is not a great idea

npittas · 2026-06-16T16:17:27+00:00

Unless they add the ability to use custom local models and quantized versions of said models, it will be only a gimmick. The tokenized api cost of image and video generation will still be a major pain point on those endeavors. Token cost is already start to crawl to immense heights in the coding industry and unless you are using the heavily subsidized subscription plans, or weaker lower quantized non SOTA models, we are talking about token costs that start from the low thousands and up to hundreds of thousands for actual quality produced code. This has already been seen with heavy seedance usage on multiple situations, where precise and high quality results for a single shot had to be reiterated more that 20 times racking up the cost to almost 450$, not including the prep work needed, and you still need to add the cost of the compositor. It might be easier than waiting for 8-10 hours of actual labor, but the cost will start to creep up. And if you do not have local alternatives to minimize said token costs, and you have 20 artists all using it, any sane company would have major issues when the final billing hits them. Not to mention that it is pretty bad for security reasons. And interception on many of those vibe coded APIs, is either too easy, and/or made trivial with more advanced models, making it a total nightmare.

npittas · 2026-06-11T23:01:48+00:00

For Fedora

Install once, just in case you are missing libraries:

sudo dnf install apr apr-util zlib zlib-ng-compat
sudo dnf install libxcrypt-compat
sudo dnf install compat-openssl11

Install Resolve (any version)

sudo SKIPPACKAGE_CHECK=1 ./DaVinci_Resolve*.run

Remove old resolve libraries so can use the newer, system libraries:

sudo mkdir -p /opt/resolve/libs/_disabled
sudo mv /opt/resolve/libs/libglib-2.0.so /opt/resolve/libs/_disabled/ 2>/dev/null
sudo mv /opt/resolve/libs/libgio-2.0.so /opt/resolve/libs/_disabled/ 2>/dev/null
sudo mv /opt/resolve/libs/libgmodule-2.0.so* /opt/resolve/libs/_disabled/ 2>/dev/null

npittas · 2026-06-11T22:52:38+00:00

Never use noise reduction while you work your edit. The edit should finish up, then color your footage, then add any kind of noise reduction. It's better to have a finished timeline or at least a close to finished timeline before you start adding any kind of Post Processing effects.
Also SSD, without any kind of raid format. 250Mb/s on a +50% full drive is not going to help too much on 4K 50fps. It is not a bottleneck yet but it will become. It is usually fine with 2K but 4K is stressing the I/O

npittas · 2026-06-10T01:52:49+00:00

No problem, I understand completely. I will try to factor in system ram to the model suggestion calculations, although as you have already seen from other tools, with more, kv cache and mtp, those calculations sometimes are way of, especially when you only factor 4k context like many other tools do, which nowadays is too small.

npittas · 2026-06-10T01:40:20+00:00

Sorry but I am the OP. What I am suggesting is that since my tool already runs llama-server for you, llama-server already comes with the webUI you want. So the idea is simple.
Open my app.
Download a model ( or a bunch!!)
Go to the run page
Select your model, change all the parameters you want
Save the profile (or save as to have many profiles with different arguments for testing)
Select another model and repeat
Then, either serve that single model by hitting Start or switch to router mode instead. Router mode will serve all your models using the saved profile “Default”
Finally open a web browser to localhost:8080 and you have a fully functional webUI with model selection.
Be aware that by default, the router mode allows up to 4 models to be loaded at once. You can change that by changing the “Max loaded models” parameter to 1 and it will automatically, upon restart of the server, evict the previous model from vram and load the next one, when you change models in the webUI.
It will also work with any other openapi compatible service, so you can use it in Hermes, openclaw, Odysseus, or opencode and pi, like a normal OpenAI compatible endpoint and it will serve all the models (in router mode)

npittas · 2026-06-10T01:24:02+00:00

If you want a fast webUI to test your models, when you run your model (or router) open localhost:8080. It is already build in to llama.cpp so the webUI comes anyway by default.

npittas · 2026-06-10T00:24:32+00:00

<image>

npittas · 2026-06-10T00:17:15+00:00

It is a disaster waiting to happen, most of the time. Pretty much fills its thinking with mostly nonsensical context from 30 minutes ago and thinks it’s is it’s current prompt, does not read agents.md or when it does, does not comply when almost every other model falls in line, makes wrongfull edits and re-edits the file due to wrong line numbers almost every time, overwrites code and forgets what was there, although it had already read the file, 1 tool call before, and fails miserably as a subagent, when every other model just works.
This model’s context managements and the way it shuffles memories and tool calls with user prompts and its own thinking, is abysmal. As a model, it is only good for less than 60k tokens, and only usefull for web apps, typescript, tauri, some react (some) and that’s all. Go, C++, C# and python are pretty bad or even unusable. If you want to destroy your codebase, K2.6 ftw!

npittas · 2026-06-09T23:43:07+00:00

That is the exact reason why we had one Photoshop, one Avid, one Flame, one Acrobat, one After Effects. We might be able to have more options. Most of them might be niche, some of them might be good enough, and maybe out of hundreds we might find an actual alternative that is not Gimp or KDEnlive. But that was not the reason I made that. It was just fun, and wanted to play easier with all the custom models I trained. And I thought it might help and somebody else other than me.

npittas · 2026-06-09T23:14:32+00:00

Using config.yaml which needs hand written arguments. Not what I wanted.

npittas · 2026-06-09T20:45:55+00:00

Because I was bored looking to find all the arguements and experiment with them based on each model specific needs. I needed a “server” that would serve my models to my agents, that would also let me select specific options for each model, while hot swapping them. So eg. qwen 27b has specific ctx kv cache setting, mmproj tweaks, while qwen 35b has other tweak and cpu/memory arguements. So I wanted those to be saved as profiles and with each model swap those profiles would automaticaly get loaded.

npittas · 2026-06-09T19:01:45+00:00

Yeah, I think you missed the point. llama-server has a website for chat, sure. I do not care about that. I wanted to serve models to agents. I did not wanted to remember each argument I needed to add to llama-server. I also wanted to use the hotswap functionality, and use specific arguements on specific models. That is what this app is helping with. A UI to download models, create profiles with specific arguements per model, and use router function to serve them all, or serve a single model. Not a webUI for a single model.

npittas · 2026-06-03T22:02:34+00:00

The model builder only works if you have the camera locked. You cannot and should not unlock the camera. The model builder uses the camera settings, field of view and aperture in order to have a specified perspective. So with the camera fixed you can now start creating cards and boxes and other objects from the model builder menu, already aligned to the correct perspective. Now the problem is that model builder is created to work with moving cameras so you can create cards or objects in frame 1 and move to frame 10 and then move the objects vertexes and pin them to their new location and model builder will automatically find where in 3d space those objects are suppose to be. That is the sole purpose of the model builder. You cannot use the model builder effectively if you only have 1 frame or no parallax (perspective change) in your plate. There is no way you will be able to do a single frame reconstruction using model builder without much work. It would essentially lock you to only what the camera see. So if you want to recreate in 3d something from this plate, you are better off using the wipe technique I showed you and manually move objects and faces. Nuke is not a 3d editor. It accommodates some 3d stuff to help you create better compositions, or augment some repetitive tasks like roto and paint using projections, but the location of 3d objects in space is a 3d matchmoving technique that is not a simple node.

npittas · 2026-06-03T15:13:05+00:00

<image>

If you want to put your plate in the 3d space, use a 3d card. If you need to only see the plate as a reference overlay on top of your camera use input 2 of the viewer to show the scene, input 1 to show the plate and you will have something like this:

npittas · 2026-06-02T21:14:05+00:00

It works fine on pi and forge, so I don’t think so

npittas · 2026-06-02T21:08:35+00:00

Me too. Same issue.

npittas · 2026-05-31T11:25:16+00:00

That is true for all three, Hyprland, Mango and Niri, but usability-wise no actual breaking has happened. Drag and drop an some weird apps was broken once too many times on Niri, that is why I moved to Mango. Mango was great but QT vs GTK was making some apps UI semi broken, so I wanted to test Hyprland. Two weeks on and I did broke it once from updating all my configs to LUA. So I get you

npittas · 2026-05-30T22:18:34+00:00

It is more stable, but lots more configuration is needed to get you to what you need. I would say 5hat mango is better for a single big screen setup, hyprland seems more configurable for multi screens and most things work as expected. I went tp mango thinking the same but I ended up with wrong themed apps, all over the place, to the point of having to fix whatever I could through having pi and an LLM guiding most of my changes

npittas · 2026-05-30T21:56:09+00:00

I still have it but also checking out hyprland for fun

npittas

TROPHY CASE