ChanServ 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.1.1 is released
Shuriko has joined #ffmpeg
Hackerpcs has joined #ffmpeg
Hackerpcs has quit [Max SendQ exceeded]
Hackerpcs has joined #ffmpeg
delthas has quit [Remote host closed the connection]
delthas__ has joined #ffmpeg
delthas__ is now known as delthas
xx has quit [Ping timeout: 244 seconds]
Flat_ has joined #ffmpeg
Flat has quit [Ping timeout: 252 seconds]
YuGiOhJCJ has joined #ffmpeg
deeyes has joined #ffmpeg
deeyes has quit [Read error: Connection reset by peer]
System_Error has quit [Remote host closed the connection]
System_Error has joined #ffmpeg
maxim_d33 has quit [Ping timeout: 252 seconds]
maxim_d33 has joined #ffmpeg
lusciouslover has quit [Quit: \]
lusciouslover has joined #ffmpeg
flotwig has quit [Read error: Connection reset by peer]
<Bombo>
is there a tool that shows bitrate stats of video files? i need min/max/avg, with ffmpeg -i file or ffprobe i only get avg i guess
<Bombo>
or can it be done with ffprobe`?
<BtbN>
min and max are just not well defined
<BtbN>
min and max over what timeframe?
<Bombo>
the whole playtime
<BtbN>
over the whole playtime you get the overall average
<BtbN>
how do you define "max bitrate"?
figushki has joined #ffmpeg
<Bombo>
how is the avg measured? doesnt it need to know the bitrate of all? then it has also the lowest and highest rates i guess, no?
<BtbN>
the average is size of the file divided by its playtime
<BtbN>
bitrate is never momentary, it's always calculated over a timeframe
<BtbN>
and if you make the timeframe very small, the bitrate of those small time windows turn into an insane roller coaster, that'll be 0 most of the time, and a giant frame sized spike each time a frame comes along
<BtbN>
hence a min and max bitrate is not a well defined thing
<BtbN>
min and max over a 10 second window? 1 second window?
<BtbN>
it'd also be significantly harder to calculate that, since you can't just divide size by playtime
<furq>
you can get each packet size with ffprobe
<furq>
you could chart it with that but you'd have to do some maths yourself
<BtbN>
you still have the problem of not having a sensible window size to make a definite claim of the max and min bitrate
<BtbN>
you can chart frame sizes, sure
<furq>
yeah you would also have to define what bitrate means to you
<BtbN>
It's a bit similar to the problem that if you want to know the length of a beach, or all beaches in the world, the closer you look, the bigger the number gets
<BtbN>
approaching infinity once you reach molecular levels
figushki has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<Bombo>
oookeh ;)
<furq>
i mean i don't think it's quite that bad
<furq>
i guess the question is what you need these numbers for
<Bombo>
hmmm i just want to know what parts of a movie playing will need more (network) bitrate, because if the bitrate exceeds the max network then it will buffer
<furq>
that should be reasonably simple if you know how big the client's buffer is
<Bombo>
but how big does it need to be, are there parts in the mp4 that need more bitrate? i noticed e.g. when there are lots of explosions or water, then it buffers (kodi that is)
<K900>
Generally the more complex the scene, the more bits are needed to encode it
<Bombo>
yes, so i want to know how much birate per scene ;)
<furq>
apparently you can just set the buffer size in kodi
<furq>
so you should probably just set that as high as you can
<Bombo>
yes but then it takes longer to start and maybe seek too
<kasper93>
Can anyone help me with threading setup?
<kasper93>
0. I set `avctx->get_format = callback`
<kasper93>
1. Call avcodec_get_hw_frames_parameters() inside the callback
<kasper93>
2. it errors out completely, things are not initialized yet in avctx, like codec profile which is required
<kasper93>
3. doesn't happen with thread_count=1 or thread_type=FF_THREAD_SLICE
<kasper93>
4. FF_THREAD_SLICE>1 and thread_type=FF_THREAD_FRAME doesn't work
<kasper93>
I suspect get_format() is called too soon, not taking into account the internal threading decoding latency?
fling has quit [Ping timeout: 244 seconds]
LainIwakura has quit [Ping timeout: 272 seconds]
EmleyMoor has quit [Ping timeout: 260 seconds]
EmleyMoor has joined #ffmpeg
EmleyMoor has quit [Ping timeout: 252 seconds]
emmanuelux_ has joined #ffmpeg
emmanuelux has quit [Read error: Connection reset by peer]
EmleyMoor has joined #ffmpeg
beaver is now known as pong
emmanuelux_ has quit [Ping timeout: 252 seconds]
emmanuelux has joined #ffmpeg
pong has quit [Quit: Un canal #ubuntu-fr, au bord de l'agonie !? Voilà ce que je peux retenir de mon départ du staff-fr ? Est-ce une première ? Là est la question … Favorisons les trolls/etc ! Nous allons tutoyer les 30 users]
pong has joined #ffmpeg
kasper93 has quit [Remote host closed the connection]
emmanuelux_ has joined #ffmpeg
emmanuelux has quit [Read error: Connection reset by peer]