-
Notifications
You must be signed in to change notification settings - Fork 54
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
Non-text Event child nodes not supported #23
Comments
In case it helps anyone, I solved it as follows in the application code. Note this only considers the
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Event
nodes may have child nodes that are not of type text. The 3rd edition of the DASH spec makes this clearer by adding themessageData
attribute for use when the event data is a string (see #20 for implementation of this)An example might be SCTE35 cues with schemeIdUri
urn:scte:scte35:2013:xml
orurn:scte:scte35:2014:xml+bin
, where the child node would be<Signal>
, with further children as required.The library does not currently support this - the Event content is always considered to be text for parsing and writing - causing data to be lost when transforming a manifest.
The text was updated successfully, but these errors were encountered: