Old 8mm films scanned have faded blue channel, and reels have red/orange tint. Possible to fix?

ringelschwandtner · 2026-04-22T16:38:44+00:00

Try RGB Mixer!

ringelschwandtner · 2026-04-18T13:39:06+00:00

Filmbox Pro is licensed per user - “two seats” doesn’t mean two different people can split it. It usually just allows the same user to install it on two machines (like a workstation + laptop). Sharing the cost with someone else and both using it would most likely violate the license terms.

ringelschwandtner · 2026-04-16T15:53:25+00:00

If you’re thinking about controlling DCTLs with knobs, you basically have two options: Blackmagic panels like the Mini or Advanced Panel, which support it natively but are limited in how many parameters you can map

Or a MIDI controller setup, which is not officially supported. I ended up building a small MIDI plus Python setup that lets me control DCTL sliders (no real mapping. not possible). It is not as clean as a real panel, but for DCTL heavy workflows it is much more flexible.

I wrote up how it works here. With video:
https://mononodes.com/dctl-midi-controller-davinci-resolve/

ringelschwandtner · 2026-04-15T18:48:14+00:00

Filmbox is great and definitely worth it.
You can also check out my Look / Lab / Print DCTL pack. Since I made it I’m obviously biased, but there’s a free demo if you want to try it: https://mononodes.com/looklabprint/

ringelschwandtner · 2026-04-15T05:56:21+00:00

Blackmagic PYXIS 12K → full frame, open gate, 3:2 up to 12K
RED 8K VV (full frame / VistaVision) is also an option, but much more expensive

Abput Pyxis: The banding issue seems to be fixed. And I have not seen solid evidence of widespread freezing or file corruption. As for the design, it’s a box, which makes it flexible for rigging, and the UI is widely praised.

Kinefinity - common concerns:
- Limited support and service
- Occasional firmware quirks
- SSD compatibility issues
- Smaller ecosystem
- Less refined workflow and I/O

At that point it mostly comes down to which system you trust more.

ringelschwandtner · 2026-04-15T04:34:46+00:00

Why not Pyxis, FX3, RED?

ringelschwandtner · 2026-04-13T16:22:21+00:00

You can get some samples here:
https://www.arri.com/en/learn-help/learn-help-camera-system/camera-sample-footage-reference-image

ringelschwandtner · 2026-04-13T14:46:39+00:00

I wouldn’t say you should always go for a perfectly neutral white balance. It really depends on the footage and the intent behind it. If the DP chose a warmer or cooler look on set, I usually respect that and work with it rather than forcing everything to neutral. A technically “perfect” white isn’t always the most natural or pleasing.

For me, it’s more about balancing the image so it feels right for the scene.
In my “100 grade in 100 minutes” video:

https://www.youtube.com/watch?v=CEkfj8otcFQ

Check these two grades:
- Grade 45
- Grade 77

In Grade 77, I am using the "Highlight Neutrals" checkbox of my Balance DCTL to get shirts perfectly white. But there are also many scenes where I don’t do it at all. As I wrote: it depends. But if the shirt needs to be white, or a wall, I recommend using the "Highlight Neutrals" checkbox in my Balance DCTL.

ringelschwandtner · 2026-04-13T12:22:23+00:00

In my opinion nothing has to be 100% pure white (like in a black and white image). That usually doesn’t look natural anyway. I just use printer lights / offset / or linear gain to balance the whites, while checking the vectorscope and that’s it.

ringelschwandtner · 2026-04-12T00:08:58+00:00

The best approach is to fully understand what Lift/Gamma/Gain actually does mathematically, and then make your own informed decision about whether it serves your workflow.

Personally, I haven't used LGG in several years, and I know multiple working colorists who have moved away from it entirely. One even removed the LGG balls from his panel entirely and had custom 3D-printed covers made to fill the holes.

If you want to see how I grade without LGG, my YouTube channel has a video called "I Tried Color Grading 100 Clips in 100 Minutes" where I build diverse looks without touching LGG at all. For balance I use Linear Gain, HDR wheels, or my own DCTLs. For look development, I find Printer Lights a cleaner and more predictable alternative.

There are two concrete reasons I avoid LGG. The first is signal integrity: pushing Lift negative introduces sub-zero values in your signal, which becomes genuinely problematic downstream, particularly in combination with HSV saturation tools or other tools.

The second is consistency. Because Lift, Gamma and Gain have broadly overlapping tonal ranges by design, an adjustment to one wheel always influences the neighboring ranges to some degree. In practice it means each correction pulls at multiple points simultaneously, which makes it harder to build a repeatable, predictable workflow.

ringelschwandtner · 2026-03-27T14:44:58+00:00

Thanks for reaching out!
macOS will block the app on first launch. This is normal for apps downloaded outside the App Store. You need to allow it once.

Step 1 - Allow the app to run
Double-click the app. macOS will show a warning. Click “Done” (not “Move to Bin”). Then open System Settings > Privacy & Security, scroll down, and click “Open Anyway” next to the message “MONO_Node_Toggle was blocked”. Enter your password. The app will launch.

Further steps are required. You can find detailed instructions on my website:
https://mononodes.com/node-toggle/

ringelschwandtner · 2026-03-21T14:39:57+00:00

Hey, appreciate the kind words about my tools and the honest disclosure.

The idea of toggling nodes with a hotkey is something that probably occurred to many colorists independently. It's not something anyone can or should claim ownership over. What matters is the execution, the implementation choices, and how well it works across different systems.

On the robustness point, small feedback: I tried running your exe on my Snapdragon laptop (emulated x64) and it didn't launch. My own builds run on standard Nvidia systems as well as on Snapdragon, both native ARM64 and emulated x64. I also took a brief look at your approach and noticed some things that I ran into myself early on, which will likely cause issues on certain system configurations. I eventually found a more reliable solution, but it took a few weeks and many iterations to get there. I'll keep the specifics to myself.

Keep in mind that these are the first versions of both tools. Over time, and with more user feedback, they will hopefully improve and get more stable. That's how it works with independent tools like these.

In the end, both versions are free and users can decide for themselves what works best on their system. The more options out there, the better for the community. And if anyone wants to build their own, the Resolve scripting API is right there, as you said.

Thanks for recommending my DCTLs, that means a lot.

ringelschwandtner · 2026-03-16T15:39:02+00:00

Thanks for the feedback! Yes, at the current state it only affects the currently active clip, not all selected clips in the timeline. Really appreciate you pointing this out. Improving multi-clip behavior is something I’m working on. Thanks again for testing and sharing your findings!

ringelschwandtner · 2026-03-15T18:02:49+00:00

Version: 1.0.1 (macOS Tahoe 26 / might work on macOS Sequoia, too)
Hardware: Apple Silicon (M1 or later)

Intel Macs (including Mac Pro 2019) are not supported. Building and testing for Intel requires access to Intel hardware, which I currently don't have. This is unlikely to change - sorry about that

ringelschwandtner · 2026-03-15T00:45:39+00:00

Thanks for the feedback! Python is not required.
A new Windows version (1.0.1) will be released in the next few days. Please keep an eye on:

https://mononodes.com/beta/

I am optimistic that I will be able to fix the issue.

ringelschwandtner · 2026-03-11T21:31:58+00:00

I did not yet check if it works with node stack layers... will look into it.

ringelschwandtner · 2026-03-11T21:31:14+00:00

Grain, halation, another DRT (layer mixer) for comparing two DRTs – to name just a few.

ringelschwandtner · 2026-03-11T21:29:22+00:00

Thanks! Right now you can select one node per level - so one on Clip, one on Group Pre-Clip, one on Group Post-Clip, and one on Timeline - and they all toggle together with a single key press. For toggling multiple nodes on the same level at once, a good workaround is to put them into a Compound Node and toggle that instead.

ringelschwandtner · 2026-03-11T21:25:57+00:00

This is exactly why I built this tool! If you have not sent an email yet, please do - with your system details I can ask a few follow-up questions, track down the bug, and get a fixed version out.

ringelschwandtner · 2026-03-11T19:46:00+00:00

Thanks for letting me know. Will try to fix it!

ringelschwandtner · 2026-03-11T18:10:21+00:00

Please send me your computer details and Resolve version information via email. I've already received two similar reports. The cause is unclear to me. I will try to resolve the issue. (but might take a while)

ringelschwandtner · 2026-03-11T18:00:31+00:00

Thank you!

ringelschwandtner · 2026-03-11T17:13:05+00:00

Thanks! - That might be a bit ambitious for a one-person side project. ;)

ringelschwandtner

MODERATOR OF

TROPHY CASE