Packager fails to parse WebM from ffmpeg over udp #172
Comments
|
Is shaka-packager started after ffmpeg or before ffmpeg? If it is the former, can you try starting shaka-packager first? I think the problem is that ffmpeg only transmits the init-segment in the beginning of the stream; the init-segment contains the track information, which is necessary to setup the packaging. |
|
If I start the packager first I get
instead once the ffmpeg stream starts. |
|
I took a look at the output generated by ffmpeg. There were two tracks generated. However, the tracks element and the second track_entry element (for audio) indicate "unknown size".
Right now, shaka packager does not handle unknown sizes except for Segment element and Cluster element: https://github.com/google/shaka-packager/blob/master/packager/media/formats/webm/webm_parser.cc#L752. They are needed as the size of these elements would not be known in live streaming case. But I don't understand why ffmpeg generates unknown size for "tracks" and "track_entry" elements, which can be computed easily during encoding. An update is needed in either ffmpeg (to properly compute the size for tracks and track_entry elements) or shaka-packager (to support unknown size tracks / track_entry elements). If you remove the audio output from transcoding, it should work, i.e.
|
|
We should check if it is already fixed in ffmpeg. If not, we need to either fix the problem in ffmpeg or handle it in packager. |
|
So I ran this again. I used this copy of Sintel as input and ran these commands in parallel.
If I started the packager first, everything worked. If I started FFMPEG first I got:
I was using a debug local build of the packager based off our master branch and was using version 3.4.1-1 of FFMPEG. @kqyang, since it works as long as you start the packager first, are we comfortable closing this issue? |
|
Commit |
|
Yeah, I can reproduce this works with ffmpeg-3.4 if the packager is started before ffmpeg. |
Hi.
With the commands
and
The packager reports
The text was updated successfully, but these errors were encountered: