James Carrick
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.
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.