michaelni changed the topic of #ffmpeg-devel to: Welcome to the FFmpeg development channel | Questions about using FFmpeg or developing with libav* libs should be asked in #ffmpeg | This channel is publicly logged | FFmpeg 7.1 has been released! | Please read ffmpeg.org/developer.html#Code-of-conduct
mkver has joined #ffmpeg-devel
<fflogger>
[editedticket] pross: Ticket #5581 ([avcodec] vp6: support decoding of interlaced video) updated https://trac.ffmpeg.org/ticket/5581
<fflogger>
[editedticket] pross: Ticket #5582 ([avcodec] vp5: support decoding of interlaced video) updated https://trac.ffmpeg.org/ticket/5582
<Lynne>
Invalid channel layout 1 channels (FL) for specified mapping family -1.
vipyne has quit [Ping timeout: 252 seconds]
\\Mr_C\\ has joined #ffmpeg-devel
vipyne has joined #ffmpeg-devel
<another|>
What about manually selecting family 0 or 1?
vipyne has quit [Ping timeout: 252 seconds]
Krowl has quit [Read error: Connection reset by peer]
mkver has quit [Ping timeout: 244 seconds]
<fflogger>
[newticket] goodbye: Ticket #11279 ([undetermined] Aspect ratio defined by the PNG resolution chunk “pHYs” is misinterpreted as its reciprocal) created https://trac.ffmpeg.org/ticket/11279
vipyne has joined #ffmpeg-devel
cone-833 has joined #ffmpeg-devel
<cone-833>
ffmpeg Zhao Zhili master:186402545802: fate/vvc: Add a sample which lose frames before 5c66a3
vipyne has quit [Ping timeout: 276 seconds]
mkver has joined #ffmpeg-devel
<Lynne>
another|: I don't select a family, -1 is afaik the default (255)
<fflogger>
[newticket] bernd_b: Ticket #11280 ([undetermined] Strange green flickering line added with a hevc_vaapi reencode) created https://trac.ffmpeg.org/ticket/11280
vipyne has quit [Ping timeout: 276 seconds]
<fflogger>
[editedticket] bernd_b: Ticket #11280 ([undetermined] Strange green flickering line added with a hevc_vaapi reencode) updated https://trac.ffmpeg.org/ticket/11280
<fflogger>
[editedticket] bernd_b: Ticket #11280 ([undetermined] Strange green flickering line added with a hevc_vaapi reencode) updated https://trac.ffmpeg.org/ticket/11280
<fflogger>
[editedticket] bernd_b: Ticket #11280 ([undetermined] Strange green flickering line added with a hevc_vaapi reencode) updated https://trac.ffmpeg.org/ticket/11280
rvalue- has joined #ffmpeg-devel
rvalue has quit [Ping timeout: 244 seconds]
vipyne has joined #ffmpeg-devel
Krowl has joined #ffmpeg-devel
rvalue- is now known as rvalue
vipyne has quit [Ping timeout: 260 seconds]
Workl has quit [Ping timeout: 244 seconds]
<fflogger>
[editedticket] Balling: Ticket #11279 ([avcodec] Aspect ratio defined by the PNG resolution chunk “pHYs” is misinterpreted as its reciprocal) updated https://trac.ffmpeg.org/ticket/11279
sebastian has joined #ffmpeg-devel
sebastian is now known as Guest309
Guest309 has quit [Client Quit]
cone-833 has quit [Quit: transmission timeout]
jamrial has joined #ffmpeg-devel
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 252 seconds]
System_Error has quit [Remote host closed the connection]
System_Error has joined #ffmpeg-devel
Krowl has quit [Read error: Connection reset by peer]
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 252 seconds]
Krowl has joined #ffmpeg-devel
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 248 seconds]
<elenril>
I accidentally most of my cash at a night market
<elenril>
is it dangerous?
Raz- has quit [Quit: Leaving]
<elenril>
jbennett1: does it hurt?
<fflogger>
[editedticket] MasterQuestionable: Ticket #11279 ([avcodec] Aspect ratio defined by the PNG resolution chunk “pHYs” is misinterpreted as its reciprocal) updated https://trac.ffmpeg.org/ticket/11279
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 260 seconds]
<fflogger>
[editedticket] Balling: Ticket #11279 ([avcodec] Aspect ratio defined by the PNG resolution chunk “pHYs” is misinterpreted as its reciprocal) updated https://trac.ffmpeg.org/ticket/11279
<elenril>
the spamming begins
vipyne has joined #ffmpeg-devel
<kasper93>
live feed from Balling also available on IRC now
<fflogger>
[editedticket] Balling: Ticket #9494 ([undetermined] Seeking in MPEG TS with copyts overflows for 13+ hours) updated https://trac.ffmpeg.org/ticket/9494
<fflogger>
[editedticket] Balling: Ticket #9468 ([avcodec] J2K is decoding rgb24 as bgr24 in native decoder) updated https://trac.ffmpeg.org/ticket/9468
lexano has joined #ffmpeg-devel
<fflogger>
[editedticket] goodbye: Ticket #11279 ([avcodec] Aspect ratio defined by the PNG resolution chunk “pHYs” is misinterpreted as its reciprocal) updated https://trac.ffmpeg.org/ticket/11279
<fflogger>
[editedticket] Balling: Ticket #11279 ([avcodec] Aspect ratio defined by the PNG resolution chunk “pHYs” is misinterpreted as its reciprocal) updated https://trac.ffmpeg.org/ticket/11279
<jamrial>
elenril: sure
<jamrial>
BtbN: imo, fflogger shouldn't post about ticket changes, only open and close
<jamrial>
it should email about ticket changes to participants
<BtbN>
That's up to each participant to set up
<BtbN>
Right now it posts about new and posting a comment
<jamrial>
yeah
<BtbN>
Problem is... the trac box does not exactly have a well setup mail server. So practically all its mails go straight to spam or get rejected
<jamrial>
then disable posting comments in fflogger, otherwise it will be too spammy here
<BtbN>
Doesn't that make it quite useless? I pretty much restored it to how it was in the old setup.
<jamrial>
mmh, maybe
<BtbN>
I looked at old logs from ZNC, and it posted _even more_ stuff
<BtbN>
Like, every "new CC" and so on. That seemed a bit excessive
<elenril>
I wouldn't want this channel to end up like #videolan
<BtbN>
What it doesn't actually post is "ticket closed", since I haven't found how trac notifies about that. And it also didn't seem thaaat useful of an info to post about
<BtbN>
While new ticket and new comment are the typical things people want to react to
<BtbN>
There's also the option of making it hyper-noisy, and parking it in its own channel. Then anyone who cares can get a live-feed of trac
<jamrial>
no, that'd be like screaming to the void
<BtbN>
On an unrelated note... wasn't Balling banned?
<elenril>
not on trac
<elenril>
and I'm sure there's an irc->twitter bridge
Workl4 has quit [Read error: Connection reset by peer]
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #ffmpeg-devel
<Marth64>
I feel like Balling comments are necessary entertainment
<fflogger>
[editedticket] Balling: Ticket #11131 ([ffmpeg] Nvenc b_ref_mode middle does not write max_num_reorder_frames == 2 in SPS) updated https://trac.ffmpeg.org/ticket/11131
<fflogger>
[editedticket] MasterQuestionable: Ticket #11279 ([avcodec] Aspect ratio defined by the PNG resolution chunk “pHYs” is misinterpreted as its reciprocal) updated https://trac.ffmpeg.org/ticket/11279
<fflogger>
[editedticket] Balling: Ticket #11279 ([avcodec] Aspect ratio defined by the PNG resolution chunk “pHYs” is misinterpreted as its reciprocal) updated https://trac.ffmpeg.org/ticket/11279
Krowl has joined #ffmpeg-devel
System_Error has quit [Remote host closed the connection]
witchymary has quit [Remote host closed the connection]
witchymary has joined #ffmpeg-devel
<fflogger>
[editedticket] Balling: Ticket #9291 ([undetermined] exact=1 crop filter for nv12-format video seems to swap color components (when specifying odd crop coordinates)) updated https://trac.ffmpeg.org/ticket/9291
System_Error has joined #ffmpeg-devel
Cheetahze has joined #ffmpeg-devel
Workl has joined #ffmpeg-devel
Workl6 has joined #ffmpeg-devel
Krowl has quit [Ping timeout: 272 seconds]
Workl has quit [Ping timeout: 276 seconds]
<fflogger>
[editedticket] goodbye: Ticket #11279 ([avcodec] Aspect ratio defined by the PNG resolution chunk “pHYs” is misinterpreted as its reciprocal) updated https://trac.ffmpeg.org/ticket/11279
<BtbN>
Do I read this right that x264, in a very roundabout way, effectively applies this logic to set the b_bitstream_restriction flag: gop_length != 1 || profile < HIGH ?
<BtbN>
Like, if b_constraint_set3 is set, and the profile is >=HIGH, is the only time it'd ever turn it off. Unless I'm missing something?
<BtbN>
And the only time b_constraint_set3 would be set while the profile is >=HIGH is if the keyint is == 1