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 :)

EDL from Avid to RedCine for Conform

G

gbalaji

Well-known member
Joined
Dec 29, 2006
Messages
655
Reaction score
0
Points
0
Location
Chennai, Tamil Nadu, India
Website
www.indieshd.com
Michael and Avid Team,

Is there tool available other than Crimson for doing conform from Avid Edl or Avid Sequence to RedCine for DPX export since we don't use neither Scratch or Nitris. We work with Lustre.

Crimson not yet supported Avid and I need to take Avid EDL to FCP and from there i need to export XML - Crimson - RedCine.

Thoughts and Suggestions from Avid are welcomed for Conforming.

By the by, when I start exporting to self contained QT using RedRushes (RedAlert 3.4.8 released 2 days before) with AvidDNXHD Codec, I am getting only noise and nothing else.

Red Rocks and hopes for Avid to Rock in the file based management as well.
 
We are still putting the DNxHD codecs through its final test stages. Once they are updated on avid.com, I will post a link here.

As far as conform, until the XML tools are finished, (and assuming you started in RedCine to create the ALE), some people are finding success in using Automatic Duck to FCP, XML from there into Crimson, then on to RedCine... Lots of steps I know, but for now that seems to be the way to do it.

Michael
 
Michael,

What's the next best way to conform if you don't have access to autoduck like myself?

Any chance the XML tools and the DNxHD codecs you mentioned will be finished by Mid-November? I'd much prefer to offline on Avid, but like I said no autoduck and no scratch either. Am I SOL without these updates? If these things are ready in time I think I'll be golden.

Thanks
 
The XML tools have taken longer than expected for a variety of reasons, but mainly to ensure we can get the proper pull list as needed - sequence composition can get quite complex and anticipating all possible workflows and providing flexibility is something we want to make sure works.

As I have mentioned in other threads, we cannot generate a generic pull list at this time to go back to RedCine unless the original ALE was generated by RedCine in the first place. This is due to specific metadata that is needed for the relink/conform back in RedCine. When starting in REDrushes or MetaCheater, those tags are not there.

We are looking to provide a solution for that with some of the third party interim database solutions since they can re-index the R3D files and make that association from the Avid XML. I can't make promises on their development or delivery times, other than to say it is being looked into and should have something to say on that front soon. Deanan has been great in providing some extra fields in the ALE at my request to make that process more streamlined to that there can be a conform path at the end when starting with REDrushes.


The overall step by step and XML tools are targeted for the next couple weeks on avid.com if all goes well. This will also include the updated DNxHD QT codecs.


Michael
 
MichaelP said:
We are still putting the DNxHD codecs through its final test stages. Once they are updated on avid.com, I will post a link here.

As far as conform, until the XML tools are finished, (and assuming you started in RedCine to create the ALE), some people are finding success in using Automatic Duck to FCP, XML from there into Crimson, then on to RedCine... Lots of steps I know, but for now that seems to be the way to do it.

Michael
Click to expand...


Hi Michael, how do you create the ALE from Redcine though do you still need to run that script you posted some time ago? So far I have used Metacheater and it worked for the last project and then converted EDL in FCP, XML to Crimson . Having seen ALE export is now in Redrushes I was planing to shift to that and miss out Metacheater as at least its one less stage, is this likely to give more complications though. I was also considering the Duck alternative are you saying that will only work if I use a redcine generated ALE and not from the other packages, if so why? What extra metadate do you get from an ALE from Redcine that you cannot in either Redrushes or Metacheater.
 
There is a unique "user" tag that we get from RedCine that is not part of the REDrushes or Metacheater:
<user>"9F0D434C-12CA-4B73-B981-3F95983E2E72"</user>

Each R3D has a unique user tag. There are other fields that are different that we are looking to see which ones are the minimum needed to make a conform work in RedCine when not started in RedCine.

Certainly taking an EDL from Avid with full file names back into FCP then XML to Crimson works but the goal is to eliminate the number of steps to get there. Pergaps this unique ID is part of the R3D file itself and in that case, REDrushes should be able to pull it out and give it to us. I have been building up an XML from a REDrushes start for a while now trying to find the missing tags to make it work.

REDrushes ALE is nice since it gives both timecodes recorded in the file and you don't have to choose one over the other before editorial begins.

A lot fo this has been a learn as you go - with multiple inputs and one output, the workflows are compounded - if all inputs were equal with metadata types then it would be easier. Much of the work has been done by looking at final XML file and working backwards from there.

As mentioned, we are looking to provide back out all the metadata we got in as XML so third parties can certainly mine the file for conform.

Michael
 
MichaelP said:
There is a unique "user" tag that we get from RedCine that is not part of the REDrushes or Metacheater:
<user>"9F0D434C-12CA-4B73-B981-3F95983E2E72"</user>

Each R3D has a unique user tag. There are other fields that are different that we are looking to see which ones are the minimum needed to make a conform work in RedCine when not started in RedCine.
Click to expand...

Is that actually generated from or stored in the RED file? If so it isn't reported with any other RED tools (REDrushes, REDline)?

It is a UUID, but I assumed was simply arbitrary rather than sepcifically related to the file. Used internally in REDCINE to identify clips.

I'd like to know more about that.

My approach as been to take a CSV from REDline of all files and an ALE from Avid, and use the information derived from the two to make a script for REDline. I assumed I would be able to do the same with a REDCINE xml, I just haven't tried.
 
I am still trying to figure that out. I do know it something that RedCine generates and is not part of the original R3D file. Still working it.

Michael
 
MichaelP,
It would like you are one popular fella with Avid questions. Not to bog you down, are there any particular places to look for offline editors (avid primarily) to look for a more standard workflow of offline through finish? Do you make $ per reference? ;-)
 
You must log in or register to reply here.
Back
Top