[Ffmpeg-devel-irc] ffmpeg-devel.log.20190617

[burek]

[09:37:23 CEST] <j-b> yo
[09:39:50 CEST] <durandal_1707> xo
[13:28:15 CEST] <cone-288> ffmpeg 03Gyan Doshi 07master:756dd9812028: doc/filters: correct typos in tinterlace flags
[15:58:29 CEST] <stuartm> nevcairiel: Thanks for the response.
[16:46:35 CEST] <mkver> jamrial: Thanks for reviewing my latest patchset. But does not answering to a patch imply a LGTM from you? (And how does it come that you are sometimes listed as op and sometimes not?)
[16:49:05 CEST] <jamrial> mkver: i don't always log in with nickserv
[16:50:50 CEST] <jamrial> and no, no reply doesn't imply lgtm
[17:19:59 CEST] <qacky> Maybe a dumb question but can anyone explain the logic behind the frame sequence check in fftools/ffmpeg.c::write_packet()?  The comment only notes audio encoders as a possible source but that isn't the case at all.  It's quite possible (and happens a lot), for networks to cause them too for example.  I have a local patch to remove the check because it causes studdering but it's not ideal.. which 
[17:20:05 CEST] <qacky> would be buffering for some short period and try to recover.
[17:20:35 CEST] <qacky> The packets aren't lost, just delayed and sometimes not even that, they are identical.
[00:00:00 CEST] --- Tue Jun 18 2019