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

Determine if multiple tracks are needed to meet requirements #18

Open
tdaede opened this issue Mar 7, 2022 · 2 comments
Open

Determine if multiple tracks are needed to meet requirements #18

tdaede opened this issue Mar 7, 2022 · 2 comments
Labels
missing feature New feature or request postpone

Comments

@tdaede
Copy link
Collaborator

tdaede commented Mar 7, 2022

With a single track, sending a subset of the audio to a client requires the audio track to be disassembled and reassembled. With multiple tracks, the client can select the tracks it needs. Determine if the single track implementation is enough to meet the requirements.

@sunghee-hwang
Copy link
Collaborator

Even with multi tracks, parsers need to get sample by sample of each track to form IA bitstream with a selected layer. A main difference is that timed metadata of a single track has the boundary information among layers while multi tracks has it as sample size info on each track.
Another option may be that file parsers output OBU streams with full layers, then OBU parsers output depacketized IA bitstream with the selected layer to the client.

@sunghee-hwang
Copy link
Collaborator

With a single track, sending a subset of the audio to a client requires the audio track to be disassembled and reassembled. With multiple tracks, the client can select the tracks it needs. Determine if the single track implementation is enough to meet the requirements.

As now we have an OBU for each Substream, the client can select Substreams it needs after parsing IA_Static_Meta.
So, the current single track meets both R-11 & R-12.

@tdaede tdaede added this to the tapas_v1 milestone Oct 4, 2022
@tdaede tdaede added the missing feature New feature or request label Oct 4, 2022
@tdaede tdaede removed this from the tapas_v1 milestone Oct 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
missing feature New feature or request postpone
Projects
None yet
Development

No branches or pull requests

2 participants