x2p can’t access media folder

[HesterCaroParticipant]

I have tried xml 1.10, 1.11 and 1.12 to create an AAF wirh x2pro. Are these still compatible? When I start the process to export to AAF I get the message that x2p can’t access one of the mediafolders due to sandboxing. After giving access to the folder, it still doesn’t continue to exporting.

Please help,

Thank you

Attachments:

You must be logged in to view attached files.

[HesterCaroParticipant]

Hi there,

I just upgraded to X2Pro5 and it still cannot access the same folder and keeps me from creating the AAF. I read the post from Annete, but I don’t understand what youa are saying about throwing away the library. This is urgent now.

Please help,

Thankk you.

Attachments:

You must be logged in to view attached files.

[HesterCaroParticipant]

Hi there,

I found out what the issue was: some files were pointing towards removed optimized media. I relinked them to the original media and that worked.
If the message in x2p was giving the proper info, I could have done it with x2p instead f buying the x2pro5, it’s only the 2nd time in 10 years that I used this…
But anyway. I got a message at the end saying that confrom rates hav enot been applied. What does that mean?

Attachments:

You must be logged in to view attached files.

[James CarrickKeymaster]

Dear Hester

Glad you resolved the issue, regarding X2Pro, and Sandboxing, we rely on reading the paths/bookmarks from the XML and attempting to then read these, you can depending on the version of OS, what rights and access were originally applied to folder, who and what last accessed it, issues with Sandboxing.

App security

Regarding conform rates FCP will fiddle the audio if its frame rate is slightly different from the projects rather than convert it. You cannot do that in ProTools or technically in the AAF, so we can state at what time a clip started and then you would need to make a decision on whether to apply an effect on the clip in ProTools, in the QA we state “A conformed clip is one that FCP has automatically re-timed because the frame rate of the clips was very close to the frame rate of the project. For example, when a 23.98fps clip is used in a 25fps project, FCP will play the clip at just over 104% speed. FCP does not alert the user when it conforms clips. X2Pro5 doesn’t support retiming or conforming, and clips will be at the original speed in the AAF. This is likely to cause a sync issue, so if any clips were retimed/conformed, the conversion report will list each one along with the time code where it appears in the project so that the audio finisher knows what to look for when they open the AAF.”

Hope the above helps

Yours Sincerely

James.

[Author]

Posts