MichaelP:

I have been working with several of the engineers at RED to create better workflows as things move forward. Something to keep in mind is that no one is editing the native R3D files for actual projects as the performance is not quite up to par for editor expectations. So, in all cases, Avid or FCP, a proxy is created - be it DNxHD or ProRes. So that part of the process is a wash.

What becomes more interesting is the metadata management for the files regardless of how you choose to finish. Avid has far better metadata management. Currently users are having to add the scene/take information to the filename since you cannot lose that for a conform back the files. Since Avid tracks file names in a separate column; editors can actually change the name of the clip to something succinct and useful like... 24A/3.

 It has already been said that RED will be releasing the SDK of the R3D files to other manufacturers after NAB. So things will change again, and all for the better.

By the way, you can run metacheater on a PC.. what problems are you having?

 

Michael

Gosh, I can run Metacheater on PC? I could have SWORN the Red>Avid workflow afforded by Metacheater was only available on a Mac. Based on my readings of the Reduser posts. But maybe it's because of the fact that RedCine does not yet export any metadata, making a PC workflow using Metacheater moot? I have never used Metacheater, but would love to start if there's actually a way to do this entirely with RedCine and a PC. Have I missed something big here?

And further to your point re: FCP and Avid both requiring renders of Red proxies (whether DNxHD or ProRes), it's true. Everyone I know with the most tricked out FCP system is not cutting r3d natively with any success. I'm very excited to see how Avid's inherent strengths will make my Red workflow as easy and effective as any other NLE, if not more so.

EDIT: I see that the coders of Metacheaters have released an updated version of Metacheater that is PC compatible. But I think I still need access to a Mac to run RedAlert to generate the files with metadata/timecode, correct?

Metacheater can run on both mac and pc.

You need a mac based Avid to get RED files into the Avid because the quicktime plugin only works on the mac side.

You can export quicktimes out of Redcine and then import into Avid but that takes a lot of time.  Also, getting Redcine to work without bugs takes a lot of work.

I cut a feature back in December that was shot on the RED camera and I cut it in Avid Media Composer.  I used a Mac based Xpress Pro to import and then moved the files over to our PC based MC.  Had no problems.

If you have any questions ask away and I will try and answer them as best as I can.

Thanks Buck50.

That's what I thought: I need a Mac somewhere in the chain to make use of Metacheater in a Red workflow.

You can bet I'll have a couple questions for you, though. Cheers.

 Excellent. You have created half of an upcoming solution that demoed a few months ago. We are waiting for RED to finish beta 16. It basically is an Automater that uses some new feature in Redline to recreate new QT proxies and an ALE automatically with more metadata than via MetaCheater - both timecodes, color parameters, etc. I am hoping to see this get out in the next 2-3 weeks.

Michael

Thanks,

I'd like to hear more about that if possible. Nice to have a reply that proves I'm not insane :-)

As I see Jim Jannard announced that Avid is working on native r3d support:

Here

Is there any confirmation? If yes, when should we expect it?

Features are never announced before they are released.

Discussing when is considered speculation, which is a violation of the Community's TOS.