MetaFuze ALE -> MC -> Redcine?

[James Rayburn]

Quick question as to how the new Metafuze will affect our current RED worflow. Currently we (Mac):

RedRushes - for DNxHD QT creation
RedCine XML-> TestXSLT -> MediaComposer ALE
Edit, then...
FilmScribe XML -> TestXSLT -> RedCine Generate DPX Files (for Discreet/Autodesk Smoke)

I know how important it is in our current workflow that the ALE is created via the Redcine/TestXSLT method, otherwise when it comes time to go back to RedCine for DPX creation, Redcine will reject the XML.

With that in mind, will a MetaFuze created ALE give me problems in this workflow? If so, what would be the solution? One of the benefits of our current workflow is that we do not need to purchase any additional software.

I'm sure I'll find the answer to a few of these questions tomorrow when I give VMware/MetaFuze a try. Just thought I'd get a head start.

-James

 

[Igor Ridanovic]

The new workflow is simpler. What you should also do is benchmark and compare the two workflows to see which one is faster.

The MetaFuze to MC process does not require any third party apps. It's all self contained.

The final RedCine to DPX output would not change in your case. The larger Avid workflow which includes Avid DS finishing via AFE does not involve DPX files because DS can read R3D. However, Smoke can not yet.

 

[MichaelP]

You do not need an ALE when using MetaFuze. Metadata is part of the MXF wrapper.

Michael

 

[James Rayburn]

I have tested this out now. I have yet to successfully go from FS to Redcine when using MetaFuze to generate my MXF media.

I do not use an ALE to import, I simply used the Media Tool to import the MXF files generated by MetaFuze. That part works great. But going then from FS to RC I have problems. I have tried using both RC 3.1.2 and 3.1.8 as well as both the old and new XSL files. (FS_Scan_REDCINE.xsl and FS_RedCine_318.xsl)

Depending on which combination of XSL/RC I use (and I've tried them all), I either get a RC crash, or a "Failed to Construct" message.

I'd be curious if anyone else has successfully used this workflow to generate DPX files.

(Is there an update to FS I should be using? Currently on FS 24.1.2 and MC 3.1.2)

 

[Igor Ridanovic]

Depending on which combination of XSL/RC I use (and I've tried them all), I either get a RC crash, or a "Failed to Construct" message.

I'd be curious if anyone else has successfully used this workflow to generate DPX files.

(Is there an update to FS I should be using? Currently on FS 24.1.2 and MC 3.1.2)

Try feeding smaller sequences to RedCine. It has an internal limit as to how many clips it can hold.

 

[James Rayburn]

unfortunately i am feeding it small sequences. for my test, i'm only loading 4 clips into the RC library and my sequence/XML is only 30 seconds.... :-\

 

[Igor Ridanovic]

Then the next thing I would do is to compare the XML that you translated to a 4 shot XML generated in RedCine and see how they differ.

It's possible that the translation rule in Xtrans (is that what you're using) is messing things up. It is also possible that your options in FilmScribe are not setup correctly.

 

[MichaelP]

We don't have all the metadata needed when ALE is not generated from REDCINE to start. A solution may be to use CineXML to re-index the R3D files from the Avid XML then back to REDCINE.

Michael