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
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 265 seconds]
thilo_ has quit [Ping timeout: 260 seconds]
vipyne has joined #ffmpeg-devel
thilo_ has joined #ffmpeg-devel
mkver has quit [Ping timeout: 252 seconds]
vipyne has quit [Ping timeout: 248 seconds]
b50d has quit [Ping timeout: 265 seconds]
b50d has joined #ffmpeg-devel
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 252 seconds]
vipyne has joined #ffmpeg-devel
vipyne_ has joined #ffmpeg-devel
b50d has quit [Remote host closed the connection]
vipyne has quit [Quit: Leaving.]
vipyne_ has quit [Ping timeout: 264 seconds]
cone-954 has quit [Quit: transmission timeout]
haihao has quit [Remote host closed the connection]
arch1t3cht4 has joined #ffmpeg-devel
haihao has joined #ffmpeg-devel
arch1t3cht has quit [Ping timeout: 246 seconds]
arch1t3cht4 is now known as arch1t3cht
sgm has quit [Ping timeout: 260 seconds]
sgm has joined #ffmpeg-devel
Marth64 has quit [Quit: Leaving]
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 244 seconds]
jamrial has quit []
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 248 seconds]
Martchus_ has joined #ffmpeg-devel
Martchus has quit [Ping timeout: 252 seconds]
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 244 seconds]
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 248 seconds]
vipyne has joined #ffmpeg-devel
rvalue has quit [Ping timeout: 252 seconds]
vipyne has quit [Ping timeout: 252 seconds]
rvalue has joined #ffmpeg-devel
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 255 seconds]
IndecisiveTurtle has joined #ffmpeg-devel
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 252 seconds]
IndecisiveTurtle has quit [Ping timeout: 265 seconds]
HarshK23 has joined #ffmpeg-devel
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 252 seconds]
feiw1 has quit [Ping timeout: 276 seconds]
feiw1 has joined #ffmpeg-devel
darkapex has joined #ffmpeg-devel
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 252 seconds]
mkver has joined #ffmpeg-devel
ngaullier has joined #ffmpeg-devel
ngaullier has quit [Client Quit]
Krowl has joined #ffmpeg-devel
vipyne has joined #ffmpeg-devel
ngaullier has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 265 seconds]
vipyne has joined #ffmpeg-devel
Krowl has quit [Read error: Connection reset by peer]
vipyne has quit [Ping timeout: 245 seconds]
feiw1 has quit [Ping timeout: 252 seconds]
feiw1 has joined #ffmpeg-devel
___nick___ has joined #ffmpeg-devel
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 248 seconds]
Krowl has joined #ffmpeg-devel
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 252 seconds]
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 252 seconds]
tufei_ has joined #ffmpeg-devel
tufei has quit [Ping timeout: 260 seconds]
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 248 seconds]
<haasn>
is it sane to reject interlaced frames with odd height?
<haasn>
or is that something we should go out of our way to support?
<Lynne>
it sadly isn't, users may crop for whatever odd reasons
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 265 seconds]
<haasn>
okay, not too hard to support
Krowl has quit [Read error: Connection reset by peer]
<Lynne>
you're adding interlaced-aware scaling?
<haasn>
no
<haasn>
just scaling each field independently
<Lynne>
yeah, that's what I meant
<Lynne>
sws didn't do this before, didn't it?
<haasn>
correct
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 264 seconds]
System_Error has quit [Remote host closed the connection]
System_Error has joined #ffmpeg-devel
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 272 seconds]
jamrial has joined #ffmpeg-devel
Krowl has joined #ffmpeg-devel
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 252 seconds]
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 260 seconds]
Krowl has quit [Read error: Connection reset by peer]
vipyne has joined #ffmpeg-devel
vipyne has quit [Ping timeout: 252 seconds]
cone-474 has joined #ffmpeg-devel
<cone-474>
ffmpeg James Almer master:667e22e85dcd: avfilter/vsdc_testsrc: simplify yuvtest_fill_picture
<cone-474>
ffmpeg James Almer master:f2853002dd33: avfilter/vsrc_testsrc: add support for packed YUV formats in yuvtestsrc
<cone-474>
ffmpeg James Almer master:4f0514df62a6: fate/filter-video: add tests for packed YUV in yuvtestsrc
<kasper93>
it is ossfuzz build for mpv, everything is disabled, except two sources used. --disable-filters --enable-filter={sine,yuvtestsrc}
<beastd>
I actually like those tests. We should also be doing those in FATE. IIRC mans actually implemented sth like that to be used in e.g. some fate instances.
ccawley2011 has joined #ffmpeg-devel
<beastd>
ah yeah it was --enable-random for configure. not sure any fate clients use it ATM
kasper93_ has joined #ffmpeg-devel
kasper93 has quit [Ping timeout: 276 seconds]
Krowl has quit [Read error: Connection reset by peer]
dukesook has joined #ffmpeg-devel
<dukesook>
What are the PGP Signatures that are attached to the ffmpeg emails?
<Marth64>
signature of email sender authenticity basically
<Marth64>
search pgp or gpg to learn morre
dukesook has quit [Quit: Client closed]
Krowl has joined #ffmpeg-devel
ngaullier has quit [Ping timeout: 255 seconds]
<beastd>
Anyone also experiencing FATE failures with zlib-ng? Guess it is not producing bit by bit indentical output compared to original zlib
<ePirat>
sb, reply to the initial mail with "Ping for review" or so
<sb>
Okey, great, ty
Kei_N_ has joined #ffmpeg-devel
Kei_N has quit [Ping timeout: 252 seconds]
<sb>
Damn, seems I deleted that mail accidentally when cleaning up my inbox from all the mails sent from ffmpeg-devel. Can I reply via https://patchwork.ffmpeg.org web interface instead? I forgot my password to that site though, and password resent seems broken, or really slow?
<llyyr>
patchwork can't send mails to gmail
<llyyr>
it's broken and known and nobody really cares
mkver has quit [Ping timeout: 248 seconds]
<Marth64>
it works for me
<Marth64>
but i use git send-email with it
<sb>
Okey, thank you, I'll figure something else out. I had a feeling my patch was not that interesting anyway :D
<BtbN>
llyyr: it can't be fixed. Google has absolutely insane requirements to deem you worthy of sending mail to them
<BtbN>
if you're not another big ISP or something, you got almost no chance
<llyyr>
how does fd.o or videolan's gitlab instance manage to send emails?
<llyyr>
I receive them on gmail
<BtbN>
The ML also manages it. My own personal mail server as well. At least for me it was multiple days of work, very intricate config, and multiple month of trying to reach out to them
<BtbN>
But that was years ago
<BtbN>
So it's kinda grandfathered in.
<BtbN>
Most people solve it by paying mailgun or some other service
<llyyr>
I heard from hanging around in fd.o channels that you need to configure DMARC, DKIM and SPF for gmail to receive your emails
System_Error has quit [Remote host closed the connection]
<BtbN>
That's the very minimum. Your IP also needs to be "in good standing" and you need to verify it to Google as you owning it, and sign up with them and a bunch of shenangans
System_Error has joined #ffmpeg-devel
<beastd>
llyyr: About your patch for metadata in chained ogg for flac. Why is your solution different from the one in oggparsevorbis.c ? Not saying better or worse, just curious because I don't understand why it should be much different.
<beastd>
Also it seems to be a disadvantage of ogg container or our implementation if we need to dup this for every codec
sb has quit [Quit: Leaving]
<llyyr>
beastd: it is not my patch, but I can look into why it needs to be duplicated
___nick___ has quit [Ping timeout: 252 seconds]
<llyyr>
please reply to the mail instead so the original author sees your comments
<vipyne1>
what's the joke about the FF in FFmpeg standing for something Febreze ?
<beastd>
llyyr: ah sorry. i didn't know it's not your patch. ok will try to reply to the original message then.
iive has joined #ffmpeg-devel
<michaelni>
ramiro, your zlib patch seems to also change fate-png-mdcv and fate-mov-cover-image
<michaelni>
actually i see you did update them but it seems i get diferent checksums
<michaelni>
ramiro, see ML for the exact diff from fate