Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

RedRocket Avid MXF outputs

ThomtheEditor

ThomtheEditor

Banned
Joined
Apr 1, 2008
Messages
262
Reaction score
0
Points
0
Location
Los Angeles, CA
So yeah client promises subclient today that we can do red to Avid dnxhd wrapped mxf transfers today and we've never done this before.

Updated drivers, firmware, etc, pull up a clip to test using dnxhd 1080p 175, 10bit and crash...everytime.

-What could be causing this; render gets to 99% then fails.
-Also, they requested Rec709 for the color space, how important is changing that for base-light? We're used to doing everything in redspace for either proresHQ or dpx transfers.

Need solution ASAP, thanks in advance.
~Thom
 
  • Thread starter
  • Banned
  • #2
*UPDATE*

so doing some digging found that there can be no space in the output file-path for avid renders; seems to be running fine; but rather slow compared to other compressed formats like prores or anything qt based. Is that right?
 
Check to see that you have no spaces in the file path.
 
ThomtheEditor said:
*UPDATE*

so doing some digging found that there can be no space in the output file-path for avid renders; seems to be running fine; but rather slow compared to other compressed formats like prores or anything qt based. Is that right?
Click to expand...

It should be running as fast or faster than prores. Which dnx codec are you going to and what source resolutions?
 
  • Thread starter
  • Banned
  • #5
4k 2:1 source processing to 1080, did test with fit width; actual might be fit height; dnxhd 175 p23.98 10bit.

Also, should be grading in rec709 or redspace; client requested 709; but does it matter if it's graded in the improved space of redspace and rendered to mxf? Sorry, i'm not familiar with avid codecs.
 
My tests have shown DNxHD to be 30% faster than ProRes for the same files on the same system configuration. HD is REC709, so targeting that would be the way to go.

Michael
 
i have a client that can't get them into his avid; i'm a final cut guy so i don't what the different file types are; but he's getting an error that says can not import mxf file; HELP!
 
ThomtheEditor said:
i have a client that can't get them into his avid; i'm a final cut guy so i don't what the different file types are; but he's getting an error that says can not import mxf file; HELP!
Click to expand...

You'll want to import via AAF or ALE.
(i'm not the right person to answer to hopefully michael or someone else will give better instructions)
 
he finally got it by dragging in the mxf's one at a time; can't help but think theres an easier way than that!
 
You can drag all the AAF's at once. Select all and drag and drop into bin. We are working on a version of the SDK that will create a single AAF (composition) for all the sources so it is one file only. You can also instead, import the ALE and do a relink to the media if that is easier. The ALE also carries more metadata.

Michael
 
ThomtheEditor I'm having problems with the AAF/MXF workflow something you may want to be aware of if you are sending material out and have no way of viewing the MXF.

I'd be curious if you are experiencing the same problem with levels exporting MXF's out of RocketCine-X for import into the Avid not matching the Rocket Card output?

From my testing I would not want to send these files to one of my clients.

MichaelP, Deanan just looking for a solution hoping someone would have time to confirm what I am observing or tell me what I'm doing wrong.

A Young
 
I haven't looked at the signal based output yet from the card. What is the gamma set for through the hardware to the monitor? Calibrated REC709?

Michael
 
Color Space and Gamma/Tone Space in RocketCine-X are both set to REC709.

I am comparing the HD-SDI out of the Rocket Card to the Avid Symphony Nitrus HD-SDI out once the file is imported.
 
MichaelP said:
You can drag all the AAF's at once. Select all and drag and drop into bin. We are working on a version of the SDK that will create a single AAF (composition) for all the sources so it is one file only. You can also instead, import the ALE and do a relink to the media if that is easier. The ALE also carries more metadata.

Michael
Click to expand...

When i did my output i checked the box for providing a separate folder for each clip; should all the mxf's and aaf's go into 1 master folder per reel?
Where should that folder be in relation to the ale that gets created?
Is both the audio & video stored in the mxf in avid land?

When he tried to import the ALE he said the video came thru with all the shoot information attached; but no audio.

Any other suggestions for avid based output?

Thanks,
~T
 
I don't check that box. Each batch of renders will go into a target folder you have designated. In that folder ROCKETCINE-X will make a folder with the AAF's and another with the MXF's. When prompted for the ALE name. I put in the targer folder. That way one folder has all the assets for each batch process.

From there, move/copy the MXF to the Avid MediaFiles folder.

Michael
 
MichaelP said:
When prompted for the ALE name. I put in the targer folder.

Michael
Click to expand...

Michael.

Is the ALE the file with the .RD extension? I have been following this and looking for a file with a .ALE extension.

Thanks,

Mike Costelloe
 
As soon as you click for the transcode function to begin, you are prompted to name the ALE. Where are you putting that file?

Michae
 
You must log in or register to reply here.
Back
Top