problem with ProTools 10

Hello, and sorry for the late reply.
I couldn't get feedback anymore from my sound team, so I couldn't develop more.

But, I ran into the same problem again. Once again, AAF from X2Pro and import into ProTools 10. On the first import, the timeline was off, some sounds where missing, others out of sync.
This time, the trick to get it right was to set the media option to "Copy from source media". With this option enabled, the timeline imported as expected.
I'll attach a screenshot so that you can see how the import windows was set (mainly in spanish, though).
Hope this help others with the same issue to get a proper import in ProTools 10. I'll post more feedback if I run in the problem again.

The Audio Sample Rate is set as the file is imported into Pro Tools.
I loaded your project into my Pro Tools version 11 and it imported as your Good Photo looks.

I did look again and the project name at the top of the pro tools window looks tobe different in the BAD photo (the PT 10 picture).

Have you had any success re-importing the project in PT10 with the Sample Rate set to 48 kHz and the SRC turned off, or have you tried it again?
I do not see any problem and do not expect to see any difference between the 2 with the same project.

Let us know and many thanks.

AAF and FCPXML uploaded per FTP: I hope I did it right...

As you brought my attention on the SRC issue, I noticed something. The FCP project is at 48.000 Khz, yet ProTools 10 recognises it at 44.100 Khz and ask for a conform... Maybe we have a metadata issue, or there is an option on export (either FCPX or X2PRO) that I don't know about, that messed up the sound frequency rate?

I will email you our FTP details.

Thank you for your reply.
I am still waiting on the sound editors comment, be sure I'll let you know as soon as I receive it.
In the meantime, I would gladly send you the FCPXML and corresponding AAF, but as I said in a previous post, I'd rather do it via a non-public mean. It is not ultra confidential, but it is advertising and I'd prefer not to publish the "work in progress" publicly. How could we do that?

I would be interested in your Sound editors comment and the results of the last test.
The reason i said that it appeared to be 2 different AAFs that were imported, is that the number of tracks is not the same and the role of the different tracks is not the same.

If you are still having problems with this in PT 10, we would like to get the FCPXML that you used to convert and the AAF that was outputted.

Please let us know how you have progressed.

Well, I believe it is actually the same AAF imported on 2 different versions of protools (you can actually see that the clips have the same name). The "bad" one would be protools 10, the "good" one protools 12. The problem is precisely that it imported wrongly in the protools 10, and I had to find a protools 12 for import and then transfer the session...
I'll ask them to make an import without SRC and come back to you.
Thank you!

I cannot entirely tell what you are trying to show me here, because it does not appear to be the same project that is imported into both Pro Tools versions.
One thing i can see is that you are using SRC (Standard Rates Conversion) on import on the one you label as bad.
This can cause sync issues with Pro Tools, but it converts all of the clip rates to the same rate, which can make clips become longer or shorter than they originally were and are meant to be.

Try your import without SRC enabled and see if that looks any better.

Hello,
sorry for the late reply, but I finally can give you the screenshots you are asking for.
I hope this helps understand what is going on. (I am editor, not sound designer, so my understanding of the matter is limited). If you want, I could also get you the AAF and FCPXML, although I'd rather do it per private mail.
Regards

The bad one


Import settings for the bad one



The good one

X2Pro is not developed for any specific version of Pro Tools, and we certainly would expect there to be any problem with importing the AAF in different versions of Pro Tools.
There may be some import settings that are different in the various versions of Pro Tools, buit that does affect the AAF that is created, only how it is imported into the different Pro Tools sessions.

Would you be able to give some specific examples (screen captures) of the problems you are talking about with Pro Tools 10 that you did not see with PT 12?
Also, please include some screen captures of your import settings when you import the AAF into PT.

Many thanks.

Hello X2Pro team!
I am very happy with X2Pro, but I ran into a small problem.
The process of creating the AAF went flawlessly, but when the sound department tried to open the AAF, everything went wrong: the timelines duration had change, the clips were truncated... After a bit of investigation, we came to the conclusion that the AAF didn't communicate well with ProTools 10. We opened it in ProTools 12, everything was OK, and from there exported the session, reimported in ProTools 10, and that went well.
It seems that here in Spain, many sound editors are still working on ProTools 10, is there any hope that the problem could be fixed?
Thanks in advance!

PS: couldn't find the issue in other forum posts, sorry if I am asking something that was already answered...