<CounterPillow>
try adding a modulo 2pi at the end
<CounterPillow>
otherwise your rotation angle just keeps getting larger until it overflows
Marth64 has joined #ffmpeg
minimal has quit [Quit: Leaving]
fling has quit [Remote host closed the connection]
fling has joined #ffmpeg
waleee has quit [Ping timeout: 255 seconds]
another| has joined #ffmpeg
zsoltiv_ has quit [Ping timeout: 255 seconds]
lec_thege8042 has quit [Read error: Connection reset by peer]
lec_thege8042 has joined #ffmpeg
MootPoot has quit [Quit: Connection closed for inactivity]
AbleBacon_ has quit [Read error: Connection reset by peer]
Marth64 has quit [Ping timeout: 260 seconds]
Marth64 has joined #ffmpeg
iliv has joined #ffmpeg
Ox7C5_ has joined #ffmpeg
Marth64 has quit [Ping timeout: 264 seconds]
Marth64 has joined #ffmpeg
rpthms has quit [Ping timeout: 255 seconds]
buzel has quit [Quit: bye]
rpthms has joined #ffmpeg
buzel has joined #ffmpeg
Marth64 has quit [Ping timeout: 240 seconds]
Marth64 has joined #ffmpeg
jarthur_ has quit [Quit: jarthur_]
rish has left #ffmpeg [#ffmpeg]
<yrc>
Hello. Do you know if video similarity detection (e.g. by czkawka) works best with low-definition video (e.g. 256x144), or high-definition (e.g. 720p or 1080p)?
<MisterMinister>
CounterPillow: unsure what would that do please?
<CounterPillow>
MisterMinister: keep the number from overflowing while keeping the behaviour in terms of rotation the same
<CounterPillow>
i.e., fix your problem
<CounterPillow>
2pi rotation is the same as 4pi rotation, 6pi rotation, etc.
<furq>
-vf "rotate=angle=90*PI/180*mod(t\,4)"
chiselfu1e is now known as chiselfuse
rpthms has quit [Ping timeout: 264 seconds]
elastic_dog has quit [Ping timeout: 272 seconds]
rpthms has joined #ffmpeg
rpthms has quit [Remote host closed the connection]
<MisterMinister>
CounterPillow: tryed `angle='mod(90*t,360)'` and it worked in CLI, but video looks jittery. This Using "rotate=angle='mod(PI/2*t,2PI)'," should have worked but it didnt... furq's example seem to have worked OK. Thank you.
rpthms has joined #ffmpeg
elastic_dog has joined #ffmpeg
<MisterMinister>
furq: Thanks got it now )
anticw has quit [Quit: leaving]
epony has joined #ffmpeg
anticw has joined #ffmpeg
elastic_dog has quit [Excess Flood]
elastic_dog has joined #ffmpeg
JanC_ has joined #ffmpeg
JanC is now known as Guest1755
Guest1755 has quit [Killed (lead.libera.chat (Nickname regained by services))]
JanC_ is now known as JanC
epony has quit [Remote host closed the connection]
epony has joined #ffmpeg
Capstan has joined #ffmpeg
FlorianBad has quit [Remote host closed the connection]
Ogobaga has quit [Read error: Connection reset by peer]
Blacker47 has joined #ffmpeg
Ogobaga has joined #ffmpeg
fling_ has joined #ffmpeg
fling has quit [Ping timeout: 255 seconds]
fling_ has quit [Remote host closed the connection]
fling has joined #ffmpeg
Marth64 has quit [Ping timeout: 268 seconds]
Marth64 has joined #ffmpeg
bitbinge has joined #ffmpeg
FH_thecat has quit [Quit: Leaving]
Vonter has quit [Ping timeout: 256 seconds]
vlm has joined #ffmpeg
Vonter has joined #ffmpeg
FH_thecat has joined #ffmpeg
Marth64 has quit [Ping timeout: 256 seconds]
Marth64 has joined #ffmpeg
bitbinge has quit [Ping timeout: 255 seconds]
Ox7C5_ has quit [Ping timeout: 264 seconds]
Kei_N has quit [Read error: Connection reset by peer]
Kei_N has joined #ffmpeg
Ox7C5_ has joined #ffmpeg
Ox7C5_ has quit [Client Quit]
five6184806 has joined #ffmpeg
five618480 has quit [Ping timeout: 272 seconds]
five6184806 is now known as five618480
five6184804 has joined #ffmpeg
five618480 has quit [Ping timeout: 255 seconds]
five6184804 is now known as five618480
alexherbo2 has joined #ffmpeg
Tano has quit [Quit: WeeChat 4.1.2]
lexano has joined #ffmpeg
FH_thecat has quit [Quit: Leaving]
fossdd has joined #ffmpeg
bitbinge has joined #ffmpeg
Tinos has quit [Remote host closed the connection]
Tinos has joined #ffmpeg
lavaball has joined #ffmpeg
theobjectivedad has quit [Remote host closed the connection]
theobjectivedad has joined #ffmpeg
theobjectivedad has quit [Read error: Connection reset by peer]
theobjectivedad has joined #ffmpeg
fossdd has quit [Ping timeout: 264 seconds]
FH_thecat has joined #ffmpeg
fling has quit [Remote host closed the connection]
fling has joined #ffmpeg
fling has quit [Remote host closed the connection]
fling has joined #ffmpeg
jagannatharjun has joined #ffmpeg
theobjectivedad has quit [Remote host closed the connection]
theobjectivedad has joined #ffmpeg
theobjectivedad has quit [Read error: Connection reset by peer]
theobjectivedad has joined #ffmpeg
theobjectivedad has quit [Read error: Connection reset by peer]
five618480 has quit [Remote host closed the connection]
five618480 has joined #ffmpeg
Guest8996 has joined #ffmpeg
Marth64 has quit [Ping timeout: 246 seconds]
Marth64 has joined #ffmpeg
theobjectivedad has joined #ffmpeg
Guest8996 is now known as FlorianBad
sirmangler has joined #ffmpeg
alexherbo2 has quit [Remote host closed the connection]
BtbN has quit [Remote host closed the connection]
BtbN has joined #ffmpeg
<sirmangler>
I was hoping someone could point me in the right direction, im trying to send a h264 stream down RTMP to an nginx server, and while it works in command line, ffmpeg doesn't seem to write the header properly in C++. The error I'm getting in nginx is "invalid video codec header size=5", but ffmpeg gives me no errors.
<sirmangler>
What could cause ffmpeg to write the header wrong? The file format is flv. Storing it as a file instead works perfectly.
luc4 has joined #ffmpeg
EmleyMoor has quit [Ping timeout: 240 seconds]
Ox7C5_ has joined #ffmpeg
five618480 has quit [Remote host closed the connection]
five618480 has joined #ffmpeg
Marth64 has quit [Ping timeout: 264 seconds]
Marth64 has joined #ffmpeg
Vonter has quit [Ping timeout: 264 seconds]
Tano has joined #ffmpeg
Vonter has joined #ffmpeg
vlm has quit [Quit: Leaving]
Marth64 has quit [Ping timeout: 268 seconds]
Marth64 has joined #ffmpeg
Vonter has quit [Ping timeout: 246 seconds]
Vonter has joined #ffmpeg
EmleyMoor has joined #ffmpeg
<drew>
I have AVCHD video from a digital camera that I would like to back up in a sensible lossless way. right now the videos exist in PRIVATE/AVCHD/BDMV/STREAM/*MTS and there are lots of other smaller metadata files around them, but I think the MTS files can exist on their own. Would using ffmpeg with copy on v and a streams into an mkv be losslessly muxing them into an mkv container? Is there a better
<drew>
way I should be backing up these files in a sane way?
<drew>
then with the avc videos backed up, I can encode smaller forms of the videos using x264/aac or something to easily share or whatever
luc4 has quit [Quit: Konversation terminated!]
<drew>
actually if the mts files can survive on their own I guess I can just back those up lol
<drew>
it would be very hard to navigate if I back up all these dirs and files that may not do anything important
<Marth64>
It depends on what value the metadata adds. Thr MTS files should just be standard MPEG-TS streams, in practice, they may be fine to keep on their own
<JEEB>
I dislike java, but this is the least bad inspection software for MPEG-TS :)
Marth128 has joined #ffmpeg
Marth64 has quit [Killed (NickServ (GHOST command used by Marth128!~Marth64@173.239.204.116))]
linext_ has joined #ffmpeg
Marth128 is now known as Marth64
linext has quit [Ping timeout: 240 seconds]
Capstan has quit [Ping timeout: 250 seconds]
xyproblem has joined #ffmpeg
AbleBacon has joined #ffmpeg
<xyproblem>
hello i have a question about the command line output of ffmpeg relating to the speed that is printed near the end of the command line output
<xyproblem>
can i find documentation for this command line output somewhere?
<xyproblem>
the output is frame, fps, q, Lsize, time, bitrate, speed
ivanich has joined #ffmpeg
<xyproblem>
what exactly are these?
<JEEB>
I think that's the stats, so the stats might be documented
<JEEB>
I think frame number and fps are quite self-explanatory. q is generally some sort of quantizer average if the encoder exposes it.
<sonicrules1234>
Speed is how fast ffmpeg is going through the file compared to real time playback
<xyproblem>
i guess its the average speed?
theobjectivedad has quit [Remote host closed the connection]
<xyproblem>
im trying to profile a bunch of ffmpeg commands to see how long it takes for them to run
<xyproblem>
so i need the total runtime of the command or the average speed
<JEEB>
/usr/bin/time -v ?
<xyproblem>
when the command is running the values keep changing im just making sure that speed is the average value
<JEEB>
that should have both real time of the command as well as CPU time etc
<xyproblem>
i do use time but if ffmpeg provides stats i might aswell use those
theobjectivedad has joined #ffmpeg
<xyproblem>
but i need to be sure what they mean
<xyproblem>
after a quick search i didnt find any documentation for it
<JEEB>
yea the exact calculation and gotchas you can only figure out by the code. a general explanation of the stats output is probably somewhere
theobjectivedad has quit [Remote host closed the connection]
<xyproblem>
so should i stick with time?
Tinos has quit [Ping timeout: 250 seconds]
<xyproblem>
or if anyone knows i could use a link to the documentation
<JEEB>
that gives you the full time of the command
<JEEB>
and esp. the /usr/bin/time with verbose output gives you a whole bunch of stats
theobjectivedad has joined #ffmpeg
<xyproblem>
i didnt use verbose i will try that next
<xyproblem>
thanks again
<JEEB>
note that just "time" only gives you the built-in of your shell