EDL TO REDCINE-X Applescript (beta)

[Jonas Rejman]

Thanks for this tool!
It is fratin' awesome.

I would like to request functionality before B16...
I have a project shot on B15, that I would like to look at one more time with redcineX and the new algorithms.
B16 introduced a new naming structure, and the script does not find R3D file names for B15 footage and below.

I attached a short EDL made from B15 R3D's

Thank you!!

Jonas

 

[Mikael Lubtchansky]

Thanks for this tool!
I would like to request functionality before B16...
I have a project shot on B15, that I would like to look at one more time with redcineX and the new algorithms.
B16 introduced a new naming structure, and the script does not find R3D file names for B15 footage and below.

Hi Jonas

EDL2RCX should now work with footage created on pre 16 camera firmware.

Check the updated 1st post...

 

[Bal Deo]

so clipfinder is able to generate a script from my edl or xml from fcp and open it RCX with the edits of my fcp timeline?
Or is the process some what different?

Hey Kids,

You might want to look for the new version of CLIPFINDER. Which does all of this and more.

David

 

[Mikael Lubtchansky]

so clipfinder is able to generate a script from my edl or xml from fcp and open it RCX with the edits of my fcp timeline?
Or is the process some what different?

Yes Clipfinder can do the same with xml files (not edls) and can also do MUCH more than this script (it will document your clips, reconform to proxies for color, set metadatas, control Rocketcine-X, make ALEs, render offlines etc).
My script is just a quick and simple EDL to RCX timeline conform tool.

I've updated the first post of this thread with information on how to obtain an unlock code : donate any amount over $15 to my email using paypal (mika at nerim.fr) and I'll send you back your unlock code via email. It will remove permanently the '10 first edits' limit from the evaluation version.

 

[Jonas Rejman]

in the last version, 0.25 and 0.26 I get a:
"edrc.plist of <script>" missing, and the script does not start.

Can someone point out, what is missing on my system?
the 0.2 version worked with no problems.

Thank you.

 

[Mikael Lubtchansky]

in the last version, 0.25 and 0.26 I get a:
"edrc.plist of <script>" missing, and the script does not start.
Can someone point out, what is missing on my system?
the 0.2 version worked with no problems.
Thank you.

fixed in 0.31, sorry guys.

Thanks Jonas for being an early tester of the unlocked version.

 

[Brian_Obee]

It works well with proxys too, no need to convert if that is your preffered workflow.

I just posted a new version (0.25) that might work also with Premiere... (not fully tested yet)

Mikael

Thanks. After I select the R3D file folder and click 'no' I don't have any more R3D files to look for, I get a pop up message that starts with 'Can't get text item 2 of "TITLE: CMX3...' and the script ends. Any clue as to what I'm doing wrong?

 

[Mikael Lubtchansky]

Thanks. After I select the R3D file folder and click 'no' I don't have any more R3D files to look for, I get a pop up message that starts with 'Can't get text item 2 of "TITLE: CMX3...' and the script ends. Any clue as to what I'm doing wrong?

can you send me the EDL you're using ? It might be a 'new' flavor I haven't tested yet, I'll try to see what happened here and fix it.

thanks

 

[Brian_Obee]

can you send me the EDL you're using


thanks

Attached. Thanks!

 

[Brian_Obee]

Thanks. After I select the R3D file folder and click 'no' I don't have any more R3D files to look for, I get a pop up message that starts with 'Can't get text item 2 of "TITLE: CMX3...' and the script ends. Any clue as to what I'm doing wrong?

We got it to work by deleting all but one of the audio tracks in FCP prior to exporting the EDL.

 

[Mikael Lubtchansky]

We got it to work by deleting all but one of the audio tracks in FCP prior to exporting the EDL.

Yes I try to work around those audio issues but it's always safer to export an 'image only' EDL whenever possible.

0.35 fixed the error you ran into and a few other issues....

thanks for the feedback

 

[Brian_Obee]

Yes I try to work around those audio issues but it's always safer to export an 'image only' EDL whenever possible.

0.35 fixed the error you ran into and a few other issues....

thanks for the feedback

Thanks for your effort! We really appreciate it.

 

[Mikael Lubtchansky]

Thanks for your effort! We really appreciate it.

Anyone had succes using my script with cs4 and Avid EDLs ? I can only test it in full with FCP right now but it should work in theory...

Thanks to report here if you had any specific issue

 

[James Rayburn]

I've used it successfully with an Avid EDL. Seems to work great.

Now if RCX158 would actually make MXF media properly, I'd have an actual workflow!

Thanks for your efforts, its great.

 

[Jonas Rejman]

I have two feature requests:

1.)
I often end up changing the speed of 120fps high-speed 2K material one shoots on the R1.
(its just too tempting not to give it a go on set...)

If I use the script on such a sequence, the conform does not work - the images are all over the place and the timeline falls apart.

I am not sure, if RCX already supports varispeed framerates, probably not.
What would help though, if the script pics up the sequences with changed speed,
and just reconstructs the timeline as if they were at normal speed.

That way, one can at least export the in and outs to ProRez, and re-do the speedups in the finishing system.

2.)
Add the ability for handles please.


Thanks!

 

[Mikael Lubtchansky]

Jonas,

RCX doesn't handle any speed change at the moment and it son't think it is coming soon... not really the philosophy of the app as it's more a dailies tool than a finishing tool (same goes for secondary grading i think)...

What I can still do is upon detection of any speed change, calculate in/out points for all clips and send to the RCX bin instead of timeline.

adding handles on the way to a RCX bin is also possible (makes little sense to make a timeline with handles) BUT :

Sometimes handles cannot be created to the desired length (if you edited a clip from frame 0 or from frame 5 while asking for a 10 frames handle) so we need a way to be aware of this before the edit can be re-constructed back once each clip was re-exported out of RCX... so adding handles would also require to recreate a new EDL, or more probably an XML file so you keep frame accuracy all the way back and forth. Will see what can be done but don't hold your breath on this one yet...

....

Another feature that maybe could be useful once each R3Ds was identified from the EDL is an option to duplicate all clips to a separate directory and make a LUA file linking to those clips instead of the original ones. It would reduce the overall file size needed to move the project around to other machines and still be able to reopen the edit in RCX. But I would have to work around some AppleScript limitations as it cannot display any progress window or any dialog while doing the copy so you'd have no way to know if everything is going OK while staring for several minutes at the spinning ball... I could use growl to notify of copy progress or launch a secondary script just to display some info. Would such a copy feature be useful ?

 

[Jonas Rejman]

1.
Well, picking up the right in and outs, and placing them in the timeline would be a good start.

2.
This is a typical handle-problem, but I wonder how often this one comes up. Having 20 frames handles is usually more then enough for a slate and a after "cut" pan, so this might be not an issue when shooting shorts.
It might be critical for documentaries and run&gun or similar.
The easiest solution for now might be, to just ignore the handle command, if such event occurs, and log it into a file.

3.
Copying only what is in EDL will surely be incredible useful. Clipfinder has this option with a little workaround and it works well.
I suggest however to create a rsynch terminal batch command, that the user has to launch separately. This way you can follow the process in the terminal, it will be parity-checked for data errors and will not hang up the apple script.

 

[James Rayburn]

Avid EDL issues

Avid EDL issues

I've had success with a couple EDL's, and not so much with others.

First, does the "CLIP NAME" in the EDL matter? Because in the original EDL I sent you, my "CLIP NAME" were the same as my Tape Name. (both 16 character R3D naming).

Second, is there a limit to the number of folders this will search? I have a folder with lots of R3Ds, and your script seems to search the whole thing. (finding 171 total clips). But for whatever reason 1 of my 10 clips from my EDL isn't found.

Here is the screenshot of the shot which isn't found:

But as you can see, its in the same folder structure as the rest of my files:

I've attached my EDL.

Thanks.

-James @ charlieuniformtango

 

[Mikael Lubtchansky]

James

as I couldn't reproduce the error here with your EDL, I have to send you a special version that will write a log file with the content of the scan folder and will log any error to a text file.

Re-run your EDL thru this version and send me the log file please.

 

[LaChris]

HI!, I have successfully used EDL2RCX_0.35 - and it is super - but where can I obtain REDCine-X B158? On red.com / support / is only Build 104th ...
Thanks
Christina