[FFmpeg-user] RES: HLS - command line hls_segment_size creates problems in segments
Phantom Scripts
phantomscripts at hotmail.com
Sun Apr 7 20:26:13 EEST 2019
Sorry, I'm sending another email, but I still have not got an answer that has a solution.
I downloaded the GIT version today, and tested it with the same video, same command line, but the problem still continues.
I did not understand your answer, do I have to open a bug ticket?
Am I using the command in the wrong way? I'm forgetting something?
thank you.
________________________________
De: ffmpeg-user <ffmpeg-user-bounces at ffmpeg.org> em nome de Phantom Scripts <phantomscripts at hotmail.com>
Enviado: Saturday, April 6, 2019 11:16:15 AM
Para: FFmpeg user questions
Assunto: [FFmpeg-user] RES: RES: RES: HLS - command line hls_segment_size creates problems in segments
Hi, thanks for the reply again.
I did not quite understand your answer, the 'git builds' version was fix for this?
or do I have to open a bug ticket? (I tried to open a ticket, but the pages do not work)
De: Moritz Barsnick<mailto:barsnick at gmx.net>
Enviado:sexta-feira, 5 de abril de 2019 12:17
Para: FFmpeg user discussions<mailto:ffmpeg-user at ffmpeg.org>
Assunto: Re: [FFmpeg-user] RES: RES: HLS - command line hls_segment_size creates problems in segments
On Fri, Apr 05, 2019 at 11:36:29 +0000, Phantom Scripts wrote:
> I'm using this video:
> https://sample-videos.com/video123/mp4/720/big_buck_bunny_720p_30mb.mp4
[...]
> ffmpeg.exe -i SampleVideo_1280x720_30mb.mp4 -vcodec copy -acodec aac -hls_list_size 0 -hls_segment_size 2000000 -f hls SampleVideo_1280x720_30mb.m3u8
> - Console output:
> https://pastebin.com/B7tgTGp8
The only interesting bit here: One such message:
> [hls @ 00000155b4a9e280] Cannot use rename on non file protocol, this may lead to races and temporary partial files
> this time I used ffplay.exe, and this is the output of the console:
> https://pastebin.com/aSRnuyJF
The interesting bit here: A lot of errors when playing:
> [h264 @ 000001a348c3e1c0] error while decoding MB 6 23, bytestream -5
> [h264 @ 000001a348c3e1c0] concealing 1803 DC, 1803 AC, 1803 MV errors in P frame
and dozens others.
> sorry if I forgot to send you more details.
Thanks for all the details.
I can reproduce the encoding warning with 4.1, it's gone with relative
recent git master (probably fixed by commit c822d70).
I can reproduce the error log on decoding. So apparently, ffmpeg cannot
decode its own muxing successfully. Or it introduces errors while
muxing. This doesn't happen when muxing to mp4 or mpegts (for some
reason noticably slower than mp4).
We may need to open a bug ticket for this.
Thanks,
Moritz
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user at ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user at ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
More information about the ffmpeg-user
mailing list