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

FCP to AE to Color. Where all the experts?

Have you tried using Clipfinder to link the FCP XML to RED files and importing that? I thought you could import FCP XML to the new CS?

Another option is rough out your comps in FCP, make sure the Red footage needed is on the layer it should be and send to Color first. Then render DPX out of Color and send Color EDL to AE and finish everything in AE.


Dusty
 
I have only had a quick try of clipfinder everyone recommends it, but I don't think it will bring my edit in just the red files which would need reassembly, not really sure if that is correct
Paul
 
I have only had a quick try of clipfinder everyone recommends it, but I don't think it will bring my edit in just the red files which would need reassembly, not really sure if that is correct
Paul

Clipfinder can do neat stuff like go through an FCP XML and change from the proxies to the R3D files. It can also gather the R3D files used in a project

Except when I tried it, it didn't work for me. I was giving it a really complicated FCP file done by a client.

So I had to write my own scripts to do what Clipfinder does.

To be honest I really ticked off the moment. Been on the project all day and nowhere!

Yep, I feel your pain - I've been doing FCP / Premiere -> AE stuff since 2001.

It's a love / hate relationship.

It works flawlessly and is a killer indie tool... until it fails. If you originate in Premiere you're okay but with FCP there are troubles more regularly.

I think it's for people with more time than money. There's a reason the pros who have to do this on a daily basis use a different approach - load the offline into an Avid DS / Smoke / Scratch etc, then output stacks of frames to AE, then bring the AE renders back in.

For one thing, you can change your edit and not be in a world of pain conforming in After Effects!

One last suggestion: try Boris XML import. It has a 14-day trial and worked kinda okay on the last project I did this way (Premiere completely refused to load the XML file btw). It still messed up some in-points for me by a frame each way. So you need to export a reference from FCP and check.

I am also an owner of Automatic Duck. I hate the fact that they keep expecting you to pay nearly full price just to get it to work on a current version of After Effects.

The cost (time & money) of all of the little components needed to make things work really gets to me. Plus I wanted more flexibility to change my edit. Hence Avid + DaVinci.

Bruce Allen
www.boacinema.com
 
Does anyone know how to contact automatic duck?
 
I purchased Automatic duck.
It does bring in the red files, to AE but the trim points are jumbled up and in the wrong sequence.
I have tried to contact automatic duct but failed

The submit ticket form comes up with an error
They are offline with instant messaging
The telephone number they give comes back wit a message the numbers not allocated.
No support email address

To be honest I really ticked off the moment. Been on the project all day and nowhere!

That sounds unusual from a few standpoints, so I wouldn't throw in the towel just yet. First, I have really good success with Auto Duck, I use it daily to move footage to AE to share edits with our animation and compositing department. It almost always works like a charm. Be sure you are using the free AutoDuck FCP XML export tool to send your sequence from FCP.

Second, Wes Plate (Mr. AutoDuck) has always been great about tech support, first by releasing a very stable product to begin with, but is generally very good about follow up. Sorry to hear his website is down or your having a less than stellar experience. There must be an explanation.
 
Thanks Brandon.

I am using the AD xml export from fcp and import into AE.
There is an option to reconnect to R3D files instead of the footage you are using in FCP. that's where my problem lies, not as a general export import.
Glad to here the guy is normally good with support, but i been so frustrated today trying to get the edited r3d files into fcp and decided to with AD it's not all that cheap, and then find I am still back where I was was at 8 am this morning UK time.

Paul
 
I hear you Paul. No, AD is not cheap... it's $400, nothing to sneeze at for a plugin.

There could be a few reasons for your issue. First, were these proxies your cutting with generated with the camera, or with a build of RedCine X? If it's the latter, you might be dealing with bad time code data in the proxies. Regenerating them with the most recent build of RCX would fix that bug.

Second, and this is something I did prior to the latest version of AutoDuck that allows proxy relink... can you manually relink your proxy source clips in your project window with the .R3D files? Try one or two and see if they align correctly in the comp. The scale will be off, but that is resettable globally. If not, it might be because of the same proxy time code bug.

I did a project where I cut with proxies, relinked my source proxy clips with the .R3D before I did my effects work which included scaling. Then I set "proxies" for all my .R3D source layers in After Effects, setting the AE proxies to the red_M proxies. Worked to speed up previews until it was time to render for real.

If any of this helps give us an update.
 
The files are straight out of the camera. so thats not it.
I am not sure how you relink in AE. are you saying to export the proxy xml from fcp to ae as proxies. ie no r3d. and then link them in AE?

Paul
 
The files are straight out of the camera. so thats not it.
I am not sure how you relink in AE. are you saying to export the proxy xml from fcp to ae as proxies. ie no r3d. and then link them in AE?

Paul

yes that is what I am suggesting. If you have a lot of clips, it would be tedious but would get you over the hurdle. In the project window select your proxy clip and do a Cmd-H to "replace" the footage... it should show the proxy file in the dialog box, the .R3D would be adjacent in the same folder... select it and your clip is now relinked to the red raw.

Then if you want to toggle between .R3D and proxies... opt+cmd+p will allow you to retarget your proxies... then you have your choice of either.

Not as elegant as what Auto Duck 5.0 is supposed to do, but it should work.
 
Thanks Brandon. This could get me out of trouble, there isn't a large amount of clips to reconnect. I will try it out tomorrow morning.

Paul
 
If you export XML of a proxy edit from FCP using the built in XML export, then use Clipfinder to replace the proxies with R3Ds, you can then import that into After Effects using Automatic Duck Pro Import AE.

I just tested it and it worked, although I am still running After Effects CS4.
 
Brandon. Does this assemble the edit when brought into AE? or do I have to manually assemble the edit?
Paul
 
The method I just described assembles the edit for you in AE. No manual re-linking necessary.
 
Excellent! can't wait to try it. Might give it a go now! before going to bed.
Paul
 
Nick Just tried it it did replace all the files but the result is the same trim points incorrect. I must be doing something wrong in FCP
Paul
 
Good evening Paul...
To me that sounds like something with your Project settings isn't correct.
It must be a frame rate issue.
I had this once, when I broght R3Ds into AE they were at 30fps not 25.
Do check your Project and R3D settings in FC and AE to be what you want them to.
 
Hi Frank.

Just tried it again same result.
I export XML from FCP and import XML into AE but with the r3d file unchecked I get the correct edit in .mov files.
If I then go to replace footage with the red files it's all over the place.
Not sure what to do next

Paul
 
Back
Top