DNxHD from RedCine into Avid MC6 - PC

[roryhinds]

I'm having a real problem getting Avid to import the DNxHD files I transcoded via RedCineXPro.
I'm on a PC using the latest RedCineXPro and Avid MC 6.

When I import the DNxHD files they just show up as "media offline"

I'm new to Avid but it seems something is wrong like Avid can't work with RCXPro files or something.

Anyone else have this issue?
Any tips?

[Nick Morrison]

Refresh your media database. In the "file" menu.

What you are experiencing could be because of a number of things, but THIS is the most common solution to this problem. Good luck.

[Nick Morrison]

Also, don't bother IMPORTING your DNXHD files. Takes way too long.

Just AMA the quicktimes in, and then TRANSCODE them to your whatever media rate you desire. It's about 5x faster. Trust me.

Importing is just SAFER, and should be used if you are changing frame rates (ie loading in 23.98 files into a 59.94 project).

[MichaelP]

If you're making DNxHD via REDCINE, it is native MXF wrapped DNx so it is not an import. Drop the .mxf files into the Avid MediaFiles/MXF/1 (numbered folder, could be 2, 3, 4, etc.). Open project and bin and drag and drop or import the AAF files created at the same time during the transcode. It automatically links.

Michae

[Tom.Wong]

if it doesn't automatically link when you drop the AAF into the bins, you can select them, right click go to relink media and manually select the drive the avid media files is on.

[Nick Morrison]

If you're making DNxHD via REDCINE, it is native MXF wrapped DNx so it is not an import. Drop the .mxf files into the Avid MediaFiles/MXF/1 (numbered folder, could be 2, 3, 4, etc.). Open project and bin and drag and drop or import the AAF files created at the same time during the transcode. It automatically links.

Michae

True. I thought he meant DNXHD codec QUICKTIMES. I guess he means MXF media.

[MichaelP]

Don't confuse the codec with the wrapper. Avid internal managed wrapper is MXF and the codec is DNxHD for picture (although it can manage ProRes internally as well when wrapped as MXF) REDCINE can export QuickTime wrapped DNxHD or MXF wrapped DNxHD. The one you drop directly into the Avid MediaFiles folder is MXF wrapped DNxHD (extension .mxf). You don't want to be AMA linking to the QuickTimes proxies of the R3D made by the camera as you lose all control of the color parameters.

From REDCINE, create native MXF wrapped DNxHD and do the steps I referenced in my previous posting. Also see the AVID+RED Webinar that shows the different ways you can work with R3D files at www.avid.com/red


Michael

[Bruce Allen]

This klnda brings up an interesting point... people don't seem to read manuals or guides much these days. Rory is a super-smart guy and really, Avid should make it easier for him to import stuff without having to go to help.

Part of the reason that Avid is having trouble is that people have no idea what their software can do... because it's not immediately obvious when using the software. The functionality is there... it just needs to be made more user-friendly to users who don't read the manual.

I think it would help a lot if someone from Avid sits down and just watches non-expert Avid users try to use the software. Then go through and fix all of the sticking points.

For, example, in this case... it wouldn't be much trouble for Avid to adjust the Import function so that:

IF file type is MXF:
1. copy MXF file into Avid MediaFiles > 1 on the specified import drive
2. add to current bin

ELSE do normal import

Bruce Allen
www.boacinema.com

[MichaelP]

For, example, in this case... it wouldn't be much trouble for Avid to adjust the Import function so that:

IF file type is MXF:
1. copy MXF file into Avid MediaFiles > 1 on the specified import drive
2. add to current bin

ELSE do normal import

I agee, and that has been a feature request for a long time, I tried for a couple years to get that very functionality into Media Composer. Along with right click clips in bin would automatically allow you to move/copy media files to a target destination. It's a matter of priority and where Product Managers and Designers want to take the product. We'll see what 6.5 has to offer.

Michael

[Tom.Wong]

on the reverse side though, the stringent folder structure and how you get the media into composer is one of the main reasons it's one of the most rock solid NLE's out there. the database system is what keeps composer constantly on top of where all your files are. AMA breaks down in that aspect for very long for projects, you stick with the mxf database file structure system and you're pretty much guaranteed to be able to keep all your files online even when jumping from system to system, or in a massive networked edit environment. there's never really a reconnect dance you have to do like in FCP. which is why a lot of big hollywood movies stick with avid. with 10's of terabytes of footage to sort through, a offline/online workflow, and huge conforms, the way it's structured is the way to go.

i don't really see too many ways around the existing system to keep that kind of functionality.