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.1 has been released! | Please read ffmpeg.org/developer.html#Code-of-conduct
<BtbN>
lei convert has no support for v2 format output in the latest release
<ePirat>
I think I will be in for some fun because apparently the mbox file for one of the xiph lists has some errors in it leading to it to not properly tell when one mail ends and the other starts
<BtbN>
I found this random script in the ffmpeg-devel mbox dir: https://bpa.st/APNQ No idea what it does, but it was named fix.py, and is probably python2
<ePirat>
I found a mailman tools script which can supposedly fix it at some point just didnt get around to try it yet
<ePirat>
and given we soon need to migrate some things anyway, I might just wait till then
<BtbN>
I'm not sure if I should pull the trigger and migrate ffmpeg-devel/user and libav-user
<BtbN>
and cvslog
<ePirat>
maybe do the latter first as its less high impact and if it goes well, the other ones too?
<BtbN>
libav-user seems largely dead
<BtbN>
ffmpeg-user is somewhat alive
<ePirat>
I didnt know libav-user exists
<BtbN>
It's supposed to be cli-user-help and api user help
minimal has quit [Quit: Leaving]
<beastd>
libav-user is about using the libraries
<beastd>
the problem is that there are not enough developers and/or other users subscribed to help with the questions
<ePirat>
I find mailing lists for support to be annoying because they are not easily searchable so you get a lot of questions asked over and over again
<beastd>
after migration into public-inbox it will be directly searchable (for mailman2 pipermail archives search engines used to do a good job as well, but that can very.)
<BtbN>
well, both hyperkitty and public-inbox have a quite capable search
<beastd>
if some more devs could subscribe to libav-user it might help. especially with experience of using ffmpeg libs that could help. even just pointing the users to relevant docs or code bases could help.
<BtbN>
Well, I'll migrate both the -user lists now, and then we can subscribe and find out
<BtbN>
That is apparently a valid charset, but I have never seen it
kurosu has quit [Quit: Connection closed for inactivity]
<beastd>
ffmpeg-user is faring bettter then libav-user, in the former there is a little base regular ffmpeg users helping out and also some devs and paul do participate in helpful ways (even if paul's replies are as terse as usual)
srikanth has quit [Read error: Connection reset by peer]
<fjlogger>
[FFmpeg/FFmpeg] Issue #20309 opened: FFMpeg crashes or segfaults internally with this corrupted mpeg video.... but only if hwaccel=d3d11va (https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/20309) by signumnova
<beastd>
for users jumping over the hoops and their own pride (sometimes) asking questions on libav-user, it currently feels like "asking into an empty chamber". so anyone helping to overcome this would help ffmpeg a lot. it might also help to see the weak points in our examples, api and docs