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
<fflogger>
[newticket] Wallboy: Ticket #11469 ([ffmpeg] ffmpeg_demux: readrate plays "catch up" if output is blocked, then later resumed) created https://trac.ffmpeg.org/ticket/11469
<Compn>
haasn, hah the comments are great. this must be good. thanks
<frankplow>
BtbN: I think the registration confirmation emails for the Forgejo aren't working. I've tried a couple of times and haven't received any confirmation mail. I checked my spam folder and mail provider's logs and it appears none was sent.
<BtbN>
It's simply not sending them for some people. I don't know why.
<BtbN>
Like, it's not even attempting it
<Riviera>
Reminds me of Twilio Sendgrid, if Forgejo uses something like that: Once a failed attempt (or whatever else) lands destination email addresses in blacklists with no further delivery attempts in the future, until somebody manually delists or some (long) timeout removes it.
IndecisiveTurtle has joined #ffmpeg-devel
<IndecisiveTurtle>
Lynne: Update ping just in case, pinged a few days ago about the vc2 vulkan commit for an extra review, I suspect my client could have swallowed it
<Lynne>
IndecisiveTurtle: no, it's just that you weren't on often after you sent it so I could reply
<IndecisiveTurtle>
Oh I see
<Lynne>
I just have minor notes
<Lynne>
do you need to change the type of put_bytes_count() to signed?
<Lynne>
other than that, the code looks pretty much perfect now
<IndecisiveTurtle>
It was mostly done to avoid shader complaining that it cant convert between uint and int, as my shader was using int
<IndecisiveTurtle>
I think when I tried to modify my shader to use uint it turned into a whack-a-mole
<Lynne>
ah
<Lynne>
as long as it doesn't break ffv1, should be fine
<Lynne>
how's the performance? do you need access to a big machine again?
<IndecisiveTurtle>
I didn't really benchmark it compared to the old BDA path, maybe should do so to update the commit message
<IndecisiveTurtle>
About the machine, I think it would be nice to some final validation for intel specifically cause I cant test it
MyNetAz has quit [Remote host closed the connection]
MyNetAz has joined #ffmpeg-devel
Tanay has quit [Ping timeout: 248 seconds]
<Lynne>
IndecisiveTurtle: you should have access again
<Lynne>
updated mesa and nvidia drivers
jamrial has joined #ffmpeg-devel
^Neo has joined #ffmpeg-devel
^Neo has quit [Changing host]
^Neo has joined #ffmpeg-devel
<fflogger>
[editedticket] Gyan: Ticket #11469 ([ffmpeg] ffmpeg_demux: readrate plays "catch up" if output is blocked, then later resumed) updated https://trac.ffmpeg.org/ticket/11469#comment:2
odrling has quit [Read error: Connection reset by peer]
odrling has joined #ffmpeg-devel
elvis_a_presley has quit [Quit: smoke-bomb ; grapple-hook]
elvis_a_presley has joined #ffmpeg-devel
<Lynne>
michaelni: added a prores vulkan decoder gsoc project
<michaelni>
Thanks!
rvalue- has joined #ffmpeg-devel
rvalue has quit [Ping timeout: 248 seconds]
rvalue- is now known as rvalue
<fflogger>
[newticket] pkoshevoy: Ticket #11470 ([avformat] get_eia608_packet misparses well formed files and corrupts Close Captions since 2020) created https://trac.ffmpeg.org/ticket/11470
HarshK23 has quit [Quit: Connection closed for inactivity]
<fflogger>
[newticket] johanseg: Ticket #11471 ([avformat] Integer wrap-around in oggparsevorbis.c vorbis_packet() final packet handling creating frames with very long duration) created https://trac.ffmpeg.org/ticket/11471