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
HarshK23 has quit [Quit: Connection closed for inactivity]
Everything has quit [Quit: leaving]
Kei_N_ has joined #ffmpeg-devel
Kei_N has quit [Read error: Connection reset by peer]
\\Mr_C\\ has quit [Remote host closed the connection]
stazthebox6 has joined #ffmpeg-devel
stazthebox has quit [Ping timeout: 252 seconds]
stazthebox6 is now known as stazthebox
<elenril>
pross: why are you reading in a muxer?
Martchus_ has joined #ffmpeg-devel
Martchus has quit [Ping timeout: 248 seconds]
Sean_McG has quit [Quit: Lost terminal]
<pross>
i am writing a qmage muxer. each packet stores the total number of frames, so i need a way to revisit each packet at the end of muxing when total number of frames is known.
<pross>
the initial, but not workable idea, was to seek through the file (each packet has a length field written to disk) and write the total number of frames.
<elenril>
kinky
<Lynne>
keep everything in a buffer and only output on EOF?
<Lynne>
alternatively, check if writing 0 or INT_MAX is supported by demuxers
<Lynne>
its not mp4 or matroska after all, its something with as much use as a video game format used in some 90's adventure game once
<elenril>
keep a list of offsets to update?
<elenril>
no reading required
<pross>
keeping a list of offsets is what i will do
<pross>
thanks. currently wrestling with motion_est_template
HarshK23 has joined #ffmpeg-devel
SuperFashi has quit [Quit: No Ping reply in 180 seconds.]
witchymary has quit [Remote host closed the connection]
witchymary has joined #ffmpeg-devel
rvalue- is now known as rvalue
ccawley2011 has quit [Ping timeout: 252 seconds]
Krowl has joined #ffmpeg-devel
Marth64 has joined #ffmpeg-devel
Everything has joined #ffmpeg-devel
<fflogger>
[newticket] Slimbizkit: Ticket #11321 ([avcodec] dolby digital plus 7.1 defective decoding) created https://trac.ffmpeg.org/ticket/11321
Workl has joined #ffmpeg-devel
<Marth64>
i streamhashed sample ^ from 4.x and master and result is same
<Marth64>
no headphones with me though ;-;
Krowl has quit [Ping timeout: 252 seconds]
<Marth64>
(and thats decoded to pcm_s32le)
MrZeus__ has joined #ffmpeg-devel
Krowl has joined #ffmpeg-devel
Workl has quit [Ping timeout: 246 seconds]
ccawley2011 has joined #ffmpeg-devel
psykose has quit [Remote host closed the connection]
psykose has joined #ffmpeg-devel
Workl has joined #ffmpeg-devel
Krowl has quit [Ping timeout: 260 seconds]
Krowl has joined #ffmpeg-devel
Krowl has quit [Read error: Connection reset by peer]
b50d has joined #ffmpeg-devel
Workl has quit [Ping timeout: 246 seconds]
<BBB>
maybe someone should tell ffmpeg.pete to use -i 00/%d.jpg instead of -i 00/*.jpg
Krowl has joined #ffmpeg-devel
Krowl has quit [Read error: Connection reset by peer]
Krowl has joined #ffmpeg-devel
<Traneptora>
he did comment that he realized what he did wrong
Workl has joined #ffmpeg-devel
Krowl has quit [Ping timeout: 276 seconds]
Krowl has joined #ffmpeg-devel
Workl has quit [Ping timeout: 244 seconds]
Everything has quit [Quit: leaving]
<beastd>
Definitely not a good idea to use -y on the first runs (better to add it later, if you need to encode multiple times but have checked the command line does what you want)
<beastd>
Though I believe the -i syntax for the inputs instead of e.g. a -o syntax for the outputs is a pitty.
<beastd>
There are not many use cases for using shell globbing for the outputs, while there are many for using it on the inputs. also it comes to mind naturally for typical CLI users.
Workl has joined #ffmpeg-devel
Krowl has quit [Ping timeout: 246 seconds]
mkver has quit [Ping timeout: 252 seconds]
mkver has joined #ffmpeg-devel
b50d has quit [Remote host closed the connection]
Krowl has joined #ffmpeg-devel
zenmov has quit [Ping timeout: 252 seconds]
Krowl has quit [Read error: Connection reset by peer]
Workl has quit [Ping timeout: 265 seconds]
Marth64 has quit [Quit: Leaving]
b50d has joined #ffmpeg-devel
Marth64 has joined #ffmpeg-devel
b50d has quit [Remote host closed the connection]
witchymary has quit [Remote host closed the connection]
zsoltiv_ has joined #ffmpeg-devel
iive has joined #ffmpeg-devel
b50d has joined #ffmpeg-devel
<BBB>
dav1d has both -i and -o, which is slightly more protective in that sense
b50d has quit [Remote host closed the connection]
<beastd>
BBB: agree. that's actually a little better in regards to misuse. would still be better to not require -i for inputs i would think ATM
<BBB>
not requiring -i means shell expansion becomes a thing, yes
<BBB>
but a bit late now ;)
<haasn>
does anybody actually use the AVCOL_TRC_LOG(_SQRT) ever?
<haasn>
are there any sample files for it I could look at?
<haasn>
or documentation other than what's in H.273?
<JEEB>
the drafts might have some information but you'd have to see how old those values are
<JEEB>
that is actually there in the 2003 ed of H.264, so that's an old value
<JEEB>
with a quick scroll can't find :/ I wonder if older specs also had this
<JEEB>
it at least also exists in the mpeg-4 part 2 (visual) space, wonder if it's in H.263, too
<JEEB>
doesn't seem so
witchymary has joined #ffmpeg-devel
___nick___ has quit [Ping timeout: 245 seconds]
___nick___ has joined #ffmpeg-devel
fflogger has quit [Remote host closed the connection]
fflogger has joined #ffmpeg-devel
Marth64 has quit [Quit: Leaving]
<ePirat>
BBB, I also wish we had -o, I keep frequently typing it by mistake because I am so used to from other tools… but that ship has probably long sailed :D
___nick___ has quit [Ping timeout: 246 seconds]
<BBB>
right :) being backwards-compatible is probably much more widely appreciated
<ePirat>
yeah its such a fundamental thing that we can never change it…
<ePirat>
BtbN, patchwork is still veeery slow
<BtbN>
yes, but there is nothing I can do about it. It's just sending insanely stupid SQL queries