Re: OpenTimelineIO meeting agenda 2019-10-03
toggle quoted messageShow quoted text
Here are my notes from today's meeting:
Joshua Minor (Pixar)
Stephan Steinbach (Pixar)
Nick Porcino (Pixar)
Eric Reinecke (Netflix)Michel Eid (Autodesk)
Eric Desruisseaux (Autodesk)
Josh Burnell (Dreamworks)
Sean Wallitsch (Dreamworks)
John Mertic (Linux Foundation)
Daniel Flehner Heen
- Documentation updated to emphasize use of "python setup.py install" instead of "pip install ." (setup.py is much faster & avoids some problems)
- Discussion about building Python wheels (Netflix to investigate)
- Dreamworks fixed plugin loading order to allow overriding built-in adapters.
- Accepted Dreamworks PR related to extracting UNC media paths
Universal Coordinate System
- General agreement that this is a good direction for OTIO to expand.
- Autodesk next step is a PR with schema additions for MediaReference bounds.
- We had some discussion about the long term expansion of OTIO into realms of spatial, color, audio, caption, animated effect data.
- Adding support for spatial effects leads to animated parameters, splines, etc. which begs the question of how much computer graphics math should go into OTIO to support calculating transformations etc.
- In the limit OTIO overlaps heavily with USD.
- There have been informal discussions about putting OTIO schema into USD.
- For now we're deferring this topic, but there is general interest in continuing that discussion longer term.
Rational Time v2
- Discussed pros/cons of using 64 vs 32 bit ints
- Nick raised a concern about mixing signed and unsigned ints in the numerator/denominator of the rate.
- We questioned why anyone would want a negative rate at all (perhaps playing backwards? but use case is dubious)
- There is agreement that RationalTime is really a representation of seconds, encoded ticks (value) with a specified temporal granularity (rate)
- We discussed possibly keeping the ticks (value) field of RationalTime as a double, and only switching the rate to an int/int rational.
- Next steps: Josh M to gather these points for further discussion and to post the proposal more publicly (not the current Google Doc)
- Stephan outlined the OTIOZ proposal PR
- OTIOZ is a zip-based bundle that holds an OTIO and the referenced media in one file.
- Example use cases:
- Converting to/from AAF with embedded media
- Handing off self-contained deliveries (similar to IMF or DCP) but with fewer constraints
- Adding support for this broadens the scope of OTIO and creates a desire for more file & media wrangling utilities (e.g. trimming media, copying media files, etc.)
- We discussed the need for more formal support for image sequences.
- Daniel, the author of this PR: https://github.com/PixarAnimationStudios/OpenTimelineIO/pull/536 had some audio difficulty, so we will discuss this further in a future meeting.
- Next steps: gather more feedback
Several of these topics deserve more significant discussion time than the current TSC meeting allows, so we may dedicate some future meetings (TSC or separate working meetings) to move these forwards. If you have suggestions about good process or mechanism for long distance working meetings, please let us know :)
Joshua Minor (he-him)
Pixar Studio Tools Story/Editorial/VR Previs Tech Lead