Welcome to our community

Be a part of something great, join today!

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

RedTrip

Success! Tried it out quite a few times and it's happy. Made a sequence with layers, transitions, even sync audio and we went all the way through, even to Color and back, and no problems. WELL DONE!
 
Success! Tried it out quite a few times and it's happy. Made a sequence with layers, transitions, even sync audio and we went all the way through, even to Color and back, and no problems. WELL DONE!

Yup. Crazy good stuff.

Did I mention that the forthcoming Release Version of RedTrip contains a magic trick?

You may need some depends, when you figure it out.
 
Thats perfectly fine. One should get compensated for their time and talents. Expecting things for free all the time is pretty tacky. Although it is suggested not to use this on real projects as it is still Alpha, it has worked pretty good for our needs so far. I would like to see some way that the redcine edl and droplet 2 connect to an image sequence or change the extension in the edl of the used files. Maybe it already does and Im not doing it right. But on things that need better color control than redcine allows, we most likely will take dpx's into color, and I don't want to loose my edl just because I went to an image sequence instead of mov's if that makes sense.

I see this Final Cut Roundtrip as a stepping stone to some more advanced workflows, involving image sequences. That's what I want for myself. I want to keep all twelve bits and do some awesome secondaries, seperate curves, selective colors and all kindza cool shizzle. Skipping over quicktime is the right thing to do and I think GlueTools and Autoduck + son-of-RedTrip might be the way to go. But lets get some ROI on these cameras first... one thing at a time...

Hey, double the APPLAUSE to Ian here! Being a post guy I can say that to me and my clients the RED camera is really only as good as the post workflow which isn't quite there yet. I think we all forgive a lot since this is so new and revolutionary. Those tireless efforts of Ian are making it better. Hell, he was online last night at something like 4 AM! It's that kind of dedication that will make all this work in the end.

Much to the dismay of my girlfriend.

Success! Tried it out quite a few times and it's happy. Made a sequence with layers, transitions, even sync audio and we went all the way through, even to Color and back, and no problems. WELL DONE!

Music to my ears!

I think the secret is to make a very clean timeline and treat your redcode like you are cutting film at first, and then do your crazy final cut pro hijinx after you've got your footage through the system. Keeping your handles is IMHO better than cropping them and worth the additional render time, that's why I made it the default button in the droplet.

I
 
To put things in perspective:

I bought Automatic Duck (AVID to FCP OMF import) to online ONE project in HD, to prove a point, when it cost 999$. And that was NOT a bad choice.

(This may become a bad business decission to tell ian... :) )

But there are about 2500 (guestimate) of the Red 3500 (another guestimate) who have much more pressing issues to prove some points.

If the workflow could approach that kind of ease, I wouldn't mind contributing to make iBloom a "500$ (current a-duck price) x 3500 (current customer base for Red)" aire...

Gunleik
 
To put things in perspective:

I bought Automatic Duck (AVID to FCP OMF import) to online ONE project in HD, to prove a point, when it cost 999$. And that was NOT a bad choice.

(This may become a bad business decission to tell ian... :) )
Well ... Ian is one of the smarter folks I have met in last few years. He'll do just fine.
 
SUCCESS!! I got it working last night I'm so stoked. Thank you guys soooo much. I am now going to try to import the second step FCP XML into AE with this script: http://basicfcptoae.laurenthenriot.net/index.en.html I'm away from the office today but I'll give it a go later.


I'm so stoked!!! now make it work with redalert!
 
I'm so stoked!!! now make it work with redalert!
Or even better:
make the RC correction "export" controll the command-line tool on a cluster...
Cool idea, would you want that to look something like this:
582_1203805480.jpg

I'll think about it.

I
 
Well for starters there is no color info coming out of Redcine yet...
I

LOL!!!

Now they all know it doesn't work .... yet. We need to discuss your "smoke and mirror skills".

Now, help me out with this new novel ....

All work and no color settings in REDCINE XML makes Ian and Mark dull boys -
All work and no color settings in REDCINE XML makes Ian and Mark dull boys -
All work and no color settings in REDCINE XML makes Ian and Mark dull boys -
All work and no color settings in REDCINE XML makes Ian and Mark dull boys -
All work and no color settings in REDCINE XML makes Ian and Mark dull boys -
All work and no color settings in REDCINE XML makes Ian and Mark dull boys -
 
Cool idea, would you want that to look something like this:
582_1203805480.jpg

I'll think about it.

I

Yup.

Even if it doesn't work, that's pretty much it...

And this makes the tool usable for the non-FCP crowd for creating onlines/offlines as well. At least if RC starts to handle TC right.

There was just now a guy on the CML crying out for a solution to batch footage for an Adrenaline edit...

Gunleik
 
So question for ya Ian. Today I tried using the substitute way of going about things. I exported all of my footage to SD letterboxed using the DV50 codec and added _DV50 to the end of my files (Yeah yeah, 2k & 4k to SD letterboxed doesn't make too much sense, but for this particular application it does). So an example of my file name that I edited in FCP is A002_C018_080220_DV50.mov So theoretically I should be able to type in _DV50 in RedTripDroplet Step 1 and have it find the appropriate Red file, but the bash window is saying that the file is not found. Where do I need to place my DV50 files and Red files in relation to each other so that the script works accordingly? Thanks.
 
Ok. So I got it to work. As of now you need to have your exported proxies (doesn't matter which codec or export settings you use) in the same folder as the Red file that it is a proxie of. It loads the construct just fine and all my ins and outs are dead on. It is kind of a big pain right now, unless I'm missing something, but when I export my proxies, I export them into a separate folder so that all my clips are in one folder. It's easier to find footage and not have to navigate through all my folders just to find a clip. How hard would it be to add in a feature that you could tell Redtrip where your proxies are located and the root folder of where your .r3d files are located so that you it can still make a connection between the clips even though they aren't in the same folder? Does that make sense? That is something very important to me. All things aside though, it has been really fun testing this script out in semi-real life situations.
 
Ok. So I got it to work. As of now you need to have your exported proxies (doesn't matter which codec or export settings you use) in the same folder as the Red file that it is a proxie of. It loads the construct just fine and all my ins and outs are dead on. It is kind of a big pain right now, unless I'm missing something, but when I export my proxies, I export them into a separate folder so that all my clips are in one folder. It's easier to find footage and not have to navigate through all my folders just to find a clip. How hard would it be to add in a feature that you could tell Redtrip where your proxies are located and the root folder of where your .r3d files are located so that you it can still make a connection between the clips even though they aren't in the same folder? Does that make sense? That is something very important to me. All things aside though, it has been really fun testing this script out in semi-real life situations.

StrongBad,

Thanks for your feedback. I'm very aware of your problem. The solution was a little complicated to implement in a command line script. For the time being I would suggest compressing proxies into their original folders. It's the only pointer we have back to your original footage.

IBloom
 
StrongBad,

Thanks for your feedback. I'm very aware of your problem. The solution was a little complicated to implement in a command line script. For the time being I would suggest compressing proxies into their original folders. It's the only pointer we have back to your original footage.

IBloom
I don't consider myself a Redcine expert by any means, so is there a way to export my proxies so that they automatically go into that folder? Because right now I'm having to manually move them into the folders, and that's fine for a couple of shots, but once it gets into the 100's it takes some time.

I can't express my gratitude enough for this though. It definitely opens many doors that were once closed. Thanks for your time and efforts on this.
 
I don't consider myself a Redcine expert by any means, so is there a way to export my proxies so that they automatically go into that folder? Because right now I'm having to manually move them into the folders, and that's fine for a couple of shots, but once it gets into the 100's it takes some time.

I can't express my gratitude enough for this though. It definitely opens many doors that were once closed. Thanks for your time and efforts on this.

You would have to manually move them into a Compressor droplet, then compress to source. That is the only way right now. It's easier if you use the details view in finder and open each folder with the triangle expander thinger.

IBloom
 
Back
Top