Skip to content
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

FCP X XML adapter #309

Merged
merged 11 commits into from
Oct 1, 2018
Merged

FCP X XML adapter #309

merged 11 commits into from
Oct 1, 2018

Conversation

eric-with-a-c
Copy link
Contributor

This is a basic adapter for working with FCP X XMLs. While this adapter will handle basic FCP X projects, including compound clips, it does not, at present, support markers or video clips that have detached audio.

ffprobe is required to create FCP X XMLs from an otio without errors on import. If ffprobe is not available or is not in the path, then an error will be displayed in FCP X when importing the XML. However, the timeline will still look an function properly in FCP X.

#37

@codecov-io
Copy link

codecov-io commented Aug 14, 2018

Codecov Report

Merging #309 into master will increase coverage by 0.11%.
The diff coverage is 92.47%.

Impacted file tree graph

@@           Coverage Diff            @@
##           master   #309      +/-   ##
========================================
+ Coverage   90.89%    91%   +0.11%     
========================================
  Files          53     55       +2     
  Lines        4512   4890     +378     
========================================
+ Hits         4101   4450     +349     
- Misses        411    440      +29
Impacted Files Coverage Δ
opentimelineio_contrib/adapters/fcpx_xml.py 92.19% <92.19%> (ø)
...lineio_contrib/adapters/tests/test_fcpx_adapter.py 96.15% <96.15%> (ø)
opentimelineio/plugins/manifest.py 90.47% <0%> (-2.03%) ⬇️
...neio_contrib/adapters/advanced_authoring_format.py 91.42% <0%> (+0.34%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6f15035...4a5efd8. Read the comment docs.

@jminor
Copy link
Collaborator

jminor commented Aug 14, 2018

Thanks @eric-with-a-c ! This is really helpful. We'll take a closer look when we get back from SIGGRAPH.

Copy link
Collaborator

@ssteinbach ssteinbach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few small things. We're also trying to find someone with a bit more FCPX experience to take a look, sorry this has taken a while to get around to.

opentimelineio_contrib/adapters/tests/test_fcpx_adapter.py Outdated Show resolved Hide resolved
opentimelineio_contrib/adapters/tests/test_fcpx_adapter.py Outdated Show resolved Hide resolved
opentimelineio_contrib/adapters/fcpx_xml.py Show resolved Hide resolved
@ssteinbach ssteinbach added this to the Public Beta 9 milestone Sep 7, 2018
@jminor
Copy link
Collaborator

jminor commented Sep 29, 2018

So we were able to track down an expert on the FCP X XML format. Here is a summary of their comments & advice:

  • Since an FCP library can contain multiple sequences, the adapter could use a SerializableCollection of Timelines to hold several of them in one file.
  • You might want to keep the event name in some metadata so you can reconstruct the organization if you round trip back to FCP.
  • Using the lane position to build tracks makes sense.

Regarding the format information:

  • It should be possible to include assets without a format, but you need to provide one for a sequence.
  • There is a default of 720p60 for assets without a format.

@eric-with-a-c
Copy link
Contributor Author

Thanks for the feedback!

I added the use of a SerializableCollection of Timelines to account for the possibility of having more than 1 sequence in an event. I also played around with adding another SerializableCollection of SerializableCollections since an FCP X Library can have multiple events, which can have multiple sequences. However, otioview didn't seem to like that level of nesting, so I left it out for now.

Presently the event name is being stored as the SerializableCollection's name and then the SerailizableCollection's name is used to set the event name when round tripping. But I could make it a piece of metadata if that's the preferred way of handling that. Let me know if you'd like it changed.

That's good to know about the formats. Since we still need a format for the sequence, it looks like there's still a dependency on ffprobe.

Let me know if there is anything else that needs to be adjusted before merging.

Thanks again!

@jminor jminor merged commit 59a60bb into AcademySoftwareFoundation:master Oct 1, 2018
@jminor
Copy link
Collaborator

jminor commented Oct 1, 2018

@eric-with-a-c, thanks for the contribution!

alatdneg pushed a commit to alatdneg/OpenTimelineIO that referenced this pull request Nov 13, 2018
@latenitefilms
Copy link

Amazing work @eric-with-a-c ! Thank you!!

@apetrynet
Copy link
Contributor

apetrynet commented Jan 9, 2023

Hi @eric-with-a-c!

Sorry for reaching out to you via this old PR. I'm not sure if you're on the ASWF slack(?).

I'm reaching out on the behalf of OpenTimelineIO as we're in the process of moving adapters out of the main OTIO repo and over to individual repos under OpenTimelineIO organisation. We're doing this as part of the v1.0 release plan.
Moving the adapters out of the core repo will ease maintenance/updates as they no longer are held back by the OTIO core release cycle.
Since you're the main author of the "fcpx_xml" I'd like to ask if you'd prefer hosting this adapter under another location or if we should move it over to the OTIO organisation together with the other adapters?

Please let me know what you think.
You can reach me directly on the ASWF slack under my real name or in the "opentimelineio" channel.

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

Successfully merging this pull request may close these issues.

6 participants