XML2RCX script (mac only)

[Mikael Lubtchansky]

XML to REDCine-X Conform Tool (Mac only)
version 0.92 - Mikael Lubtchansky

http://foolcolor.net/XML2RCX_0.92.zip

:::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::::::::
Instructions

1. Shoot some RED footage. Transcode to offline files and edit in Avid, FCP (also supports L&T or Quicktime proxies).
2. Export XML
3. Launch XML2RCX Script and follow onscreen instructions
4. After pointing to your XML file and the original R3D location, a LUA script file will be generated on your desktop
5. Launch REDCINE-X, under file menu, choose 'Run script', select the LUA file and your edit will be recreated in the timeline.

Options includes adding handles, exporting to timeline or bin.

:::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::::::::
Unlocking :

To unlock the demo version and remove the 7 clips limit, you should send a donation via Paypal to mika at nerim.net
Any amount over $15 will get you a code to unlock all my current scripts

:::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::::::::
Update history :

- included Satimage osax extension in the app package
- fixed an issue with sequence markers
- clips renamed in FCP (not files, just their reference in FCP) should now be re-linked correctly
- fixed some permission errors when scanning full drives
- preliminary Avid support
- Multi layers Avid files will now export all clips to timeline (layer 1 clips, then layers 2 clips etc...)
- more LUA options : export to timeline, with or without handles, export to bin with handles, without handles or as whole clips.
- fixed a bug with "long" Avid xml files
- much much faster source folder scanning
- will search for R3D filename in ClipName if CamRoll and TapeID are missing (Avid)
- added a "skip all"option when several clips are missing and you wish to continue
- will search for R3D filename in "file id" tags when clip name were changed in FCP and a marker related error (FCP)
- now works with FCP subclips
- less restrictive as far as setting handles size
- much faster when source R3D folder contains lots of files
- can now scan up to 20 source directories
- fixed a bug in snow leopard causing a looping bug with some xml files.
- detects any illegal characters in Sequence name to avoid .lua file creation error

:::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::::::::
Support :

If you encounter any issues, please email me your XML and corresponding .lua files.
I'll do my best to keep the scripts bug free and up to date (time permitting)
Thanks for any feedback by email or on the REDuser thread.

:::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::::::::
Legal info :

The EDL2RCX / XML2RCX / RCX2XML / EDL2R3D software and documentation are offered AS IS and WITHOUT ANY WARRANTY express or implied, including but not limited to warranty of design, merchantability, or fitness for a particular purpose. In no event shall we be liable for any incidental, indirect, special, or consequential damages resulting from the use of the software or documentation.
In no event will our total liability to you for all damages, losses, and causes of action, whether in contract, tort (including negligence), or otherwise, exceed the amount paid by you for the software.

This script uses the XML lib scripting addition freeware, developed by Satimage :
www.satimage.fr/software/en/downloads/downloads_companion_osaxen.html
It is included in this app bundle so you don't need to install it manualy.

This software is not affiliated with RED.com, Inc.
REDCINE-X, R3D are trademarks of RED.com, Inc.
Final Cut Pro is a trademark of Apple Inc.
Avid is a trademark of Avid Technology, Inc

[Luis Otero]

Hello,

Whenever I try to open a XML file created by FC, I receive this message: "Fine_Name" doesn't understand the <<event XML open>> message.

Please advise,

[Mikael Lubtchansky]

oops sorry, forgot to mention that !
my script relies on a great freeware Applescript addition called XML lib

you can read more about it here :
http://www.satimage.fr/software/en/downloads/downloads_companion_osaxen.html
http://www.satimage.fr/software/en/readme/readme_xmllib315.html

edit : version 0.2 beta now includes the scripting addition and it is not longer needed to install it manually...

Mikael

[Jonas Rejman]

I moved my R3D files out of the folders, where they were originally created.
(I should not have done that, but that was my first RED project ...)

Now, the script does not seem to find those files, stating i selected the wrong folder.

XML:
5715

[Mikael Lubtchansky]

I moved my R3D files out of the folders, where they were originally created.


Can you email me a screen capture of what your folder structure looks like ?

Thanks

[Luis Otero]

Mikael,

I downloaded the latest beta version, but when I try to unzip the file it creates another zip file called "XML2RCX_0.2.zip.cpgz". Then, it I try to open the created one, it creates a copy of the original zip file... It is a never-ending-story. :crazy:

Please advise,

[Mikael Lubtchansky]

I downloaded the latest beta version, but when I try to unzip the file it creates another zip file called "XML2RCX_0.2.zip.cpgz". Then, it I try to open the created one, it creates a copy of the original zip file... It is a never-ending-story. :crazy:


I just tried again here and the downloaded file unzipped fine... strange.

anyone got it working ?

[Jonas Rejman]

unzip is fine over here, too

[Mikael Lubtchansky]

unzip is fine over here, too

Jonas I've spotted your issue, it is related to some markers in your FCP XML... will post a new version as soon as it is fixed.

[Mikael Lubtchansky]

Now, the script does not seem to find those files, stating i selected the wrong folder.


Nothing was wrong with the file structure you've send by email, my script had an issue with sequence markers

I just posted beta 0.25 and it should fix this issue...

Mikael

[Luis Otero]

I can correctly unzip this version...! :seeya:

Thanks,

[LaChris]

Hi Mikael;
I get the message:
"No edit points could be relinked. You may have selected the wrong R3D directory".
I am pointing at the right place; although I have to make the 2 x point, because when I selekt the intire disk I get this message:
" find: /Volumes/Boxer 1//.Trashes: Permission denied".

And tell me where can I donate? :-)

Yours,
Christina

[Mikael Lubtchansky]

Hi Mikael;
I get the message:
"No edit points could be relinked. You may have selected the wrong R3D directory".
Christina

Looking at the XML you've sent, it seems you have renamed all your clips in FCP. But hopefully you've kept the movie file name unchanged so the script can read those instead...

beta 0.3 should fix that.

http://www.foolcolor.net/XML2RCX_0.3.zip

will look into the trash permission bug and get rid of it to for next version

Best

[Mikael Lubtchansky]

when I selekt the intire disk I get this message:
" find: /Volumes/Boxer 1//.Trashes: Permission denied".


fixed in 0.31 :

http://www.foolcolor.net/XML2RCX_0.31.zip

I would recommend pointing to one or several folders where you know your R3Ds are located instead of a whole disk as it could be much faster if your drive contains a lot of non red files but it should now work without the permission error.

Thanks for the feedback !

[Mikael Lubtchansky]

0.41 now supports Avid XML...

only 1 layer will export for now, more to come soon on this (read the 1st post or read me file) :

http://www.foolcolor.net/XML2RCX_0.41.zip

Thanks for feedback on this if you test it...

[Mikael Lubtchansky]

new version 0.5 adds support for multi layer Avid XMLs, and will now export to bin with handles (or not) along with the timeline and whole clips to bin options...

http://www.foolcolor.net/XML2RCX_0.5.zip

[James Rayburn]

Thanks Mikael! Your script rocks.

[Luis Otero]

Great!!! I was just about to post a petition to have the footage to be located to both places!

Thanks a million! :party:

[Mikael Lubtchansky]

Great!!! I was just about to post a petition to have the footage to be located to both places!

Up to 10 source R3D folders can be scanned in current version, but it's very easy to add more if needed by anyone...

[Luis Otero]

Hey,

I am using it for a feature, so I really do need it to have much more than 10 clips.

Thanks!

[Mikael Lubtchansky]

Luis,

R3D Clips are unlimited in the full version that you have.

10 is just the current limit as to how many scan folders you can add to reconnect the original R3D files (it can reconnect your XML if your R3D files are located on up to 10 different disk drives...).

But if you need more than 10 source drives I can do a quick update to the script...

Mikael

[Mikael Lubtchansky]

version 0.7 fixes several major and minor issues conforming FCP and Avid xmls. Thanks to all who sent their tests XMLs, it has been very helpful


----
FYI version 0.7 will no longer work with the bogus name/serial floating around...

I received so far 7 donations (thanks guys) for my 2 scripts and even if I didn't wrote them to make any money I was surprised to discover someone was interested in using the full version without supporting future development... and save 15$ !!

[Brandon Kraemer]

version 0.7 fixes several major and minor issues conforming FCP and Avid xmls. Thanks to all who sent their tests XMLs, it has been very helpful


----
FYI version 0.7 will no longer work with the bogus name/serial floating around...

I received so far 7 donations (thanks guys) for my 2 scripts and even if I didn't wrote them to make any money I was surprised to discover someone was interested in using the full version without supporting future development... and save 15$ !!

Sorry, but where is the link to 0.7, if that is the latest version... on this thread, I only see a link to 0.5.

AH... NEVERMIND... my bad.

[Mikael Lubtchansky]

XML2RCX version 0.75

http://www.foolcolor.net/XML2RCX_0.75.zip

now with a much faster source folder scanning

[Mikael Lubtchansky]

v 0.76 will search for R3D filename in ClipName if CamRoll and TapeID are missing (Avid)

http://www.foolcolor.net/XML2RCX_0.76.zip

[Nikola Stefanovic]

I want to thank you once again Mikael. Your tool saves me an hour or two and couple of hundreds of gigabytes on a daily basis. I'm color grading mostly commercials. My previous workflow was like this: go trough timeline and write down RED file names, then locate that files on hard drive and convert it in full duration with RocketCineX to DPX sequences to finish it on the DaVinci Resolve. I know that there is a tools like clipfinder, crimson and similar, but that tools are very complicated. XML2RCX for me was a missing link. Export XML, point to raw RED files and even add a handles! Wow. Load lua to Redcine-x, drag files from timeline to bin and export. Easy is the keyword.
My files and project are ready for less than a 10 minutes now, and just couple a days ago it last for hour or two. For me XML2RCX is every day life/time saver.
Best regards

[MichaelP]

v 0.76 will search for R3D filename in ClipName if CamRoll and TapeID are missing (Avid)

Mikael -

Avid Media Composer tracks original filename in many areas depending on how the original R3D was referenced or transcoded. I have been trying to get some consistency in metadata mapping over the past year... it is slowly happening.

With v5 of Media Composer and AMA, the filename will also appear "Source File" and has the equivalent properties of "Tape" when working with file based sources. v5 also takes advantage with EDL Manager and ALE tweaks from REDCINE-X to track R3D file names in the 8 character truncated style of FCP so that an EDL can be generated that Apple Color can link to with full filename as a *comment.

Michael

[Mikael Lubtchansky]

Mikael -

Avid Media Composer tracks original filename in many areas depending on how the original R3D was referenced or transcoded. I have been trying to get some consistency in metadata mapping over the past year... it is slowly happening.

Michael

Thanks Michael for the info, as I do not use or own any Avid Media Composer my script are just trying to adapt to whatever xml files exists in the real world (sent by some of my users/testers). I'd gladly add the "Source File" tag as a possible place to dig the info but since not everyone will update their editing station to v. 5 at the same time I'll still have to keep the script trying to parse any exotic xml it may encounter...

Mikael

[Peter Osinski]

will this work with premiere pro cs5's xml export abilities?

[Mikael Lubtchansky]

Peter,

I have added preliminary adobe support in the EDL version but not yet in the xml one as I do not have CS5 here yet. If you send me a few example XML files (with several clips/tracks/ some with audio, some non red footage/graphics) it should not be too hard to support Premiere Pro xml

Mikael

[Peter Osinski]

thank you for the offer....I am not going to get CS5 until I finally get my scarlet cinema as CS4 can still handle everything I need.

If anyone else has sample cs5 xml files please send them in so this can be added

[James Page]

Hi Mika, I've sent you my donation, looking forward to receiving the code!

[Mikael Lubtchansky]

Hi James

My home droid sent it a few hours ago to your paypal address... will resend it now to your signature address...

cheers and thanks for your support

Mikael

[Mikael Lubtchansky]

Minor update adding a "skip all" option when several R3D files are missing but you wish to continue with all the available one...

http://www.foolcolor.net/XML2RCX_0.77.zip

[Brandon Kraemer]

Love this script. Donation sent.

Having a bug with the XML version, but the EDL works like a charm. Bug email and XML file/screen capture sent as well.

bk

[Mikael Lubtchansky]

Thanks for the donation and the bug report...

your issue is now fixed in version 0.78 :

http://www.foolcolor.net/XML2RCX_0.78.zip

clip names where changed in FCP (Scene 1 etc...) so the script searched for the R3D filename elsewhere... it could find it but then made an error when it reached a marker.

should be all good now

Mikael

[Brandon Kraemer]

Thanks for the donation and the bug report...

your issue is now fixed in version 0.78 :

http://www.foolcolor.net/XML2RCX_0.78.zip

clip names where changed in FCP (Scene 1 etc...) so the script searched for the R3D filename elsewhere... it could find it but then made an error when it reached a marker.

should be all good now

Mikael

Damn! That was fast. Will try it tomorrow with the unlocked version. Thank you!!

bk

[Brandon Kraemer]

Mikael,

Trying to download the 2.2 mb file... getting a timed out message from the source server.

[Mikael Lubtchansky]

seems to work fine from here, maybe a temporary problem somewhere in the internet wires...

will send you a copy now via email...

[Eric Rainey]

Awesome!!!! Thanks!!!! It worked perfectly!!!!!

[Henk van den Doel]

We just gave the full version a spin and it works really easy to get a timeline to Redcine_X this way. Cooool.. thanks for that!

You think you can have a look at that Epic/Scarlet bug while you're at it?

[Mikael Lubtchansky]

http://www.foolcolor.net/XML2RCX_0.8.zip

will now search for R3D filename in "file id" tags when clip name were changed in FCP and also fixes a marker related error (FCP)

(thanks Brandon for the xml file that allowed to kill those 2 nasty bugs)

[Brandon Kraemer]

http://www.foolcolor.net/XML2RCX_0.8.zip

will now search for R3D filename in "file id" tags when clip name were changed in FCP and also fixes a marker related error (FCP)

(thanks Brandon for the xml file that allowed to kill those 2 nasty bugs)

Great! In the interim the EDL script worked.

Feature request: the ability to add handles would be awesome.

bk

[Mikael Lubtchansky]

Great! In the interim the EDL script worked.

Feature request: the ability to add handles would be awesome.

bk

sometime EDL is good enough technology :-)

handles are already featured in the XML version... both when sending to the timeline (default) and to a RCX bin... see attachments below

[Mikael Lubtchansky]

here is the first beta version of the roundtrip RCX->XML to re-conform your graded QT clips back to Final Cut Pro (Avid might come later... haven't looked into it yet) :

http://www.reduser.net/forum/showthread.php?p=629718

It takes your original xml file, scan your QuickTime export folder once you finished batch rendering all your clips (with or without handles) and re-conform everything into a new sequence matching your new codec/resolution.

It works well when long R3D clips are used several times in the edit.
Just have to tell RCX to not 'overwrite existing files' (each .mov file will get a new name ending with _S000, _S001 etc).

Thanks for sending your xml files by email if you run into any specific issues, will do my best to fix asap.

Mikael

[Mikael Lubtchansky]

New version 0.82 posted today supports FCP subclips and will relink with correct in/out points relative to the original clip :

http://foolcolor.net/XML2RCX_0.82.zip
http://mika.nerim.net/XML2RCX_0.82.zip

Thanks Tom Oswald for this one !

[James Page]

This is great, can't tell you how grateful i am for your efforts with this Mikael. It's amazing to me that RED haven't bought this from you. I find it indispensable.

[John McStravick]

Mikael, long time lurker, first time poster. Love XML2RCX, but I am experiencing an issue with the handles option. It is calculating the maximum number of handles possible, but no matter what amount I enter it still reverts back to the maximum number of handles. Any thoughts on how to fix this?

[Mikael Lubtchansky]

Mikael, long time lurker, first time poster. Love XML2RCX, but I am experiencing an issue with the handles option. It is calculating the maximum number of handles possible, but no matter what amount I enter it still reverts back to the maximum number of handles. Any thoughts on how to fix this?

John, Can you email me your xml file. I'll have a look

scripts calculates the max handles size and *should* let you select a smaller value... if not there might be a bug left over. Will check it out.

Thanks

EDIT : Just tried here again and it works as it should... do you use the latest version ?

[John McStravick]

John, Can you email me your xml file. I'll have a look

scripts calculates the max handles size and *should* let you select a smaller value... if not there might be a bug left over. Will check it out.

Thanks

EDIT : Just tried here again and it works as it should... do you use the latest version ?

Just emailed my XML, let me know if that doesn't go through. We are currently using XML2RCX 0.82 which appears to be the latest, let me know if I missed an update. Thanks for your help! :costumed-smiley-047

[Mikael Lubtchansky]

I've made a quick fix in the hotel room (we're traveling in Buthan for a shoot with our MX)... this new version is far less restrictive as far as checking max handle size and should let you add handles whenever some shots were done around midnight TOD or if any exotic Edgecode/TOD issues arises between shoot and post. I will take a closer look at the issue if it is still a problem when I'm back :

http://foolcolor.net/XML2RCX_0.83.zip
http://mika.nerim.net/XML2RCX_0.83.zip

let me know if it helps

cheers

Mikael

[John McStravick]

I've made a quick fix in the hotel room (we're traveling in Buthan for a shoot with our MX)... this new version is far less restrictive as far as checking max handle size and should let you add handles whenever some shots were done around midnight TOD or if any exotic Edgecode/TOD issues arises between shoot and post. I will take a closer look at the issue if it is still a problem when I'm back :

http://foolcolor.net/XML2RCX_0.83.zip
http://mika.nerim.net/XML2RCX_0.83.zip

let me know if it helps

cheers

Mikael

Yahtzee! This worked perfectly. Be sure to check out the Taktsang Monastery while you're in Bhutan

[Mikael Lubtchansky]

v 0.84 will be much faster when scanning thousands of source R3D files...

http://foolcolor.net/XML2RCX_0.84.zip
http://mika.nerim.net/XML2RCX_0.84.zip

[Mikael Lubtchansky]

As requested by one user XML2RCX 0.85 can now scan up to 20 sources directories (before it was limited to 10)... just let me know if anyone needs more than that...

http://foolcolor.net/XML2RCX_0.85.zip
http://mika.nerim.net/XML2RCX_0.85.zip

Mikael

[Mikael Lubtchansky]

version 0.91 fixes a nasty looping bug under snow leopard (same clip getting repeated in the .lua file) :

http://foolcolor.net/XML2RCX_0.91.zip

[Mikael Lubtchansky]

http://foolcolor.net/XML2RCX_0.92.zip

:::::::::::::::::::::::::::::::::::::::::::::::::: ::::::::::::::

detects any illegal characters in Sequence name to avoid .lua file creation error

[Jody Neckles]

Hi Mikael just want to thank you for making such a cool script.
How long does it take to receive the unlock key after making a donation via Paypal? I made the donation a couple of hours ago and need the script code urgently :-)

[Brandon Kraemer]

Mikael, is 0.92 the last release of your script?

[Mikael Lubtchansky]

Mikael, is 0.92 the last release of your script?

yes 0.92 is latest but it is getting oldish (not updated in 18 months). Now that RCX can import XML directly I use that most of the time...
Do you still use my script ?
Let me know if you need something updated... my recent free time was spent learning Xcode to use the RED SDK and update my latest script (foolcat) to make it much faster...

[Brandon Kraemer]

yes 0.92 is latest but it is getting oldish (not updated in 18 months). Now that RCX can import XML directly I use that most of the time...
Do you still use my script ?
Let me know if you need something updated... my recent free time was spent learning Xcode to use the RED SDK and update my latest script (foolcat) to make it much faster...

We still use it because the direct XML has proved buggy in the past. However we found today that the resulting LUA script from version 0.92 did not import with any in/out range, only the full clip would import in RCX-PRO.

[Mikael Lubtchansky]

Could you send me the xml file and resulting lua by email I will have a look see if anything is wrong...
Do you remember updating anything specific on your machine since it last worked ?

[Brandon Kraemer]

Just emailed you. Only thing we have changed is RCX-Pro itself with the built in update tool.

Thanks Mikael.

[Mikael Lubtchansky]

In / Out points look to be OK in the lua file relative to the XML values so I'd say maybe something is broken in recent RCX-PRO lua reading.

I'll dig more see if I can reproduce the problem here but if you are in a rush to conform I can suggest :

- try loading the lua in an older REDCINE-X version (even if you updated to the latest you should be able to manually download and run an older version) then you could always save the project and reopen in latest version.

- give latest REDCINE-X PRO a new chance to read your XML, I have gotten good result not so long ago (it is true I did sent simple cut / silence edits)

[Brandon Kraemer]

In / Out points look to be OK in the lua file relative to the XML values so I'd say maybe something is broken in recent RCX-PRO lua reading.

I'll dig more see if I can reproduce the problem here but if you are in a rush to conform I can suggest :

- try loading the lua in an older REDCINE-X version (even if you updated to the latest you should be able to manually download and run an older version) then you could always save the project and reopen in latest version.

- give latest REDCINE-X PRO a new chance to read your XML, I have gotten good result not so long ago (it is true I did sent simple cut / silence edits)

Mikael,

The direct XML route works for us this time, I suspect it will usually continue to. Thanks for confirming it's likely something in RCX's LUA import tool. We would love to have options when it comes to this kind of workflow because in the past things like this come up and we need to try it a different way.

Thanks again.

[Mikael Lubtchansky]

Glad it worked :-)

will have a deeper look at this lua thing and hopefully will find time one day to merge all the useful tools into a cool and smart app !