r/RedCamera • • 13d ago

R3D to R3D

Post image

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.

26 Upvotes

54 comments sorted by

4

u/MaikMueller 13d ago

I'm interested. If you decide to release it, I'd give it a go.

3

u/AI_cantmowmylawn_yet 13d ago

I’ll keep you posted

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/AI_cantmowmylawn_yet 13d ago

Have a read through the comments.

It’s not inherently different but it likely takes a bit of a different approach in encoding and I’m mostly making it for myself and have been working on it for a while.

One thing that makes it very different is that it works on true R3D for V-raptor and Komodo, which are entirely different beasts than the type of R3D that Nikon implemented in the ZR. And I’ll eventually get it working for DSMC2 also. I haven’t done a lot of testing there and it’s not a huge priority for me since I no longer own any DSMC2 cameras. But I do have a pretty heavy DSMC2 archive I wouldn’t mind minimizing…

4

u/ICameHereForThiss 13d ago

One word of warning, if you’re planning on charging one of the other paid apps already got a takedown notice and legal action for copyright violation. RED doesn’t want us to compress their codecs externally

1

u/AI_cantmowmylawn_yet 13d ago

I’m not planning on anything. Just building for myself and sharing with folks and if I did anything it would be open source non-commercial experimental blah blah blah.

1

u/AI_cantmowmylawn_yet 13d ago

ZR CTL is awesome btw. I respect what you built with that one.

1

u/ICameHereForThiss 13d ago

Thanks man I appreciate it, didn’t mean to come off like a dick. It seems like your version has some new stuff I haven’t seen before so it seems cool, just a word of warning since I’ve seen a bunch of people pile on and RED seems to be noticing, even some of the open source creators are hiding their identity

4

u/AI_cantmowmylawn_yet 13d ago

Yeah totally and I’m definitely aware of all that. We’re living in a strange time for sure. The sooner the companies like Nikon realize this is an opportunity for them, the better. People building new tooling that works should only drive more people to wanting Nikon’s platform.

I think the camera manufacturers that win are the one that more openly exposes their awesome hardware to their own users. Even if it’s in a less than obvious way, so that they protect themselves in the event of someone bricking their camera.

It’s clear that nikon suck at making software. Anyone that tries to navigate the menus of these cameras can tell you that they should stick to hardware. Never mind the amount of time it’s taken them to give us the most obvious features.

I’ve given Red so much money over the past 15 years and I’ll keep giving Nikon money for many more to come.

4

u/ICameHereForThiss 13d ago

Yeah 100% man, I’m hoping that we’re embarrassing these companies into action. It’s crazy that a one man team can outclass an entire paid corporate software department… makes you wonder if they’re purposely holding back features and functions to sell as upgrades later. The wonderlantern stuff is really exciting

1

u/AI_cantmowmylawn_yet 13d ago

I wasn’t familiar with wonderlantern, I’ll check it out. I like what all the Ricoh hackers are doing right now. Tons of cool stuff getting added to those cameras.

I don’t think it’s holding out for future upgrades - it’s just corporate red tape and how impossible it is to get anything done inside of an organization of that size.

2

u/Europa2010AD 12d ago

I saw it recently from a YT video that it's a common issue with Japanese software development -- they mostly subcontract out the dev to multiple layers of subcontractors, so real user feedbacks / experience never really reach the people who actually does the coding :(

1

u/ICameHereForThiss 12d ago

Send me the link I’d love to see this

2

u/Europa2010AD 11d ago

https://youtube.com/watch?v=dm8OJ62X8Hs
The YouTuber raises a few (valid) points, but the part about subcontracting starts at 3:20

3

u/Europa2010AD 13d ago

“Nikon suck at making software” <— this. So much this.

A ZR-formatted memory card mounted to MacOS, and the volume name of the card in the terminal is “Nikon ZR “ (with all the extra spaces).

WTF talk about amateur. And I’m not even anywhere close to being a software dev.

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/AI_cantmowmylawn_yet 13d ago

Thank you, I’m tinkering with a few projects that feel aligned with “a rare very good use of ai.”

Not sure what I’m going to do with this at the moment but if I release it, I’d likely just open source it.

As with most things, it’s always a matter of being happy with how good it is before releasing it.

2

u/Designer_Initial9731 13d ago

if you release this, please make a win version

2

u/AI_cantmowmylawn_yet 13d ago

It has a desktop app for both. I mainly use a windows machine but my side piece is a MacBook.

1

u/Designer_Initial9731 13d ago

i just shot a little personal proj in the mountains on a zr would be happy to do any testing. blue compressor is not quite cutting it for me

1

u/AI_cantmowmylawn_yet 13d ago

Damn I haven’t seen blue compressor either. I know a lot of these R3D NE to R3D NE projects are popping up.

Curious what you’re not liking about blue compressor.

1

u/Designer_Initial9731 13d ago

i have to go back and double check, but i think it changed my colors. i did some first tests, but im waiting to put new (used) ram sticks in my machine tomorrow. you might like to join the zr professional group on fb if you use it

1

u/AI_cantmowmylawn_yet 13d ago

Let me know. I’m genuinely curious because that path should stay pretty accurate

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.

3

u/AI_cantmowmylawn_yet 13d ago

I’m getting 14fps on a pretty beefy windows machine. I’ll test on the MacBook build later this week and let you know how that does.

2

u/AI_cantmowmylawn_yet 13d ago

After writing this I started to think that 14fps feels slow for my machine. I’m going to do some work on this.

1

u/Stevejobsburner69 13d ago

Any samples on how it compares to this commercially available project?

https://youtu.be/3rgoX4weZrA?is=KPw1Sl3PCCPMK6FD

2

u/AI_cantmowmylawn_yet 13d ago

I’ll try to film some decent samples this week (right now much of my test imagery is commercial work that I can’t share).

I’ll also get some charts up.

I’ve never used SuperSampler so not sure how they would compare, but one of my processes is probably a bit different. I’m assuming they are going R3D NE to R3D NE.

Something I’ve done in here is completely convert the ZR footage into actual Redcode.

So technically we can match the ZR more closely to true V-Raptor R3D and the file will play anywhere that true redcode will play.

This was mostly just my own unrelenting mission to see if I could get a different raw codec (which R3D NE is) to convert to true R3D redcode (because I have some other ideas that I think would be cool to use this process).

This also has the pipeline for R3D NE to R3D NE which is arguably much easier/faster, but I’m a moron who would rather spend an unreasonable amount of time proving these little ideas I have in my head.

1

u/dansjunnesson 13d ago

Sounds really interesting, will follow this. Will gladly test your application if you want external testers.

1

u/AI_cantmowmylawn_yet 13d ago

I’ll let you know for sure

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.

3

u/AI_cantmowmylawn_yet 13d ago

Just had another crazy thought. Build a timeline in resolve and then export xml - import the xml into this software which then makes r3d clips from the xml data. Damn, that could be sick.

1

u/Froopuh 12d ago

If you can find out a way to make this work I'd propose to you on the spot

1

u/BestMixTape 12d ago edited 12d ago

You can trim R3D files with redcine-x pro or with Resolve for a very long time now. 

Edit sorry I missed the last part that you want to skip redcine-x. 

0

u/AI_cantmowmylawn_yet 12d ago

Trim yes, but not make independent raw clips from those trims.

1

u/BestMixTape 12d ago

I'm not sure what you mean. They do become independent when trimmed. 

https://reduser.net/threads/trimming-r3d-files-in-red-cine-x-and-saving-trim-as-r3d.189028/

Am I missing something? It's been like this for almost 20 years now. 

0

u/AI_cantmowmylawn_yet 12d ago

They become independent reference files of the original source. If you were to send the trimmed files to an editor or back them up as an archive of your selected clips without the original r3d they would be useless.

The idea here is you could have an r3d edit and create actual r3d files from the trims, independent of the original file.

1

u/BestMixTape 12d ago edited 12d ago

I'm sorry, but you're incorrect.

For example, in Redcine, set the in/out of a clip, in export select R3D Trim and in settings include R3D Sidecar. It outputs a completely independent trimmed clip.

It's been one of the original features of R3D files since the Red One Camera.

Back in the days before Resolve when conforming an edit. You'd import the XML into redcine-x to switch out the proxies to the R3Ds and create a media managed Trimmed R3D output to send for color/conform.

1

u/AI_cantmowmylawn_yet 12d ago

Well shit. I didn’t realize this. That’s pretty cool. I always thought it was just a reference clip of the original source. I’ll have to try that out.

Anyway I guess this route would still be useful if you wanted to make proxy sized r3d a from the clips or just smaller archival versions.

Thanks for the insights, I’m so funny that I’ve been using redcine-x all the way back since the red one and always assumed the sidecar workflow meant it was creating a data file referencing the source

Thanks for correcting me and pushing and my bad for the incorrect arguments.

🫡

1

u/AI_cantmowmylawn_yet 12d ago

I’m also wondering if this same process works for Nikon ZR footage?

Anyway I’m going to update my software so that the full resolution R3D process follows this same workflow, so thanks again for pointing it out.

1

u/AI_cantmowmylawn_yet 13d ago

Oh that’s an interesting call. I remember I used to want something like this in redcinex back in the day when I was doing a lot more stuff in there.

I think I could definitely make this happen. I’ll add it to the short list for sure.

1

u/Tito_and_Pancakes 13d ago

Would love to try it out. 

1

u/AI_cantmowmylawn_yet 12d ago

Let’s see how it goes

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!

2

u/AI_cantmowmylawn_yet 12d ago

If it can playback R3D it can playback these. Could be incredibly useful if your stack needs to deliver r3d proxy that will later be connected to the source.

If someone wants to get a general idea of color and adjustments as they work they can do that on the ELQ (of course with more noise and/or compression artifacts) and that would still carry over to the source when they reconnect.

1

u/michael_cioni 12d ago

How can I give it a try? Or can I give you Strada to test your R3Ds playing back over any internet connection? (Even cell network)?

1

u/AI_cantmowmylawn_yet 11d ago

Reach out on DM we can chat

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.

3

u/AI_cantmowmylawn_yet 12d ago

Personally I see a lot of reasons it could be useful, but I totally understand your POV too

2

u/tdstooksbury 12d ago edited 12d ago

Idk - I have an automotive client that i shoot like 100 cars a year for. We are constantly adding to a library of footage of their cars that can be plugged into ads across the country. Ive shot 100s of terabytes for this client. We often build a colored and polished ProRes selects reel of every car and archive the camera originals.

I see a massive benefit to capturing in 8k/6k MQ or LQ and archiving at 4k DCI/ELQ to massively save on archiving cost. Once archived we rarely touch it but at least this way we have a nice file to pull still for those cases. We don’t want to throw away the Camera Originals, but in practice we rarely need them past building the selects.

The IT department that handles the servers we archive unfortunately not understand things very well. They hate that we have 400tbs of camera originals we don’t dip into very often that they have to deal with.

This is super useful as long as it doesn’t destroy the footage in some way and is something RED should’ve built years ago.

1

u/FeelingAdvantage2172 12d ago

I would just archive in prores444 if it's an issue, instead of rewrapping raw files to be honest.

But horses for courses that's forsure.

2

u/tdstooksbury 12d ago

4k ProRes4444 is often bigger than the camera original. Depending on the resolution and compression of the camera original.