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

Add Chunked or Segmented file reference #924

Open
reinecke opened this issue Mar 25, 2021 · 1 comment
Open

Add Chunked or Segmented file reference #924

reinecke opened this issue Mar 25, 2021 · 1 comment

Comments

@reinecke
Copy link
Collaborator

Feature Request

It would be useful to have a type of MediaReference that refers to a contiguous clip that has been "chunked" or "segmented" out over multiple files.

Description

Much like an ImageSequenceReference(#69) there is a similar kind of single conceptual asset that can be spread over multiple files but rather than containing a single sample (frame) from that file, they contain a subset of the samples that make up the source. These are typically referred to as "chunked" or "segmented" files.

Some common example cases where these may come up include:

  • Camera files recorded by RED cameras in both R3D and mov formats
  • Files used in streaming in either fragmented mp4 or .ts files

In most cases, this is done to work around file size limitations. Many software packages (like Nuke) have the user point to the first file in the sequence and then implicitly discover the other files in the sequence. It would be nice for OpenTimelineIO to represent this more explicitly to aid in detecting cases where perhaps the last file in a sequence is missing and the clip may be truncated as a result.

#630 is related to this, but it's a bit more targeted at bundling together alternate media references, this would be focussed on media on-disk that is meant to be concatenated to form the full contiguous source.

@apetrynet
Copy link
Contributor

Support for these chunked files would be very useful for archiving/packaging timelines with the otioz adapter for instance.

I'll copy one of my initial ideas from slack discussion in here for future reference.

Each chunk or R3D file for instance would have it's own media ref and they all wrap together in a "container ref". That container ref can then tackle providing the correct file segment corresponding to time. Similar to ImageSequenceReference.target_url_for_image_number()

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

No branches or pull requests

3 participants