[Dave Groenier]

Thanks, Dave.

Yeah, it’s just that I’ve used AutoDuck for years, and I like doing as much of the edit in my editing app before I get over to AE. I always had to reformat my titles after jumping over to AE but at least the text content was already there. Now I have to constantly refer back to my Premiere timeline to see which title this black solid represents, and then re-type it.
Ugh. I don’t ever really pre-produce things before I have a rough edit so that’s why I’m a little disappointed about this.

If anyone at Adobe is reading this, it’s time to upgrade the PP title tool. If AutoDuck could make it work with FCP/Avid over a decade ago, I think you guys should be able to do something.

[Dave Groenier]

Very cool. Thank you.

[Dave Groenier]

Dave,
Thanks for getting back to me so quick.
I thought the whole dynamic link thing was an integration of Automatic Duck, which works fine with FCP title tool.
Funny that it works well with arch nemesis Apple but not with sister apps. Or am I wrong on that?

Is there another way to input titles that will come across? It’s hard to time supers in AE where it’s a total pain to playback in RT. Maybe a third party titler?
Thanks again.

[Dave Groenier]

Sorry, I see Im on the wrong forum. Will re-post in After Effects forum.

[Dave Groenier]

Thanks again, Andy. Please bear with me. I can see and navigate to my disc so FAM driver is probably OK. Forget audio for now too.

Where do I tell Content Browser Exporter to do the mov to mxf conversion. There are no options for Content Browser in FCPX. When I open it as a stand alone app, all I see for settings is a checkbox to quit when finished. When I open a .mov media file in the stand alone app, it looks like it is set up to convert to mxf files to the XDCAM disc, but it grays out the ‘Clip’ folder on the disc where the clips should go. If I select the Disc itself as a destination it tells me the disc is write protected which it isn’t.

Content Browser has some settings for converting EX clips to mxf on import but nothing about destination file presets. But since Content Browser doesn’t appear to see any media files at all I don’t know what this software actually does. When I look at your screen shots in your previous post I’m seeing lots of options that don’t appear in my interface on FCPX. I’m running 10.0.9 which is apparently up to date according to my software check.

[Dave Groenier]

Thanks so much, Andy.
Still not having any luck though. I get an error saying that the file name is more than 31 characters (which it isn’t). Even if I assign a one character file name, it fails because “file could not be written” (no other explanation given). Can not find any settings for file naming conventions in either FCPX or Content Browser Exp. Besides I think the XDCAM deck does its own naming. Do I need some kind of FAM driver maybe? I thought I had it already but maybe needs an update with X.

Plus it still seems like it wants to create Quicktime instead of mxf. Also, what’s with no stereo? Do I need to split my audio track in two and pan them L/R and then do the export to two mono track?

Sorry to be such a whiner I really appreciate the feedback. 🙂

[Dave Groenier]

Thanks so much for the info. I don’t need the machine for anything other than offfline editing and exporting the mp4s from our Drift innovations cameras. Usually long timelapses and on-vehicle mounts.. Do I really need more RAM for just that?