-
Notifications
You must be signed in to change notification settings - Fork 439
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
problems with webm support #823
Comments
I checked this sample, there are 2 issues here -
I created a quick hack for the second issue, and the video plays fine. A more elegant fix can probably be implemented quite easily, but considering the first issue and the fact MKV in general has been discontinued, I'm not sure it's worth the effort. |
First thank you for the quick reply. Could you propose how to (re)encode/mux the file in order for the current source to work? The fix, even the hack one, would be greatly appreciated as even though MKV might be discontinued, which I am not aware of, webm seems to be doing good for itself. |
Sorry, I meant 'discontinued in the context of this module', not the format as a whole :) |
Is there any update on the fix? |
Sorry for the delay, I now pushed the change that I wrote shortly after you opened this issue - #867 |
For me this fix did not change the returned playlist - I still get only around 3 seconds of playthrough. |
Hi @mstoykov, any news on this? Thanks. |
+1 |
I use tears of steel webm file as the test file (http://ftp.nluug.nl/pub/graphics/blender/demo/movies/ToS/tears_of_steel_1080p.webm) . Using it just like it is I get 404 and this in the logs
After some hours of trial and error I figured that the audio was the problem. Removing the audio yielded manifest with two segments with total length of 7 seconds although full 15 seconds were played by dash.js.
After some reencoding, looking up what was recommended around the issues and the web I used:
The
-t 30 -s 960x400
is to minimize the size of the encode time. With these options and practically anything else I tried with very little deviation (and not positive at that) I will get a manifest likewhich because of the single audio segment and it size will play for 3 seconds and stop, without the audio I would get the same behavior as before.
Also I hit #780, but because the size of the video I just raised the value of vod_max_frames_size to 1024m,
If I change the container to mp4 add
-strict -2
and change the audio codec to ac3, the generated manifest for the mp4 will be fine and playable (atleast for the 30 seconds, I am going to try the whole video soon)I suppose I am doing something wrong. But no changes in the way I encode or the whether I use mkv or webm yielded a playable dash manifest.
All the videos are playable from the same firefox I am testing the manifest, so they are not corrupted or something else that will make them unplayable
The text was updated successfully, but these errors were encountered: