AcademySoftwareFoundation / AcademySoftwareFoundation/OpenTimelineIO
Nested sequences cause unnecessary massive duplication of data
- Dominant language
- C++
- Stars
- 2k
- Forks
- 351
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 1
Description
I've seen insanely large .otio files because every nested clip also includes the same duplicate nested sequence data.
Is there any plan to deal with nested clips by using references to sequence data only included once (like happens in XML formats)?
NLEs also use nested sequences for other purposes (apart from compound clips) such as multicam but there needs to be a way to indicate the which part of the sequence is actually used in the edit by that clip i.e. the select angle and audio tracks.
Can we update the standard to better reflect the common purposes of nested clips?
Contributor guide
Research direction
Start by reviewing OpenTimelineIO's treatment of nested clips and the duplicated nested sequence data described here. Compare the requested reference model with multicam needs, including selected angles and audio tracks. Done means an agreed specification for representing shared sequence data and the portion used by each nested clip.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100