Closed cars10 closed 2 years ago
This sounds like an ffmpeg issue to me and not like a dash.js issue. Can you check the behavior in Shaka player please as well: https://shaka-player-demo.appspot.com/ . If it shows the same behavior it is very unlikely that this is a player issue.
Thanks, i can reproduce the issue with shaka. I will open an issue in the ffmpeg bugtracker and link it here.
FFMPEG issue: https://trac.ffmpeg.org/ticket/9701#ticket
Hey @cars10 . Did you get to workaround that issue?
Unfortunately no. We are still using 4.2.2 because of this issue. Do you have the same problem?
Yeah, I do. The original manifest files that you linked in the ffmpeg bug tracker have minimal differences (e.g. few attributes and a different segment duration). I was wondering if you ever got to try to find if removing some of the differences will fix the problem (or maybe the problem is in reencoded files itself)
Looks like SegmentList.duration
that ffmpeg produces in the manifest is 4.3 is no longer valid and is just some 5000000
upd. nevermind. the problem was that I used -use_template 1
while using -single_file_name
Environment
Steps to reproduce
Observed behavior
FFMPEG <= 4.2.2 works as expected. You can skip to an unbuffered part, dashjs loads the video, and starts playing.
FFMPEG > 4.2.2 does not work. It does not load the needed parts and play/pause do not work. The videos is broken until you reload the player. You can only skip to buffered parts of the video.
Console output
I think the specific issue is:
Expected behavior
The player should load the video correctly, as it does when the file is generated with ffmpeg <= 4.2.2
I have tested multiple versions of ffmpeg (4.3, 4.4, etc) and i can reproduce the issue with every version > 4.2.2. The last working version for this setup is 4.2.2. I have also tested multiple videos from different sources.
It is irrelevant which version of ffmpeg you use to create the 480p and 720p files, only the last step (dash manifest creation) matters.