Red Frame Rate Query

[David Cawte]

Hi,

This problem is related to r3d files that do not match the native frame rate of a project. For example, we have a 1080p23.98 Avid project. All of our red has been shot at 23.98 and we have generated edit proxies. When we come to conform this session in either a Baselight or Nucoda system, we create a 23.98 session and everything conforms as it should.

However, we are then given some additional red material that has been shot at 25fps. Our goal here is to process this into the Avid for edit in the offline and then conform this back to raw into a Nucoda or Baselight. Both of these systems will handle the non-native frame rate media but won't conform without the need for time consuming eyematching.

If we were working with a quicktime source, we would use cinema tools to re-clock a 25fps file to 23.98 before we ingest it into the Avid. We keep the 23.98 quicktime as hi-res and conform to it later.

Ideally, what we are looking for is a way to change the frame rate of an r3d file. We don't want to standards convert, we just want to slow it down 4% to 23.98 and make a new master file.

Is this possible? Does anyone have a workaround that allows you to easily conform to the raw r3d file with a frame rate that doesn't match that of the session?

Thanks for your time.

 

[MichaelP]

Well you still have a conform issue to keep track of, even after doing a frame for frame slow down of the media. Since editing will still be 23.976, timecode is going to roll over at :23 - :00. To properly track the original 25fps material will need to be at 25 with rollover of :24 - :00. Media Composer can track all timecode types within that project, so you will need to enter the original 25TC into that file. Redcine X does not allow for a frame for frame, but Avid MetaFuze does - but is windows only.

To do this in MC, I would suggest transcoding at 25fps, export QT reference - import into the 23.976 (not AMA) and enter "IgnoreQtRate true" in the console. Now it will be frame fro frame and 4.1% longer in duration. For each clip - enter the original TC value into the 25TC column and that will track at 25fps while START will track at the converted 23.976. At some point, Baselight or whatever will need to conform to a single frame rate.


Michael

 

[David Cawte]

Hi Michael,

Thanks for your reply. I understand what you are saying.

However, all of this fiddling could be avoided if we could just change the frame rate of the r3d raw file. One Pass, new master file, simple conform.

Is there any way that this is possible? Could I make a feature request?

 

[MichaelP]

That would be a feature request for RED to basically update the existing R3D file, or create a new R3D file as the new master. Audio if existing on the R3D would need to be sample rate converted (to be frame for frame change) or removed for this process.

Michael

 

[David Cawte]

Hi Michael,

Can I make a feature request through this forum? If not I can get hold of our contact at this end.

Thanks, Dave

 

[MichaelP]

The RED folks are pretty good about reading through all the forums, but it is not a guarantee they will see all of them. I suggest contacting them directly or via their support email address.

Michael