[Ffmpeg-devel-irc] ffmpeg.log.20160515

[burek]

[01:13:14 CEST] <neuro_sys> Hello again. Despite the timings are right, there's a slight delay between streams for this command: https://gist.github.com/neuro-sys/1d857664c5a32cabae4a2b1d0a826a60
[01:13:49 CEST] <neuro_sys> I wonder if there is such a thing like one should synchronize streams first before passing them to filters?
[01:14:05 CEST] <neuro_sys> Or what might be the reason of the delay between two streams that are overlayed on top.
[02:20:36 CEST] <interest1ng> hey all
[02:20:47 CEST] <interest1ng> firstly, thanks for making ffmpeg, it's great :)
[02:21:17 CEST] <interest1ng> however, i have encoded some videos with vp9, and seeking/scrubbing (going to another time in the resulting video) is very slow
[02:21:24 CEST] <interest1ng> for example, i have used this command:
[02:21:31 CEST] <interest1ng> ffmpeg -i BigBuckBunny_512kb.mp4 -c:v libvpx-vp9 -crf 10 -b:v 0 -c:a libopus BigBuckBunny_512kb.webm
[02:23:02 CEST] <interest1ng> the original mp4 allows me to select any time and goes to it pretty much instantly, but the webm takes quite a few seconds
[02:23:05 CEST] <interest1ng> what gives?
[02:30:06 CEST] <kode54> hardware decoding versus full software decoding?
[02:30:18 CEST] <kode54> improper use of keyframes?
[02:35:19 CEST] <interest1ng> kode54: i'm quite new to codecs and all, but how could i fix the keyframes issue? (vp9 is most likely purely software decoded anyway)
[02:44:14 CEST] <neuro_sys> Is AV_PIX_FMT_RGB24 all continous RGBRGB without any paddings?
[02:45:50 CEST] <neuro_sys> Do we actually need to take AV_Frame's line_size into account when reading its data and pix_fmt is RGB24?
[02:46:53 CEST] <pzich> In the docs I see "AV_PIX_FMT_RGB24: 	
[02:46:55 CEST] <pzich> packed RGB 8:8:8, 24bpp, RGBRGB..."
[02:51:48 CEST] <neuro_sys> Well then can you help me identify what's wrong with this one? https://gist.github.com/neuro-sys/dd78f1672af4d1b93036360681a1a063
[03:02:35 CEST] <neuro_sys> nevermind, it's fixed
[05:20:24 CEST] <jclone> hell-o
[05:20:53 CEST] <jclone> looked about the ffmpeg site, where are the gpg public keys?
[05:21:56 CEST] <c_14> Listed at the bottom of the MAINTAINERS file
[05:23:06 CEST] <jclone> I'm looking for the keys for checking the releases sigs
[05:23:22 CEST] <jclone> not really to participate in development, perhaps later!
[05:24:37 CEST] <c_14> They're probably signed by Michael's key
[05:25:03 CEST] <jclone> ahh
[05:26:15 CEST] <jclone> Thank you!
[05:29:00 CEST] <c_14> Ah, no. There's apparently a release signing key
[05:29:35 CEST] <jclone> ok where is that..sorry
[05:30:06 CEST] <jclone> I thought it would for the entire org
[05:32:46 CEST] <c_14> The release signing key is also listed in the MAINTAINERS file
[05:33:31 CEST] <c_14> As FFmpeg release signing key
[05:35:16 CEST] <jclone> thanks
[05:35:21 CEST] <jclone> cheers
[05:52:07 CEST] <jclone> c_14, I got it from the mit public key server, all good, fingerprint checks out.
[05:52:29 CEST] <jclone> https://pgp.mit.edu/pks/lookup?op=get&search=0x611EC787040B0FAB
[05:53:12 CEST] <jclone> thanks again.
[06:44:55 CEST] <Admin__> hey guys.. can anyone see here why it would not respect the bit rate  ? $ffmpeg_path/ffmpeg -y -i "$files" -fflags sortdts -vcodec nvenc -preset llhq -2pass 1 -b:v 1800k -minrate 100k -maxrate 2500k -bufsize:v 1800k -bf 2 -g 15 -i_qfactor 1.1 -b_qfactor 1.25 -qmin 21 -qmax 23 -c:a libfdk_aac -b:a 128k -ac 2 -f mpegts /mnt/extra/$channel/"$files".conv
[06:45:21 CEST] <Admin__> basically its encoding with nvenc and it shows output should be 1800k .. but when i look at the actual bit rate its like 10Mbit/s which is the source speed
[06:45:24 CEST] <Admin__> any ideas ?
[06:57:04 CEST] <Admin__> anyone?
[06:57:26 CEST] <anachronism> What is the CSCD encoding exactly? I can't find much info on it, other than that it seems to be related to camstudio, and the bitrate leads me to believe it's lossless and uncompressed.
[07:02:06 CEST] <anachronism> Nvm, I found some info. http://wiki.multimedia.cx/index.php?title=CamStudio_Screen_Codec
[09:14:50 CEST] <ehsanv> hi, i'm trying to convert a bgr565be format raw data to bmp file, all ok but in some file ffmpeg give me error : "P22.raw: Invalid data found when processing input"
[09:15:13 CEST] <ehsanv> actually files are not raw format, they are only pixel data!
[09:17:27 CEST] <ehsanv> my command is: ffmpeg -s 640x479 -pix_fmt bgr565be -i P22.raw P22.bmp
[09:18:30 CEST] <ehsanv> + if there is a way that i can only give "width" and ffmpeg guess height would be a lot better! i tried srcw but it gave me error
[09:20:25 CEST] <furq> ehsanv: you may need -f rawvideo and/or -c:v rawvideo before -i
[09:25:08 CEST] <ehsanv> furq: thanks man, worked!
[09:34:33 CEST] <ehsanv> sorry i disconnected
[09:35:17 CEST] <ehsanv> furq: and what about input width? i want to tell ffmpeg what is width and it guess the height
[09:40:10 CEST] <furq> guess it based on what
[10:02:50 CEST] <Fjorgynn> Life
[10:47:49 CEST] <ehsanv> furq: based on input size
[11:53:18 CEST] <MrSassyPants> How to enable scene cut keyframes in libvpx / vp9 ? I can't seem to find the right doc
[12:13:08 CEST] <dershark_> hey , I'am trying to build ffmpeg for tvheadend on freebsd , but I won't compile . Don't know where to start troubleshooting http://pastebin.com/L1qmJUmR
[12:14:51 CEST] <furq> dershark_: what's wrong with the version in ports/pkgng
[12:17:22 CEST] <dershark_> it is not 3.0.2 and I don't know if that works for tvh , but I didn't tried.
[12:17:39 CEST] <dershark_> try*
[12:40:47 CEST] <ap0> Hello. I am using ffmpeg co trim movies without encoding. for that I tell it a start time and an end time. Is there also a way to tell fmpeg to trim by chapters instead absolute time?
[13:12:41 CEST] <ChocolateArmpits> ap0: you'll have to use a script for that, get the chapter times and use as arguments for the start and end time parameters
[13:23:21 CEST] <ap0> ChocolateArmpits, too bad. But thank you.
[13:23:36 CEST] <JEEB> or you can of course implement the feature yourself
[13:23:48 CEST] <JEEB> since the chapters should be available to ffmpeg.c
[13:24:03 CEST] <JEEB> (that's the command line application)
[13:26:52 CEST] <ap0> It would take me a very long time to read myself into that project
[13:27:43 CEST] <JEEB> possibly
[13:56:04 CEST] <Roest> hi, anyone here that could help with a problem with libav, I'm trying to export video, basically using the example code, but for some reason it encodes about 10 seconds of video and then just skips the rest
[13:56:15 CEST] <Roest> http://pastebin.com/Nrpz75bX
[14:00:34 CEST] <MrSassyPants> How do you enable scene cut keyframes in libvpx / vp9 in ffmpeg? I can't seem to find it in the documentation
[14:56:52 CEST] <Admin__> hey guys.. can anyone see here why it would not respect the bit rate  ? $ffmpeg_path/ffmpeg -y -i "$files" -fflags sortdts -vcodec nvenc -preset llhq -2pass 1 -b:v 1800k -minrate 100k -maxrate 2500k -bufsize:v 1800k -bf 2 -g 15 -i_qfactor 1.1 -b_qfactor 1.25 -qmin 21 -qmax 23 -c:a libfdk_aac -b:a 128k -ac 2 -f mpegts /mnt/extra/$channel/"$files".conv
[14:56:57 CEST] <Admin__> basically its encoding with nvenc and it shows output should be 1800k .. but when i look at the actual bit rate its like 10Mbit/s which is the source speed
[14:57:00 CEST] <Admin__> anyone?
[15:06:07 CEST] <jkqxz> Admin__:  Bounding the qp in [21,23] likely makes your bitrate setting ineffective.
[15:07:04 CEST] <Admin__> really?
[15:07:14 CEST] <Admin__> do you mean that i should leave it automatic ?
[15:08:51 CEST] <jkqxz> Yeah.  Try removing the -i_qfactor, -b_qfactor, -qmin and -qmax arguments.
[15:09:23 CEST] <Admin__> ok.. i just want to get the best quality out of it.. also -ref 1 .. i tried to put that in but it says ref is not a known option.. very odd
[15:15:09 CEST] <jkqxz> Not sure the reference frame count will do anything even if you do manage to set it.
[15:15:38 CEST] <jkqxz> Really if you want best quality you shouldn't be using a hardware encoder.
[15:18:56 CEST] <ripmind> Hi, how can i convert a 3d to 2d? I tried: ffmpeg -i Bolt\ \(2008\).mkv -aspect 16:9 -vf crop=960:1080:960:0 -vcodec copy -acodec copy bolt\ 2d.mkv
[15:22:30 CEST] <iive> ripmind: look in `man ffmpeg-filter` for "stereo3d" one. it have output options for mono (left eye or right eye)
[15:24:13 CEST] <ripmind> Thanks iive
[15:34:19 CEST] <Admin__> no hardware encoding ? but the new nvidia m4000 cards are very good quality.. and the do lossless
[15:47:19 CEST] <afox_> hello
[15:53:38 CEST] <ripmind> iive: stereo3d filter is not available
[16:03:18 CEST] <ripmind> How do i compile ffmpeg with stereo3d filter?
[16:03:19 CEST] <Admin__> jkqxz > one more thing.. not sure why i can't get low latency enabled
[16:04:08 CEST] <Admin__>  $ffmpeg_path/ffmpeg -y -i "$files" -fflags sortdts -vcodec nvenc -preset llhq -2pass 1 -b:v 1800k -minrate 100k -maxrate 2500k -bufsize:v 1800k -bf 2 -g 15 -c:a libfdk_aac -b:a 128k -ac 2 -f mpegts /mnt/extra/$channel/"$files".conv
[16:04:08 CEST] <Admin__> <Admin__> basically its encoding with nvenc
[16:04:19 CEST] <Admin__> its complaining about the -tune option not used
[16:04:29 CEST] <iive> ripmind: afaik it doesn't have any external dependency, you just need recent version of ffmpeg
[16:04:30 CEST] <Admin__> ehh nevermind...
[16:04:40 CEST] <Admin__> i changed the preset already my bad
[16:04:51 CEST] <ripmind> iive: just Compiled it from git master
[16:05:00 CEST] <ripmind> So.. I shoukd have latest
[16:05:45 CEST] <ripmind> ffmpeg version N-79998-gfd4a52e
[17:44:20 CEST] <Fyr> guys, does FFMPEG support MKV metadata? I tried to set default audio channel - it seems like FFMPEG skips it.
[17:44:28 CEST] <Fyr> so as default subtitle
[17:45:22 CEST] <Fyr> and comment to metadata, like title. I attached a cover image, titled it, however, the final MKV file doesn't contain the title.
[17:48:54 CEST] <Admin__> hey guys... soo strange.. /nvidia_video_sdk_6.0.1/Samples/NvEncoder/NvEncoder  -i /dev/stdin -o /dev/stdout -size 1280 720 -bitrate 1800000 -vbvMaxBitrate 2500000  -vbvSize 1000000 -deviceID 0 -preset lowLatencyHQ  -qp 21 -numB 1 -goplength 180 -rcmode 32 -fps 30 .. i am using this to encode and the quality is amazing... but when i try to use ffmpeg with v:c nvenc i get horrible quality.. what am i doing wrong ? $ffmpeg_path/ffmpeg -y -i
[17:48:55 CEST] <Admin__> "$files" -fflags sortdts -vcodec nvenc -preset llhq -2pass 1 -b:v 1800k -minrate 100k -maxrate 2500k -bufsize:v 1800k -bf 2 -g 15 -c:a libfdk_aac -b:a 128k -ac 2 -f mpegts /mnt/extra/$channel/"$files".conv
[17:52:52 CEST] <furq> is the nvenc file actually sticking to the specified bitrate or is it using -qp 21
[17:52:56 CEST] <Aerroon> if i have a video + audio file like a .mkv where the video length is different from the audio length (there's apparently some missing frames at the start of the video file) is it somehow possible to demux said file into a video file and an audio file BUT their lengths would be the same?
[17:53:00 CEST] <furq> also the gop length is different
[17:53:09 CEST] <Aerroon> so that ffmpeg would not cut out the first few seconds of "no new frames" at the start?
[17:57:56 CEST] <Admin__> i tried to use -qp 21
[17:58:12 CEST] <Admin__> oh that... you mean nvtranscoder ?
[17:58:23 CEST] <Admin__> it is sticking to 2Mbit/s..
[17:58:24 CEST] <furq> yeah
[17:58:30 CEST] <Admin__> and qp is like 21 i thik
[17:58:37 CEST] <Admin__> the quality is amazing at the same 1.8Mbit/s
[17:58:54 CEST] <Admin__> where as ffmpeg.. it doesn't respect the bit rate with the qmin and qmax at like 21
[17:59:48 CEST] <Admin__> i am a tad confused.. i want to use ffmpeg... with nvenc but .. i can't get over the quality difference. Now why would it respect bit rate and still maintain qp 21
[17:59:59 CEST] <Admin__> i can't seem to do that with ffmpeg
[18:00:45 CEST] <Admin__> the problem i am having with nvtranscoder is there must be something up with the decoder because videos get corrupt when i use the input as concat because sizes and audio rates and everything keeps changing. The nvtranscoder can't handle those changes too much i guess
[18:01:01 CEST] <Admin__> works very well when source is live stream at mpeg2video .. never changes so the quality is amazing
[18:01:36 CEST] <furq> are you sure it's actually 2mbps
[18:01:40 CEST] <Admin__> but i am trying to do this with concat files and use nvencoder hardware with llhq and qp 21
[18:01:47 CEST] <Admin__> yes i am sure its 2Mbit/s
[18:01:49 CEST] <furq> i'd have thought setting the qp would force it to ignore all the other bitrate settings
[18:01:58 CEST] <furq> or to ignore the requested qp
[18:01:59 CEST] <Admin__> using vlc , it respects the variable bit rate with min and max
[18:02:19 CEST] <Admin__> doesn't seem to do it.. i don't know why to be honest.. but it works very very well
[18:02:27 CEST] <furq> shrug
[18:02:30 CEST] <furq> can't say i've ever used nvenc
[18:02:48 CEST] <furq> the only other obvious difference is the gop length
[18:02:54 CEST] <Admin__> yup... and the file sizes.. are hugely different.. its able to compress amazing compared to nvenc with ffmpeg
[18:02:57 CEST] <furq> i can't see that making such a huge quality difference
[18:03:12 CEST] <Admin__> well that is for testing... gop 180 was the same for ffmpeg .. i must have changed that for testing
[18:03:25 CEST] <Admin__> i did try them both at 180 before.. same result
[18:04:02 CEST] <furq> why are you passing -2pass 1
[18:04:06 CEST] <Admin__> so, it seems i am back to nvtranscoder unfortunatly :(
[18:08:10 CEST] <jkqxz> I don't really believe that bitrate number at all; 2Mbps is not enough for good quality at 720p with any sort of dynamic content (though maybe if your stream has very little activity).  Have you verified it by dividing the output file size by the length, rather than looking at possibly-wrong metadata?
[18:11:25 CEST] <furq> decent 720 at 2mbit isn't that hard if you have a clean source
[18:12:07 CEST] <furq> i'd say "just ask youtube" but it's a stretch to call that decent
[18:12:11 CEST] <furq> it's acceptable though
[18:12:26 CEST] <furq> granted they're probably not using nvenc
[18:13:46 CEST] <jkqxz> Yeah, it can be decent, but frames containing lots of movement will still have visible artifacts.  It's not like constant-QP = 21.
[18:25:29 CEST] <Admin__> quality is amazing.. even in sports.. i have sports running at 2.2 and it looks great!!
[18:25:45 CEST] <Admin__> yes i have a clean source for 720p
[18:25:59 CEST] <Admin__> my source is actually 1080p
[18:32:08 CEST] <Th3R0b> hi, im wondering if there is an anaglyph output mode for red/blue other then grayscale like there is for red/cyan?
[18:32:21 CEST] <Admin__> hey you guys know how i get rid of these errors : [mpegts @ 0x31bcee0] pts (5370840) < dts (5373840) in stream 0
[18:32:21 CEST] <Admin__> [mpegts @ 0x31bcee0] pts (5376840) < dts (5379840) in stream 0
[18:32:21 CEST] <Admin__> [mpegts @ 0x31bcee0] pts (5382840) < dts (5385840) in stream 0
[18:32:33 CEST] <Admin__> is there some filter i can use to clean that up ?
[18:36:48 CEST] <Th3R0b> right now im using --vf=lavfi="stereo3d=sbs2l:arbg" but, arbg makes the movie grayscale (black and white), I'd much like something like the dubois (arcb) mode there is for red/cyan...
[18:37:13 CEST] <Th3R0b> I suspect im simply overlooking something
[18:38:29 CEST] <hmir_> hi guys. I hope this is the riht place to ask this.
[18:39:20 CEST] <hmir_> When I run an encoding job, is there some way to decrease the verbosity of the running job? I dn't want to turn it off 'cause then I could just redirect it to /dev/null. i just want to decrease the amount of infomration being spit to screen.
[18:43:38 CEST] <rocky_> i need help installed ffmpeg version 2.5.11 on RHEL 6. Is there a yum package for that?
[18:51:35 CEST] <c_14> hmir_: you can use '+' to increase and '-' to decrease verbosity
[18:56:50 CEST] <Admin__> hey so nobody knows how i can get rid of these errors ? [mpegts @ 0x31bcee0] pts (5376840) < dts (5379840) in stream 0
[19:00:47 CEST] <jkqxz> They indicate that the encoder/muxer making the stream screwed up somehow.  Where has the stream come from?
[19:03:24 CEST] <tab1293> Does anyone here have any experience using webm_chunks and the webm_dash_manifest formats?
[19:04:11 CEST] <tab1293> I get this error when trying to generate the manifest file: Could not write header for output file #0 (incorrect codec parameters ?): Invalid data found when processing input
[19:07:13 CEST] <jkqxz> That's the generic "something went wrong" error at the muxer starting.  Look further up in the log to see if there are any other errors?
[19:10:09 CEST] <tab1293> jkqxz: is there a debug flag to get more info?
[19:10:44 CEST] <tab1293> ahh maybe -loglevel debug ?
[19:12:50 CEST] <tab1293> hmm doesnt give much more info
[19:13:57 CEST] <Admin__> wow.. so NVtranscoder took a 1.9 GIG file.. down to 40Mbit/s and the quality is spectactular
[19:14:04 CEST] <Admin__> i can't seem to replicate this with ffmpeg and nvenc
[19:14:07 CEST] <Admin__> i am not sure why
[19:14:23 CEST] <Admin__> 40MB file.. i mean. not mbits
[19:14:33 CEST] <Admin__> 1.9 GIG > 40MB
[19:14:47 CEST] <Admin__> at 2Mbit/s with 720 .. and amazing quality.. hard to tell the difference
[19:15:09 CEST] <anddam> what library does provide h.265 encoding?
[19:15:41 CEST] <JEEB> you can use either libkvazaar or libx265 for it
[19:16:32 CEST] <JEEB> kvazaar being newer and not yet as far project that has a community, while libx265 is a MultiCoreWare product that also got released under the GPL because they licensed the name and rights to use code from x264
[19:16:40 CEST] <anddam> I figure I don't have it https://gist.githubusercontent.com/anddam/c35db9804d08f794e651a09839dcb6d8/raw/1312f7c3af9357d04d85eafa66ec191a71281b7f/gistfile1.txt
[19:16:48 CEST] <anddam> woa long URL, sorry
[19:17:11 CEST] <anddam> what's odd is that it doesn't show h.264 that I'm pretty sure I've transcoded
[19:17:30 CEST] <JEEB> you can decode it just fine, you only need it for encoding. the only realistic alternative for AVC encoding is libx264
[19:17:44 CEST] <JEEB> and since your configure options don't include --enable-libx264 you don't have it
[19:18:04 CEST] <JEEB> both avc and hevc decoders are within libavcodec, it's just encoding that is usually started in a separate project
[19:18:15 CEST] <anddam> I see
[19:18:46 CEST] <anddam> I have several variants available, libx265 among those
[19:19:01 CEST] <anddam> but not h.264
[19:19:03 CEST] <anddam> odd
[19:20:08 CEST] <rocky_> i need help installed ffmpeg version 2.5.11 on RHEL 6. Is there a yum package for that?
[19:20:08 CEST] <JEEB> x265 is one of those projects where you reall see how much an open source community is beneficial to an encoder. they're making progress but since there's no-one who's got any passion about it they're still having issues trying to optimize the new things added in HEVC. Because you can't just rip those heuristics etc from x264
[19:21:05 CEST] <anddam> JEEB: no I mean I don't see any specific option for enabling x64
[19:21:29 CEST] <JEEB> the configure script has --enable-libx264
[19:21:39 CEST] <JEEB> if that's not enabled you're not building with libx264 linked in
[19:21:55 CEST] <JEEB> that is only required for encoding as I said, though. decoding is within libavcodec
[19:22:18 CEST] <anddam> I want to encode
[19:22:47 CEST] <JEEB> then you need to build with libx264 and you will have to have x264 built first for the configure check to pass
[19:23:10 CEST] <anddam> I already have x264 installed, I'm looking at the provided options of the ffmpeg port
[19:24:47 CEST] <anddam> does "high10" mean anything to you?
[19:24:59 CEST] <furq> yes
[19:25:01 CEST] <JEEB> it's a profile
[19:25:01 CEST] <anddam> it's a variant that "Build using libx264 with 10-bit output"
[19:25:11 CEST] <furq> if you don't know what that is then you don't want it
[19:25:22 CEST] <JEEB> basically since libx264 can only be built with 8bit OR 10bit bit depth output
[19:25:35 CEST] <anddam> I'm looking at it since it pulls in libx264
[19:25:35 CEST] <JEEB> for general usage you will want 8bit
[19:25:52 CEST] <JEEB> because, among other things, 10bit AVC is not HW decode'able
[19:25:53 CEST] <anddam> seems that since I was disabling gpl2 in the port building I excluded libx264
[19:26:03 CEST] <JEEB> that makes no sense
[19:26:06 CEST] <rocky_> Unrecognized option 'vf'
[19:26:07 CEST] <JEEB> wait
[19:26:10 CEST] <anddam> well it's a packaging thing
[19:26:11 CEST] <JEEB> LGPL vs GPL
[19:26:17 CEST] <JEEB> that kind of makes sense
[19:26:24 CEST] <JEEB> I thought you disabled gplv3 and that would have made no sense
[19:26:28 CEST] <JEEB> because libx264 is GPLv2+
[19:26:29 CEST] <JEEB> but yes
[19:26:32 CEST] <furq> by "not hardware decodable" do you mean that all hardware implementers are too lazy to bother
[19:26:35 CEST] <anddam> and someone thought it may be clashing, I included a set of "nonfree" codecs
[19:26:53 CEST] <anddam> ah here it is--enable-nonfree
[19:27:01 CEST] <JEEB> the nonfree ones are generally not too useful with the latest version unless you like HE-AAC
[19:27:04 CEST] <furq> you don't need that for x264
[19:27:10 CEST] <JEEB> yeah
[19:27:25 CEST] <hmir_>                  /wc
[19:27:42 CEST] <anddam> ohh I see, it was my bad, I thought the nonfree bits clashed with gpl2, but seems they don't, it's just that the resulting binary is not redistributable
[19:27:46 CEST] <anddam> but it's for my personal use
[19:27:48 CEST] <furq> right
[19:28:08 CEST] <anddam> and ofc I just completed the build with libx265 but I now lack x264
[19:28:14 CEST] <anddam> let's rebuild
[19:29:36 CEST] <furq> you probably also want to upgrade to a newer version while you're at it
[19:29:48 CEST] <anddam> newer than?
[19:29:53 CEST] <furq> the one in the paste
[19:30:20 CEST] <anddam> I have either @2.8.6 or 20160210
[19:30:28 CEST] <furq> yeah 3.0 is out now
[19:30:33 CEST] <anddam> stable?
[19:30:33 CEST] <furq> 3.0.2, even
[19:30:35 CEST] <furq> yes
[19:30:43 CEST] <anddam> I'll file a ticket for upgrading the port
[19:31:28 CEST] <anddam> I prefer packaged software to fetching and building by hand
[19:35:40 CEST] <anddam> furq: https://github.com/FFmpeg/FFmpeg doesn't have 3.0.2
[19:36:38 CEST] <anddam> all that said I'm not even sure my ipad 2 can decode h.265
[19:45:50 CEST] <Threads> anyway to force ffmpeg to make x264/mkv files constant had in the past variable framerate
[19:46:28 CEST] <Threads> i know x264 on videolan has the option of force-cfr does ffmpeg have one ?
[19:48:07 CEST] <furq> anddam: that's not an official repo
[19:48:12 CEST] <furq> http://ffmpeg.org/download.html#releases
[19:48:39 CEST] <Fyr> Threads, what command are you using and what exactly are you willing to get in result?
[19:49:23 CEST] <anddam> furq: that was linked from the download page tho'
[19:49:58 CEST] <furq> oh so it is
[19:50:06 CEST] <furq> i thought it was an unofficial mirror
[19:50:22 CEST] <furq> either way it's a mirror
[19:50:52 CEST] <furq> it looks to be missing a bunch of releases
[20:01:35 CEST] <Threads> Fyr its ok found it force-cfr=1 it is apprently
[20:48:38 CEST] <anddam> what's the difference in using aac, libfaac or libfdk_aac?
[20:49:28 CEST] <anddam> also I tried -preset help as per https://trac.ffmpeg.org/wiki/Encode/H.264 and I got
[20:49:30 CEST] <anddam> x264 [error]: invalid preset 'help'
[20:49:32 CEST] <anddam> [libx264 @ 0x7fddf983bc00] Error setting preset/tune help/(null).
[20:49:59 CEST] <__jack__> anddam: libfdk_aac is supposed to be better is some cases; however, it requires you to compile you own ffmpeg; aac is built-in, so easier to use; dunno anything about libfaac (almost useless now, maybe)
[20:50:47 CEST] <anddam> __jack__: I already built ffmpeg, and libfdk_aac is listed in aac encoding support
[20:50:58 CEST] <ChocolateArmpits> __jack__: anddam: devs are saying aac may be better now than libfdk
[20:51:12 CEST] <JEEB> for LC-AAC you should no longer require fdk-aac
[20:51:16 CEST] <JEEB> but HE-AAC fdk-aac is still the best
[20:52:54 CEST] <anddam> I don't really know what those are
[20:53:07 CEST] <anddam> my use of video is limited to transcoding in order to watch those on ipad
[20:53:32 CEST] <__jack__> lc-aac is the common one, he-aac is the 'bandwidth efficient' one
[20:53:35 CEST] <__jack__> anddam: see https://en.wikipedia.org/wiki/High-Efficiency_Advanced_Audio_Coding
[20:54:29 CEST] <JEEB> basically you don't want HE-AAC if you value quality and can do >=64kbps for stereo
[20:54:51 CEST] <ChocolateArmpits> just use aac, it's as good as any other
[20:55:33 CEST] <ChocolateArmpits> it also helps that I don't have to compile libfdk anymore
[20:56:14 CEST] <__jack__> ChocolateArmpits: exactly :)
[20:56:39 CEST] <__jack__> using stock ffmpeg is so much easier
[20:57:56 CEST] <furq> anddam: if you're on 2.8.6 then stick with fdk
[20:58:07 CEST] <furq> the improvements to the builtin encoder didn't land until 3.0
[20:58:12 CEST] <furq> faac is just garbage
[20:58:46 CEST] <furq> also if you're building from ports then you might as well stick with fdk after upgrade, it's probably a bit better
[20:58:51 CEST] <furq> pending a proper listening test
[20:59:42 CEST] <anddam> furq: no, I'm now using 20160210 that should be a few days before 3.0
[21:00:44 CEST] <furq> well yeah i still use fdk but i wouldn't go out of my way to add it
[21:01:02 CEST] <furq> the builtin encoder is good enough
[21:01:44 CEST] <anddam> wow I'm hitting 33 fps at reencoding
[21:01:47 CEST] <anddam> old i5
[21:01:52 CEST] <furq> also faac is no longer supported afaik
[21:02:12 CEST] <furq> it was only supported because there was no better gpl-compatible aac encoder
[21:02:59 CEST] <JEEB> which faac ended up not even being
[21:03:04 CEST] <JEEB> which is why it's nonfree
[21:03:25 CEST] <furq> oh
[21:03:29 CEST] <furq> am i thinking of vo-aacenc
[21:04:41 CEST] <JEEB> yeah, that one was apache v2
[21:04:45 CEST] <JEEB> and actually licensed as such
[21:05:02 CEST] <JEEB> faac was like "wait this code is suspiciously similar to the reference one which is not GPL compatible"
[21:05:40 CEST] <anddam> can code not be compatible with a license?
[21:05:58 CEST] <anddam> I thought the compatibility applied among licenses
[21:06:04 CEST] <__jack__> anddam: nope
[21:06:19 CEST] <__jack__> anddam: licence can forbid redistribution of binaries, however
[21:06:33 CEST] <JEEB> if you have one license that limits you more than the other, and the less limiting one says you can't apply more limitations then those two licenses are not compatible
[21:07:23 CEST] <JEEB> f.ex. fdk-aac has a custom license that says you can't distribute it under X or Y, which constitutes extra limitations. Thus it is incompatible with GPL and most probably LGPL - although IANAL. But that is why fdk-aac requires enable-nonfree
[21:07:54 CEST] <JustinHitla> I use that command to concatenate 2 videos 1.avi and 2.avi: "ffmpeg -f concat -i list.txt -c copy -y -f avi out.avi", and these are ffprobe output for videos http://sprunge.us/cYbM, they both the same format and the same fps, lets assume there are 60 frames in first video and 60 frames, and the thing is in out video there are not 120 frames but
[21:07:55 CEST] <JEEB> in case of faac it was copying code from a thing which was under extra limitations, which actually made it incompatible with its own license
[21:07:59 CEST] <JustinHitla>  124, and I checked them and there are first 60 frames from first video, as it should be but then it goes like: 61,62,63 frame are all duplicates of 1st frame from second video and 64,65,66 frames are all duplicates of 2nd frame from 2 video, so if I call video 1.avi "a" and video 2.avi "b" it goes like a58,a59,a60,b1,b1,b1,b2,b2,b2,b3,b4,b5 and
[21:08:03 CEST] <JustinHitla>  instead of normal a58,a59,a60,b1,b2,b3,b4,b5 anyone knows what the reason ?
[21:08:43 CEST] <JustinHitla> and of course when I play out video it stutters on place of concatenation because of those duplicate frames
[21:09:09 CEST] <JustinHitla> now I even thinking of making video into png pictures and remove duplicates by hand and then reassemble them again
[21:10:05 CEST] <JustinHitla> I even concatenated videos without audio track, thinking if that could be encoder adjasting for async audio video, but that doesn't helped also
[21:10:35 CEST] <furq> anddam: https://github.com/mstorsjo/fdk-aac/blob/master/NOTICE#L57-L58
[21:10:39 CEST] <furq> in case you're wondering what all the fuss is about
[21:10:42 CEST] <JustinHitla> if nothing, I really go that video->png->video way
[21:11:35 CEST] <JustinHitla> anyway, is my question even clear ?
[21:12:04 CEST] <JustinHitla> so other words, concatenation made 4 duplicate frames appear in output video
[21:14:16 CEST] <JustinHitla> I want to say I concatenated many videos and sometimes it just happens like that, have no idea what is the reason
[21:17:17 CEST] <JustinHitla> also first piece I got assembling png files using "ffmpeg -f image2pipe -vcodec png -r 29.970" command and second piece I got cutting out it from other video using that command "ffmpeg -ss 27 -i _/2fyzySVrA7A.mp4 -c:v mpeg4 -vb 10000k" but that shouldn't be a problem
[21:28:28 CEST] <arbi> I have an interlaced 720x576 AVI file but for some reason Ubuntu sees it as 720x288 (ffmpeg reads it correctly). Can I somehow correct this information without re-encoding the whole thing?
[21:28:31 CEST] <JustinHitla> herp derp
[21:29:39 CEST] <JustinHitla> Ubuntu sees it ?
[21:29:48 CEST] <JustinHitla> how Ubuntu a video software ?
[21:30:15 CEST] <arbi> JustinHitla: When I look at file properties
[21:30:34 CEST] <JustinHitla> that is file manager
[21:30:48 CEST] <arbi> Also when I play with Videos (the software)
[21:31:03 CEST] <arbi> JustinHitla: Yes it's the file manager
[21:31:49 CEST] <arbi> Video editing program Cinelerra also decodes it as 720x288.. half the screen becomes green :-/
[21:32:45 CEST] <arbi> Have you seen this before?
[21:32:55 CEST] <JustinHitla> no
[21:37:07 CEST] <arbi> eh I'll re-encode it
[21:43:27 CEST] <JustinHitla> arbi: do you know by any chance why I got duplicate frames when concatenated 2 videos ? so now output video stutters in place of concatenation because of those frames
[21:44:29 CEST] <arbi> I've only done that with Cinelerra
[22:06:57 CEST] <JustinHitla> herp derp
[22:11:44 CEST] <_Vi> Is update of FFmpeg to version 3.0 more breaking than usual? Has the major version bumped per semantic versioning or just to avoid two-digit numbers in minor version?
[22:12:22 CEST] <JEEB> there can always be major updates in non-step releases
[22:12:37 CEST] <JEEB> so in that sense "3.0" is no different
[22:13:03 CEST] <JEEB> the libraries all have separate versioning so semantic versioning really doesn't make too much sense in the project as a whole
[22:13:14 CEST] <JEEB> the libraries do try to abide to semantic versioning
[22:14:04 CEST] <_Vi> Semantic versioning should tell me if my scripts employing complicated FFmpeg filter chains guarantied not to break or not.
[22:14:26 CEST] <JEEB> that would be libavfilter version then
[22:14:57 CEST] <JEEB> it's simpler when a thing has a single library around :)
[22:15:18 CEST] <JEEB> in this case there's libavcodec, libavformat, libavfilter, libswscale, libswresample, libavresample, libavutil...
[22:15:28 CEST] <_Vi> I.e. bump major version number on removal of some effect, renaming options (without leaving deprecated variant), changing how command line is parsed i general. Middle version bump - new effects, new formats, new options. Patchlevel bump - fixes, optimisations.
[22:15:58 CEST] <_Vi> I mean the version of ffmpeg command line tool (maybe also ffserver and ffprobe).
[22:16:11 CEST] <JEEB> yeah, I've generally seen that on API side, not so much on cli side. Generally ffmpeg.c cli breakage is frowned upon, of course
[22:17:18 CEST] <_Vi> Bumping major version may hint that CLI breakage has finally occurred (e.g. major CLI refactor) and hints packaging FFmpeg to allow co-existance of FFmpeg2 and FFmpeg3.
[22:17:48 CEST] <_Vi> So FFmpeg 3.0 is basically FFmpeg 2.9.
[22:17:50 CEST] <JEEB> yes, but the only thing with FFmpeg currently is that you get point releases for releases
[22:18:04 CEST] <JEEB> and otherwise the main release version can be whatever the person making the release fancies
[22:18:32 CEST] <JEEB> for cli generally testing a new release should be simple enough since you can build a static FFmpeg and test that once
[22:18:45 CEST] <JEEB> only after that you can actually start migrating to it
[22:18:54 CEST] <_Vi> I think semantic versioning should also be used for command line tools scripts may rely upon.
[22:19:05 CEST] <_Vi> CLI tools are "libraries" for Bash.
[22:19:25 CEST] <JEEB> I don't disagree, I just don't see too much care about releases in general here :P they're there mostly for distros that really like having versions
[22:19:32 CEST] <__jack__> that's what people do
[22:19:44 CEST] <JEEB> also as I said, ffmpeg.c usage breakage is generally frowned upon
[22:20:05 CEST] <JEEB> like, we have the -c:v et al syntax, but -vcodec et al are not yet removed and probably will never be
[22:21:04 CEST] <JEEB> it does happen every now and then of course, like the removal of the ultra-crappy "deinterlacer" which wasn't really a deinterlacer (-deinterlace option I think?)
[22:21:44 CEST] <_Vi> I'd prefered FFmpeg's major version remaining "2" unless there is finally a decision of remove all those deprecated things and/or change how CLI works in general.
[22:22:27 CEST] <_Vi> As "3.0" already happened, maybe it should be called "3.00" to prevent further needless "overflowing" to "4.0"?
[22:22:44 CEST] <JEEB> you could make a proposal about that, but the issue is that ffmpeg.c usage compatibility is generally broken so rarely... :)
[22:23:23 CEST] <_Vi> JEEB, A library whose API is never broken can be ever v1.* and this is a good thing.
[22:24:17 CEST] <JEEB> anyways, me or anyone I'm related to isn't using the releases so while I do understand and more or less agree with your point... I don't have any strong feelings any way :)
[22:24:39 CEST] <_Vi> (I also don't like how Linux kernel version is managed. One cannot specify "I want >= 4.4.8, < 5.0.0" and expect things not to break).
[22:24:41 CEST] <JEEB> (and not to mention I'm not someone who can do something about it without doing something proactive about it)
[22:25:13 CEST] <JEEB> (and because I don't really gain much from any versioning scheme changes I'm going to be a lazy git)
[22:25:31 CEST] <JEEB> but as I said, feel free to propose it on trac or the mailing list
[22:25:39 CEST] <_Vi> Maybe somebody has specified in some dependency list "FFmpeg > 2.7, < 3.0" and there are already missed upgrade opportunities because of 3.0-ness.
[22:26:19 CEST] <JEEB> well if it's a dependency that's a bigger issue, and that person probably wouldn't be so liberal in general
[22:26:43 CEST] <JEEB> because APIs can and do change between each (branched-off) release
[22:27:23 CEST] <JEEB> so if a person knows that their thing would work with 2.7.x and 2.8.x they most probably wouldn't automagically let it grab >2.8
[22:27:39 CEST] <_Vi> JEEB, You have told that FFmpeg's API (that is CLI) should not change. And FFmpeg's libraries have their own version numbers.
[22:27:49 CEST] <JEEB> yes
[22:28:17 CEST] <JEEB> basically it depends on if you're packaging the whole of ffmpeg under "ffmpeg" or just the cli, although the cli depends on the libraries
[22:28:27 CEST] <JEEB> and if you're dependant on the cli or the libraries
[22:28:59 CEST] <JEEB> yes, with libraries you usually have stuff like libavcodec > 56
[22:29:33 CEST] <_Vi> Sometimes I write programs that use FFmpeg as a subprocess, without linking to the libraries. Obviously I need to declare dependency on FFmpeg CLI tool. What version range should I use?
[22:32:28 CEST] <JEEB> generally given that ffmpeg.c cli usage isn't usually broken, you set it to ><the lowest version you've tested to work>
[22:32:50 CEST] <JEEB> and then try to test master periodically, that should keep you up to snuff
[22:34:11 CEST] <JEEB> general health of FFmpeg can be seen with http://fatebeta.ffmpeg.org/
[22:36:06 CEST] <_Vi> So you recommend just lower version bound. OK.
[22:36:45 CEST] <JEEB> yes, but that does require semi-constant quick checks with latest stuff. just in case a breakage occurs for you. it is, as I said, rather rare though
[22:37:34 CEST] <JEEB> most projects depending on FFmpeg do try to follow the master relatively closely so they spot any breakage before it gets pushed out into a release
[22:38:56 CEST] <MrSassyPants> How do you enable scene cut keyframes in libvpx / vp9 in ffmpeg? I can't seem to find it in the documentation
[22:39:56 CEST] <JEEB> libvpx unfortunately still sucks for my use cases so E_NO_IDEA from me. But I would have guessed that'd be the default for any sane encoder :P
[22:40:13 CEST] <JEEB> -g would set the maximum GOP length, and then IRAPs would be set according to the clip
[22:40:47 CEST] <JEEB> of course I wouldn't be surprised if libvpx's scenechange stuff wouldn't be exactly too great (although I'd think that'd be one of the simpler things to get done)
[22:42:18 CEST] <_Vi> The point of semantic versioning is to avoid such checks. That looks as if there is invisible major version number (like FFmpeg "1.3.0.2" where "1." is hidden, invisible version number) with a promise that this invisible major version number will never bump. But will this "never" last, for example, 10 years?
[22:44:32 CEST] <JustinHitla> "invisible monsters, thats going to be fun" -- Barry
[22:46:16 CEST] <JEEB> _Vi: I do understand what you're aiming at but unfortunately that's not how it works :) and when stuff is decided to be broken it will be - generally by outputting a warning and then plugging it out.
[23:00:19 CEST] <JustinHitla> are there any specs my videos must conform to in order to be concatenated properly ?
[23:00:35 CEST] <JustinHitla> should I convert both to some generic format and then concatenate ?
[23:00:53 CEST] <JustinHitla> I think it concatenates on "stream" level not file level so it shouldn't be an issue
[23:13:47 CEST] <JustinHitla> I got "[mpeg4 @ 0x8190a40] warning: first frame is no keyframe" could it be when I concatenate two videos and in second one first frame is not a key frame I get those duplicate frames ?
[00:00:00 CEST] --- Mon May 16 2016