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

ROCKETcine-X XML workaround

Kaku Ito

Kaku Ito

Well-known member
Joined
Feb 20, 2008
Messages
2,803
Reaction score
3
Points
38
Age
65
Location
Chiyoda-ku, Tokyo
Website
www.dittok.info
Since ROCKETcine-X does not read XML at this moment, but my job requires to render a lot of edited files. I wanted to load up only the clips in the edited timeline on the XML for baselight with ROCKETcine-X.

I realized that I can use Monkey Extract or Clipfinder for this.
You can load the XML in say Monkey Extract, then export to REDCINE feature in the rendering section. Monkey Extract generates the XML for REDCINE AND the aliases for the R3Ds that are used in the XML. Simply load those aliases and you can just deal with the clips in the timeline.

You can use Clipfinder's move feature, too, but I feel safer using the above method.

Now, does anyone know how to applied in/out points in the edit XML to transfer to metadata in/out parameter?
 
Wow, interestingly, I just found out that when you adjust the metadata using the aliases of the R3D footage created with Monkey Extract, the RSX files are saved with the aliases. Hmmm, this is the way to keep different RSX versions.
 
Thanks Chris,

However, I found a problem to the Monkey Extract method. ME only makes the alias of the first R3D, so I'd have to make aliases of the rest manually.

I'll email Rubber Monkey to see if they can do something.
 
Wait a minute, Crimson probably creates intermediate R3Ds better.....
 
Oh, yes, Crimson's creating intermediate feature worked fine for even with spanned R3D clips. so, now I can create multiple version of RSX easily.
 
Now, it would be great if XML's in/out points transfers to metadata in/out.
 
The solution to the above would be creating an alias folder for the each cuts in the XML. Thus each alias would carry independent RSX, then edit in/out transferred to metadata in/out. Then load the whole thing with load folder in ROCKETcine-X.

Hans, please make this work!
 
Well, also RED has to help for output folder manipulation for the clips under the same names. Deanan?
 
Chris,

There are some development to this. Stay tuned.
 
Amazing, now I can edit in FCP, export XML, read that with special version of Clipfinder, conform and export the aliases of each cuts with in/out points translated to RSX in/out, then export aliases (just like the intermediates of Crimson) of each cuts with its own RSX with special manner, manner that creates folders automatically to differentiate the cuts from the same R3D clip.

Then I can import them by folders to ROCKETcine-X, ending up all of the cuts from the XML are there in the list with each edit in/out and its own RSX so that when you adjust the metadata, they are all independently adjusted and kept in the alias location. Then you can export using "output with Clip Filename to Clip Folder" then even if the cuts are from the same R3D clip, each cuts would be rendered in the each alias location!

This is amazing, Hans is amazing. Someone laughed at me about this idea and the thread, I don't care, because I know this is the fastest and most practical way to utilize REDROCKET at this moment.
 
Holy @#@#,

Calling Hans right now!!!
This guy is fantastic :)

Thanks for the info Kaku!

Antoine
 
Hello Antoine my friend,

I woke and this morning and checked my email on my iPhone, and Hans sent me a alpha on a soon to be standalone app. for this workflow. The app. he calls it "Flight Director" would run automatically to process XML for rendering in ROCKETcine-X. For the last two days, I feel like I had him as my personal programmer, I guess he thought my idea was worth trying :).
 
I did, sorry doing about five things at the same time.

I actually have to crank the fans in Mac Pro Nehalem to keep my ATTO R380 functioning, so don't really hear the RR's fan :).
 
Hi Kaku,

Ah...

I have a "old" Mac Pro 3.2.

Testing with the other "old" Mac 2.8 tonight to see if i still hear that fan running high speed.

Antoine
 
Nehalem Mac Pros have six fans....now My Mac Pro is as noisy as Windows machines.
 
Hans made an another update to this function. It is sent out to the alpha team, so public will see this soon.
 
You must log in or register to reply here.
Back
Top