You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operating System: all Shaka Packager Version: latest
Issue and steps to reproduce the problem
Issue 1393 was created to address a problem with adaptation-set-switching using representationIDs instead of adaptationsetIDs. The fix has a problem with the --force_cl_index. If --force_cl_index=false is set, the manifest is correct.
Packager Command:
The problem becomes obvious with a large set of input files where the forced ordering makes a large difference. When used without --force_cl_index=false, the resulting manifest looks like this (grep "Adap|switching"):
// Iterate thru AdaptationSets and add them to one big Period element.
// Also force AdaptationSets Id to incremental order, which might not
// be the case if force_cl_index is used.
int idx = 0;
for (const auto& adaptation_set : adaptation_sets_) {
auto child = adaptation_set->GetXml();
if (!child || !child->SetId(idx++) || !period.AddChild(std::move(*child)))
return std::nullopt;
}
It's reseting the AdaptationSet id without updating the adaptation-set-switching SupplementalProperty during the MPD generation.
It feels unnecessary to me considering that the AdaptationSets have already been sorted in the beginning of the function (i.e. Period::GetXml).
unext-wendong
added a commit
to unext-wendong/shaka-packager
that referenced
this issue
Sep 11, 2024
System info
Operating System: all
Shaka Packager Version: latest
Issue and steps to reproduce the problem
Issue 1393 was created to address a problem with adaptation-set-switching using representationIDs instead of adaptationsetIDs. The fix has a problem with the --force_cl_index. If --force_cl_index=false is set, the manifest is correct.
Packager Command:
The problem becomes obvious with a large set of input files where the forced ordering makes a large difference. When used without --force_cl_index=false, the resulting manifest looks like this (grep "Adap|switching"):
What is the expected result?
When used with --force_cl_index=false, the correct manifest is created:
The text was updated successfully, but these errors were encountered: