In case you missed it ...

[Rainer Fritz]

thx will try to get it !

 

[Deanan]

I have re-Installed my Rocket Cine X. And the MXF output is working great!
I have had success with 2k16X9, 2K2:1, 4K 16x9 and 4K 2:1 (using audio fed to camera).

The only thing I am now missing is the 16x9 frameline cropping. When ever you set any cropping it seems to be disregarding the scale. Maybe there is a different order in which things are done then I am used to with Red Rushes?

One other question I had was whether or not I am indeed getting all of the meta deta I will need to push my project through the whole pipeline. This is how I am exporting and importing into Avid:
- Export MXF and AAF from RED Rocket™™
- Drag MXF and AAf file into my Avid Media Files folder
- Open Avid Media Composer, making my project on the same drive.
- Click on Tools from the top menu options.
- Select Media Tool
- Select my hard drive in which the MXF and AAF file are on. Hit O.K
- Media Tool window appears with 2 files for each clip. Drag all into my bin. And one file will appear within the bin per clip. (the other is hidden)


If anyone knows of a better workflow, I would love to hear your thoughts!

Thanks,

It works a little differently in rocketcine because it's based on a full resolution debayer so crop happens on the full res numbers and then the scale is the destination.

To get all the metadata, the ALE import method would be better. Michael can explain better than I can.

 

[Jesse Korosi]

It works a little differently in rocketcine because it's based on a full resolution debayer so crop happens on the full res numbers and then the scale is the destination.

To get all the metadata, the ALE import method would be better. Michael can explain better than I can.

Thanks for the response Deanan.
That makes sense about the ALE import. It is working like a charm!

As for the cropping settings. I am still a little unclear.
- Within my Format Tab; I am choosing my "Output Resolution" Example 1080P
- Within my Crop Tab, Choosing Custom, and adding in different numbers to test.
- And then the Source Resolution Section within the Crop tab I am setting to my original frame size.

When my file is outputted, regardless of file Format. It disregards the scaling of any type and just crops. Do you know where I went wrong?

Thanks,

 

[MichaelP]

There will be a step by step guide posted soon on avid.com/red for ROCKETCINE-X. In summary, importing AAF only gets you 16 character source, time of day START and END but does an automatic relink based on additional MOB ID in the file. One can always import AAF first, then select all clips and do an import/ALE with merge based on known events in the options (last radio button) and all additional metadata from ALE will be added. Or one can bypass the AAF and import the ALE directly but there is the additional relink step as per the MetaFuze workflow.

Michael

 

[Erik Greensmith]

Can we add 720x480 DV25 411 codec MXF to the export options? The editor on my current show wants it and I'm having to create prores and automatic duck to MXF.

 

[Jesse Korosi]

I second the option for DV25!

That seems like an odd workflow for your MXFs? Why aernt you directly outputting DNXHD files and just importing them in to Avid for your conversion?

 

[JD Marlow]

I'd like to also add my vote for DV25 and / or Meridien compressed codec at various resolutions. Can't tell you how many clients request SD AVID media for RED shows because they're cutting on older systems. It's a headache and a half to find the proper workaround to get Letterboxed SD media into Meridien 14:1 MXF from RED.

There's also the issue of the ALE from 23.98 RED media into an NTSC Avid project. We've always had to import DNX media into our Media Composer and then transcode within Avid to NTSC media to force the system to count in 24. Otherwise it will always count 30, as if there is pulldown (or missing pulldown). Perhaps Michael P can comment to this...

 

[MichaelP]

NTSC is a 30 rame format regardless of the edit rate. MC can track both the 30 and the 24 (TC24) when editing in SD (Same for PAL at 25fps). Physical media is 23.976, 24, and 25 - it is the metadata that needs to adjust for this. Only app that does this right now is MetaCheater for the metadata when dealing with Qt files.

Michael

 

[Deanan]

NTSC is a 30 rame format regardless of the edit rate. MC can track both the 30 and the 24 (TC24) when editing in SD (Same for PAL at 25fps). Physical media is 23.976, 24, and 25 - it is the metadata that needs to adjust for this. Only app that does this right now is MetaCheater for the metadata when dealing with Qt files.

Michael

To reiterate what Michael is saying, ALE output from rocketcine does not do the framerate adjustment and assume camera project rate matches the DNxHD framerate.

 

[Emery Wells]

Anyone else having trouble with camera audio from MXF exports? Doing some testing today and the video tracks look perfect but the camera audio is playing back distorted. Sounds like its being played back in slow motion. This is in Media Composer 3.5.

 

[MichaelP]

That is my next series of test, all my shooting is done double system.

Michael

 

[Jesse Korosi]

and then transcode within Avid to NTSC media to force the system to count in 24. Otherwise it will always count 30, as if there is pulldown (or missing pulldown)

If you have to cut in SD, is exporting your DNX QT files out as 23.98 and cutting in a DV25 23.98 project not an option?

 

[Emery Wells]

That is my next series of test, all my shooting is done double system.

Michael

Spoke to Deanan, he has a fix. Im sure it will pop up in the next beta.