No idea, I just compiled the code. When searching for my previous bug, counting of frames, I saw there were some comments in the changelog about code removal that touched x264 integration that caused regression problems. I supposed that's what caused my problem on 3.1.2 and 3.1.3 that wasn't there on 3.1.1 and HEAD.
FYI the previous bug: This command (I found the bug on another video, but here it is on this same one) ffprobe -v error -show_entries stream=nb_read_frames -count_frames -pretty 2708-1.m3u8 3.1.1 (expected answer) 67133 3.1.2 67283 3.1.3 67283 HEAD 67133 Anyways, this seeking bug is the opposite, fine on 3.1.3 but broken on 3.1.1 and HEAD. Louis On Tue, Sep 13, 2016 at 12:44 PM, Carl Eugen Hoyos <ceffm...@gmail.com> wrote: > 2016-09-13 18:15 GMT+02:00 Louis Letourneau <lletour...@gmail.com>: > > > FFMPEG 3.1.3 with ss 0 > > ffmpeg -y -loglevel error -ss 00:00:00 -vsync 0 -i 2708-1.m3u8 -f image2 > > -q:v 1 -vframes 1 dude.png ; feh dude.png > > > > Is the first frame > > > > FFMPEG HEAD with ss 0 > > ffmpeg -y -loglevel error -ss 00:00:00 -vsync 0 -i 2708-1.m3u8 -f image2 > > -q:v 1 -vframes 1 dude.png ; feh dude.png > > > > Is way off. > > Which change introduced this regression? > > Carl Eugen > _______________________________________________ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
