BtbN changed the topic of #ffmpeg to: Welcome to the FFmpeg USER support channel | Development channel: #ffmpeg-devel | Bug reports: https://ffmpeg.org/bugreports.html | Wiki: https://trac.ffmpeg.org/ | This channel is publically logged | FFmpeg 7.0 is released
linext has joined #ffmpeg
iive has quit [Quit: They came for me...]
fairway has joined #ffmpeg
internatetional has joined #ffmpeg
<fairway>
everybody ffmpeg has this huge bug outputting as 60 fps/tbr when the file is 30 fps/tbr
<Marth64>
and Windows media framework reports it as 30fps (again, though, tbr != fps)
<fairway>
vlt only later versions have this bug (strangly)
<xx>
what's tbr anyway?
<xx>
fairway: new bugs get put into the code every day
<xx>
it's not strange at all
internatetional has quit [Quit: WeeChat 4.5.1]
<xx>
I wrote like 3 bugs today that I can remember
<Marth64>
fairway: we have looked at this several times, there is no evidence it is a bug. we have reviewed the file and informed you it is VFR (variable frame rate)
<Marth64>
i am not discrediting you but please be understanding that many people have tried to look and help
<Marth64>
have you filed a TRAC bug ticket on this?
<xx>
long-range wifi with huge aggregation currently
<xx>
anyway if you can't answer questions like "how many seconds is the video" and "how many frames are in that video" then why would the fps/tbr values even matter to you?
<fairway>
marth64 you keep saying/repeating (again, though, tbr != fps) but fact is old version still reports that 30 fps video has 30 tbr
<fairway>
marth64 you keep saying/repeating (again, though, tbr != fps) but fact is old version still reports that 30 fps video as 30 tbr
<fairway>
so if tbr is not same as fps, why is it acting like it is
<Marth64>
hold on please i am trying to find the commit where this changed for your sample file
<fairway>
marth64, i see, are you one of the ffmpeg developer?
<fairway>
<Marth64> hold on please i am trying to find the commit where this changed for your sample file. wow that's actually very smart move:, i never even thought of that
<xx>
ok, so 20s video with 601 frames indeed implies it should show up as 30 average frames per second
<fairway>
exactly
<fairway>
so why is new version of ffmpeg/ffprobe showing as 60 tbr
<xx>
I don't know, I'd have to git bisect the commit, which is what Marth64 is already doing, the commit message might say why the behavior/output changed
<fairway>
xx what version of ffmpeg/ffprobe you using may i ask
<xx>
5.1.6-0+deb12u1
<fairway>
okay
<fairway>
so not the latest one
<fairway>
there is no reason ffmpeg/ffprobe should reports as 60 fps/tbr if nb_read_frames=601 and duration = 20 seconds
lavaball has quit [Remote host closed the connection]
wziko has quit [Ping timeout: 265 seconds]
JanC has joined #ffmpeg
JanC has quit [Killed (iridium.libera.chat (Nickname regained by services))]
lullerhaus has quit []
<another|>
fairway: ffmpeg master does not report 60 fps. We've been over this multiple times now.
<fairway>
another| it reports 60 tbr though
<fairway>
where old version reports 30 tbr
<another|>
yes. and that seems to be correct given the file
<fairway>
it's not correct 30 tbr is
lullerhaus has joined #ffmpeg
<another|>
Why do you believe that 30 is correct?
<fairway>
<fairway> there is no reason ffmpeg/ffprobe should reports as 60 fps/tbr if nb_read_frames=601 and duration = 20 seconds
<another|>
You don't even seem to understand what a timebase is.
<fairway>
601 divide by 20 seconds = 30.05
<fairway>
that's why
<another|>
That's not how it works.
<fairway>
yes it does
<another|>
fps != timebase
<fairway>
another| i might not fully understand what "timebase" is but i know enough that it shouldn't be 60
<another|>
BS
<fairway>
okay send me a sample video file where it reports 30 fps but 60 tbr then
<fairway>
i bet you won't able to find one
<another|>
No, I will not.
<fairway>
you know why? because you won't find one that will do that
<another|>
No, it's because you're an asshole.
<another|>
We've been over this multiple times and you still refuse to listen. And come back every time with this "huge bug".
<fairway>
and you refuse to understand that oldversion reports as 30 tbr which is correct
<Marth64>
ok, couple of things
<fairway>
all ffmpeg has to do is undo that "commmit" where the version that started to report as 60 tbr
<another|>
You demand that people do stuff for you. You ridicule people you don't want to download your big files.
<Marth64>
1) fairway you are not in a position to make demands
<another|>
I am done with you.
<Marth64>
2) this is the commit where it changed e930b834a928546f9cbc937f6633709053448232
Nixkernal has quit [Ping timeout: 276 seconds]
<fairway>
marth64 i see, and how do i get people to undo that commit
<fairway>
Marth64 and thanks for finding that commit
<Marth64>
you don't.
<fairway>
why? is it hard to undo a "commit"?
<fairway>
another| 50MB is not big in year 2024 maybe in 1999
<Marth64>
no, you don't "get" people to do things for you. you should appreciate the fact that i just spent the past hour trying to do this for you as well as the past few DAYS that people have been helping you but instead you are coming in here harassing people
<Marth64>
so again, for the last time
<Marth64>
if you REALLY think this is still a bug, take that commit number, file a proper TRAC ticket, and have a GOOD argument that you can articulate
<Marth64>
because we have gone over it so many times
<Marth64>
you have a VFR file
<Marth64>
the way that ffmpeg displays tbr has changed
<fairway>
marth64 isn't pretty much any videos these days are VFR ?
<Marth64>
irrelevant, do not generalize and reflect this back to me
<Marth64>
if you believe it is a bug, follow the process and file a ticket with a good argument
<Marth64>
we have spoonfed you a lot of the info but you are not listening to us
<fairway>
marth64 only info that people kept repeating is tbr is not same as fps
<Marth64>
bro
<Marth64>
I literally have a file called "fairway.wmv" on my computer for the past week looking at this in and out
<Marth64>
we have spent a lot of time on this
<fairway>
i see
<Marth64>
BtbN, JEEB, another|, and others have all chimed in
<fairway>
and is the fairway.wmv is the 50MB wmv sample video file?
<Marth64>
it is YOUR file that is why I named it that
<Marth64>
the sample you provided
<fairway>
i see
<fairway>
and what did you conclude from that fairway.wmv 50MB video file
<fairway>
<Marth64> if you believe it is a bug, follow the process and file a ticket with a good argument : my argument is : tbr might not be same as fps but i know it should NOT double the value of fps
<another|>
Marth64: You have way too much patience. ;)
<Marth64>
we discussed this in the past 2 days. some of the frames in your file are shorter than the others. you have a VFR file and how FFmpeg represents that has changed since May 2023
FlorianBad has quit [Remote host closed the connection]
<fairway>
marth64 it has: nb_read_frames=601 and duration = 20 seconds
<Marth64>
another| :)
<another|>
Further investigations into my logs paint this user as a troll.
<fairway>
another| you think i am making this up? i have sample.wmv file to prove it
<fairway>
another| if this bug never existed, i wouldn't have shown up to #ffmpeg in the first place
<Marth64>
if I had @ you would be temp muted by now for repeatedly being disrespectful to the people here
<Marth64>
you should really consider framing and asking your questions/problems in a more friendly way and practicing being a better listener
<fairway>
martha64 which means you don't have a lot of patience
<Marth64>
no, you're right, I don't, thats why I spent the past hour of my holiday helping you
<Marth64>
we are done here
kozaic has quit [Ping timeout: 240 seconds]
<Marth64>
file a TRAC ticket with a concrete articulation of the problem or let it go
<fairway>
martha64 how did you find the commit #? that's impressive how you were able to locate that
<xx>
fairway: git bisect
<Marth64>
<fairway> i don't know what that means
<Marth64>
I thought you didn't know what that means
<Marth64>
and yes, I painfully went back and bisected it 20 commits at a time
<fairway>
marth64 how did you find "e930b834a928546f9cbc937f6633709053448232" is the commit that broke the ffmpeg/ffprobe
<fairway>
that's very impressive actually
<Marth64>
I literally reverted 20 commits at a time and wasted an hour of CPU cycle building ffmpeg
<Marth64>
It's not, it's called trying to be a team player which is something you are not
<Marth64>
so I am done trying to help
<xx>
fairway: you will not get more out of this channel, I suggest you take the advice to write it up coherently on the bug tracker should you choose to follow up on this
<fairway>
<Marth64> I literally reverted 20 commits at a time and wasted an hour of CPU cycle building ffmpeg, i see, that's a lot of work
<Marth64>
yes, you're lucky I have a nostalgic affinity to WMV/WMA
<fairway>
maybe you do have a lot of patience
<Marth64>
ok we are done here
<Marth64>
ciao
<fairway>
who are the top ffmpeg developers here
<Marth64>
rofl
<fairway>
why is that funny? are you one of them?
System_Error has quit [Ping timeout: 264 seconds]
<CounterPillow>
Your idea that you need to shame developers into making free software precisely to your tastes is the funny part.
<CounterPillow>
as I was saying, <CounterPillow> you guys could just get rid of this schizo already but I guess that's not in the Christmas spirit
<fairway>
CounterPillow there is one flaw to that statement : before e930b834a928546f9cbc937f6633709053448232 commit, it worked fine
<CounterPillow>
why are you doing this to your spacebar
<fairway>
if it never worked fine, then you are right
<CounterPillow>
so you're still refusing to read what people keep telling you, ok
<CounterPillow>
can we talk to your nurse and ask them to up your dose?
<another|>
Santa brings you all the wonders of /ignore
<another|>
Merry Christmas!
<fairway>
CounterPillow you are completely forgetting that version 5.xx and under reports fine
<fairway>
reports fine or "the way i want it to"
<xx>
then use version 5.xx
<xx>
problem solved
<fairway>
xx good suggestion, but there is one problem
<fairway>
there are other 3rd party app that uses ffmpeg
<fairway>
and they are not goging to use old version
<CounterPillow>
fairway: I am inside of your walls and reading your thoughts with 5G energy there are bugs under your skin there are bugs under your skin DIG THEM OUT DIG THEM OUT
<fairway>
going*
<Marth64>
its not our problem fairway. report the bug in a well articulated manner or figure out whatever workaround makes you happy
<Marth64>
and i will re-iterate for the many'th time multiple people have tried to help and spoonfeed you answers
<CounterPillow>
no he'll just post the same statement again in a day or two
<Marth64>
exactly
<Marth64>
which needs to kindly stop
<fairway>
<CounterPillow> no he'll just post the same statement again in a day or two not if it's fixed
<Marth64>
we don't answer to you
<CounterPillow>
again, stop doing that to your spacebar, it's very unkind to it
<Marth64>
:)
<fairway>
sorry,my keyyboard is broken
<fairway>
or semi broken
<CounterPillow>
are you gonna demand that be fixed as well?
<fairway>
CounterPillow no, but i will let people know to avoid this brand
<Marth64>
we're terrified
<CounterPillow>
Marth64: fairway is a very important person after all, don't you know?
<Marth64>
top ffmpeg developer
<fairway>
CounterPillow i would never say that however i will say" this is huge bug" i found
linext has quit [Quit: Client closed]
<fairway>
is there #ffmpeg channel log i can check via website
<xx>
yes
<fairway>
do you have the link. i need to keep track of the people who was generous to help me on this matter
<xx>
it's on the ffmpeg.org webpage if you click on irc, it should have a link to archives
<fairway>
okay thanks
<fairway>
by checking the logs, i noticed the lack of typing going on in #ffmpeg, until i brought up this bug topic
<Marth64>
because its usually chill and most people are able to sustain cordial conversation
<fairway>
lack of typing also means there are not many huge bugs in ffmpeg until i found this one
squeaktoy has quit [Ping timeout: 252 seconds]
squeaktoy has joined #ffmpeg
<CounterPillow>
no, people just use the appropriate place to report bugs
<CounterPillow>
instead of repeatedly screeching on IRC about how you wish to speak to the manager
<fairway>
CounterPillow true, that is my ultimate intent
<CounterPillow>
what is?
<fairway>
<CounterPillow> instead of repeatedly screeching on IRC about how you wish to speak to the manager
<CounterPillow>
you wish to speak to the manager?
<fairway>
that's fair and true statement
<Marth64>
LOL
<CounterPillow>
incredible
<Marth64>
this is not a customer service call
<CounterPillow>
actually fucking learn anything about the project please, clearly you don't know how the sausage is made.
<fairway>
marth64 why else would this channel exist in the first place then
FlorianBad has joined #ffmpeg
<fairway>
it's for people like to me to report bugs in a personal level
<CounterPillow>
no
wziko has joined #ffmpeg
wziko has quit [Max SendQ exceeded]
wziko has joined #ffmpeg
wziko has quit [Max SendQ exceeded]
<fairway>
by looking at the past #ffmpeg logs, there was this user name "Traneptora" told me why ffmpeg could be reporting the numbers incorrectly
<fairway>
something about avg_frame_rate=0/0
<Marth64>
and he's a respectable name, I would listen to him, and instead of nagging us collect your thoughts into a well crafted bug report and follow the ticket proceds
<Marth64>
process*
<fairway>
"if avg_frame_rate=0/0 show up as 0 then ffrobe doesn't know what to do" that's why traneptora told me
<fairway>
why = what
<fairway>
<Marth64> and he's a respectable name , so there is a hierarchy of important people in #ffmpeg
<CounterPillow>
hope you find the CEO of ffmpeg some day bro
<fairway>
marth64 can i ask you this then. if i created the sample.wmv via ffmpeg and sample.wmv reported the numbers wrong in v7.0 but reported right numbers in v5.0, then would you take this bug more seriously
<Marth64>
I already took you seriously and put forth effort to look into it for you. But you insisted on not being a good listener and not reciprocating the energy
<Marth64>
So no, Marth64 is going to watch shows now
<another|>
I know it's the holidays and all but y'all are feeding the troll way too much
Guest1664 has quit [Killed (mercury.libera.chat (Nickname regained by services))]
Marth64 has joined #ffmpeg
Marth64 has quit [Quit: Leaving]
{{{{{}}}} has joined #ffmpeg
<{{{{{}}}}>
Hi all, mediamtx is streaming with ffmpeg but mplayer/smplayer start reading the rtsp stream but just hang, vlc won't even start (tried the flatpak version too)
<{{{{{}}}}>
I don't see any errors in mplayer or mediamtx, mediamtx is showing an increasing frame count and varying framerate,bitrate,etc... indicating it is actually streaming something
Marth64 has joined #ffmpeg
TheSilentLink has quit [Ping timeout: 244 seconds]
TheSilentLink has joined #ffmpeg
lolok has joined #ffmpeg
JanC has joined #ffmpeg
JanC has quit [Killed (erbium.libera.chat (Nickname regained by services))]
Marth64 has left #ffmpeg [Leaving]
Marth64 has joined #ffmpeg
JanC has joined #ffmpeg
JanC is now known as Guest9440
Guest9440 has quit [Killed (mercury.libera.chat (Nickname regained by services))]
{{{{{}}} has joined #ffmpeg
{{{{{}}}} has quit [Ping timeout: 265 seconds]
{{{{{}}}}} has joined #ffmpeg
{{{{{}}} has quit [Ping timeout: 276 seconds]
Marth64 has quit [Quit: Leaving]
JanC has joined #ffmpeg
JanC has quit [Killed (calcium.libera.chat (Nickname regained by services))]
JanC is now known as Guest224
JanC has joined #ffmpeg
Guest224 has quit [Killed (platinum.libera.chat (Nickname regained by services))]
aaii has joined #ffmpeg
JanC has joined #ffmpeg
JanC is now known as Guest5374
Guest5374 has quit [Killed (erbium.libera.chat (Nickname regained by services))]
rsx has joined #ffmpeg
JanC has joined #ffmpeg
JanC is now known as Guest9604
Guest9604 has quit [Killed (iridium.libera.chat (Nickname regained by services))]
qubuepe24 has joined #ffmpeg
rvalue has quit [Ping timeout: 244 seconds]
JanC has joined #ffmpeg
JanC is now known as Guest2364
Guest2364 has quit [Killed (lead.libera.chat (Nickname regained by services))]
coldfeet has joined #ffmpeg
rvalue has joined #ffmpeg
JanC has joined #ffmpeg
JanC is now known as Guest8496
Guest8496 has quit [Killed (tungsten.libera.chat (Nickname regained by services))]
qubuepe24 has quit [Remote host closed the connection]
qubuepe24 has joined #ffmpeg
qubuepe24 has quit [Remote host closed the connection]