[Blase Theodore]

Erik,

I assumed that x264 was a different (open source) codec to h264. In that the end user must have the x264 codec installed on their machine. So while it may be a superior codec, its not a universal one.

Am i wrong in that regard?

Have you found that Sorenson gets you something accurate? Tested across Non-CL, CL and PC quicktime platforms?

I’m pretty sure ther problem with compressor h264 is a metadata problem where CoreVideo hardware accelleration results in a different image than the actual codec itself. For example I believe the same h264 will correctly map on a PC or older mac. If squeeze is getting better results, I wonder if its on the metadata level.

[Blase Theodore]

The ALE would be if you wanted to have a file that linked the audio and video. If its just the davinci video mxf you’re trying to bring in, it shouldn’t be a problem.

Load the mfx files into your Avid Mediafiles/MXF/(whatever)/
Delete the database files. Load Avid, create a project which matches your resolution and framerate. Refresh media databases, then use the media tool to search for the files on your drive.

[Blase Theodore]

Solution:
Bad drives, confirmed with 2 other brands of RAID cards.
The seagate 7200.11 1.5TB has bad firmware – version CC1H.

I did switch to an ATTO card anyway, specifically for their support department. ATTO has a list of good and bad drives which I’d advise anyone to read before making a purchase.

[Blase Theodore]

I think the RED clip info is saved as part of the grade in the newest versions. Is it possibly just recalling a grade that had no red settings applied to it?

[Blase Theodore]

For FCP, I tried that. But because it was using the R3D audio, it gave me errors.
This may work with other dailies like 5D or Alexa.

– Batch export – created the clips, but the clips were bad when I tried to re-import them to test them.
– Media manage copy – fails
– MM recompress – fails

Either way, there’s no way to batch link the clips, so its not really an option for me.

[Blase Theodore]

Here’s what I tried..

Avid –
Export mxf audio and video through redcine X.
Export audio mxf only through redcine x
Export video only mxf through Resolve

Add redcine vid and audio mxf’s to avidMediaFiles directory.
Media Tool shows unified clip.

Add resolve video and redcine audio mxf’s to avidMediaFiles directory.
Media Tool shows separate audio and video clips.

Imported redcine generated ALE. ALE will not relink to Resolve mxfs.

One strange note, if I import a Resolve generated QT or even the source QT, AVID screws up the timecode. CHecking those same QT’s in FCP, the timecode is correct.

– FCP
Imported resolve QT (video only) and source R3d proxy QT (vid and audio) – all timecodes correct.
Overlayed and hand linked resolve QT vid to pxy audio. Tried to export/media manage/mm recompress to create new clips.
All options failed.

In both AVID and FCP, all clips were generated with correct timecodes.

Conclusion: There is no way to create dailies with camera audio in resolve.

[Blase Theodore]

Anyone care to comment on this workflow?

Which I’m too busy to test…

Resolve grades out MXF from red.
Redcine x renders out MXF and .AAf with audio only checked.
Redcine x renders out .ALE

Avid imports .ALE to create offline clips.
Dump all media into avid_mediafiles folder
Avid marries audio and video?

Thoughts?

[Blase Theodore]

Yeah but it doesn’t do mxf, which is what I need to deliver.

[Blase Theodore]

I’m having a bit of trouble with it.

Setting the render prefix to %T_ gives me rendered files such as..

%T_00062243.mov

Its not injecting the reel name.

[Blase Theodore]

Maybe I haven’t fully wrapped my head around how to use this yet, but..

Importing an EDL into FCP will lose geometry, filters, keyframes, speed warps, multi-layers, etc.

If you can create an XML that links to your newly named media, but preserves all of the original “extras”, that would be pretty cool.