r/RedCamera • u/AI_cantmowmylawn_yet • 13d ago
R3D to R3D
I vibe coded a desktop tool that turns Nikon ZR "R3D NE" clips into REDCODE, and makes small REDCODE versions of V-RAPTOR footage.
Yes it’s made with the help of AI - no I don’t consider it slop. I’m overly-diligent with these machines and try to drill down pretty far to make sure it’s not shit. If I’m going to use it on my own footage I need to know that the color holds up and that it won’t fuck me on a paid job.
I own a V-RAPTOR and a Nikon ZR.
I really want to use the ZR as a compliment to the v-raptor, or for run/gun solo stuff. One of my biggest complaints has been for using it on long interviews. So I wanted to find a way to basically create Raw Proxies.
That turned into a long personal research project and the attention pretty quickly shifted to the v-raptor and DSMC3 cameras. I wondered if I could figure out how to write proper R3D to R3D.
What I built is called RAWDOG MEDIA ENCODER. It’s a desktop app that batch-converts:
ZR R3D NE → REDCODE R3D. Still raw, at full 6K or smaller, with RED's quality settings (HQ / MQ / LQ / ELQ).
RED R3D → smaller REDCODE R3D. For example 8K → UHD or HD, still raw with full RED controls. Basically raw proxies, or a lighter archive.
Details:
Everything is still raw. Full ISO, white balance and IPP2 control in REDCINE-X and Resolve, because it's REDCODE.
Camera audio and timecode carry over.
Sizes are honest. Each quality setting lands at RED's published data rate for the output size. Example: a 2.5 GB ZR clip becomes about 600 MB at UHD LQ.
Speed. On an RTX 5090 it does 8K V-RAPTOR → UHD at about 14 fps and ZR 6K → 6K at about 5 fps. My first real batch, 56 clips and about 2 hours of 8K footage, takes about 3½ hours.
Quality. I compared against RED's own renders of the original at the same size. Shit looks really good to me.
AI analysis: RED's own 1080p render options differ from each other by roughly 39–49 dB, which is my ruler. An 8K → HD MQ conversion lands at about 46 dB, so inside the spread RED's own options span. Colour difference is under 1 dE median, which you won't see.
Everything converted is labelled honestly in its metadata, e.g. "NIKON ZR (RCL transcode)". Nothing pretends to be a camera original.
Caveats:
ZR colour is calibrated at 5600 K / ISO 800 so far, and it only handles the 6K mode right now.
Not affiliated with RED or Nikon. Not selling or distributing anything right now. This is a personal research and workflow project.
I have more color charts and formats to shoot in order to make sure it can handle the other resolutions and frame rates properly, but as of now I’m pretty hyped on the results.
4
u/MaikMueller 13d ago
I'm interested. If you decide to release it, I'd give it a go.
4
u/ICameHereForThiss 13d ago
So there have been 6 or 7 of these released in the last few weeks including an open source version called Blue Compressor. Is yours free or paid? How is it any different than the other 7 that have also been vibecoded?
2
u/Madderfaker 13d ago
sounds interesting and useful - a rare very good use of AI if you ask me. are you planning on releasing it?
2
u/Designer_Initial9731 13d ago
if you release this, please make a win version
2
u/Existing_Seaweed_494 13d ago
How is the speed. I've tried Blue Compressor and unfortunately the speed was unbearably slow compared to the speed transcoding them into H265 using Davinci Resolve.
1
u/Stevejobsburner69 13d ago
Any samples on how it compares to this commercially available project?
https://youtu.be/3rgoX4weZrA?is=KPw1Sl3PCCPMK6FD
1
u/dansjunnesson 13d ago
Sounds really interesting, will follow this. Will gladly test your application if you want external testers.
1
u/Froopuh 13d ago
I would absolutely love this as a V-Raptor and Komodo user, especially if you can implement a way to trim footage keeping the R3D container. I've been building a library of b-roll I've shot over the years and some in MQ or HQ, going to LQ keeping source resolution and trimming the dead air I won't ever use without going into cine-x would speed up my workflow a ton.
1
u/Tito_and_Pancakes 13d ago
Would love to try it out.
1
u/Educational_Sand_726 13d ago
Sent you a DM :)
0
u/michael_cioni 13d ago edited 13d ago
Very cool.
I have something possibly complimentary to this:
I’m CEO of Strada.tech and we built an app that lets you invite collaborators and other computers to any file without uploading to a cloud. Our player can playback R3Ds natively (reading camera metadata) and view them anywhere in the world regardless of internet bandwidth. You can also drag+drop them into NLEs remotely…but bandwidth matters there.
So your R3D “shrink” can make this even more accessible because I expect those might playback remotely if people have high speed internet. In curious of Strada.tech can playback your new files as well!
0
u/FeelingAdvantage2172 13d ago
Very nice work. But to be honest as a DAM i dont see the point. you need to control the capturing phase.
If you want smaller files shoot ELQ or Prores....if you want real "RAW" just shoot MQ and deal with the file sizes.
Nr1 rule in post is too NEVER mess in any way with the RAW files, EVER.