EDL challenges with build 356 and 449 OSX

[jimhare]

***NOTE - I will continue to troubleshoot this on my own and provide updates as I get closer***

Overall I have had excellent results bringing an FCP EDL into RCX 356 OSX. When I get it right, it works absolutely perfectly.

Having said that, I would like to get to the bottom of a couple of issues I am having:

1. I haven't quite figured it out, but it appears that if RCX can't find a clip, or maybe it's if the EDL references any non-Red info, it creates a bizarre timeline that is several hours long and pretty much random clips. I have had a certain degree of luck cleaning up the EDL before import. For example if I search and replace clips that have been renamed to their original R3D name, it seems to work.

2. I can only get build 356 to import my EDLs. Build 449 seems to ignore my EDL import instructions and the timeline remains blank. Both OSX 64-bit.

3. My workflow is based on making prores edit files in RCX with Red Rocket, editing in FCP (combination of multicam and straight clips,) then saving an EDL and going back to RCX. By selecting the original R3D folder as source it references the R3Ds instead of .MOVs without the need for Clipfinder etc. I am NOT using proxies and can't use XML because I am using multiclips in FCP, which prevents it from making a proper XML. This is a bug from way back.


Again, there are a few things going on here so I'm not sure where to focus. My immediate problem is that I have an EDL that I can't seem to correct and properly import. It just gives me the multi hour timeline with random clips, even though I feel like I have addressed any issues. This happens both when I select REPLACE WITH SLUG or MANUAL RELINK under "if unable to relink."

Any advice would be greatly apprecaited about any of this.

Thanks!

Jim Hare
Sydney

 

[David Ibbitson]

Hi Jim,

1. If you can send me a simple EDL that demonstrates this problem, I can look into this right away.

2. Don't use 449 -- it had a bug that prevented any importing of any EDL whatsoever. Stick to Build 454.

3. Not sure what you are asking here -- It doesn't matter if the EDL references .mov's or .R3D's. It looks for filenames that begin of the form A001_C001_C12345 and attempts
to match an R3D on the same name in the original source directory.

Hope this helps. Feel free to shoot me an email at david dot ibbitson at red dot com with more details.

Cheers,
David

 

[jimhare]

Thanks David, sending email now.

Regarding 3, was just explaining my workflow in case it was assumed I was editing with proxies or something. Understand that it matches to the R3D, which is fantastic!

 

[jake blackstone]

If you're doing editing with FCP, why are you using EDL? XML is a much better option and for me it works absolutely perfect every time.

 

[jimhare]

Hi Jake,

I mentioned in point 3 from my original message that I need to use EDL because FCP cannot create a proper XML from a multiclip project.

Have made some progress on this. I have discovered that the offending clip spans midnight in its timecode. Starts around 22:50:00 and ends around 00:50:00. Up until this point it works fine, then goes haywire.

Couple of other strange things happening as well, but narrowing in on them.

 

[jimhare]

Now using Build 454 OSX 64-bit version.

Think I have identified the issue as noted in last message, if an R3D timecode spans midnight, it loses the plot when used in an EDL in RCX. Probably not a common issue for most, but I shoot live shows and have 120 minute single takes. Then to complicate it further put up to 7 Reds together in a Multicam in FCP.

Should be easy to avoid the timecode issue on future shoots, but hoping RCX can be updated to deal with this. Otherwise I'll have to rebuild large sections of my edit, which would be painful.

 

[jake blackstone]

Hi Jake,

I mentioned in point 3 from my original message that I need to use EDL because FCP cannot create a proper XML from a multiclip project.

Have made some progress on this. I have discovered that the offending clip spans midnight in its timecode. Starts around 22:50:00 and ends around 00:50:00. Up until this point it works fine, then goes haywire.

Couple of other strange things happening as well, but narrowing in on them.

Strange, I had number of multiclips in my timeline and no problem with XML...
May be I misunderstand what you mean by multiclip...

 

[jimhare]

Hi Jake, I'll try it again but have been told on several occasions that the XML from multicam is bizarre.

Works in Color but not out in the world.

By multi clip I actually meant multiple cam, lining up seven clips that come up in a grid so you can do a pseudo live cut.

Great feature but munches the XML.

Let me know if this is what you are doing and I'll try again.

 

[jake blackstone]

Hi Jake, I'll try it again but have been told on several occasions that the XML from multicam is bizarre.

Works in Color but not out in the world.

By multi clip I actually meant multiple cam, lining up seven clips that come up in a grid so you can do a pseudo live cut.

Great feature but munches the XML.

Let me know if this is what you are doing and I'll try again.

Aaah, I see now what you're saying. No, that is not what I'm doing, Sorry for misunderstanding...