[Solved] Video transcoding issues in 6.0 - 'hlsjs: Video...'
Posted: Tue May 10, 2016 6:14 amTL;DR: If you see the 'hlsjs: Video not properly encoded' error, edit your HTTP Live Streaming command to replace '-map 0:0 -map 0:1' with '-map 0:v:0 -map 0:a:0'
Hi all,
I've noticed transcoding issues with the new player on certain files, and I think I've tracked the issue down to a simple change that can be made to the HTTP Live Streaming command.
I re-ran the ffmpeg command I found in the logs for the video that wouldn't transcode, with verbosity increased. This is the command that should transcode 10 seconds of video, but I found that it would output nothing. After some analysis, it appears that this is because it attempts to transcode the first two streams in the file (-map 0:0 -map 0:1), which in this case are both subtitle tracks. Using a slightly different map syntax (-map 0:v:0 -map 0:a:0) should have the effect of mapping the first video and the first audio stream, which I assume is what was intended.
It seems that updating the HTTP Live Streaming command accordingly fixes the issue. I haven't done a ton of testing yet, but everything I've tried so far seems to work.
If you encounter this issue as well, please let me know whether or not the change worked for you.
Hi all,
I've noticed transcoding issues with the new player on certain files, and I think I've tracked the issue down to a simple change that can be made to the HTTP Live Streaming command.
I re-ran the ffmpeg command I found in the logs for the video that wouldn't transcode, with verbosity increased. This is the command that should transcode 10 seconds of video, but I found that it would output nothing. After some analysis, it appears that this is because it attempts to transcode the first two streams in the file (-map 0:0 -map 0:1), which in this case are both subtitle tracks. Using a slightly different map syntax (-map 0:v:0 -map 0:a:0) should have the effect of mapping the first video and the first audio stream, which I assume is what was intended.
It seems that updating the HTTP Live Streaming command accordingly fixes the issue. I haven't done a ton of testing yet, but everything I've tried so far seems to work.
If you encounter this issue as well, please let me know whether or not the change worked for you.