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
bitbinge has joined #ffmpeg
Thul is now known as Thulinma
emanuele6 has quit [Ping timeout: 272 seconds]
johnjaye has joined #ffmpeg
<johnjaye>
i don't mean for this to sound nitpicky, but why does .ass/.ssa format require a decimal point in lieu of a hundreths digit?
MrZeus__ has joined #ffmpeg
<johnjaye>
i.e. instead of 1:22:333:444 you can type 1:22:333.444 and it parses fine?
lucasta has joined #ffmpeg
wziko has quit [Ping timeout: 246 seconds]
<johnjaye>
I donwloaded a specification document but the exact timecode format is only described as the former. but the libass option in ffmpeg apparently allows either
<johnjaye>
I only noticed because ffmpeg spits out a bad spec error if you write 1:22:33 in a .ass file
<johnjaye>
hmm. the libass github page doesn't have any specs. but it does have a rough guide that describes this format
xx has quit [Ping timeout: 264 seconds]
emanuele6 has joined #ffmpeg
wziko has joined #ffmpeg
wziko has quit [Ping timeout: 248 seconds]
lucasta has quit [Quit: Leaving]
MisterMinister has quit [Ping timeout: 244 seconds]
Marth64 has joined #ffmpeg
vzeroupper has quit [Quit: Client closed]
Magissia has quit [Ping timeout: 252 seconds]
iive has quit [Quit: They came for me...]
gchound has joined #ffmpeg
bitbinge has quit [Ping timeout: 264 seconds]
MrZeus__ has quit [Read error: Connection reset by peer]
MrZeus__ has joined #ffmpeg
Magissia has joined #ffmpeg
MrZeus__ has quit [Read error: Connection reset by peer]
MrZeus has joined #ffmpeg
MrZeus_ has joined #ffmpeg
MrZeus has quit [Ping timeout: 252 seconds]
Marth64 has quit [Quit: Leaving]
Mirarora has quit [Quit: Mirarora encountered a fatal error and needs to close]
Mirarora has joined #ffmpeg
johnjaye has quit [Ping timeout: 264 seconds]
johnjaye has joined #ffmpeg
System_Error has joined #ffmpeg
MrZeus_ has quit [Read error: Connection reset by peer]
Marth64 has joined #ffmpeg
MisterMinister has joined #ffmpeg
System_Error has quit [Remote host closed the connection]
MrZeus has joined #ffmpeg
Juest has quit [Ping timeout: 260 seconds]
bitbinge has joined #ffmpeg
Juest has joined #ffmpeg
System_Error has joined #ffmpeg
MrZeus has quit [Ping timeout: 252 seconds]
minimal has quit [Quit: Leaving]
Norkle has joined #ffmpeg
bitbinge has quit [Ping timeout: 264 seconds]
System_Error has quit [Remote host closed the connection]
System_Error has joined #ffmpeg
wziko has joined #ffmpeg
wziko has quit [Ping timeout: 246 seconds]
HarshK23 has quit [Quit: Connection closed for inactivity]
Dagger has quit [Ping timeout: 265 seconds]
Corroddity has quit [Quit: WeeChat 4.3.4]
five61848033917 has quit [Remote host closed the connection]
five61848033917 has joined #ffmpeg
gchound has quit [Quit: WeeChat 4.1.1]
lusciouslover has quit [Read error: Connection reset by peer]
gchound has joined #ffmpeg
lusciouslover has joined #ffmpeg
lusciouslover has quit [Read error: Connection reset by peer]
lusciouslover has joined #ffmpeg
phantomics__ has quit [Quit: Leaving]
phantomics has joined #ffmpeg
gchound has quit [Quit: WeeChat 4.1.1]
low-key has quit [Remote host closed the connection]
emanuele6 has quit [Read error: Connection reset by peer]
emanuele6 has joined #ffmpeg
HGStyle has joined #ffmpeg
HGStyle has quit [Client Quit]
HGStyle has joined #ffmpeg
HGStyle has quit [Client Quit]
wziko has joined #ffmpeg
wziko has quit [Ping timeout: 265 seconds]
jemius has joined #ffmpeg
Icedream has joined #ffmpeg
billchenchina has quit [Remote host closed the connection]
fling has quit [Remote host closed the connection]
<welder>
BtbN: I am still debugging the pulse cut issue. The culprit seems to be --enable-libx264 in Debian (it's not enabled by default), that's so odd! Do you have any clue why it may be so?
wziko has joined #ffmpeg
<BtbN>
libx264 got absolutely nothing to do with pulse
<BtbN>
no idea how you would come to that conclusion
<welder>
well I ran configure with the extra Debian flags - the issue appeared with adding this one
<welder>
I know - that's unrealted to pulse...
<BtbN>
That's virtually impossible to be the cause
<BtbN>
those two don't even get linked into the same library
<BtbN>
sounds to me like whatever test you are using just switched from some random other encoder to libx264, and that triggers the delay to show up
rex has quit [Ping timeout: 252 seconds]
<welder>
In layman terms, what exactly triggers the delay?
<welder>
omg, -v:c libx265 introduces 1 second shorter audio, libx264 2 and a half, and mpeg4 does not cut anything!!!!!!!!
<welder>
Why?!
wziko has quit [Ping timeout: 246 seconds]
<welder>
the video codec expects several frames before it starts the encoding process and that blocks the second input from being started?
<welder>
But it does not explain why the audio is cut from the END, and not beginning (it's perfectly in sync)?
coldfeet has joined #ffmpeg
wziko has joined #ffmpeg
pyre_ has joined #ffmpeg
pyre has quit [Ping timeout: 260 seconds]
rex has joined #ffmpeg
Sketch has quit [Ping timeout: 260 seconds]
wziko has quit [Ping timeout: 248 seconds]
wziko has joined #ffmpeg
lexano has quit [Quit: Leaving]
Sketch has joined #ffmpeg
Dan55 has joined #ffmpeg
elvis_a_presley has quit [Quit: smoke-bomb ; grapple-hook]
elvis_a_presley has joined #ffmpeg
<Dan55>
I'm trying to segment a wav file to 5 parts
<Dan55>
4 parts
<Dan55>
if I use absolute timestamps it works but if I use relative timestamps, the third part duration is wrong
<furq>
but then the third output is only one second long
<furq>
so maybe an off by one error somewhere
<Dan55>
thanks
lexano has joined #ffmpeg
<furq>
that's with a build from today as well
<Dan55>
furq: reported. thanks
coldfeet has quit [Quit: Lost terminal]
Dan55 has quit [Quit: Client closed]
Marth64 has joined #ffmpeg
alexherbo2 has quit [Remote host closed the connection]
<johnjaye>
maybe i'm being forgetful again.
<johnjaye>
but why is -map "[0:a]" not allowed at the end of the ffmpeg command?
<johnjaye>
i guess it has to be "defined" in the filtergraph?
<furq>
[] refers to an output label
<furq>
labels can't contain :
<johnjaye>
i was told to use -map "0:a" instead
<furq>
right
<furq>
you don't need the quotes unless you have a very unusual shell
<johnjaye>
ok. but for input labels [0:a] is fine
<johnjaye>
i guess the syntax is still a bit subtle for me
<furq>
input labels are just stream specifiers in brackets
<furq>
it would maybe be clearer if link/output labels couldn't be valid stream specifiers
<johnjaye>
i see
<furq>
but 0, 1 etc are valid which isn't great
rsx has quit [Quit: rsx]
MRiddickW has joined #ffmpeg
hightower2 has quit [Ping timeout: 244 seconds]
hightower2 has joined #ffmpeg
Keshl_ has joined #ffmpeg
Keshl has quit [Read error: Connection reset by peer]
KillerWasp has joined #ffmpeg
<KillerWasp>
hello
<KillerWasp>
This time I come not to ask for help, but to say that I have already managed to save an mp4 with video and audio, and everything works perfectly.
<KillerWasp>
I give thanks for the help received here.
<KillerWasp>
I only have one question left regarding RTMP transmissions, is the data sent raw data that is stored in the AVFrame buffer?
<KillerWasp>
mmmmm, ok, seem not all are fine... Something is wrong where i use it for twitch...
nd has quit [Ping timeout: 252 seconds]
coldfeet has joined #ffmpeg
wziko has joined #ffmpeg
Sketch has quit [Ping timeout: 244 seconds]
wziko has quit [Ping timeout: 245 seconds]
nd has joined #ffmpeg
<BtbN>
rtmp is not uncompressed video/audio, if you mean that
<BtbN>
it's typically h264+aac
<KillerWasp>
BtbN: but what have in the data of RTMP? Because until now their protocol is a damn mystery, and I don't know what goes there.
<BtbN>
What do you mean?
<BtbN>
It just streams h264 video and aac audio to a remote server
<KillerWasp>
BtbN: That its documentation does not explain anything about what data to transmit.
<furq>
flv
<KillerWasp>
lol, but what?
<BtbN>
Whatever you send it?
<BtbN>
I really don't understand what you mean
<KillerWasp>
the content of AVFrame? i guessing.
<BtbN>
h264 and aac data
<BtbN>
again, it's not uncompressed
<KillerWasp>
BtbN: you're saying that av_interleaved_write_frame compress the raw data from AVFrame to a compressed data using the codec of h264 and aac?
<BtbN>
av_interleaved_write_frame, despite it names, takes packets.
<BtbN>
*its name
<KillerWasp>
takes packets and send to mp4 or stream of rtmp. But what happen with rtmp? what are inside of datas of video/audio in a rtmp?
<BtbN>
If you want to know how flv and rtmp are muxed, you'll need to read the spec
<BtbN>
but normally you don't need to care about that from a user level
<KillerWasp>
BtbN: i already read, and don't say nothing, that's i'm ask here.
<BtbN>
Well, I don't get what you're asking then
<BtbN>
It sends whatever data you give it
<KillerWasp>
but what data? i don't believe that i can put in the data any garbage for RTMP.
<BtbN>
Well, a codec it supports.
<BtbN>
technically, rtmp only supports flv, and then flv a couple codecs
Sketch has joined #ffmpeg
<KillerWasp>
well, nothing is useful. So far I have not found any documentation that says, for the data section you have to store the raw data of 1000 audio samples in 2-channel planar style float, and for the videos also raw data of a size WxH with 32 bits per pixel RGBX, transparency is not supported. This does explain to you exactly what is in the data.
<KillerWasp>
It doesn't even explain if the raw data is involved or if there is some type of compression involved.
JanC has quit [Killed (calcium.libera.chat (Nickname regained by services))]
<welder>
When recording video and audio, is there some flag that can ensure that both streams are of equal length before exiting? So that when pressing "q" ffmpeg will wait for more audio if video is bit longer and vice versa?
Dagger has joined #ffmpeg
wziko has joined #ffmpeg
MRiddickW has quit [Ping timeout: 264 seconds]
kasper93_ has joined #ffmpeg
kasper93 has quit [Ping timeout: 272 seconds]
wziko has quit [Ping timeout: 265 seconds]
Rena has quit [Quit: $WITTY_QUIT_MESSAGE]
Rena has joined #ffmpeg
rv1sr has quit [Ping timeout: 265 seconds]
rv1sr has joined #ffmpeg
jemius has joined #ffmpeg
rv1sr has quit []
rv1sr has joined #ffmpeg
PAUL007 has joined #ffmpeg
Perflosopher has quit [Quit: Ping timeout (120 seconds)]
Perflosopher has joined #ffmpeg
JanC_ has joined #ffmpeg
JanC is now known as Guest2066
Guest2066 has quit [Killed (molybdenum.libera.chat (Nickname regained by services))]
JanC_ is now known as JanC
PAUL007 has quit [Quit: Client closed]
coldfeet has quit [Ping timeout: 248 seconds]
Ohtani has quit [Ping timeout: 260 seconds]
coldfeet has joined #ffmpeg
lavaball has quit [Remote host closed the connection]
<fairway>
everybody, this channel is not acknowledging huge bug i found in ffmpeg
fairway has quit [Quit: Going offline, see ya! (www.adiirc.com)]
<Marth64>
?
<furq>
they left
<furq>
the bug is only huge enough to be worth 71 seconds
<furq>
21:28:33 ( fairway) i found a huge bug with ffmpeg
<furq>
21:29:04 ( fairway) when i do ffprobe.exe video.wmv with v4.2.1 it showed 29.97 fps but with latest version it's showingg 59.94
<furq>
oh no!
MRiddickW has joined #ffmpeg
jemius has quit [Quit: Leaving]
darkapex has quit [Remote host closed the connection]
darkapex has joined #ffmpeg
coldfeet has quit [Remote host closed the connection]
five61848033917 has quit [Ping timeout: 252 seconds]
SuicideShow has quit [Ping timeout: 260 seconds]
SuicideShow has joined #ffmpeg
wziko has joined #ffmpeg
<KillerWasp>
another|: When I said about flv? I'm talking about RTMP.