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

[burek]

[00:15:22 CET] <yuhl_rec> hi, I'm trying to record 2 video streams and 1 audio to a mkv. It does works well  videos and audio are no syncronized
[00:19:08 CET] <yuhl_rec> http://pastebin.com/zL3XsYLN
[00:20:44 CET] <yuhl_rec> I do use a logitech C920 and a datapath video grabber from http://www.datapath.co.uk/video-capture-cards/vision-range/visionrgb-e1s
[00:21:11 CET] <yuhl_rec> Is there some stuff I can do to tell ffmpeg to keep it syncronized ?
[01:18:15 CET] <CFS-MP3> is it possible to generate a reencoded file (let's suppose a ts, but probably irrelevant) and at the same time a report of frame types for that file?
[01:18:40 CET] <CFS-MP3> Obviously ffprobe can do it in a 2nd pass, but the idea here is to generate the video and the report at the same time, live
[01:21:51 CET] <furq> CFS-MP3: https://ffmpeg.org/ffmpeg-filters.html#showinfo
[01:24:12 CET] <furq> no idea if it's possible for output frames
[01:24:29 CET] <furq> i doubt it though
[01:33:56 CET] <CFS-MP3> you're mistaken but as usual you sent me to the right place
[01:34:17 CET] <CFS-MP3> where in the world are you? You've earned at least a lunch
[01:35:59 CET] <CFS-MP3> -filter_complex "fps=12,scale=416:-2:flags=lanczos,showinfo" -map v -codec:v libx264  -f segment -segment_time 6 -segment_list_type m3u8 -segment_list wwseg.m3u8  wwseg%05d.ts
[01:36:10 CET] <CFS-MP3> that seems to be in the right direction
[01:36:25 CET] <CFS-MP3> it reports size being 416 so clearly it refers to the output stream
[01:38:09 CET] <CFS-MP3> is there a way to somehow write each of the lines to a file that is named following the segments? Ideally if I have wwseg00004.ts the report (or console dump, whatever yhou want to call it) should be wwseg00004.txt
[01:41:01 CET] <deweydb> i have an ffmpeg process running inside a celery instance, it will run for a bit at about 100% cpu but eventually it will just hang, and it always hangs on message like "write(2, "Past duration 0.988655 too large"..., 33 " (when i inspect the thread with strace)
[01:41:11 CET] <deweydb> what does that mean? past duration too large?
[01:41:56 CET] <DHE> thats' not what matters. file descriptor 2 is stderr, usually your console. something jamming up the controlling terminal?
[01:42:31 CET] <deweydb> interesting.
[01:43:07 CET] <deweydb> i don't really know what you mean by :"jamming up the controlling terminal"
[01:43:53 CET] <DHE> well stderr is traditionally the console, unless you explicitly redirect it.
[01:44:02 CET] <DHE> so what are you running it under? linux text console? xterm? screen? ssh?
[01:44:32 CET] <deweydb> its being run as a subprocess from python, within a celery task.
[01:44:44 CET] <deweydb> the whole thing is then run with supervisor.
[01:45:00 CET] <DHE> is there an interface in said process or supervisor to collect the output of ffmpeg?
[01:45:23 CET] <deweydb> i think output is, but not stderr.
[01:45:26 CET] <deweydb> checking..
[01:49:21 CET] <deweydb> interesting. yeah, so i have stderr passing to subprocess.PIPE i'll have to check with the #python guys why this would be an issue. thanks for giving me a lead.
[01:49:48 CET] <deweydb> i removed that part, and ran it.
[01:49:56 CET] <deweydb> i see how. there's literally 100000s of those messages:
[01:52:08 CET] <deweydb> DHE: http://termbin.com/4aix
[01:52:22 CET] <deweydb> is that normal, that ffmpeg would report this error so many times during a render?
[01:53:08 CET] <deweydb> so i guess that because this error happened so many times the stderr=subprocess.PIPE got overloaded. funny.
[01:53:18 CET] <DHE> yeah that's probably the cause
[01:53:31 CET] <DHE> as for the past duration, I'm not sure. check the output to see if it's okay
[02:29:51 CET] <deweydb> DHE: thank you for your help, you saved me hours of headaches.
[02:37:43 CET] <DHE> it's what I do
[02:40:52 CET] <_2016Trump> a 10 page beginner's guide to ffmpeg would be nice
[02:40:57 CET] <_2016Trump> I'll make it for $100
[02:41:28 CET] <_2016Trump> I think government grants should fund software development
[02:41:49 CET] <CFS-MP3> _2016Trump And what would you cover? You probably need half a page for each of the 10000 different things FFmpeg can do
[02:42:52 CET] <_2016Trump> Just start out by showing how to encode in to the most common formats
[02:43:12 CET] <_2016Trump> How to set audio / video bit rates, frame rates, sample rates
[02:44:05 CET] <_2016Trump> how to do video capture and screen captures as inputs
[02:44:11 CET] <_2016Trump> setting resolution
[02:44:19 CET] <_2016Trump> and a table of the optimal bit rates for the various formats
[02:44:36 CET] <CFS-MP3> _2016Trump all that is well document
[02:44:47 CET] <CFS-MP3> to be honest what we need is a collection of advanced recipes
[02:44:56 CET] <_2016Trump> For a DVD, 4mbps will look great with MPEG2, but at 2mbps MPEG4 will be better than mpeg2
[02:45:34 CET] <CFS-MP3> show me a way to do what I need to do right now without coding and I'll give you those $100 :-)
[03:11:39 CET] <_2016Trump> CFS-MP3, I wish I could!
[03:34:49 CET] <fling> Is there an audio format with which it is possible to convert stereo to mono dropping one of the channels with '-c copy'?
[03:42:43 CET] <_2016Trump> fling, I sort of thought ffmpeg can't change audio channels
[03:42:51 CET] <_2016Trump> there's an audio transforming tool called sox though
[03:44:29 CET] <fling> _2016Trump: are you saying it can't change audio channels in general?
[03:45:00 CET] <llogan> sure it can, if you're willing to re-encode: http://trac.ffmpeg.org/wiki/AudioChannelManipulation
[03:45:16 CET] <fling> The question was about '-c copy'
[03:45:17 CET] <_2016Trump> I'm not sure
[03:45:44 CET] <_2016Trump> Well MP3 is joint stereo
[03:45:55 CET] <fling> _2016Trump: not always.
[03:45:55 CET] <_2016Trump> so they aren't really separate channels
[03:46:23 CET] <fling> _2016Trump: but you still _can_ copy the left channel. It is encoded the regular way.
[03:46:34 CET] <fling> In theory ^
[03:46:51 CET] <_2016Trump> It's not a mixture of the left and right channels?
[03:48:24 CET] <fling> _2016Trump: It is probably two streams. First is the left channel, second is the stream of frames calculated with $(left - right)
[03:49:33 CET] <fling> The idea is to encode less data in the second stream if there is any mono in the stream.
[03:49:58 CET] <fling> But this is kinof inefficient for true stereo streams where is no mono.
[03:50:30 CET] <fling> Idk if it is possible to have both joind and non-joint chunks in a single mp3 stream.
[03:50:35 CET] Action: fling is not using mp3 much anyway :P
[03:51:02 CET] <fling> There are mostly flac, opus and different variants of pcm
[03:51:19 CET] <fling> aac sometimes&
[04:01:16 CET] <_2016Trump> You can have it not joint stereo as I think you said
[04:04:35 CET] <fling> Sure.
[04:26:23 CET] <xiaowl> hi, ffmepg keeps dropping frames when using x11grap on Debian Jessie, using version 3.14. command: ffmpeg -video_size 1024x768 -framerate 25 -f x11grab -i :0.0+100,200 output.mp4
[04:26:32 CET] <xiaowl> any ideas?
[04:26:48 CET] <fling> xiaowl: slow storage?
[04:27:14 CET] <fling> xiaowl: slow encoding?
[04:28:12 CET] <fling> xiaowl: try tuning libx264 preset
[04:28:15 CET] <xiaowl> no sure, this debug message keeps printing:
[04:28:17 CET] <xiaowl> [rawvideo @ 0x2117a80] PACKET SIZE: 3145728, STRIDE: 4096
[04:28:19 CET] <xiaowl> *** dropping frame 3 from stream 0 at ts 0
[04:28:21 CET] <xiaowl> cur_dts is invalid (this is harmless if it occurs once at the start per stream)
[04:28:47 CET] <xiaowl> Intel CPu i7 + SSD, shouldn't be encoding or storage issue?
[04:29:19 CET] <fling> xiaowl: just try it, don't guess.
[04:29:41 CET] <xiaowl> the same command works well on another laptop with i5 + normal disk
[04:30:01 CET] <fling> xiaowl: -c libx264 -crf 28 -preset ultrafast
[04:32:21 CET] <xiaowl> same output, no luck:(   ffmpeg -s 1366x768 -f x11grab -framerate 10 -i :0.0 -c libx264 -crf 28 -preset ultrafast output.mp4
[04:32:45 CET] <xiaowl> how can i get more output logs? trying debug flag seems not help
[04:32:57 CET] <xiaowl> or maybe i missed some import logs?
[04:32:57 CET] <fling> pastebin the command and the full output
[04:34:51 CET] <xiaowl> http://pastebin.com/DNGkzqtp
[08:35:49 CET] <ElAngelo> there is no demuxer for mov in ffmpeg?
[08:37:38 CET] <bencoh> ElAngelo: mp4?
[08:37:52 CET] <ElAngelo> yeah... no
[08:38:04 CET] <ElAngelo> i have a couple of mov's that don't want to play with ffplay
[08:38:27 CET] <ElAngelo> if i play them with mplayer they don't play as well... just untill i tell it explicitely to use the mov demuxer
[08:38:31 CET] <JEEB> there is a demuxer just fine for mov/mp4/derivatives
[08:38:40 CET] <JEEB> in FFmpeg
[08:38:59 CET] <ElAngelo> then they play just fine
[08:38:59 CET] <JEEB> thus either you found a bug, missing feature or the file is bonkers
[08:39:18 CET] <ElAngelo> is there a way to figure out what it is?
[08:39:29 CET] <JEEB> feel free to post a sample on the tra
[08:39:33 CET] <JEEB> *trac
[08:39:40 CET] <JEEB> in an issue
[08:39:49 CET] <ElAngelo> would love too... only these are not files i own :(
[08:40:14 CET] <JEEB> also the demuxer lately got "support" for edit lists from google
[08:40:14 CET] <ElAngelo> anything i can figure out  myself?
[08:41:09 CET] <JEEB> boxdumper from l-smash, ffprobe etc
[08:41:16 CET] <bencoh> does mplayer use avformat to demux mov/mp4 or does it have its own demux?
[08:41:40 CET] <ElAngelo> i asked at the #mplayer channel and they tell me mplayer comes with it's own mov demuxer
[08:41:44 CET] <ElAngelo> not sure if that is correct
[08:41:54 CET] <JEEB> also try downgrading FFmpeg to before el google's edit list stuff
[08:42:26 CET] <JEEB> because that broke a lot of stuff because they stuffed presentation level shit into a demuxer
[08:43:05 CET] <JEEB> and now bugs keep getting reported and nobody wants to revert that stuff for whatever reason
[08:43:10 CET] <ElAngelo> i have the issue both with an old ffmpeg version (2014) and a new one (3.2....)
[08:43:27 CET] <JEEB> instead more and more hacks keep getting added :v
[08:43:42 CET] <ElAngelo> when was that stuff merged?
[08:43:44 CET] <ElAngelo> rougly?
[08:44:24 CET] <JEEB> very lately. not sure if 3.2 has it
[08:45:23 CET] <JEEB> http://git.videolan.org/?p=ffmpeg.git;a=commit;h=ca6cae73db207f17a0d5507609de12842d8f0ca3
[08:46:01 CET] <ElAngelo> ok, then that can't be the problem
[08:46:10 CET] <ElAngelo> most of the time i'm using a version from may
[08:47:10 CET] <JEEB> also of course that thing does "fix" some files as long as you don't even think of -c copy and are using ffmpeg cli ... (api users had their stuff broken without compilation breaking)
[08:47:41 CET] <JEEB> so I guess it's worth trying the latest head :p
[08:48:43 CET] <ElAngelo> ok let's see if i can get a version from git
[08:49:16 CET] <JEEB> and in the end unless you want to find out whether it was a bad file or missing support for x yourself you'll have to come up with a sample that you can share
[08:50:03 CET] <ElAngelo> yes i figure so. i'm going to check with my client if there is any movie they wouldn't mind sharing
[08:50:32 CET] <JEEB> well it doesn't mean movie, just a file that's created the same way. the smaller the better actually
[08:50:53 CET] <JEEB> as long as it gets created the same way
[08:50:59 CET] <JEEB> and is affected
[08:51:30 CET] <ElAngelo> nod
[08:51:40 CET] <ElAngelo> the one i have now is only 1 minute long
[08:51:43 CET] <ElAngelo> but it's 1.8G
[08:51:50 CET] <ElAngelo> rawvideo
[08:51:57 CET] <ElAngelo> av1x codec
[08:52:02 CET] <ElAngelo> pcm audio
[08:52:13 CET] <ElAngelo> and actually a very low resolution
[09:40:38 CET] <sopparus> hello, is there a way to "restream" dash like hls? I noticed .mpd as input didnt work very well
[09:41:32 CET] <sopparus> probably what I want is https://trac.ffmpeg.org/ticket/5269 then
[09:44:59 CET] <JEEB> I think people are waiting on which XML parser FFmpeg will end up with so that DASH demuxer can be written
[09:48:32 CET] <sopparus> ok so its work in progress then, thanks
[10:14:51 CET] <sopparus> think we're talking within six months?
[13:28:20 CET] <JonG> I am trying to make use of the FFmpeg MediaCodec decoder for Android that is in the current FFmpeg git master branch. I have built FFmpeg for Android using a variation of the JNI example from https://github.com/appunite/AndroidFFmpeg. I have written some code to take an command string and run the ffmpeg.c main function. I have used the --enable-jni
[13:28:21 CET] <JonG>  and --enable-mediacodec options in my configuration script. I am now wondering how I know whether MediaCodec is being used or not?
[13:28:26 CET] <JonG> Here is paste of my command and output (-loglevel debug): http://pastebin.com/JaTC5hSc
[13:28:33 CET] <JonG> I was expecting to see some mention of MediaCodec, such as: "h264_mediacodec" (https://github.com/FFmpeg/FFmpeg/blob/d5082a2ce776a2e43e25998aa07541c9ab7af0d3/libavcodec/mediacodecdec.c#L547) or "MediaCodec started successfully, ret = %d\n" (https://github.com/FFmpeg/FFmpeg/blob/d5082a2ce776a2e43e25998aa07541c9ab7af0d3/libavcodec/mediacodecdec.c#L38
[13:28:33 CET] <JonG> 2), but I don't see either.
[14:01:45 CET] <leotreasure> Hello, can someone please help me turn pictures into a movie?
[14:02:08 CET] <leotreasure> i have them in this format: crazydancehair_00001.png
[14:02:16 CET] <leotreasure> all the way to crazydancehair_00120.png
[14:02:45 CET] <leotreasure> I tried this, but it didnt work:  ffmpeg -f image2 -i crazydancehair%d_00120.png /tmp/crazyhair.mpg
[14:03:16 CET] <JonG> Have you seen this: http://trac.ffmpeg.org/wiki/Create%20a%20video%20slideshow%20from%20images
[14:06:45 CET] <leotreasure> JonG: I hadnt thanks this has a png example - perfect!
[14:07:10 CET] <squ> how select audio channel with filter_complex
[14:07:31 CET] <squ> .mkv file contains multipe audio streams and subtitles
[14:12:06 CET] <JonG> @squ You could use the -map command: https://trac.ffmpeg.org/wiki/Map
[14:12:31 CET] <squ> JonG: can you explain?
[14:12:45 CET] <ciawal> Im trying to add an overlay image to only the last frame of a video without altering the video at all, but it seems whatever I do is resulting in the video sometimes being altered
[14:12:46 CET] <ciawal> could anyone take a look at my script and see if theres a way to improve it? https://gist.github.com/ciaran/f37d71332d764d46aba6e1655099a4af
[14:13:35 CET] <squ> -filter_complex [0:a] ...
[14:14:03 CET] <squ> JonG: how to specify a stream here: -filter_complex [0:a] ... [0:v] ...
[14:17:20 CET] <JonG> squ: If your file has e.g. 3 streams: [video, audio, audio], I think you can reference them as [0:0], [0:1] and [0:2] respectively. [0:a] chooses the best quality audio stream.
[14:17:36 CET] <klaxa> to select the first audio stream: [0:a:0]
[14:17:55 CET] <klaxa> that works with -map at least not sure if -filter_complex does too (but i'd think so)
[14:18:18 CET] <squ> klaxa: how to do it with -map and keep filter_complex too?
[14:18:55 CET] <klaxa> i don't understand
[14:20:29 CET] <squ> JonG: so I need just replace [0:a] and [0:v] with [0:x] and [0:y] inside filter_complex, where x and y are streams
[14:20:48 CET] <furq> yes
[14:21:32 CET] <squ> is video always at 0?
[14:21:39 CET] <squ> may I keep [0:v]?
[14:21:42 CET] <furq> 13:17:36 ( klaxa) to select the first audio stream: [0:a:0]
[14:25:22 CET] <furq> ciawal: what does "the video sometimes being altered" mean
[14:27:35 CET] <ciawal> furq: e.g. sometimes the output video was clipped or out of sync
[14:27:44 CET] <ciawal> current example I have is seemingly skipping the first frame
[14:30:30 CET] <ciawal> it's a shame there's no way to get the frame count in the enable= expression, this approach seems so clumsy and brittle
[15:07:01 CET] <pomaranc> does hls allow to somehow reset media sequence to 0?
[16:16:35 CET] <nacho2k> hi, little question, I am trying to make a video of sequence pictures, but they have been made with different orientation, and the resolution is different, I have try to convert all pictures to the same resolution, but when I create the video it has pictures with different orientation, I have try to rotate them with convert, but it still the issue. Any advice? regards!
[16:22:00 CET] <JonG> nacho2k: You can use the transpose filter to rotate content, e.g: http://stackoverflow.com/a/9570992/1847734 . I thought more recent versions of FFmpeg did this automatically based on meta data though ...
[16:22:27 CET] <nacho2k> Jong: Thanks ! I will try it!
[16:34:35 CET] <nacho2k> JonG: Actually, the issue is with the pictures, that I have mixed, in different Orientations, I have checked them with exiftool, and I have 2 kind of orientations, any idea?
[16:43:36 CET] <JonG> I am certain there is a better way that this if you have a large number of images, or need to automate the function, but you can rotate individual images with e.g: 'ffmpeg -i input.png -vf "transpose=1" output.png'.
[16:44:54 CET] <furq> you can try ffmpeg -i in.png -metadata:s:v:0 rotate=0 out.png
[16:45:21 CET] <furq> if you have jpegs then you'd need to convert them to png if you use ffmpeg
[16:45:26 CET] <furq> i imagine there are tools that can strip that metadata inplace
[17:14:26 CET] <ciawal> I'm dumping all(?) the frames from a video like this: ffmpeg -i foo.mp4 thumb%02d.jpg
[17:14:26 CET] <ciawal> but when I look at the first image, its not the image I see when I load up the video in quicktime and look at the first frame
[17:14:26 CET] <ciawal> can anyone think of a reason why that could be? is it not exporting every frame?
[17:22:48 CET] <relaxed> ciawal: use png
[17:23:40 CET] <relaxed> ciawal: oh, try using thumb%04d.jpg
[17:24:25 CET] <ciawal> no change
[17:35:31 CET] <bencoh> then which frame do you see?
[17:37:33 CET] <ciawal> it seems to start from the 2nd frame
[17:38:24 CET] <ciawal> hm but VLC also skips this first frame
[17:38:38 CET] <ciawal> what would quicktime be doing differently/special?
[17:40:19 CET] <ritsuka> maybe quicktime handles the edit list properly, I don't know if it was eventually implemented in ffmpeg or not
[17:43:17 CET] <bencoh> you mean that https://ffmpeg.org/pipermail/ffmpeg-devel/2016-August/197509.html ?
[17:53:24 CET] <TheHumanPerson> Hello guys!
[17:53:49 CET] <nacho2k> JonG,furq: thanks for your advice, I have fixed it, removing the exif  rotation value to each .jpg
[17:53:55 CET] <TheHumanPerson> I'm a bit of a newb at ffmpeg, used some GUIs before, but there's nothing better than the real deal.
[17:54:40 CET] <klaxa> i do agree, i used guis before diving into the command line too
[17:56:20 CET] <TheHumanPerson> Anyways, I want to ask, this is going to sound stupid, but bear with me, I'm looking to encode a video to h265 in a pure, true losless quality for certain reasons, and at the same time, very weirdly,  I still want to achieve the lowest possible filesize while keeping the quality truly 100% losless. I know there are much better options out there, bu
[17:56:20 CET] <TheHumanPerson> t I want to do this and I know what I'm doing. Any ideas?
[18:00:10 CET] <TheHumanPerson> I think I could do:ffmpeg -i INPUT.mkv -c:v libx265 -preset placebo -x265-params lossless=1 OUTPUT.mkv
[18:00:46 CET] <TheHumanPerson> however im not sure if this will generate the lowest file size at such quality settings. particularly, I'm not sure if this option uses 2 pass encoding or not
[18:02:35 CET] <klaxa> you think correctly
[18:02:50 CET] <klaxa> lossless encoding does not need 2 pass though
[18:03:21 CET] <dl2s4> isnt the parameter for lossless -qp 0? but i guess most people dont now what they are doing when they encode to x265
[18:03:24 CET] <klaxa> i *think* in some rare cases -preset veryslow can yield better results than placebo but i'm not sure
[18:03:32 CET] <klaxa> dl2s4: not for x265
[18:03:36 CET] <dl2s4> kk
[18:03:39 CET] <dl2s4> ok
[18:03:40 CET] <furq> -qp 0 is for x264
[18:03:47 CET] <furq> i'm not sure if -qp is even mapped for x265
[18:05:00 CET] <furq> you'll probably want to encode a short sample with veryslow and placebo
[18:05:26 CET] <furq> i expect placebo is significantly slower so you probably want to make sure it's worth the marginal filesize reduction
[18:05:27 CET] <klaxa> i would also advise to compare to lossless x264 encodes
[18:05:42 CET] <furq> he seems pretty set on using hevc
[18:06:17 CET] <klaxa> right
[18:06:52 CET] <furq> if you just want lowest filesize then obviously do check other codecs
[18:13:05 CET] <TheHumanPerson> furq: im not familiar with other codecs. I don't wish to use those weirdly named ones
[18:13:33 CET] <TheHumanPerson> x265 is quite popular, has passed the test of time, and has better compatibility on some systems
[18:13:45 CET] <furq> are you thinking of x264
[18:13:54 CET] <TheHumanPerson> no, x264 is old school now :P
[18:14:03 CET] <furq> x265 doesn't meet the last two criteria
[18:14:13 CET] <TheHumanPerson> which ones?
[18:14:26 CET] <furq> the ones which aren't the first one
[18:14:33 CET] <TheHumanPerson> -_-
[18:14:41 CET] <furq> and it's not that popular really
[18:15:13 CET] <furq> it's still unclear whether there'll ever be major uptake of hevc because of the insane licensing situation
[18:15:14 CET] <TheHumanPerson> Well, h265 is quite popular
[18:15:38 CET] <TheHumanPerson> But as a specific encoder, then I don't know how much popular x265 is.
[18:15:45 CET] <furq> i'm talking about h265
[18:16:01 CET] <furq> x265 is the most popular h265 encoder by miles
[18:16:09 CET] <TheHumanPerson> I thought so as well.
[18:16:40 CET] <furq> and yeah try decoding any >1080p hevc content with libavcodec
[18:16:42 CET] <TheHumanPerson> So, just to be sure, do I go ahead and select the options I showed you before?
[18:16:58 CET] <furq> probably
[18:17:01 CET] <TheHumanPerson> furq: also libavacodec doesn't count, ffmpeg devs take half of it every release
[18:17:12 CET] <furq> well it's used by a lot of media players
[18:17:22 CET] <TheHumanPerson> I wouldn't be surprised if libavacoded == ffmpeg
[18:17:42 CET] <TheHumanPerson> they take so much code from each other anyways
[18:17:47 CET] <furq> uh
[18:17:55 CET] <furq> libavcodec is part of ffmpeg
[18:18:00 CET] <TheHumanPerson> wtf
[18:18:15 CET] <furq> are you thinking of libav
[18:18:20 CET] <TheHumanPerson> yes
[18:18:24 CET] Last message repeated 1 time(s).
[18:18:24 CET] <TheHumanPerson> libav
[18:18:24 CET] <furq> the badly-named ffmpeg fork which burned out
[18:18:38 CET] <TheHumanPerson> um, first of all the name isnt too bad, and secondly its fine
[18:18:48 CET] <furq> the name is bad because it's needlessly confusing
[18:18:53 CET] <furq> as we just found out
[18:19:09 CET] <TheHumanPerson> in fact, before it "burned out", ffmpeg devs took lots of its code. they wouldn't have done that if it sucked
[18:19:32 CET] <furq> they took pretty much all of its new code
[18:19:39 CET] <TheHumanPerson> and its not burned out or anything, version 12.0 was released 21 days ago
[18:20:12 CET] <furq> all the major distros have switched back to ffmpeg though
[18:20:45 CET] <TheHumanPerson> You might be thinking of the time libav changed the command names to "avconv", but that's a loong time ago
[18:21:08 CET] <furq> huh
[18:21:09 CET] <TheHumanPerson> However, I agree with you, Debain Strech has switched to ffmpeg back then
[18:21:16 CET] <TheHumanPerson> Stretch*
[18:21:28 CET] <bencoh> (finally!)
[18:22:08 CET] <bencoh> furq: libav "burned out"?
[18:22:26 CET] <furq> most people seem to have stopped using it
[18:22:32 CET] <TheHumanPerson> bencoh: nah, it's up and running
[18:23:07 CET] <TheHumanPerson> furq: if most people counts as "Debain Stretch switched to ffmpeg, and Gentoo is one of the distros that lets you choose on your own", that's hardly most people
[18:23:28 CET] <furq> are there any major distros which use libav
[18:23:38 CET] <TheHumanPerson> furq
[18:23:41 CET] <TheHumanPerson> yeah
[18:23:52 CET] <TheHumanPerson> Gentoo lets you pick between libav and ffmpeg: https://packages.gentoo.org/packages/virtual/ffmpeg
[18:24:09 CET] <furq> i said major
[18:24:48 CET] <TheHumanPerson> Since when is Gentoo "minor"??
[18:25:09 CET] <TheHumanPerson> By that logic, Ubuntu isn't major, it's based off Debian
[18:25:15 CET] <TheHumanPerson> So Debian is "more
[18:25:21 CET] <TheHumanPerson> "more" major than Ubuntu
[18:25:31 CET] <TheHumanPerson> which doesn't make sense
[18:25:32 CET] <TheHumanPerson> anyways
[18:25:56 CET] <TheHumanPerson> I'm going to encode my video with ffmpeg -i INPUT.mkv -c:v libx265 -preset placebo -x265-params lossless=1 OUTPUT.mkv
[18:26:15 CET] <TheHumanPerson> this is going to take a looooooong time, so I want to make sure my settings are right
[18:27:08 CET] <furq> like i said, encode a sample first
[18:27:46 CET] <TheHumanPerson> well, i dont have a sample
[18:27:50 CET] <furq> -t 60
[18:27:55 CET] <TheHumanPerson> ??
[18:28:10 CET] <furq> add -t 60 to that command and it'll encode the first minute
[18:28:25 CET] <TheHumanPerson> I found a random 100KB video
[18:28:27 CET] <TheHumanPerson> ill try that
[18:28:38 CET] <furq> you probably want it to be a representative sample
[18:28:44 CET] <TheHumanPerson> okay
[18:28:47 CET] <TheHumanPerson> ill do that now
[18:28:48 CET] <furq> and yeah i would compare it with other presets and codecs
[18:29:04 CET] <furq> i have no idea how good x265's lossless mode is
[18:29:33 CET] <TheHumanPerson> "no such file or directory"
[18:29:36 CET] <TheHumanPerson> weird error
[18:30:01 CET] <furq> -t 60 goes after the input filename
[18:30:57 CET] <bencoh> silly question, but .... why would you encode a video using x265/placebo?
[18:31:34 CET] <TheHumanPerson> bencoh: Because I'm crazy and I want to do it.
[18:31:48 CET] <bencoh> I mean ... I get the idea of lossless compression and storage size, but .... it'll just take ages. is it worth it?
[18:32:27 CET] <bencoh> TheHumanPerson: most people around here aren't exactly sane either, but ... :D
[18:32:36 CET] <TheHumanPerson> bencoh: :D
[18:32:46 CET] <TheHumanPerson> How do I know when the command is finished processing?
[18:32:55 CET] <bencoh> when it returns (?)
[18:33:30 CET] <TheHumanPerson> Okay :P
[18:33:43 CET] <TheHumanPerson> im a newb at this stuff :P
[18:35:10 CET] <TheHumanPerson> I'm a large proponent of graphical interfaces, but sometimes graphics cannot provide what the classic command-line can do
[18:35:49 CET] <TheHumanPerson> And it took me a while to understand this, no amount of trying and installing and uninstalling software will ever beat just using raw ffmpeg
[18:39:34 CET] <furq> guis are nice if you need to do one very specific thing
[18:39:58 CET] <TheHumanPerson> bencoh: I read the numbers wrong, thought I was 100 fps, but I'm 0.4 fps :D
[18:40:18 CET] <furq> if it's even possible to write a gui tool that covers everything ffmpeg does then i'm pretty sure it'll be unusably complex
[18:41:15 CET] <furq> and yeah you might want to use -t 30 for your sample
[18:41:30 CET] <TheHumanPerson> I did
[18:41:41 CET] <TheHumanPerson> GPU temp was 85C so I closed ffmpeg :P
[18:41:59 CET] <furq> gpu?
[18:42:03 CET] <TheHumanPerson> yeah
[18:42:10 CET] <TheHumanPerson> doesnt ffmpeg use gpu video block?
[18:42:16 CET] <furq> not unless you tell it to
[18:42:23 CET] <TheHumanPerson> I'm running a very old GPU though
[18:42:25 CET] <furq> and certainly not for encoding with x265
[18:42:39 CET] <furq> it could maybe use it for decoding, depending on the codec
[18:42:54 CET] <TheHumanPerson> so you mean in this case it _wasn't_ heating up my GPU?
[18:42:59 CET] <furq> i doubt it
[18:43:11 CET] <TheHumanPerson> All I know is the fan noise was super crazy
[18:43:32 CET] <TheHumanPerson> I shouldn
[18:43:35 CET] <TheHumanPerson> shouldn
[18:43:35 CET] <furq> maybe x265 automatically uses some opencl stuff
[18:43:41 CET] <TheHumanPerson> I don't know
[18:43:50 CET] <furq> i know x264 can use it for lookahead but you need to explicitly enable it
[18:43:57 CET] <TheHumanPerson> I shouldn't try doing losless encoding on such an old system, but im a crazy person
[18:44:06 CET] <furq> how old is this system
[18:44:12 CET] <furq> by which i mean what cpu is it
[18:44:14 CET] <TheHumanPerson> Sandy Bridge
[18:44:27 CET] <furq> that's not that old
[18:44:29 CET] <TheHumanPerson> mobile CPU
[18:44:35 CET] <TheHumanPerson> i5-2540M
[18:44:38 CET] <furq> yeah that's a much bigger problem
[18:45:00 CET] <TheHumanPerson> it was a fast, high-end model back at the time it was made
[18:45:17 CET] <TheHumanPerson> at least that's what notebookcheck says
[18:45:19 CET] <furq> x265 placebo on a 35W dualcore sounds like a thoroughly miserable experience
[18:45:41 CET] <furq> i guess at least your source isn't 4k
[18:46:08 CET] <bencoh> :D
[18:46:13 CET] <TheHumanPerson> it's 720p. I would have downloaded the 4k version now that you reminded me, but the file size was just stupid
[18:46:15 CET] <TheHumanPerson> :P
[18:46:35 CET] <bencoh> are you actually decoding from h265 as well?
[18:46:36 CET] <furq> well yeah you'd be lucky to get 0.1fps with a 4k source
[18:46:43 CET] <furq> especially if the source is hevc
[18:46:51 CET] <TheHumanPerson> bencoh: No idea what the source file is.
[18:46:53 CET] <furq> i get about 5fps decoding 4k hevc with ffmpeg on a desktop
[18:47:01 CET] <TheHumanPerson> furq: what specs?
[18:47:06 CET] <bencoh> furq: 5fps? nice :p
[18:47:11 CET] <bencoh> could be worst
[18:47:16 CET] <bencoh> -t+e
[18:47:16 CET] <furq> i7 920 at 3.4 or so
[18:47:24 CET] <TheHumanPerson> bencoh: mine was 0.4 fps
[18:47:29 CET] <TheHumanPerson> could be worse, eh?
[18:47:36 CET] <furq> i'm talking about decoding
[18:47:57 CET] <TheHumanPerson> ah well then time to upgrade, folks!
[18:48:01 CET] <TheHumanPerson> i7 920 is old school
[18:48:08 CET] <furq> it's not really the cpu's fault
[18:48:13 CET] <furq> ffmpeg's hevc decoder is really slow
[18:48:28 CET] <TheHumanPerson> If you're really on a budget, get a good quality used 3rd gen CPU
[18:48:30 CET] <bencoh> s/slow/still not heavily optimized/ :)
[18:48:36 CET] <TheHumanPerson> Or better yet, a used Haswell i7
[18:48:49 CET] <TheHumanPerson> that thing will CRUSH your i7 920\
[18:48:51 CET] <furq> bencoh: isn't it that they don't want intrinsics in the core
[18:49:23 CET] <TheHumanPerson> Sorry, I mean destroy, not crush.
[18:49:41 CET] <furq> the problem with sandy bridge and newer is that you need to pay the intel overclocking premium
[18:49:49 CET] <TheHumanPerson> lol
[18:49:56 CET] <furq> which is something i'd rather not do
[18:49:57 CET] <TheHumanPerson> then keep your years old cpu
[18:50:08 CET] <TheHumanPerson> and browse facebook
[18:50:15 CET] <furq> i'm still looking for a xeon x5670
[18:50:44 CET] <TheHumanPerson> furq: Wait until the Kaby Lake Xeon 3 is released, and then read the reviews.
[18:51:23 CET] <TheHumanPerson> x5670 is EOL
[18:51:33 CET] <TheHumanPerson> And costed $1440.00 - $1443.00 at release
[18:51:43 CET] <furq> yeah it costs £60 now and fits in my motherboard
[18:51:47 CET] <TheHumanPerson> Now it's much cheaper, maybe, but wait for Kaby Lake
[18:51:47 CET] <furq> and it's 6-core and clocks to 4ghz
[18:51:52 CET] <TheHumanPerson> Now it's much cheaper, maybe, but wait for Kaby Lake
[18:52:53 CET] <TheHumanPerson> bencoh: so uh, if I don't do losless, what other settings would your recommend that offer a good balance?
[18:53:12 CET] <kerio> TheHumanPerson: can't you just use ffv1
[18:53:21 CET] <furq> ^
[18:53:55 CET] <TheHumanPerson> Keridos: not sure if ffv1 is even better than h265 in the first place
[18:54:06 CET] <TheHumanPerson> h265 will have better support than ffv1 ever will, as a plus
[18:54:09 CET] <kerio> "better" how
[18:54:23 CET] <kerio> ffv1 is lossless
[18:54:27 CET] <kerio> does h265 even have a lossless mode?
[18:54:31 CET] <klaxa> on my laptop i get a hole 15 fps decoding :P
[18:54:39 CET] <klaxa> kerio: yes
[18:54:40 CET] <kerio> does it support high bpc?
[18:54:56 CET] <kerio> like grayscale 16bpp
[18:55:44 CET] <TheHumanPerson> kerio: anyways how I do encode ffv1.3, then?
[18:55:54 CET] <kerio> -c:v ffv1 -level 3
[18:57:29 CET] <TheHumanPerson> kerio:  Thanks. However, I read this article ( http://blogs.library.duke.edu/bitstreams/2015/05/08/the-pros-and-cons-of-ffv1/ ) and it claims, just claims, that ffv1 may not be truly lossless
[18:58:03 CET] <TheHumanPerson> and, seems like ffv1.3 , latest version, no updates since THREE years ago
[18:58:16 CET] <TheHumanPerson> But I'm willing to deal with that for the timebeing
[18:58:48 CET] <furq> In testing, it is difficult to verify that a file converted (compressed) to FFV1 and then converted back (decompressed) is an identical file to its original state.
[18:58:51 CET] <furq> what
[18:58:57 CET] <kerio> like
[18:59:00 CET] <kerio> -f hash
[18:59:03 CET] <kerio> :\
[18:59:03 CET] <furq> this article is bad
[18:59:33 CET] <furq> the comments are pretty good though
[19:00:00 CET] <furq> The concept of lossless compression is mysterious, and seemingly a paradox. How can it make a file smaller, without eliminating or irreversibly altering any data?
[19:00:05 CET] <furq> who wrote this
[19:00:17 CET] <bencoh> :D
[19:00:27 CET] <TheHumanPerson> furq: Yeah, but the point was he claims ffv1 might not be truly lossless
[19:00:35 CET] <TheHumanPerson> is this, truly true? (heh)
[19:00:55 CET] <furq> well sadly he also claims there is no way of testing
[19:00:59 CET] <furq> so i guess we will never know for sure
[19:01:17 CET] <TheHumanPerson> you've not answered me
[19:01:23 CET] <TheHumanPerson> and yes, you can easily test it
[19:01:38 CET] <TheHumanPerson> take the pixel difference between two files
[19:02:34 CET] <TheHumanPerson> anyways ill try it
[19:02:36 CET] <furq> why are you giving credence to his other claims if you know that claim is bullshit
[19:02:39 CET] <TheHumanPerson> ffmpeg -i <input_video> \
[19:02:40 CET] <TheHumanPerson>     -acodec  copy       \
[19:02:40 CET] <TheHumanPerson>     -vcodec  ffv1       \
[19:02:40 CET] <TheHumanPerson>     -level   1          \
[19:02:40 CET] <TheHumanPerson>     -coder   1          \
[19:02:40 CET] <TheHumanPerson>     -context 1          \
[19:02:40 CET] <TheHumanPerson>     -g       1          \
[19:02:41 CET] <TheHumanPerson>     <output_video>
[19:04:25 CET] <TheHumanPerson> doesn't work
[19:04:26 CET] <TheHumanPerson> weird
[19:04:51 CET] <TheHumanPerson> looks like ffv1 has 2 pass though, should I use that?
[19:08:00 CET] <TheHumanPerson> sorry for spamming too many lines :P
[19:08:44 CET] <TheHumanPerson> furq: im getting significantly higher fps with ffv1 than x265, which is good, but how can this be?
[19:09:05 CET] <TheHumanPerson> what does ffv1 do differently to achieve this?
[19:11:20 CET] <furq> i imagine it doesn't compress as well
[19:12:48 CET] <TheHumanPerson> perhaps, but at least it seems a bit faster
[19:12:55 CET] <furq> it should be several orders of magnitude faster
[19:13:07 CET] <bencoh> the usual tradeoff, yeah :p
[19:13:48 CET] <furq> also you were using x265 placebo
[19:14:02 CET] <bencoh> size, quality, speed, pick two
[19:14:05 CET] <TheHumanPerson> on an unrelated note, im trying to check the total frames of the video, is this correct? ffprobe -v error -count_frames -select_streams v:0 -show_entries stream=nb_read_frames -of default=nokey=1:noprint_wrappers=1 input.mkv
[19:14:23 CET] <furq> the slower presets will use significantly slower methods which don't compress that much better (if at all)
[19:15:14 CET] <TheHumanPerson> Is x265 lossless ultrafast preset, actually ultrafast?
[19:15:17 CET] <furq> e.g. x264 placebo will try to use 16 consecutive bframes, which takes much longer to analyse, even though it's very rare you'll ever see as many as 8 consecutive bframes
[19:15:38 CET] <furq> i usually use -bf 5 because everything i've ever analysed drops to <1% after that
[19:16:07 CET] <furq> -bf 16 on a clip which never uses more than 8 is spending a bunch of time effectively doing nothing
[19:17:38 CET] <furq> and yeah at least with x264 lossless the slower presets are slower and compress better
[19:17:49 CET] <furq> they won't set the same set of options because some of them don't make sense for lossless
[19:18:08 CET] <furq> the same set as they would for lossy, that is
[19:18:14 CET] <TheHumanPerson> So with x265, going slower doesn't bring as much benefits than it did with x264?
[19:18:27 CET] <furq> i have no idea, i've used x265 once in my life to test something
[19:19:02 CET] <furq> i assume the concepts are roughly the same
[19:21:04 CET] <furq> fwiw if i was encoding a 720p clip lossless i'd probably use x264 with default settings
[19:21:31 CET] <furq> it's not worth using anything slower than that unless you're encoding a ton of stuff and/or you're starved for space
[19:23:32 CET] <TheHumanPerson> Basically, my 720p file is 1.5GB. I'm just testing what settings produce almost identical quality at a smaller size
[19:23:42 CET] <JonG> furq: Someway back in the conversation you mention that FFmpeg won't use the GPU unless you tell it to... What is the option I should be looking at for that? I just wondered if it might be related to my question from earlier today about trying to use MediaCodec and the GPU on Android.
[19:23:52 CET] <furq> nothing lossless will come out smaller
[19:24:04 CET] <TheHumanPerson> Initially I'm trying true lossless, but next time when I encode I'll hopefully be much more reasonable :D :P
[19:24:08 CET] <bencoh> TheHumanPerson: then don't use lossless encoding
[19:24:13 CET] <bencoh> :)
[19:24:20 CET] <furq> even x265 lossless with placebo will be orders of magnitude larger
[19:24:32 CET] <furq> assuming that even gives the best compression
[19:24:50 CET] <TheHumanPerson> bencoh: Like I said, im just trying it out. Sadly, wish I could figure out if the source video was already compressed or not, and uncompress it first
[19:25:04 CET] <furq> JonG: -hwaccel [decoder-name]
[19:25:06 CET] <bencoh> uncompress?
[19:25:20 CET] <TheHumanPerson> bencoh: I mean extract the raw video
[19:25:24 CET] <furq> i have no idea how that would work on android though
[19:25:48 CET] <furq> TheHumanPerson: you can extract the raw video with -i src.mkv -c:v rawvideo dest.mkv
[19:25:52 CET] <furq> you probably don't want to do that though
[19:25:55 CET] <TheHumanPerson> furq: why?
[19:25:57 CET] <TheHumanPerson> :D
[19:26:02 CET] <dl2s4> huggeee :)
[19:26:10 CET] <TheHumanPerson> I can already tell
[19:26:13 CET] <furq> because it's the exact same video you already have
[19:26:20 CET] <furq> it won't be "uncompressed"
[19:26:25 CET] <furq> it'll still have all the compression artifacts
[19:26:31 CET] <furq> just without any of the compression
[19:26:53 CET] <furq> much like decoding an mp3 to wav
[19:27:16 CET] <TheHumanPerson> furq: Actually, if the source video im testing is already compressed in some shape or form, then im wasting my time. hence the suggestion to extract the raw video first. otherwise if I can find from the metadata what compression it uses, i'd love that
[19:27:26 CET] <furq> use mediainfo or ffprobe
[19:28:01 CET] <furq> ffprobe -show_streams -select_streams 0:v -show_entries stream=codec_name foo.mkv
[19:28:21 CET] <TheHumanPerson> Thanks!
[19:29:02 CET] <bencoh> if you dont have the source then you're doomed. there is no such thing as "extracting the raw" :)
[19:29:42 CET] <TheHumanPerson> furq: looks like the source video is h264. audio is aac 48khz
[19:30:42 CET] <TheHumanPerson> Which means I partly wasted my time, however I've never really tried ffmpeg (the raw CLI) before, so I guess I'm doing it for science!!
[19:30:50 CET] <TheHumanPerson> :D
[19:30:52 CET] <JonG> Well maybe it is a naive assumption, but this: https://github.com/FFmpeg/FFmpeg/blob/21b68cdbae6576bb58c19dd44c0669293f7d05d1/libavcodec/allcodecs.c#L75 suggests mediacodec gets registered as a possible hwaccel option. And MediaCodec seems to be the thing for HW acceleration on Android... Only one way to find out! Thanks. (That and I emailed the de
[19:30:52 CET] <JonG> veloper who wrote the mediacodec code for FFmpeg)
[19:31:02 CET] <JonG> furq**
[19:31:10 CET] <TheHumanPerson> JonG: ask on #ffmpeg-devel, not here
[19:32:07 CET] <JonG> OK, I assumed that was for FFmpeg developers only ... but I'll give it a try.
[19:32:18 CET] <bencoh> actually it is, somehow
[19:32:19 CET] <TheHumanPerson> Well, if you have a dev question, yes
[19:32:36 CET] <TheHumanPerson> dev questions go to #ffmpeg-devel if I understand correctly.
[19:32:41 CET] <bencoh> ffmpeg-devel is focused on ffmpeg internal dev
[19:33:53 CET] <TheHumanPerson> ohhh okay then
[19:34:02 CET] <JonG> I am not an ffmpeg internal developer (yet) :)
[19:34:38 CET] <TheHumanPerson> :)
[19:41:59 CET] <TheHumanPerson> bencoh: So, if I want to encode something in general in the future, what is a good balance of quality and speed for my poor hardware?
[19:42:57 CET] <furq> x264 with the slowest preset you can tolerate
[19:43:06 CET] <furq> except placebo which is a waste of time
[19:43:12 CET] <furq> as the name implies
[19:43:21 CET] <TheHumanPerson> furq: why not x265
[19:43:43 CET] <furq> if x264 veryslow is faster than you're willing to put up with then try x265
[19:43:47 CET] <furq> otherwise there's no point
[19:44:30 CET] <furq> last time i checked, at the same encoding speed they performed roughly the same
[19:44:46 CET] <furq> x265 only pulls ahead when you use the really slow presets
[19:45:26 CET] <furq> and h264 is generally much nicer to work with than h265
[19:49:11 CET] <TheHumanPerson> furq: Guess what? source is 1.5GB, encoded is 27GB :P
[19:49:31 CET] <TheHumanPerson> ive deleted it
[19:49:43 CET] <TheHumanPerson> silly me for encoding an already h264 compressed video
[19:50:23 CET] <TheHumanPerson> anyways, the source video is h264, around 58 minutes. im looking to reduce that 1.5GB to something quite less as a test, with similar quality
[19:51:38 CET] <TheHumanPerson> not sure what presets to use
[19:53:51 CET] <furq> -crf controls filesize
[19:53:57 CET] <furq> higher value = smaller file
[19:55:13 CET] <TheHumanPerson> furq: okay, but how do I let ffmpeg understand the video is already encoded in h264? I don't want to encode over that, I just want to modify the encoding
[19:57:34 CET] <furq> you can't do that
[19:58:12 CET] <TheHumanPerson> then what do I do?
[19:58:24 CET] <TheHumanPerson> I've decided I want a CRF of 18 by the way, seems like a sane value
[19:58:27 CET] <furq> either deal with the current filesize or deal with the generation loss
[19:59:30 CET] <TheHumanPerson> I can deal with the current filesize, I'm just testing the options that's all
[20:00:15 CET] <TheHumanPerson> You told me I shouldn't ever try to extract the raw video, which I supposed I would then encode again
[20:01:18 CET] <furq> well that is what you're doing but ffmpeg does it internally
[20:01:51 CET] <kerio> TheHumanPerson: ffmpeg -i sourcevideo.whatever -c:a copy -c:v h264 -crf 18 destvideo.mkv
[20:06:01 CET] <TheHumanPerson> Thanks!
[21:24:15 CET] <Phi> Moop
[21:24:36 CET] <Phi> any idea how to detect if a hardware accelerated thing is usable on the platform?
[21:24:59 CET] <BtbN> if it works, it's probably supported.
[21:37:57 CET] <Phi> *faceplants*
[21:38:22 CET] <Phi> I would hope so, but I'd rather detect if it doesn't work so I can set up fallbacks
[21:38:30 CET] <kepstin> in other words, you check whether it's usable by trying to use it. If it doesn't work, do something else.
[21:39:43 CET] <pgorley> there's nothing like that with the hwaccel api
[21:40:19 CET] <pgorley> the way i do it in our own application is through a call to av_hwdevice_ctx_create and if it returns 0, it should work
[21:40:55 CET] <pgorley> if it still doesn't work, i've set up my own fallback method that reinits the AVCodecContext
[21:49:54 CET] <Phi> right-o
[21:49:56 CET] <jkqxz> If you are only decoding with proper hwaccels (dxva, vaapi, vdpau) attached to normal ffmpeg decoders, then it is already set up to use the hardware when it can and otherwise transparently fall back to using software.
[21:50:20 CET] <Phi> well, I'm going to be using Intel QSV, and if not, fall back on libx264
[21:50:44 CET] <jkqxz> The standalone decoders (cuvid, qsv, ...) do require you to do that yourself manually, since they don't work alongside the ffmpeg software decoders.
[22:03:17 CET] <Phi> the thing is, Intel QSV will fall back by itself if it's not supported
[22:15:47 CET] <Phi> which is bad, because then libx264 won't be used, sob sob
[22:24:39 CET] <Phi> okay, I did configure with enable-hwaccel=h264_qsv, but nothing
[22:25:16 CET] <jkqxz> What platform are you building on?
[22:25:23 CET] <Phi> MinGW, the funnest one
[22:25:31 CET] <jkqxz> (The option you want is --enable-libmfx.)
[22:25:34 CET] <Phi> Windoze
[22:25:41 CET] <Phi> I'll chuck that in there too
[23:02:17 CET] <dkc> is there a pixel format for packed YUV422 10bpp? I only see 16 or 12bpp in AVPixelFormat
[23:05:22 CET] <kerio> does hevc support gray16?
[23:07:56 CET] <kepstin> no, but nothing stopping you from putting 16-bit grey into the luma of color video with the chroma channels left neutral.
[23:08:18 CET] <kepstin> oh, wait, i'm wrong
[23:08:27 CET] <kepstin> there is a monochrome 16 profile, huh
[23:08:28 CET] <kepstin> neat
[23:08:57 CET] <kepstin> whether you can find an encoder that supports it is the other question :)
[23:12:06 CET] <kerio> x265 doesn't :<
[23:12:27 CET] <kerio> hm what's a color profile with 16bit luma?
[23:12:45 CET] <kepstin> looks like x265 tops out at 12bit support right now
[23:13:34 CET] <kepstin> or i'm wrong about that too, need to stop looking at outdated docs
[23:13:48 CET] <furq> kepstin: yuv4**p16le
[23:13:53 CET] <furq> s/kepstin/kerio/
[23:14:04 CET] <Min> hey guys, i could need some help with a little issue ;)
[23:14:57 CET] <kerio> can i assume that a constant chroma will result in negligible space increase?
[23:15:33 CET] <furq> probably
[23:15:33 CET] <kepstin> interesting, according to the docs on https://x265.readthedocs.io/en/default/cli.html#input-output-file-options you might actually be able to do 16 bit monochrome?
[23:15:50 CET] <kepstin> they list 4:0:0 monochrome as a supported chroma subsampling
[23:16:46 CET] <kepstin> oh, the output depth does still max out at 12
[23:16:52 CET] <kerio> rip
[23:16:55 CET] <kepstin> you can give it 16bit input :/
[23:16:56 CET] <Min> so i got the following command:  ffmpeg -r 1 -loop 1 -i picture.jpg -i audio.m4a -c:v libx264 -tune stillimage -c:a aac -b:a 256k -r 1 -shortest "video.mp4"  Its working, but my output file has an extra one minute longer without audio in the end
[23:17:21 CET] <Min> *is
[23:17:26 CET] <furq> Min: use a higher -r
[23:17:47 CET] <furq> or a newer ffmpeg since iirc this was fixed
[23:18:39 CET] <Min> higher -r muliplies the render time ;I downloaded the lastest windows version today
[23:19:10 CET] <Min> but thanks, ill try other values for -r
[23:24:35 CET] <furq> oh nvm i remember how i worked around this
[23:25:03 CET] <furq> for some reason if you encode the audio in the same command it gets the length wrong
[23:25:13 CET] <furq> if your source is m4a then the audio is probably already aac, so use -c:a copy
[23:27:41 CET] <Min> I get "Could not find tag for codec alac in stream #1, codec not currently supported in container Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument" using copy instead of acc
[23:28:19 CET] <Min> already tried that earlier
[23:39:47 CET] <kibibyte> hi
[23:40:08 CET] <kibibyte> whats -bf option for ffmpeg ?
[23:41:40 CET] <llogan> Min: a dumb workaround is to add -g 1
[23:41:54 CET] <kibibyte> is it video bit frames ?
[23:43:02 CET] <llogan> "set maximum number of B-frames between non-B-frames"
[23:43:25 CET] <kibibyte> but its only for specific codec ?
[23:43:41 CET] <kepstin> it affects multiple codecs, in different ways
[23:44:31 CET] <kibibyte> hm but is same as -bsf:v ?
[23:44:47 CET] <kibibyte> bit stream filter
[23:44:52 CET] <kepstin> no, they're completely unrelated
[23:45:35 CET] <kibibyte> ok
[23:46:27 CET] <llogan> most likely you can ignore -bf. if you're encoding with x264 the preset will automatically handle it anyway
[23:46:55 CET] <Min> llogan: extra minute goes down to ~15 seconds
[23:47:12 CET] <llogan> i guess i was wrong.
[23:47:41 CET] <furq> encode it to a separate file first and then mux it in
[23:47:55 CET] <furq> alternatively, if this is for youtube then just mux the existing file into mkv because youtube don't care
[23:48:30 CET] <llogan> oh, i misread the duration when I did my single lazy ass test
[00:00:00 CET] --- Wed Nov  9 2016