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
MPD elements are not ordered based the <xs:sequence> of the DASH schema.
The results is that MPDs generated by this library are not passing the XML Schema validation
Is generating the following error when validating with DASH-MPD.xsd :
Element '{urn:mpeg:dash:schema:mpd:2011}AudioChannelConfiguration': This element is not expected. Expected is ( {urn:mpeg:dash:schema:mpd:2011}Representation ).
The text was updated successfully, but these errors were encountered:
This is correct, most players don't care.
However I'm using this project to manipulate and serialize MPDs, generated MPDs are passing through validators before going on production and they are rejected.
I'd be very happy if it can be fixed 👍
There is some initial support for this in HEAD. I don't currently have fully satisfactory test support in place (in part because many manifests in the wild don't appear to be valid), so please report and remaining problems.
I moved to the HEAD and I confirm that the generated MDPs are now valid against the schema .
However I'm using only a very limited subset of DASH, but I'll report if I see a problem.
MPD elements are not ordered based the
<xs:sequence>
of the DASH schema.The results is that MPDs generated by this library are not passing the XML Schema validation
For example, the following MPD Instance :
Is generating the following error when validating with DASH-MPD.xsd :
Element '{urn:mpeg:dash:schema:mpd:2011}AudioChannelConfiguration': This element is not expected. Expected is ( {urn:mpeg:dash:schema:mpd:2011}Representation ).
The text was updated successfully, but these errors were encountered: