Skip to content

FCPXML v1.11 doesn't support Soundtracks #94

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
latenitefilms opened this issue May 28, 2023 · 1 comment
Open

FCPXML v1.11 doesn't support Soundtracks #94

latenitefilms opened this issue May 28, 2023 · 1 comment

Comments

@latenitefilms
Copy link
Contributor

latenitefilms commented May 28, 2023

Apple Feedback Assistant ID: FB12209024

If you export a project from Final Cut Pro on iPad to Final Cut Pro on Mac that contains Soundtracks, whilst the Soundtracks will work correctly in Final Cut Pro 10.6.6 on Mac - if you export a FCPXML v1.11, the Soundtracks simply do not export, even though, they're just regular audio files on the file-system level.

Originally reported on Twitter:

FCPX for iPad Limitation >> When importing a Soundtrack from iPad to Mac, a trimmed m4a comes across. However, the Soundtrack file doesn't appear in FCPXML, so you can't send to Resolve. It's actually a FFAnchoredFlexMusicObject - which FCPXML doesn't support.

image

image

@latenitefilms
Copy link
Contributor Author

Apple responded on 14th Sept with the following:

Engineering has provided the following information regarding this issue:

To summarize the steps to repro:

  1. Export an FCP iPad project into a .fcpproj file.
  2. Bring that .fcpproj file onto a MacOS machine.
  3. Do secondary click on the file and select Show Package Contents.
  4. Traverse down a couple folders and find the .fcpbundle in it.
  5. Open the .fcpbundle with FCPX MacOS.

This is not a supported workflow. Users should not be diving into their project bundles. Instead, these bundles should be imported into FCP macOS via the import option inside of the app.

However their comments don't make a lot of sense, because it is a supported workflow to go from iPad to Mac. Will need to do more testing with the latest FCPX updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant