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

[burek]

[00:00:10 CEST] <JEEB> I guess -x264-params "deblock=2:2" or even more?
[00:00:18 CEST] <JEEB> I'm checking what psnr tune did again
[00:01:46 CEST] <kepstin> "--aq-mode 0 --no-psy"
[00:01:50 CEST] <JEEB> yea, I found it
[00:02:32 CEST] <JEEB> although wait, x264-params won't work like that because : is the delimiter
[00:02:33 CEST] <JEEB> lol
[00:03:05 CEST] <JEEB> unless it was ","
[00:03:10 CEST] <JEEB> in which case it will work
[00:03:31 CEST] <JEEB> av_dict_parse_string(&dict, x4->x264_params, "=", ":", 0)
[00:03:40 CEST] <JEEB> yup, it was = and : so no-go with 2:2
[00:03:51 CEST] <redrabbit> its a TV>phone use case, when on the move i have to go for the lowest bitrate situation when on the move
[00:04:05 CEST] <redrabbit> so 800k is optimal, i dont get much cuts
[00:04:21 CEST] <JEEB> oh, there's an avoption for libx264
[00:04:23 CEST] <redrabbit> just 1 second or 2 when changing tower
[00:04:24 CEST] <JEEB> -deblock
[00:04:27 CEST] <kepstin> JEEB: deblock is mapped as an avoption, just use taht
[00:04:28 CEST] <kepstin> yeah
[00:04:29 CEST] <JEEB> yes
[00:04:34 CEST] <JEEB> -deblock "2:2"
[00:04:37 CEST] <JEEB> or more
[00:04:40 CEST] <JEEB> see the results and tweak
[00:04:44 CEST] <redrabbit> ok
[00:04:55 CEST] <horox> ffplay output: https://pastebin.com/Z7jV9knA
[00:05:01 CEST] <horox> test file: http://openartist.org/magiclantern/10bit.MLVFS
[00:05:12 CEST] <horox> even more samples:  http://www.magiclantern.fm/forum/index.php?topic=11899.0
[00:05:40 CEST] <kepstin> x264's defaults are designed to prefer blocking rather than smoothing on parts of the video which originally had high-frequency details
[00:06:07 CEST] <kepstin> works better on higher-res videos, where the block size is relatively smaller.
[00:07:15 CEST] <JEEB> horox: ok, so what happens is that most likely swscale cannot handle bayer_rggb16 correctly. I get the same effect because mpv doesn't handle bayer_rggb16 either
[00:07:31 CEST] <JEEB> as in, the decoding might be correct
[00:07:37 CEST] <horox> ok
[00:07:38 CEST] <JEEB> but what happens after decoding
[00:07:44 CEST] <JEEB> as in conversion to ye normal RGB
[00:07:45 CEST] <JEEB> goes bonkers
[00:07:58 CEST] <JEEB> horox: for funzies post that file on mpv's bug tracker ;)
[00:08:19 CEST] <JEEB> if you're on windows you can grab mpv from https://mpv.srsfckn.biz/ for a screenshot
[00:08:21 CEST] <horox> I also get the same color on mpv
[00:08:23 CEST] <JEEB> yea
[00:08:31 CEST] <JEEB> make an issue and attach the sample on the issue :D
[00:08:39 CEST] <JEEB> let's see if haasn bites it :P
[00:09:02 CEST] <JEEB> (he's the video renderer guy, so if he adds support for bayer_rggb16
[00:09:23 CEST] <horox> so mpv bug tracker.. I will do so, thanks!
[00:09:47 CEST] <JEEB> of course it will not fix ffmpeg's conversion, but it might give us insight into how to do it correctly :)
[00:10:10 CEST] <JEEB> because so far I've learned that that guy wants to do things Correctly
[00:11:47 CEST] <horox> nice.
[00:11:54 CEST] <horox> as for now, I use  -vf lut3d=/opt/FFplay_mlv_dump.cube posted at https://www.magiclantern.fm/forum/index.php?topic=18392.0
[00:12:49 CEST] <JEEB> that might be worth noting as well, together with any possible references on how magic lantern saves data in those files
[00:14:36 CEST] <horox> I have also used little crossplatform floss MLV App http://www.magiclantern.fm/forum/index.php?topic=20025.0 which is kind of a developer.converter for .mlv files, they get it right
[00:14:56 CEST] <JEEB> specifications are generally preferred, but sure
[00:15:11 CEST] <horox> yeah
[00:15:41 CEST] <horox> would be nice to iron that out, it disturbs me
[00:19:53 CEST] <redrabbit> -deblock 2:2 does seems to smooth it out
[00:20:20 CEST] <redrabbit> does look a bit better for low res
[00:21:47 CEST] <JEEB> seems like it's kind of specified @ http://www.magiclantern.fm/forum/index.php?topic=7122.0
[00:21:53 CEST] <JEEB> I wonder what the multimedia.cx wiki says
[00:22:48 CEST] <JEEB> not much else than the header :D https://wiki.multimedia.cx/index.php/MLV
[00:24:58 CEST] <redrabbit> Deblock has two parameters: alpha (strength) and beta (threshold)., 2 2 seems nice for my 700k avc 640*360 stream. idk if i should try other values
[00:26:39 CEST] <JEEB> if it works it works. if it's good enough why work harder :D
[00:26:48 CEST] <JEEB>  (since you're not making a "proper" test anyways)
[00:26:53 CEST] <redrabbit> yep
[00:27:14 CEST] <redrabbit> what would be proper just curious
[00:28:08 CEST] <JEEB> playing with the parameter in various ways while keeping other things static (including file size). and then doing blind tests between the results
[00:28:26 CEST] <redrabbit> oh that's far from my protocol
[00:28:51 CEST] <redrabbit> im just tuning in to tv from my mobile phone and look for artifacts / overall feeling
[00:32:14 CEST] <redrabbit> ah, looks like i can increase resolution a bit now
[00:32:18 CEST] <redrabbit> looks better
[01:02:22 CEST] <redrabbit>  -vcodec libx264 -x264-params vbv-maxrate=700:vbv-bufsize=1400:aq-mode=0:no-psy -deblock 2:2 -crf 24 -g 50 {framerate} -map 0:v:0 -map 0:a:0 -s 896x504 -preset veryslow
[01:04:33 CEST] <JEEB> maxrate and bufsize of course have global avoptions, and those latter two are just -tune psnr
[01:04:46 CEST] <JEEB> so no x264-params needed
[01:05:01 CEST] <redrabbit> works the same heh
[01:05:14 CEST] <JEEB> yes, the result should be the same
[01:05:41 CEST] <redrabbit> this is looking a lot better than my old setting
[01:05:55 CEST] <redrabbit> -vcodec libx264 -bufsize 1400k -maxrate 700k
[01:06:02 CEST] <hanna> JEEB: this would most likely be a user shader sort of thing
[01:06:04 CEST] <redrabbit> -crf 24 -g 50 {framerate} -map 0:v:0 -map 0:a:0 -s 640x360 -preset veryslow
[01:06:11 CEST] <hanna> actually I guess not
[01:06:43 CEST] <redrabbit> it does look more like HEVC
[01:06:46 CEST] <redrabbit> neat
[01:07:37 CEST] <JEEB> redrabbit: so basically until a certain point the stuff that makes higher bit rates look good start creating artifacts, which bring an image of sharpness first and then just look bad
[01:08:06 CEST] <JEEB> at that point just blurring crap the hell out actually leads to a more watchable image
[01:08:40 CEST] <JEEB> and yes, HEVC seems to have a lot of coding tools that are really simple to optimize for that, since optimizing for PSNR has similar effects
[01:08:55 CEST] <JEEB> plus x265 doesn't seem to have as much psychovisual stuff going on in general
[01:44:04 CEST] <iive> HEVC does blur the hell out of low bitrate videos. It doesn't look like artifacts, but it looks like lower resolution.
[02:04:19 CEST] <moniker-> what does term "caps" mean? as in raster caps
[02:04:53 CEST] <moniker-> limit?
[02:05:10 CEST] <moniker-> or for ex "shader caps"
[02:06:05 CEST] <drv> capabilities
[02:06:12 CEST] <moniker-> right
[02:13:00 CEST] <moniker-> i've run into a comment confirming my card amd r7 poor dxva performance running multiple streams https://ffmpeg.org/pipermail/libav-user/2015-September/008527.html
[02:13:15 CEST] <moniker-> from the comment: "With Intel (HD5500) we see 4+ 4K30 and 30+ FHD
[02:13:15 CEST] <moniker-> streams running in parallel, AMD/ATI from R7 to
[02:13:15 CEST] <moniker-> W8100 does not support 4K and is more or less unusable
[02:13:15 CEST] <moniker-> with more than 2 streams(?)."
[03:24:12 CEST] <thebombzen_> does anyone here have a recommendation for a container to put mp3 streams in? raw mp3 is really awkward
[03:35:10 CEST] <furq> m4a, mka
[03:40:59 CEST] <thebombzen_> I thought about m4a but I was worried that it might confuse players because m4a usually contains AAC
[03:41:12 CEST] <thebombzen_> or will that not really be a problem
[03:41:22 CEST] <thebombzen_> (obviously not for mpv, but I meant on mobile)
[03:42:13 CEST] <moniker-> are there any particular benefits (performance) in using ffmpeg64.dll ?
[03:43:04 CEST] <thebombzen_> you should always use 64-bit programs on a 64-bit operating system
[03:43:17 CEST] <moniker-> right
[03:45:09 CEST] <redrabbit> anybody tried staxrip
[03:46:07 CEST] <redrabbit> the nvenc stuff work wonders with ti
[03:46:16 CEST] <redrabbit> it.. i get 600+fps
[04:05:01 CEST] <furq> well yeah it's nvenc
[04:12:08 CEST] <redrabbit> output plays fine with vlc however dvbviewer seems to have micro lags.. like it stutters for fraction of seconsd
[04:12:12 CEST] <redrabbit> uploading it
[04:23:57 CEST] <redrabbit> imgpost.cf/sample.mkv
[04:31:45 CEST] <redrabbit> well mpchc works fine as well, only dvbviewer has the playback issue
[04:34:20 CEST] <Ch3ck> Anyone tried this: https://github.com/giorgisio/goav
[05:16:28 CEST] <acos> Howdy folks
[05:23:11 CEST] <redrabbit> -c:v h264_nvenc -x264-params output-depth=10 < this is strange that i have to use -x264-params but i didnt found another way to use 10 biot
[05:23:14 CEST] <redrabbit> bit*
[05:27:32 CEST] <redrabbit> https://github.com/Brainiarc7/ffmpeg-nvenc-windows-build-with-mxe/blob/master/libavcodec/libnvenc.c
[05:27:39 CEST] <redrabbit>  char *x264_params; // List of x264 options in opt:arg or opt=arg format
[05:30:10 CEST] <dkh> is that a newish feature or no?
[05:31:03 CEST] <redrabbit> well its looking like i can use x264_params to use command line parameters for nvenc
[05:31:13 CEST] <dkh> not sure what it handles, but i know ive had difficulty in the past attempting to figure out reasonable settings similar to what i would set in x264, since crf/cq are different in each
[05:31:16 CEST] <redrabbit> its just an odd syntax
[05:31:49 CEST] <dkh> yeah 10bit seems like something it ought to support on its own as well
[05:33:13 CEST] <acos> So I just exported a video I'm working on to a bunch of frames because the other export options are no good.  I'm wondering if ffpmeg will be the right tool to use to merge 5000 frames to make a video.
[05:36:17 CEST] <dkh> acos, sure
[05:36:47 CEST] <acos> It's still exporting.  Is it a long command I have to type in?
[05:37:51 CEST] <acos> It's a tiff sequence with file names 0336 to 5000
[05:39:56 CEST] <dkh> not really. `ffmpeg -i {input_pattern} -framerate 30 -vcodec libx264 {output}.mp4` or similar
[05:40:09 CEST] <acos> Do I need to use %d?
[05:42:11 CEST] <dkh> %04d.tiff in your case i think
[05:43:33 CEST] <dkh> you should also just be able to do `-pattern_type glob -i "*.tiff"` if you dont need to be precise about it
[05:43:38 CEST] <acos> Thanks dkh :) will it auto magically set frame size based on the frames?
[05:43:51 CEST] <acos> Ah I'm on Windows if that help any
[05:44:17 CEST] <dkh> you can set `-s 1280x720` or whatever if you need to scale them
[05:46:00 CEST] <acos> Cool sounds great
[05:50:08 CEST] <redrabbit> Reading option '-x264-params' & matched as AVOption 'x264-params' with argument 'output-depth=10'.
[05:50:12 CEST] <redrabbit> from my logs
[05:50:23 CEST] <redrabbit> im not sure it does work in 10 bit though
[05:51:26 CEST] <redrabbit> makes no sense that -x264-params is a parameter name with nvenc
[05:51:37 CEST] <redrabbit> but its in libnvenc.c
[05:51:50 CEST] Action: redrabbit is puzzled
[05:52:28 CEST] <acos> redrabbit: video is confusing
[05:57:51 CEST] <c3r1c3-Win> But isn't NVENC a form of x264?
[05:58:04 CEST] <c3r1c3-Win> which means it's run on the same parameters (in general)?
[05:59:38 CEST] <acos> Perhaps
[06:02:00 CEST] <dkh> it's the encoder for gpu encoding with nvidia cards
[06:02:51 CEST] <c3r1c3-Win> dkh: Yes, and it encodes a few different formats... one of them being x264...
[06:03:48 CEST] <dkh> yes, it is for x264, no, the parameters are not identical
[06:04:06 CEST] <dkh> in fact many are a few totally different concepts between them
[06:05:50 CEST] <kepstin> c3r1c3-Win: h264 is the name of a video codec, x264 and nvenc are two completely unrelated encoders that can output h264
[06:06:08 CEST] <kepstin> they options the two use are significantly different
[06:08:09 CEST] <redrabbit> looks like -profile:v main10 is the option for 10 bit, however my build doesnt support it. 'x264-params' with argument 'output-depth=10' seems to work with nvenc though idk if it does anything however
[06:08:33 CEST] <redrabbit> (my 1060 supports 10 bit but the ffmpeg build may not)
[06:08:33 CEST] <dkh> one way to find out :P
[06:08:44 CEST] <kepstin> redrabbit: assuming you're actually using nvenc, the -x264-params option should print a warning message and be ignored
[06:09:00 CEST] <dkh> haha, great
[06:09:04 CEST] <redrabbit> https://github.com/Brainiarc7/ffmpeg-nvenc-windows-build-with-mxe/blob/master/libavcodec/libnvenc.c
[06:09:08 CEST] <redrabbit> look at this
[06:09:16 CEST] <kepstin> redrabbit: that's not ffmpeg?
[06:09:17 CEST] <redrabbit> x264-params in there !
[06:09:35 CEST] <kepstin> that's some fork, ffmpeg doesn't even have a file named 'libnvenc.c'
[06:09:56 CEST] <redrabbit> strange stuff..
[06:10:03 CEST] <redrabbit> well
[06:10:49 CEST] <dkh> hadnt heard of it myself
[06:11:01 CEST] <redrabbit> im using this build https://github.com/illuspas/ffmpeg-hw-win32/tree/master/static/x86_64/bin
[06:11:32 CEST] <redrabbit> Reading option '-x264-params' & matched as AVOption 'x264-params' with argument 'output-depth=10'
[06:11:45 CEST] <redrabbit> it does take the x264-params with nvenc
[06:11:48 CEST] <redrabbit> :|
[06:12:09 CEST] <kepstin> well, i have no idea what that build is and can't support it
[06:12:49 CEST] <redrabbit> np
[06:13:32 CEST] <acos> I got my build from the official site.  Let's see if these tifs will merge to a video
[06:13:48 CEST] <kepstin> it looks like ffmpeg can do 10bit with nvenc_hevc, but not nvenc_h264
[06:14:09 CEST] <kepstin> assuming hardware support, of course.
[06:15:56 CEST] <kepstin> it looks like no nvidia hardware has ever supported 10bit h264 encoding
[06:16:21 CEST] <acos>  Cpu encode it?
[06:17:44 CEST] <kepstin> cpu encoding is generally preferred if possible, the software encoders give better quality at the same bitrate than hardware in general
[06:18:10 CEST] <kepstin> pretty much the main reason to use a hw encoder is if your cpu is busy doing something else
[06:19:15 CEST] <acos> Ah.  I walk away from my laptop during encodes and move to desktop.
[06:20:09 CEST] <notdaniel> well yeah, i mean you use nvenc to do it faster and using the gpu :P
[06:20:33 CEST] <notdaniel> saved us a loooot of money switching to nvenc, but yeah, the issue is getting the quality settings ideal
[06:21:34 CEST] <acos> Ya it's hard to get settings just right
[06:22:44 CEST] <notdaniel> still havent gotten them right
[06:23:12 CEST] <acos> I'm just trying basic h264 haha
[06:23:17 CEST] <notdaniel> 4 million encodes later or something
[06:23:52 CEST] <acos> Wow.  Hope you find the settings
[06:24:20 CEST] <notdaniel> haha yeah seriously
[06:24:29 CEST] <kepstin> x264 is a lot easier to tweak, for most use cases you just pick a rate control method, and a value for "-preset" that meets your speed requirements
[06:24:57 CEST] <kepstin> with nvenc... you're probably not gonna do better than "ok", and there's fewer things you can tweak with hw encoders.
[06:24:58 CEST] <acos> My videos look too blocky
[06:25:17 CEST] <acos> Ok I think these frames are ready to encode
[06:25:35 CEST] <notdaniel> nvenc is a harsh mistress of its own
[06:26:46 CEST] <acos> Only took 30 min to export 4213 frames it a 9.88gb. Now to move to h264
[06:28:18 CEST] <kepstin> huh, that's not really all that many frames, for such a huge file size. Only ~3 minutes of video at 24fps.
[06:31:37 CEST] <acos> Ugh globbing not supported
[06:36:36 CEST] <acos> Wow it seems to be working.
[06:41:05 CEST] <redrabbit> -c:v hevc_nvenc -profile:v main10 > works
[06:41:30 CEST] <redrabbit> while main10 and h264_nvenc wont
[06:42:12 CEST] <redrabbit> so i'm using
[06:42:13 CEST] <redrabbit> -c:v h264_nvenc -x264-params output-depth=10
[06:42:24 CEST] <redrabbit> and it works, well it outputs stuff.
[06:42:32 CEST] <redrabbit> idk if it does use 10bit !
[06:43:06 CEST] <acos> My video says yuv444p
[06:43:12 CEST] <acos> Is that bad?
[06:43:36 CEST] <acos> It also looks like it's making a 25fps I told it to be 29.97
[06:47:23 CEST] <acos> Why is the video 25fps?
[06:47:47 CEST] <redrabbit> notdaniel: can you share your nvenc settings
[06:49:05 CEST] <acos> I used the -framerate command
[06:49:10 CEST] <acos> It didn't work at all
[06:49:46 CEST] <acos> Changing it to -r seemed to work
[06:49:51 CEST] <notdaniel> acos, may need to set -r to actually force it
[06:49:52 CEST] <notdaniel> yeah
[06:49:57 CEST] <notdaniel> 29.97 blows though
[06:50:26 CEST] <redrabbit> 06:15 < kepstin> it looks like no nvidia hardware has ever supported 10bit h264 encoding > StaxRip does have the 10Bit option with AVC and nvenc
[06:50:31 CEST] <acos> Well that's what I shot it at. Trying to keep same format
[06:51:00 CEST] <redrabbit> "--output-depth 10"
[06:51:02 CEST] <acos> Will YouTube accept a 444p file?
[06:51:45 CEST] <acos> I probably should have set camera to 24p
[06:53:32 CEST] <redrabbit> notdaniel: also how do you use nvenc ?
[06:53:56 CEST] <redrabbit> only ffmpeg or straight up nvenc / both
[06:54:50 CEST] <redrabbit> -c:v h264_nvenc -x264-params output-depth=10 -b:v 3500k -maxrate 3500k -rc vbr_2pass -rc-lookahead 32 < current settings
[06:55:51 CEST] <acos> What's current version? Is it bad I'm using 20170718-012620a win64 static?
[07:00:37 CEST] <acos> Why does ffmpeg say dupe frames. It cut some off the video.
[07:03:23 CEST] <acos> Wow. Mixed the frame numbers up. Sw works great.
[07:06:12 CEST] <jnollette> hey everyone - can yall help me out - i am curious about HE-AAC... I see it in itunes, but want to compress audio, and can't find the flags or info
[07:06:26 CEST] <jnollette> any shared experiance would be helpful
[07:16:10 CEST] <notdaniel> here's the big part of our encoding command: https://ghostbin.com/paste/x3ogz
[07:16:12 CEST] <notdaniel> redrabbit
[07:18:16 CEST] <notdaniel> using it on ec2 gpu instances
[07:20:16 CEST] <notdaniel> looks like 56 of them at the moment. would be so much worse and more expensive with x264
[07:22:21 CEST] <acos> Wow
[08:11:00 CEST] <wani> why would this work:  ffmpeg -i new.mkv -c copy -ss 00:10:06.230 -t 00:00:8.175 output.mkv
[08:11:11 CEST] <wani> but this not ffmpeg -i new.mkv -c:v libvpx-vp9 -crf 30 -b:v 0 -c:a libvorbis -ss 00:10:06.230 -t 00:00:8.175 output.mkv
[08:12:17 CEST] <wani> well it just starts encoding but never gets past the first frame, just repeats frame=    0 fps=0.0 q=0.0 Lsize=       7kB time=00:00:00.00 bitrate=N/A speed=   0x
[09:18:12 CEST] <_julian> morning
[09:18:37 CEST] <_julian> is it allowed to change the codecpar struct in an AVStream on the fly to signal a format change of this stream?
[17:12:25 CEST] <acos> Thanks for the help last night everyone.  I got my video out.
[18:01:36 CEST] <Hopper_> Mornin' FFMPEG, anyone available to help me refine my video stream?
[18:10:08 CEST] <Hopper_> I am running FFMPEG on a LattePanda (A single board comp similar to the RaspberryPi, but running windows), and I am having issues with framerate and CPU usage.
[18:10:57 CEST] <Hopper_> Here is my current command: https://pastebin.com/WSHBpBEF
[18:14:32 CEST] <furq> Hopper_: the default codec for mpegts is mpeg2video
[18:14:42 CEST] <furq> if you want to use x264 then add -c:v libx264
[18:14:58 CEST] <Hopper_> Which SHOULD I use?
[18:15:05 CEST] <furq> shrug
[18:15:07 CEST] <furq> probably x264 on that cpu
[18:15:14 CEST] <Hopper_> Lower demand?
[18:15:15 CEST] <furq> i don't think the m2v encoder is multithreaded
[18:15:42 CEST] <Hopper_> It seems to increase usage on the cpu 2x when I add -=threads 0
[18:16:07 CEST] <furq> nvm i guess it does slice threading
[18:16:07 CEST] <Hopper_> And "-c:v libx264" is an output command?
[18:16:12 CEST] <furq> yes
[18:16:47 CEST] <furq> if x264 ultrafast is too slow then you're probably going to have to capture at a lower resolution
[18:17:18 CEST] <furq> i assume capturing lossless and then encoding later is out of the question on an sbc
[18:17:39 CEST] <Hopper_> Yes, this is broadcast OTA from an airborne device.
[18:18:04 CEST] <redrabbit> use hw encoders
[18:18:30 CEST] <redrabbit> you wont have enough cpu on an ARM board for encoding
[18:18:35 CEST] <furq> it's not arm
[18:18:37 CEST] <furq> it's an atom x8300
[18:18:40 CEST] <redrabbit> well, its weak
[18:18:46 CEST] <furq> which doesn't have quicksync
[18:18:54 CEST] <furq> oh wait
[18:18:55 CEST] <furq> maybe it does
[18:18:59 CEST] <redrabbit> even the rpi has hw encoders heh
[18:19:12 CEST] <redrabbit> even the rpi0, 5$ board :p
[18:19:23 CEST] <furq> well yeah but the pi's hw encoding is practically useless
[18:19:38 CEST] <redrabbit> its for the webcam
[18:19:44 CEST] <redrabbit> works mkay
[18:20:39 CEST] <Hopper_> Well "-c:v libx264" seems to maintain the same CPU usage, but does help with the framerate coming from one of the webcams.
[18:21:44 CEST] <furq> https://ark.intel.com/products/87383/Intel-Atom-x5-Z8300-Processor-2M-Cache-up-to-1_84-GHz
[18:21:56 CEST] <furq> no quicksync mentioned here but someone on a forum claims it does actually have it
[18:22:05 CEST] <furq> using quicksync on windows is some kind of nightmare though
[18:22:30 CEST] <furq> Hopper_: if those are usb3 webcams you might want to use rawvideo as input instead of mjpeg
[18:22:41 CEST] <furq> that won't work with usb2 though
[18:23:43 CEST] <Hopper_> Here are my options for both cams. https://pastebin.com/vizvERZh
[18:25:59 CEST] <Hopper_> furq: I can't capture raw with one of my devices.
[18:26:18 CEST] <furq> you can't do it with either
[18:26:41 CEST] <furq> oh wait nvm i'm reading the wrong column
[18:27:16 CEST] <furq> actually no i'm not. they both do 1080p rawvideo but only at 5fps
[18:27:23 CEST] <furq> so i'm guessing they're usb2
[18:28:00 CEST] <furq> i doubt that'll make a huge difference on an atom anyway
[18:28:27 CEST] <Hopper_> Hm, I wonder what my limitation is.
[18:29:44 CEST] <furq> that's a 4W CPU, it's never going to be good at this sort of thing
[18:30:16 CEST] <Hopper_> I know, but at a previous point in this project I was running similar encoding on the same board but running debian and it was performing better.
[18:30:56 CEST] <Hopper_> Well also, I'm tasting the code currently on my desktop and I'm still having the framerate issue.
[18:31:15 CEST] <furq> what's the issue
[18:31:21 CEST] <furq> i take it it's just not encoding at 30fps
[18:31:42 CEST] <Hopper_> Correct, one cam seems to be at full speed, but the c920 is at a low framerate.
[18:31:56 CEST] <furq> does it happen when you capture from that cam by itself
[18:32:36 CEST] <Hopper_> No, but it does look pixelated and bad.
[18:37:39 CEST] <Hopper_> I wonder what was different before.
[18:41:40 CEST] <Hopper_> furq, redrabbit:  Any clever ways to reduce overhead?
[18:44:33 CEST] <furq> not that i didn't already mention
[18:45:09 CEST] <furq> unless that cpu does actually support quicksync, in which case use that instead of x264
[18:45:09 CEST] <Hopper_> Well, Thanks!  You gave me a great starting point.
[18:45:21 CEST] <Hopper_> I can at least try, right?
[18:47:14 CEST] <furq> that build has libmfx, so i guess try -c:v h264_qsv
[18:47:28 CEST] <furq> not sure if you need anything else for it to work
[18:48:07 CEST] <Hopper_> So why would I be getting the framerate issue on my i5 desktop?
[18:48:49 CEST] <furq> oh right
[18:48:54 CEST] <furq> maybe some issue with dshow
[18:49:27 CEST] <furq> if you're not maxing out your cpu then there's probably some kind of capture issue
[18:49:40 CEST] <Hopper_> Hm, okay
[19:57:35 CEST] <rjp421> anyone with a pi and pi-cam, and updated packages+kernel+ffmpeg-git:  can you please test piping raspivid to ffprobe or ffmpeg?  confirm whether or not ffmpeg crashes (pls let me know results so i can stop spamming this)
[20:06:28 CEST] <relaxed> rjp421: can you pastebin.com the command and console output
[20:11:20 CEST] <rjp421> relaxed, i pasted it a few days ago, i will try to find the link.. sdcard is shot, so i cant get the original cmd from it... but 'raspivid <options> -o - | ffprobe -i -' i think should work
[20:15:42 CEST] <relaxed> what is raspivid piping?
[20:17:17 CEST] <rjp421> relaxed, not sure exactly, but i think h264..
[20:18:12 CEST] <rjp421> furq, JEEB, pls post my last pastebin link if you happen to have it still (im still looking)
[20:22:59 CEST] <relaxed> rjp421: you probably need something like,  raspivid <options> -o - | ffmpeg -f h264 -framerate $fps - ...
[20:23:44 CEST] <relaxed> er, that should have been "-i - ..."
[20:24:02 CEST] <rjp421> relaxed, the same cmd that crashed had been working fine, before i went and updated packages+kernel
[20:26:34 CEST] <relaxed> you can't test this now?
[20:28:38 CEST] <rjp421> relaxed, i need a new sdcard for the pi before i can test :(
[20:31:47 CEST] <relaxed> to get proper support you should wait until then
[20:33:56 CEST] <rjp421> i may not be the only one who needs it fixed, hence hoping it can be tested before i am able to (which may be a while)
[20:35:37 CEST] <relaxed> when you're back in action, see if my arm builds make any difference -> https://www.johnvansickle.com/ffmpeg/
[20:36:23 CEST] <rjp421> cool, ty :)
[20:40:05 CEST] <lindylex> I am using the following to generate a video that is side by side.   ffmpeg -i left.mp4 -i right.mp4 -filter_complex "[0:v]setpts=PTS-STARTPTS, pad=iw*2:ih[bg]; [1:v]setpts=PTS-STARTPTS[fg]; [bg][fg]overlay=w" -y final.mp4  I would like to place a vertical black line on top right in the middle or add a black border to the video on the left.  If I add a border to the left video I would like to maintain the original sum dimension
[20:40:05 CEST] <lindylex> of the original videos.  This solution would require subtracting the border width from the left videos width.  I will take either solution.
[20:53:36 CEST] <ZoeB> Hi!  When transcoding one file to another with ffmpeg, is it possible to custom map the specific metadata tags?  I'm batch converting FLACs to MP3s and would love to be able to set ALBUMARTISTSORT in the source to ARTIST in the output etc.
[20:55:59 CEST] <relaxed> lindylex: use cut,pad on both left and right
[20:56:15 CEST] <relaxed> I meant crop,pad
[20:57:44 CEST] <rjp421> relaxed, found the paste https://pastebin.com/raw/2zycD73c
[20:58:33 CEST] <rjp421> relaxed, oops wrong one, sorry. sec
[20:59:04 CEST] <rjp421> https://pastebin.com/raw/hWRK9dVC  and https://pastebin.com/raw/APRbBSgw
[21:01:03 CEST] <relaxed> can't do much until your system is back up
[21:01:21 CEST] <rjp421> that was with an old /opt/vc (incl raspivid), which i was updating when the sdcard crapped out
[21:05:15 CEST] <lindylex> relaxed: I am having some issue trying to add this to the filter.  Let me show you what I am trying.
[21:09:41 CEST] <lindylex> relaxed: This is what I tried ffmpeg -i c4.mov -i c5.mov -filter_complex "[0:v]setpts=PTS-STARTPTS, pad=iw*2:ih[bg], crop=1000:720:0:0; [1:v]setpts=PTS-STARTPTS[fg]; [bg][fg]overlay=w" -y final.mp4  It cuts the width from the original video and does not combine them.
[21:29:11 CEST] <furq> rjp421: i don't have a pi cam
[21:31:05 CEST] <rjp421> furq, i found the paste, nvm :p
[21:34:55 CEST] <lindylex> How do i crop the video to the left before placing them side by side?  ffmpeg -i c4.mov -i c5.mov -filter_complex "[0:v]setpts=PTS-STARTPTS, pad=iw*2:ih[bg], crop=1000:720:0:0; [1:v]setpts=PTS-STARTPTS[fg]; [bg][fg]overlay=w" -y final.mp4
[21:35:24 CEST] <lindylex> This crops the left video but it does not combine the videos.
[21:37:42 CEST] <furq> move crop before [bg]
[21:37:51 CEST] <furq> also you probably want to use hstack instead of pad+overlay
[21:47:41 CEST] <lindylex> Can you explain what is hstack?
[21:49:07 CEST] <llogan> a filter for horizontal stacking of video: https://ffmpeg.org/ffmpeg-filters.html#hstack
[21:50:10 CEST] <llogan> it's faster and easier than using pad+overlay
[21:57:29 CEST] <lindylex> something like this?  ffmpeg -i c4.mov -i c5.mov -filter_complex "[0:v][1:v] crop=1000:720:0:0 ,hstack[v];[0:a][1:a]amerge=inputs=2[a]" -map "[v]" -map "[a]" -ac 2 -y f2.mp4
[21:58:00 CEST] <lindylex> It fails and does nothing.  How do I target the left video for cropping?
[21:59:09 CEST] <furq> hstack goes first
[21:59:31 CEST] <furq> hstack,crop;amerge
[22:00:30 CEST] <furq> actually, if you're cropping the right side off the left-hand video, then that doesn't work
[22:01:01 CEST] <lindylex> Yes this is what i want to do and add a black 2 pixel border.
[22:01:04 CEST] <furq> [0:v]crop=1000:720[tmp0];[tmp0][1:v]hstack[out]
[22:04:42 CEST] <lindylex> furq: this throws an error :  ffmpeg -i c4.mov -i c5.mov -filter_complex "[0:v]crop=1000:720[tmp0];[tmp0][1:v]hstack[out];[0:a][1:a]amerge=inputs=2[a]" -map "[v]" -map "[a]" -ac 2 -y f2.mp4
[22:05:03 CEST] <lindylex> error  :  Output with label 'v' does not exist in any defined filter graph, or was already used elsewhere.
[22:06:33 CEST] <furq> change out to v
[22:06:42 CEST] <lindylex> I just saw that.
[22:08:06 CEST] <lindylex> Ok I think I get what you are doing.
[22:24:40 CEST] <lindylex> I think I understand but this does not work ::  ffmpeg -i c4.mov -i c5.mov -filter_complex "[0:v]crop=300:720[tmp0]; [tmp0]pad=298:720:0:0:black[tmp0]; [tmp0][1:v]hstack[v];[0:a][1:a]amerge=inputs=2[a]" -map "[tmp0]" -map "[a]" -ac 2 -y f2.mp4
[22:25:09 CEST] <lindylex> I am trying to crop the video on the left to leave a black border on the right.'
[22:27:50 CEST] <lindylex> Thought this might work ffmpeg -i c4.mov -i c5.mov -filter_complex "[0:v]crop=300:720, pad=0:0:-2:0:black[tmp0];[tmp0][1:v]hstack[v];[0:a][1:a]amerge=inputs=2[a]" -map "[v]" -map "[a]" -ac 2 -y f2.mp4
[22:33:15 CEST] <furq> lindylex: crop,pad
[22:33:40 CEST] <furq> if one filter's output goes straight to the next filter's input, use ,
[22:33:54 CEST] <furq> you only need labels and ; if you want different inputs to the next filter
[22:35:19 CEST] <lindylex> furq :  ffmpeg -i c4.mov -i c5.mov -filter_complex "[0:v]crop=300:720, pad=0:0:-2:0:black[tmp0];[tmp0][1:v]hstack[v];[0:a][1:a]amerge=inputs=2[a]" -map "[v]" -map "[a]" -ac 2 -y f2.mp4  This passes the crop to the padding correct using commas?
[22:35:34 CEST] <furq> should do
[22:37:02 CEST] <lindylex> If the left video is 300:720 I want to add 2 pixel of black to the right of left video witha final left video output of 300:720 not 302:702
[22:37:25 CEST] <lindylex> This is why I tried this ::  ffmpeg -i c4.mov -i c5.mov -filter_complex "[0:v]crop=300:720[tmp0]; [tmp0]pad=298:720:0:0:black[tmp0]; [tmp0][1:v]hstack[v];[0:a][1:a]amerge=inputs=2[a]" -map "[tmp0]" -map "[a]" -ac 2 -y f2.mp4
[22:38:00 CEST] <lindylex> sorry wait that is a mistake one sec
[22:39:02 CEST] <lindylex> furq : This is what I am trying ::  ffmpeg -i c4.mov -i c5.mov -filter_complex "[0:v]crop=300:720, pad=298:720:2:0:black[tmp0];[tmp0][1:v]hstack[v];[0:a][1:a]amerge=inputs=2[a]" -map "[v]" -map "[a]" -ac 2 -y f2.mp4
[22:43:22 CEST] <lindylex> I think I got it  ::  ffmpeg -i c4.mov -i c5.mov -filter_complex "[0:v]crop=300:720, pad=352:720:2:0:black[tmp0];[tmp0][1:v]hstack[v];[0:a][1:a]amerge=inputs=2[a]" -map "[v]" -map "[a]" -ac 2 -y f2.mp4
[22:43:41 CEST] <lindylex> furq : Thanks
[22:43:47 CEST] <lindylex> llogan: thanks
[22:43:58 CEST] <lindylex> relaxed : thanks
[23:00:23 CEST] <Hopper_> furq: Should I use this as an example for drawing a text overlay from a file on my video which updates regularly?  http://ffmpeg.gusari.org/viewtopic.php?f=11&t=1897
[23:04:10 CEST] <furq> sure?
[23:05:13 CEST] <Hopper_> so drawtext will update from a .txt file?
[23:08:56 CEST] <furq> it will with reload=1
[23:10:33 CEST] <Hopper_> Hm, so I have to figure out how to write my .txt atomically.
[23:12:48 CEST] <BtbN> write it somewhere else, then mv
[23:13:03 CEST] <BtbN> on the same fs
[00:00:00 CEST] --- Thu Sep 28 2017