RedCine to ALE

[Agustin Goya]

A feature request for Avid (not for the xsl) would be able to set the import file location in the ALE. That way you don't need to put all files in the same folder or manually locate them before batch import. You could keep them in the same folder as the original R3D file for example.

I agree that would be a great new feature!

 

[MichaelP]

While I agree, remember that the XSLT file supports RedCine - so in RedCine you need to export the rendered QT DNxHD files somewhere - so most likely it will be to a single directory since RedCine cannot export elements of a single construct to different locations.

But the ALE does contain the UNC path of the file, so it is not out of the question that getting access to the files from different directories in the future.

There will be a different approach taken with Redline when it is ready.

Michael

 

[Agustin Goya]

That's Great Michael!
Once again...... Thanks!

 

[MichaelP]

Just one more thing. For the UNC Path to work inside Avid the files and folders need to be separated by ":" not "/".

The UNC path presererved is for RedCine not Avid since the XML Redcine pull list at the back end returns that information.

Michael

 

[Chris Parker]

is this going to be crimson for avid sort of thing? or is crimson also going to release roundtrip for avid?

 

[MichaelP]

I can't speak for Crimson, but Ian was given the Avid XML export format to "play around with."

The first step is preserving all metadata appropriately which we have done with the XML to ALE format. We can hand all of it back to RedCine in a lot of different ways which we are working out now - full "takes", handles, etc. Something to remember is that the Avid bin is the database so we can pull out what we need from the source media or the timeline as needed. This does not restrict other databases from existing, since there are lots of relative metadata used for different purposes. The key is keeping the common point between all of them untouched.

Michael

 

[Jörgen Persson]

The UNC path presererved is for RedCine not Avid since the XML Redcine pull list at the back end returns that information.

Michael

But wouldn't a different heading than "UNC Path" be a better solution. Like "Source" since that's the name of property in the Redcine XML.

That way you can transform to proper Avid UNC Path and still use the ctrl + click to find the folder which is only a feature for UNC Path.

A simple solution is to transform the RedCine XML from "/" to ":" in the XML2ALE for UNC Path.
Then use the "Source" heading when going back to RedCine or transform the UNC Path in the Filmscribe XML from ":" to "/"

That way you won't get an error message in Avid when you try to find the folder.

 

[MichaelP]

There is a separate UNC path that the Avid uses for files directly imported, it does not use the UNC path as defined. This UNC path was designed as a metadata field for DPX files when tracking them on the original server from the scan. The link used in the batch import dialog comes from somewhere else... I can't remember right now.

Michael

 

[Jason Diamond]

the batch import info is hidden in the tape name? i forget where that path is stored as well but i know its there somewhere

 

[MichaelP]

No, it is somewhere else. I need to dig around - a batch re-import happens even when the UNC column has no value in it -so it is somewhere else - perhaps not revealed at the bin level. I need to ask an engineer who works in that part of the code.

Michael

 

[Corrado Silveri]

Hi guys, as of today, what is the step by step workflow to conform in Redcine from an Avid offline? Is that possible? (Assuming that I have a quicktime SD export -TC burn-in- given out for an offline edit on avid).

What kind of Edl file I need to ask to the editor?

My last chance is manually typing ins and outs in Redcine...

Thanks a lot in advance.

 

[M Most]

Hi guys, as of today, what is the step by step workflow to conform in Redcine from an Avid offline? Is that possible? (Assuming that I have a quicktime SD export -TC burn-in- given out for an offline edit on avid).

What kind of Edl file I need to ask to the editor?

My last chance is manually typing ins and outs in Redcine...

You can't "conform" in Redcine. You can do file conversions from specific frames of R3d files, but you can't create dissolves, titles, or any of the other steps commonly required in a conform. Not to mention that Redcine does not accept EDL's, it only accepts specifically formatted XML files - which the upcoming version of FilmScribe will ultimately produce, but not right now. And even when it does, you'll need to do your actual conform with a conforming program, using the files generated by Redcine as the sources.

The best way currently to finish a piece shot on Red that was cut offline on an Avid is to take all of the original R3d files and the EDL to a facility that has a Scratch system, on which the conform is very straightforward, fast, and simple.

 

[MichaelP]

mmost is correct. Conform and preparing for conform are two different things. Conform is done in Scratch, FilmLight, Digital Vision, Chroma-Image, Quantel, DS, smoke, FCP, and others. RedCine is to some extent a file based "telecine" that prepares the assets for different offline and online solutions.

The upcoming release will contain the XML expected by RedCine to do a pull of the R3D assets and prepare then for the conform station - such as exporting DPX if that is the desired path and is the supported format on the system doing the finishing and mastering.

Part of the same export process from FilmScribe is the master XML which is the entire sequence which can be used by a conform station. Chroma-Image already has basic support of this. Companies like Digital Vision and FilmLight support AAF and they also have the Avid FilmScribe XML Schema to work with.

We are still working out with Red and Assimilate what is expected in RedCine for pull lists -


Michael

 

[Corrado Silveri]

Sorry for the mistake. I know the difference, just I'm not so good with my written english...
Please read "prepare the clips for the conform process with Redcine".
In other words: there is out there any way to create a Redcine XML from an Avid timeline?

The final conform, will be performed with Fcp (no Scratch here, yet :biggrin

Thanks again.

 

[Corrado Silveri]

Don't mind. Just realized that you've already answer to the question...
:waaa:

 

[M Most]

In other words: there is out there any way to create a Redcine XML from an Avid timeline?

The final conform, will be performed with Fcp (no Scratch here, yet :biggrin

Well, if you have access to Final Cut, one way to do this would be to use Automatic Duck's conversion software to bring your Avid project over to Final Cut, generate an XML from Final Cut and use Crimson to pass the relevant information to Redcine. You would, of course, have to buy both Automatic Duck and Crimson, you would need to have used proper naming conventions during the original Avid clip imports (if you used Metacheater, this is already taken care of for you) and you would have to establish the path to the relevant R3d files prior to using Crimson, but this method should theoretically work.

 

[Corrado Silveri]

Well, if you have access to Final Cut, one way to do this would be to use Automatic Duck's conversion software to bring your Avid project over to Final Cut, generate an XML from Final Cut and use Crimson to pass the relevant information to Redcine. You would, of course, have to buy both Automatic Duck and Crimson, you would need to have used proper naming conventions during the original Avid clip imports (if you used Metacheater, this is already taken care of for you) and you would have to establish the path to the relevant R3d files prior to using Crimson, but this method should theoretically work.

Thanks mmost. Already own Crimson, going now to discover Automatic Duck...

 

[MichaelP]

In Avid, we preserve the file name in the UNC path as well as in other areas allowing the user to change the name of the clip to something more relevant to the user than an R3D file name. The XML out from FilmScribe reinstates the original file name back into the RedCine XML file for import.

Michael

 

[Corrado Silveri]

Thanks Michael.
So I wil ask the editor to output an XML from Filmscribe and start testing.

Btw I'm watching the Automatic Duck website too, just in case...

Stop boring all of you, and thanks again.

 

[MichaelP]

XML from Filmcribe wil be in about a week or two... And it will work best if the project started off with the RedCine to ALE. But we are working on generic to RedCine XML pull list.

Michael