Audio extractor error

X2Pro version 3 (with MTS support) has just been released in the app store as a free upgrade

Thank you. It would be better if it was in the forum so that other users could find the details, but if you would prefer, an email would be okay and we could explain to others if they ask.

Graeme,

Yes, I'll take time to do that. Can I write privately via email about this ?

It's funny Chris knows Joe, I have been using Sadie since vers. 2 !!!!

Best wishes,

Fred

Good news!

I don't think we've had any contact with either company regarding X2Pro, though Chris (who has been in contact with you via email) used to work with Joe Bull, who founded SADiE.

Are you able to explain any steps that you took to get the AAF to open in SADiE, or did it just work?

I'll try to find some time to write up what I did to the FCPXML in case you or anybody else need to do it in the future.

Graeme,

We did it ! Good job sir !

The project is in Sadie !

Thank you so much for your help. I don't know what you did with the xml file but you did well.

AVTransfer is from Australia, Sadie from UK, it could make a difference ? ;-))

Best wishes,

Fred

The metadata options when exporting from FCP X have no effect on the AAF that X2Pro creates. I don't think you did anything wrong in X2Pro. It sounds like if AVTransfer is crashing then it's a problem with that software, I would suggest contacting the vendors of AVTransfer or opening the AAF in Pro Tools.

As well as working in Pro Tools, some people have also reported success opening the AAFs in Nuendo and Logic X, but they are not officially supported. I'm just mentioning it in case you happen to have access to them and want to try opening it.

Well, I tried to import with AVTransfer which is an application I use to convert files. It does not work ! AVTransfer crashes at the first sound.

I am actually using Sadie to convert audio files and I have to wait it's finished to import the AAF file. But AAF is not officially supported anymore by Sadie, so I don't know what's going to happen.

I exported the xml with extended option, I noticed there is also an audio option do you think it could change something ?

We didn't tag anything special in X2PRO, do you think we should have selected a particular option ?

Fred

That's great! We got there in the end...

We haven't tested X2Pro's AAFs against SADiE (we only officially support Pro Tools import), but it might work because X2Pro creates a valid AAF file. It depends on SADiE's AAF support on how well it will work. I would be interested to know if it is able to work with X2Pro's AAF.

Graeme,

We have the AAF file !!!!!

There was a M4a file X2PRO could not find but we didn't need it so we deleted it and regenerate a new XML.

Finally we have the AAF file.

I am now going to import it in Sadie 6....

I let you know...

Fred

You can find the auditions in the timeline index (see the left of the attached screenshot). Clickin on them in the index will jump to the place on the timeline. You can finalise them by ctrl+clicking or right clicking on the clip in the timeline (see popup menu in attached screenshot).

Graeme,

We don't find any audition on the timeline, and the function finalize audition is colored gray in the menu..... We are searching...
Fred

Yes. Hopefully that will work. Let me know if it does.

If you get errors about mts files again, attach your new fcpxml and I'll fix the paths again.

Graeme,

Just to be sure.

We are going to open the xml you sent in FCP in a new library isn't it ?

Then we process the auditions or we remove them.

Then we export again the XML

Then we go to X2PRO

Is that correct ?

Fred

That's a good sign.

Those auditions are preventing X2Pro from creating an AAF. All auditions in FCP X must be finalised before exporting the FCPXML. If you can get your client to finalize those 6 auditions then export his fcpxml again, I can edit the xml to point to the movs again and we can try again.

The notes on retiming, panning and noise reduction are just notes for the user that those effects have been discarded, so the sound engineer should be made aware when receiving the AAF.

I think, a big step is passed !!!!

BUT.....

Here are the messages.....