-
Notifications
You must be signed in to change notification settings - Fork 506
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
Shaka DASH output doesn't pass conformance test with DASH validator #755
Comments
I also am seeing similar on dashif conformance: As of 2.4.2 release Im investigating playback issues relative to hevc based adapt sets, the avc based adapt sets play fine on all major ott players (roku exo). How ever Roku player does not like the hevc packaged content and wont start playback. Both the avc and the hevc source mp4s are encrypted and packaged with the below
Here are the produced manifests from the above. This might have to do with the fact that original content prior to being passed to packager command is or at one point was hevc mp4. I'm going to try some previous releases and see if I can get any to be liked by roku and also confirm that hevc in exo also doesn't work. to note both avc and the hevc adapt sets even the ones that DO play fine with roku have the same errors in dashif conformance like so - HEVC based adapt set error
AVC based adapt set error
Obviously only the I could have sworn in the past i've had no issue with it, obviously you are promoting vp9 and i know its not in the docs but maybe i just made an assumption? The dash that is generated though for the hevc based inputs is spec compliant so maybe that's why i never really second checked the support for hevc and shaka. Sorry if i hijacked this issue, @kqyang let me know if you think this should be moved to its own issue. (also that python snippet is what i was talking about and will post in our other issue regarding mpd_generator so folks maybe can use it as a starting point) |
@krzemienski Yes, please file a separate issue instead. It is related but your issue is likely not caused by the incompatibilities. |
Required by ISO/IEC 14496-14:2018 and ISO/IEC 23000-19:2018. Issue #755.
Part of #755 to improve DASH spec compliance.
This fixes warnings that 'isom' can only be a compatible instead of major brand. Issue #755.
System info
Operating System: Windows
Shaka Packager Version: 2.4.2
Issue and steps to reproduce the problem
ffmpeg -i firepit.mov -c copy firepit.mp4
Packager Command:
firepit.zip
.\packager-win.exe in=firepit.mp4,stream=audio,output=dash_audio.mp4 in=firepit.mp4,stream=video,output=dash_video.mp4 --mpd_output dash.mpd
[0423/115916:INFO:demuxer.cc(88)] Demuxer::Run() on file 'firepit.mp4'.
[0423/115916:INFO:demuxer.cc(160)] Initialize Demuxer for file 'firepit.mp4'.
[0423/115916:INFO:single_segment_segmenter.cc(107)] Update media header (moov) and rewrite the file to 'dash_video.mp4'.
[0423/115916:INFO:mp4_muxer.cc(177)] MP4 file 'dash_video.mp4' finalized.
[0423/115916:INFO:single_segment_segmenter.cc(107)] Update media header (moov) and rewrite the file to 'dash_audio.mp4'.
[0423/115917:INFO:mp4_muxer.cc(177)] MP4 file 'dash_audio.mp4' finalized.
Packaging completed successfully.
What is the expected result?
Valid DASH output
What happens instead?
Fails dash conformance at https://conformance.dashif.org/
See warnings and errors below for video log and audio log.
VIDEO LOG:
***Legend: Errors, Warnings, Information ***
Information:
ImageDescription name must be '0' not '10'
According to DASH-IF IOP Section 3.2.8 @Bandwidth of the Representation (17268150 bps) is set too high given the @minimumBufferTime (2 s), the minimum @Bandwidth value required to conform is 12970380 bps.
Warning: major brand ('isom') not also found in list of compatible brands
WARNING: In moov-1:meta-1 - unknown meta atom 'ID32'
Error: ftyp-1
The brand 'isom' can only be a compatible, not major, brand
AUDIO LOG:
***Legend: Errors, Warnings, Information ***
Information:
SoundDescription numChannels must be 2 not 1
Validate_ES_Descriptor: ES_ID should be 0 not 1 in media tracks
According to DASH-IF IOP Section 3.2.8 @Bandwidth of the Representation (81270 bps) is set too high given the @minimumBufferTime (2 s), the minimum @Bandwidth value required to conform is 60150 bps.
Warning: major brand ('isom') not also found in list of compatible brands
WARNING: In moov-1:trak-1:mdia-1:minf-1:stbl-1 - unknown sample table atom 'sgpd'
WARNING: In moov-1:meta-1 - unknown meta atom 'ID32'
error: ftyp-1
The brand 'isom' can only be a compatible, not major, brand
error (256 repetition\s) ### grouping_type roll in sbgp is not found for any sgpd in moof number 1
The text was updated successfully, but these errors were encountered: