› Forums › X2Pro5 forum › Logic Pro export AAF
- This topic has 7 replies, 2 voices, and was last updated 2 days ago by James Carrick.
-
AuthorPosts
-
24/02/2025 at 5:43 pm #1104
Jan
ParticipantHi, I have problems to export aaf to Avid or DaVinci from Logic pro. Every time there are some mistakes, errors. Can anybody has experience to use X2P for export from Logic? I mean to export fcpxml file from logic and than use X2P to export to embedded aaf??? Thank You
25/02/2025 at 9:22 am #1105James Carrick
KeymasterDear Jan,
I believe what you are experiencing is the limitations in the implementation of AAF support in LogicPro. If you can forward a screen shot of an example in ProTools and what it looked like LogicPro and the AAF we can confirm.
Yours Sincerely
James
25/02/2025 at 11:48 am #1107Jan
ParticipantHi, It is a paradox, because when I export aaf from Logic to Protools, Everythings is ok. But When I export to Avid or DaVinci it is problem. So Is there a chance to export it with X2pro? (Sorry for my english 🙂
25/02/2025 at 12:14 pm #1108James Carrick
KeymasterHi Jan,
Apologies, I thought when you mentioned Avid that this was Avid’s ProTools. I think I should talk about AAF.
AAF was an open source “standard” but at some point many many years ago Avid restricted it. Even though Avid implement AAF with their MC’s, there are differences applied to how they read and create it between ProTools and the Media Composer world. When we wrote X2Pro originally it was to specifically create an AAF that was shall we say ProTools compliant. When we create an AAF for ProTools it can be read by Logic but Logic does not read all the information contained in the AAF as it does not read and translate it like ProTools. Our experience has been that when we create an AAF that is acceptable to ProTools it may not show all the information as detailed in the AAF when opened in Logic. We have looked at creating a version solely for creating Logic compatible AAF’s. If you want to create an AAF for ProTools then X2Pro5 will do this.Hope the above helps.
Yours Sincerely
James.
25/02/2025 at 12:46 pm #1109Jan
ParticipantHi James, thanks for the explanation. It’s a bit difficult for me because I like working in Logic Pro and I don’t really want to change it. Sometimes I send my work straight to Pro Tools, but sometimes I send it to the editing room in Avid or Davinci. The only way it works is that my work always goes through Protools and then it’s sent to the editing room. I was hoping that X2Pro would make it easier and cheaper for me 🙂 I guess I’ll have to find someone who uses it and try it out. Thanks
25/02/2025 at 1:25 pm #1110James Carrick
KeymasterHi Jan,
Can you push your project from Logic into FCPX ? If you can and it looks ok in FCPX then you could export it as an FCPXML and we could convert this to a ProTools compliant AAF.
Just a thought 🙂
Yours Sincerley
James
26/02/2025 at 11:24 am #1115Jan
ParticipantHi James, that’s exactly what I thought. But is there any chance to try it?
26/02/2025 at 11:32 am #1116James Carrick
KeymasterHi Jan,
I guess the options are you could send us the fcpxml from the project you imported into FCPX and we could create an AAF and compare to the project in FCPX. Alternatively you could just buy the App and if it does not work the way you want, just ask for a refund from the AppStore.
Yours sincerely
James.
-
AuthorPosts
- You must be logged in to reply to this topic.