[Ffmpeg-devel-irc] ffmpeg.log.20190816
burek
burek at teamnet.rs
Sat Aug 17 03:05:03 EEST 2019
[00:11:29 CEST] <LigH> Hi
[00:12:06 CEST] <LigH> Are there any guidelines regarding including the ffmpeg logo into the logo of a project that is tightly related to ffmpeg?
[00:22:54 CEST] <pink_mist> LigH: https://en.wikipedia.org/wiki/File:FFmpeg_Logo_new.svg claims that the logo is too simple to meet requirements for copyright, and thus it is in the public domain ... whether or not wikipedia is correct in this assessment is something I'd leave to a lawyer though
[00:24:31 CEST] <LigH> Wouldn't mind asking an official for agreement if I knew who.
[00:24:56 CEST] <LigH> I hope there are some official lines about it.
[00:24:56 CEST] <pink_mist> I believe the original creator of the logo is Hervé Flores
[00:25:28 CEST] <pink_mist> ah yes, wikipedia agrees
[00:26:19 CEST] <LigH> Not today anymore ... GN8
[00:26:26 CEST] <LigH> Thanks so far
[02:13:12 CEST] <nicolas17> how far back can a frame reference another in h264 and h265?
[02:20:41 CEST] <furq> nicolas17: 16 frames (or 32 fields)
[02:20:53 CEST] <furq> that's the maximum, it's normally less
[02:22:18 CEST] <furq> i think hevc maxes out at 8
[02:22:29 CEST] <nicolas17> they reduced it? :/
[02:23:43 CEST] <furq> looks like it
[02:24:42 CEST] <furq> you can set >8 in x265 but it'll produce a noncompliant bitstream with no profile/level set
[02:25:20 CEST] <MoziM> i edited a video, exported it, then ran a hash check on it, i made another video the same exact way and it fails the hash check... any idea why they differ?
[02:25:46 CEST] <furq> are you checking the hashes of the files or the streams
[02:26:22 CEST] <MoziM> files
[02:26:26 CEST] <MoziM> the output videos
[02:26:30 CEST] <furq> there's probably some creation date metadata then
[02:26:38 CEST] <nicolas17> I wonder if there's any codec with even farther reference frames
[02:26:50 CEST] <MoziM> furq: but the video itself should be the same right?
[02:26:57 CEST] <furq> you'd hope
[02:27:00 CEST] <furq> you can check with the hash muxer
[02:27:19 CEST] <MoziM> hash muxer?
[02:27:32 CEST] <furq> -i video1 -i video2 -map 0:v -f hash - -map 1:v -f hash -
[02:27:52 CEST] <nicolas17> I was thinking, if the encoder could selectively mark frames as "this will be a reference frame", the decoder could keep the last 8 *marked* frames in memory (instead of last 8), and that would allow them to be arbitrarily far back (well, limited to *encoder* memory)
[02:28:15 CEST] <nicolas17> but I'm probably missing some obvious reason why all this wouldn't work ^^
[02:28:20 CEST] <furq> vp9 is capped at 8 as well
[02:28:34 CEST] <furq> it's rare to actually be able to use >8 in h264 anyway
[02:28:47 CEST] <furq> since you're normally stuck at level 4.1 for hwdec compliance
[02:28:53 CEST] <furq> which is like 3 refs at 1080p
[02:29:26 CEST] <furq> i assume hevc/vp9 capping at 8 is just to avoid the whole mess of hardware decoders that plagued h264 for a long time
[02:29:31 CEST] <furq> or help avoid
[02:31:10 CEST] <nicolas17> I think av1 limits at 8 too
[02:31:27 CEST] <furq> seems likely considering how much lineage it takes from vp9
[02:31:59 CEST] <furq> you normally hit diminishing returns pretty hard at that point anyway
[02:33:42 CEST] <nicolas17> I was thinking of cases where scene 1 and scene 3 are very similar, such that the first frame of scene 3 could predict from the last frame of scene 1 instead of being an I frame, but currently that only works if scene 2 is shorter tha 8 frames
[03:48:04 CEST] <nicolas17> x265 docs say a keyframe interval of -1 will trigger "A special case of infinite-gop (single keyframe at the beginning of the stream)"
[03:48:12 CEST] <nicolas17> but passing -g -1 to ffmpeg didn't seem to do that
[03:49:08 CEST] <kepstin> MoziM: note that x264 isn't deterministic when using frame threading. so you can get different video streams from that.
[03:57:30 CEST] <nicolas17> -x265-params "keyint=-1" this works
[04:45:23 CEST] <AiNA_TE> is there someway to specify input resolution with a direct show device?
[06:11:07 CEST] <bobbertson> Hello, how is it going.
[06:11:25 CEST] <bobbertson> getting an error when trying to stream to vaugnlive with ffmpeg "av_interleaved_write_frame(): Operation not permitted"
[06:12:20 CEST] <bobbertson> the command I am running "/usr/bin/ffmpeg -f x11grab -s 1280x768 -framerate 30 -i :0.0 -c:v libx264 -preset fast -s 1280x768 -b:v 1000k -f flv "rtmp://live.vaughnsoft.net/live/live_***"
[06:47:39 CEST] <logicWEB> hello :-) I have been asked to make a video compilation of about 40 short videos. I just took a poke at them, and they're a random distribution of 23.976, 25 and 29.97 FPS. what is my best option for combining these into one consecutive video?
[07:48:00 CEST] <pk08> hi
[07:48:21 CEST] <pk08> sorry for the off topic question
[07:48:53 CEST] <pk08> I am trying to compile and install mpv in headless Centos 7, but i am getting error in opengl code: /video/out/opengl/common.h error: unknown type name GLchar in "GLsizei, const GLchar *,const void *);"
[07:48:53 CEST] <pk08> configure command and output: https://pastebin.com/dEM2S599
[07:48:53 CEST] <pk08> compilation output: https://pastebin.com/7wBz3Uvi
[07:48:53 CEST] <pk08> i can compile of i disable gl but i want to use nvidias hardware acceleration (CUDA hwaccel) so i need to have opengl enabled.
[07:48:55 CEST] <pk08> can anyone help me to solve this?
[07:49:23 CEST] <pk08> and i have installed ffmpeg with hwaccell using this https://trac.ffmpeg.org/wiki/CompilationGuide/Centos
[16:01:16 CEST] <logicWEB> so I asked my question last night and then I went to bed and found my computer had restarted automatically for updates overnight. hooray! the public logs don't seem to be entirely complete/up-to-date, so I'm not aware of any way to see if I got replies overnight :-(
[16:05:01 CEST] <pink_mist> you didn't get any replies overnight
[16:06:29 CEST] <logicWEB> thanks :-)
[16:07:28 CEST] <danilo82> hello, i want to record the screen with h264_vaapi, but how can i record the audio too?
[16:16:26 CEST] <durandal_1707> os?
[16:26:16 CEST] <danilo82> shoot
[16:26:26 CEST] <danilo82> i lost the chat
[16:27:21 CEST] <danilo82> so i asked for help to record the screen with vaapi and record the internal audio
[16:30:16 CEST] <durandal_1707> os?
[16:34:51 CEST] <danilo82> linux
[16:48:46 CEST] <c_14> danilo82: alsa or pulse?
[16:51:35 CEST] <danilo82> i want to record pulse audio
[16:51:48 CEST] <danilo82> to not mess with alsa
[16:52:12 CEST] <c_14> create a monitor device on the pulse output using pavucontrol or something and then use -f pulse -i <device_name.monitor>
[16:55:02 CEST] <danilo82> :T wot
[16:56:14 CEST] <kepstin> in most cases the monitor should already exist, just look for the monitor device for your main audio device in `pacmd list-sources` and grab the stuff out of the <> in the name field, use that as the input device to ffmpeg.
[17:16:09 CEST] <danilo82> ok got the idea
[17:16:09 CEST] <danilo82> i'm using this command
[17:16:09 CEST] <danilo82> ffmpeg -vaapi_device /dev/dri/renderD128 -f x11grab -video_size 1366x768 -i :0 -vf 'hwupload,scale_vaapi=format=nv12' -c:v h264_vaapi -qp 24 output.mp4
[17:16:09 CEST] <danilo82> where should i put the pulse thing?
[17:24:05 CEST] <durandal_1707> after ffmpeg
[17:25:06 CEST] <danilo82> :P this way will have two " -f "
[17:25:09 CEST] <danilo82> is this right?
[17:25:14 CEST] <furq> yes
[17:25:17 CEST] <furq> one for each input
[17:26:12 CEST] <danilo82> ok
[17:28:36 CEST] <danilo82> good good
[17:28:40 CEST] <danilo82> now it works
[17:28:41 CEST] <danilo82> :)
[17:29:12 CEST] <danilo82> aye
[17:29:13 CEST] <danilo82> should i use x11grab or KMS?
[17:29:13 CEST] <danilo82> what is better?
[17:54:23 CEST] <danilo82> [kmsgrab @ 0x55a0b7bdcf80] No handle set on framebuffer: maybe you need some additional capabilities?
[17:54:24 CEST] <danilo82> pipe:: Invalid argument
[17:54:24 CEST] <danilo82> i get this every time
[18:37:51 CEST] <durandal_1707> i do not think you can use vaapi with kmsgrab
[18:39:41 CEST] <BtbN> vaapi should be able to take drm handles as input somehow
[18:39:50 CEST] <BtbN> There might be a mapper-filter for that
[18:40:41 CEST] <danilo82> i think so
[18:40:41 CEST] <danilo82> but in the site sais that kmsgrab uses less CPU so i want to use
[18:40:41 CEST] <danilo82> but i sdon't know how
[18:49:00 CEST] <DHE> ksmgrab requires DRM, so I suspect it wouldn't work if you were using an nVidia card with the binary nvidia driver for example.
[18:52:12 CEST] <BtbN> nvidia also uses drm though
[18:52:19 CEST] <BtbN> It literally comes with a Kernel module called nvidia-drm
[19:28:39 CEST] <kepstin> someone tried this a couple weeks ago, the nvidia drm module doesn't implement the required kms interfaces for the kmsgrab stuff to work
[19:28:50 CEST] <kepstin> couple of weeks? maybe a month or so, anyways.
[21:51:16 CEST] <degenerate> hey guys
[21:52:19 CEST] <degenerate> lets say i've got a junky video with a lot of noise in it (from a small CCD and low light conditions) sample here: https://uccdn.bid13.com/original_videos/i/L/iLW4ic6u7jhcDpf8ZjTrrP8CRvpBO13bJcnfWLj8Dum.mov
[21:52:35 CEST] <degenerate> is there any sort of filters i could run with FFMPEG to make it less noisy?
[21:53:13 CEST] <nicolas17> there's several denoising filters, I guess you'll have to experiment
[21:53:46 CEST] <degenerate> secondary question is there a way to detect "noise"... so i don't denoise every video, just the ones that "need" it
[22:37:17 CEST] <Oldest> why does ffmpeg support wmv to mkv but mkvtool does not
[22:37:47 CEST] <c_14> because mkvtool isn't meant to support wmv
[22:38:15 CEST] <Oldest> c14 it supports mp4 to mkv
[22:38:31 CEST] <degenerate> harumph: [AVFilterGraph @ 0x7f97225013e0] No such filter: 'fftdnoiz'
[22:38:39 CEST] <degenerate> do i need to compile it for support of this filter?
[22:39:13 CEST] <danilo82> me back here
[22:39:14 CEST] <danilo82> anyone know how to use kmsgrab?
[22:39:21 CEST] <furq> degenerate: it's new in 4.1
[22:39:24 CEST] <degenerate> ah
[22:39:37 CEST] <degenerate> i see: ffmpeg version 3.4.2
[22:39:46 CEST] <degenerate> time to upgrade :P
[22:39:46 CEST] <furq> try hqdn3d or nlmeans
[22:39:49 CEST] <furq> those are both popular
[22:44:22 CEST] <degenerate> Thanks furq, btw, do you know the answer to my question above as well, what would be the best way to denoise a video, and is there a way to detect noise before applying the filter?
[22:46:07 CEST] <kepstin> i can't really think of anything other than running the denoise filter and checking the psnr between the funfiltered and filtered video. bigger numbers means the filter did more work
[22:46:34 CEST] <kepstin> you could do that on sample segments of the video, and throw out the decoded video rather than re-encode it.
[22:48:25 CEST] <degenerate> thanks
[22:49:54 CEST] <Oldest> why does ffmpeg support wmv to mkv but mkvtool does not?
[22:50:45 CEST] <danilo82> what is mkvtool?
[22:51:37 CEST] <Oldest> https://en.wikipedia.org/wiki/MKVToolNix
[22:52:03 CEST] <pink_mist> Oldest: because mkvtool is for mkvs
[22:52:07 CEST] <pink_mist> hint: it's in the name
[22:52:27 CEST] <kepstin> Oldest: ffmpeg is a general multimedia tool with a goal of being able to read and decode pretty much every video format ever. mkvtoolnix is a tool for making mkvs, which can read some popular other formats as a convenience.
[22:52:37 CEST] <Oldest> pink_mist that's silly, you are implying that mkvtool should only able to do mkv to mkv then
[22:52:52 CEST] <Oldest> mkvtool can do mp4 to mkv
[22:53:13 CEST] <durandal_1707> ask mkvtool devs
[22:53:38 CEST] <Oldest> durandal_1707 you are right, i should
[23:44:23 CEST] <danilo82> ok, i used "sudo ffmpeg -f kmsgrab -i - -vf 'hwdownload,format=bgr0' output.mp4" because it needed something like that, i can make a video but the image is completely scranbled :| i'm almost there
[23:45:56 CEST] <danilo82> oh "Capture from the first active plane, download the result to normal frames and encode. This will only work if the framebuffer is both linear and mappable - if not, the result may be scrambled or fail to download."
[23:46:38 CEST] <danilo82> so how can i make the framebuffer linear and mappable
[00:00:00 CEST] --- Sat Aug 17 2019
More information about the Ffmpeg-devel-irc
mailing list