-
Notifications
You must be signed in to change notification settings - Fork 7
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
Switching set using single initialization constraints #43
Comments
To further clarify, to my understanding there are 3 initialisation switching use cases:
I believe our current switching set (ss1) test 8.5 addresses use case 3 (multiple initialization switching). Do we need to define additional switching set tests? |
To summarize, after further review I believe there are the following 5 cases: Single initialization:
Multiple initialization:
New tests and test content (switching sets) are needed to cover the different initialization constraints allowed for switching set playback (8.5). The current 8.5 test and test vectors used to form switching set ss1 (t19,t20,t23,t24,t25,t28,32,t34) cover what's referred to in the AVC test content sparse matrix as:
This matches with case 4 from the list referenced above:
So the current tests do not cover single initialization. I believe the next step is to confirm which of the 3 single initialization cases are relevant (based on input from MPEGGroup/CMAF#41 and any comments here). |
Currently we have tracks conforming to "general constraints" and to "single initialization constraints" as they are referred to in CMAF in clause 9.2.11. However, we only have a switching set that switches between tracks conforming to general constraints (for test 8.5 switching set playback).
Do we need a second switching set composed of tracks confirming to single initialization constraints (as defined in CMAF clause 9.2.11.4)?
For such a switching set, for AVC we only have tracks t2 and t15 to choose from currently.
It would seem appropriate to have tracks with different codec levels, as well as tracks with different resolutions and frame rates and bitrates. We could create variants of the tracks used for ss1 that conform to single initialization constraints (t19,t20,t23,t24,t25,t28,t32,t34).
Is this something we need to address?
The text was updated successfully, but these errors were encountered: