Logic Pro X or X2Pro for OMF/AAF Export

Thanks again guys. Will let you know how I fare.

This is a straight doco so no crazy fx. I might just bake the ones I have done just to make sure.

Cheers!

I was considering XtoPro but am Logic Based, not Protools. I wasn't 100% sure if it was also suitable for exporting to Logic. Does anyone here successfully use a XtoPro -> Logic Pro X workflow?

Doug Suiter wrote: I was considering XtoPro but am Logic Based, not Protools. I wasn't 100% sure if it was also suitable for exporting to Logic. Does anyone here successfully use a XtoPro -> Logic Pro X workflow?

Don't do it as workflow, but have made a few X2Pro aaf's to open and tweakin Logic. It works really well.

Thanks plysat.

I found this on the X2pro forums along with people saying that it does work with logic:

"X2Pro is designed to create an AAF for Pro Tools. It does work with some other devices (Nuendo and Pyramix) but this is because they implement AAF the same way that Pro Tools does. Essentially we are creating an AAF that is specifically Pro Tools friendly, if it works with other devices then that is good, but it is not what the software was designed to do."

The link is here:

www.x2pro.net/Search.html?childforums=1&q=logic

Doug Suiter wrote: Thanks plysat.

I found this on the X2pro forums along with people saying that it does work with logic:

"X2Pro is designed to create an AAF for Pro Tools. It does work with some other devices (Nuendo and Pyramix) but this is because they implement AAF the same way that Pro Tools does. Essentially we are creating an AAF that is specifically Pro Tools friendly, if it works with other devices then that is good, but it is not what the software was designed to do."

The link is here:

www.x2pro.net/Search.html?childforums=1&q=logic

They're covering their asses i think.
In the interest of full disclosure, I did have a problem with Logic X and an X2Pro aaf around the the time 10.1 came out, and I honestly haven't tried it since. I did report it to both Apple and Marquis, so it may be fine now. Maybe someone who's done it recently can chime in....

I'd like to think Apple has this covered and integration will be forthcoming but since I don't how long I'll be waiting, I might have to spend the $$ on X2Pro for the sake of a project I am working on now. Waiting for Apple is not a game I enjoy. A year and a half ago I told my GF to not buy a Cinema Display because it seemed like are refresh was overdue and the USB connection were still only USB2. 18 months later... I also suggested to her that Aperture would likely be updated around the release of the New Mac Pros (she's a photographer considering Lightroom. I'd better stop making predictions I think

The XML import from FCPX to Logic is not working yet. It does work to go from an XtoPro AAF pretty well. I haven't looked at it extensively.

I don't think Apple will be adding AAF functionality directly to FCPX. They may fix the XML to Logic, but it makes sense to let a third party dev handle the complex features that 90% of users will never need. Plus, Apple gets 30% just for selling it via the app store.

The third party devs like the 7toX developers can generate fixes whenever they need to. (and do very often, I wonder if they sleep!)

I remember when something would break in legacy FCP and you'd have to wait weeks or months until it was addressed by an update. Having pro level time critical functionality handled by third party developers makes sense.

I don't think Apple will be adding AAF functionality directly to FCPX. They may fix the XML to Logic, but it makes sense to let a third party dev handle the complex features that 90% of users will never need. Plus, Apple gets 30% just for selling it via the app store.

I can see your point...on the other hand if I was developer I would be seriously cautious of creating an app that Apple may well make a baked in feature in a future release without warning. It makes sense to develop an app that takes FCPX to ProTools, because Apple aren't going to address that anytime soon, but it makes less sense to develop an app that bridges two Apple Pro apps.

That's the whole conundrum right there.

I bet these developers have some sort of agreement where they won't make their apps obsolete. This is an educated guess, but the exporting and timeline translation features have always been the most cantankerous to keep up with. If Apple can hand those tasks off to others to deal with, and turn a nice profit on the sales of those apps, from a business standpoint it wouldn't make sense to kill that off.

Notice none of the key apps are available without going through the app store?

I don't remember where I read this, but I believe that a rep from Apple has strongly implied that they won't be adding AAF export, not soon if ever.

Truth be told, this omission as well as a few others (similarly like EDLs and a lack of tape support) irked me initially, but I've come to see them as making a lot of sense. For the 90% of people who don't need them, it's extra complexity that could add to the cost of the total package. If you do need them, it's a modular approach where you can get only the ones you need, and it still ends up cheaper than FCP legacy. The other big advantage is the aforementioned development time, where any bugs/features in these modules can be addressed rather quickly compared to Apple's pace.

I don't specifically want AAF export. I just want anything that can get me to Logic and back without having to bake in what has been done on the timeline.

Doug Suiter wrote: I don't specifically want AAF export. I just want anything that can get me to Logic and back without having to bake in what has been done on the timeline.

Honestly, I'd bitch at the Logic folks, there's a feedback link in the app. I've been using it. FCP X is now pretty much including all the needed info in XML, Logic just needs to use it...

Rather than give feedback to the LPX team or the FCPX I think it would make more sense to give feedback to the ProApps team or whoever it is that co-ordinates the bigger picture.

Doug Suiter wrote: Rather than give feedback to the LPX team or the FCPX I think it would make more sense to give feedback to the ProApps team or whoever it is that co-ordinates the bigger picture.

Very true, and I'm sure that's been done. But the more noise coming at them the better.

I'll be sure to add my voice to the chorus Any idea how to give feedback to the ProApps team generally (Rather than app specific)?

Doug Suiter wrote: I'll be sure to add my voice to the chorus Any idea how to give feedback to the ProApps team generally (Rather than app specific)?

I dunno... google "Apple Pro Apps head" And email them? Or send an email to Tim Cook? I've done that... no response though... lol

Doug Suiter wrote: I don't specifically want AAF export. I just want anything that can get me to Logic and back without having to bake in what has been done on the timeline.

Well, then Apple probably considers this a different issue. It's really a shame that exporting to Logic doesn't work well at launch, but I believe that's where it's heading. It's only a question of when... and in fact if we actually get round-tripping that would be ideal. We don't even have send to Motion yet, so who knows when?

However, as things are right now, almost all post sound happens in Pro Tools, and that works today. I honestly don't now of any sound houses using Logic for video work, but I'm sure they're out there. I don't know if Logic takes AAF ok, but I've heard it's fine.

I don't know of any post houses using Logic either - but I do in my own workflow.

Feedback has been sent to Apple.

Is it working all good if i use compound clips and sometimes the cam mic as well? Do I have to do any specifications when exporting the xml first? thanks a lot in advance.

It does work, and you can arrange the track order of the roles on the side panel.