Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

REDRushes durations

Court

New member
Joined
Dec 12, 2008
Messages
3
Reaction score
0
Points
0
Hi guys,

I recently tried to convert some R3D files to Avid DNxHD Quicktimes.

For some reason the QT files had a maximum duration of 00:01:33:15fr

But when I looked at the R3D proxies the duration was longer. Which meant RED Rushes had cut off the end of alot of the R3D files.

Has anyone else came up against this before? Having RED Rushes only convert a maximum duration of 1min 33secs and 15fr worth of footage when it should be longer??

(Also, when the clips were imported into RED Rushes it gives the correct duration of the R3D files, which I then create an ALE from but once Batch Imported into the Avid, with the shorter-lengthed QTs Avid DNxHD, it seems as though the Source Timecode is incorrect and the EDL references the wrong shots when we attempted to conform through Monkey Extract to the Flame)
 
Did you have in an out marks or something created with RED Alert? If you try creating a QT wrapper first for one of the R3D files, does it contain the whole shot?

Michael
 
I found out that I had an earlier version of REDRushes.

I've managed to install it and it transcodes the whole R3D clip now instead of just the 1min 33secs previously. I do need to re-do the edit and conform to find out if this was the problem with the EDL and conform.

But I was surpised to know how many different updates REDRushes had done since I last used the software. I wish they had some sort of alert built into the program.

Could have saved me alot of problems in the 1st instance.
 
We send out relevant updates to the Avid workflow when you sign up at www.avid.com/red

Michael
 
Back
Top