[Ffmpeg-devel-irc] ffmpeg.log.20190708
burek
burek021 at gmail.com
Tue Jul 9 03:05:02 EEST 2019
[01:57:40 CEST] <Kozi> hi
[01:58:59 CEST] <Kozi> finally... I have a question: can I remove specific subtitles from .mkv files (based on their language) with ffmpeg, and if so, how?
[02:01:51 CEST] <nadermx> I'm currently trying to merge a video and audio from YouTube and have it output to stdout via -. The problem is, it seems that it makes the video but the last 10-20 seconds of the video are silent. If I have it output to .mp4 it has the audio till the end.
[02:20:51 CEST] <furq> Kozi: -i foo.mkv -c copy -map -0:m:language:eng bar.mkv
[02:21:10 CEST] <furq> but that will remove all streams tagged with that language
[02:21:40 CEST] <furq> you could also just find which stream number it is and -map -0:n
[02:32:52 CEST] <Kozi> Thank you furq. Will try it out later. got to go..
[05:08:42 CEST] <ossifrage> Has anyone tried to build ffmpeg with --enable-lto and gcc 9.1.1?
[05:13:47 CEST] <furq> no but i've built with lto before
[14:22:46 CEST] <termos> /usr/bin/ld: /usr/local/lib/libavutil.a(hash.o): relocation R_X86_64_32S against `.rodata' can not be used when making a PIE object; recompile with -fPIC
[14:23:01 CEST] <termos> anyone have experience with this when compiling against ffmpeg on newer ubuntus?
[14:35:29 CEST] <DHE> static libs shouldn't have that problem unless a shared library is being built that needs it
[14:35:32 CEST] <DHE> what are you building?
[14:40:15 CEST] <termos> hmm i'm building some software we have that's linking against libffmpeg, it's being built all over the place and it's the first time we see this. really weird
[14:40:36 CEST] <JEEB> whatever libffmpeg is, have fun with that
[14:40:47 CEST] <termos> well, ffmpeg :)
[14:42:04 CEST] <durandal_1707> we do not support libffmpeg in any way
[14:42:36 CEST] <JEEB> anyways, sounds like you have a custom FFmpeg there, and if it's static make sure that PIC is utilized. I think under various circuimstances it gets enabled by default. in that case it's your own application that needs to be PIC
[14:43:09 CEST] <JEEB> checking your own FFmpeg ffbuild/config.log should see if you have enable-pic around or not
[14:43:38 CEST] <DHE> probably not. I'm guessing you want to rebuild with --enable-shared --extra-cflags=-fPIC
[14:44:01 CEST] <JEEB> there's a standard option for PIC I think
[14:44:07 CEST] <JEEB> so you don't need custom cflags for it AFAICS
[14:44:42 CEST] <DHE> looking at the configure script I don't see it for gcc
[14:46:05 CEST] <JEEB> see enabled pic && enable_weak_pic
[14:46:14 CEST] <JEEB> and the enable_weak_pic function
[14:46:30 CEST] <JEEB> if you --enable-pic you should get -fPIC to both asflags and cflags :P
[14:52:25 CEST] <termos> hmm thanks! i haven't needed any of those flags before
[14:52:43 CEST] <JEEB> it depends on what the builds depend on
[14:52:58 CEST] <JEEB> it might be FFmpeg, it might your app, it might be a dependency of FFmpeg or your app adding the requirement
[14:55:20 CEST] <DHE> I'm thinking if you're building a shared library (hypothetically, libvlc) which depended on ffmpeg, that would require these options
[17:01:20 CEST] <Thomas_J> Good Morning.
[20:29:24 CEST] <Fenrirthviti> Might be the wrong place to ask, but is anyone familiar with how the licensing for NVENC HEVC works in relation to ffmpeg? Trying to sort out of NVIDIA is sublicensing it as part of their APIs or if there are other concerns on distributing builds with it enabled.
[20:33:06 CEST] <Mavrik> Fenrirthviti, IIRC NVENC headers are MIT licensed
[20:33:39 CEST] <Fenrirthviti> Sure, but trying to sort out how they handle HEVC licensing
[20:33:45 CEST] <Fenrirthviti> not NVENC
[20:34:18 CEST] <Mavrik> You mean patents?
[20:35:09 CEST] <Fenrirthviti> No, I mean the licensing fees.
[20:35:25 CEST] <Fenrirthviti> which I guess is patent licensing?
[20:35:30 CEST] <Fenrirthviti> maybe we're talking about the same thing
[20:36:27 CEST] <Mavrik> Yeah, I think we are.
[20:36:46 CEST] <Mavrik> According to SDK license paying patent royalties is up to you... whatever that means :/
[20:36:57 CEST] <Fenrirthviti> Right, which is the part that's confusing.
[20:37:09 CEST] <Fenrirthviti> AMD has a similar disclaimer for their hardware encoders
[20:38:09 CEST] <Fenrirthviti> So I'm not sure if we would be required to provide some kind of disclaimer on that as part of the use of the NVENC HEVC encoder, or if we fail to provide that disclaimer we become liable for content created and not paid for
[20:39:29 CEST] <Mavrik> Yeah, honestly I've never managed to untangle the HEVC royalties mess properly :/
[20:42:20 CEST] <JEEB> you've got X different places wanting slightly different things, and in the best cases there are multiple places where a certain OEM is licensing their stuff
[20:42:39 CEST] <JEEB> I mean, even with H.264 it wasn't technically only MPEG-LA, but the playing field was pretty simple
[20:42:49 CEST] <JEEB> (Nokia IIRC kept out of MPEG-LA?)
[20:43:05 CEST] <Mavrik> Yeah, I'm assuming that Nvidia does pay the encoder license right?
[20:43:14 CEST] <Mavrik> That is, per-encoder HW
[20:43:21 CEST] <Mavrik> But not the parts that are per-title
[20:43:44 CEST] <JEEB> they probably pay *something*, yes. then again a lot of stuff is supposed to be paid by the entity that gives the result to an end user
[20:43:52 CEST] <JEEB> I'm not sure how that even went with MPEG-LA :P
[20:44:17 CEST] <Mavrik> Man, some of those royalties aren't even public
[20:44:22 CEST] <JEEB> if you f.ex. build a box for someone does it technically require a license to be paid by you because you are the one providing the final solution to the end user
[20:44:33 CEST] <JEEB> Mavrik: yea the best license pools don't have a tl;dr
[20:44:38 CEST] <JEEB> they make you contact them
[20:44:41 CEST] <JEEB> and then $$$
[20:47:06 CEST] <Mavrik> *sigh* So basically you buy encoders, install them and call the racketeers to check how much money they can extract from you. :D
[20:47:30 CEST] <JEEB> but yea, if you are the end user and you've been provided a hardware product then if I recall correctly most of the hw licensing doesn't apply, but then the places that have output related licensing come in
[20:48:06 CEST] <JEEB> at that point I'm just way too deep for my own good as I'm not a lawyer and such stuff is way over my pay grade :P
[20:48:17 CEST] <Mavrik> Mhm, it gets complicated when you do stuff like encode HEVC for profit. E.g. youtubers :)
[20:48:31 CEST] <JEEB> yea, I remember some places licensing the content/outputs
[20:48:49 CEST] <JEEB> I don't remember which it was that scared the shit out of people by wanting like 5% of income or something
[20:49:00 CEST] <Fenrirthviti> aight, fair enough.
[20:49:21 CEST] <Fenrirthviti> Glad I'm not the only one who finds this extremely confusing, heh
[20:51:11 CEST] <JEEB> thankfully some of the pools mostly focused on licensing hardware solutions for end users, so unless you were the one providing hardware to end users, it "didn't apply" to you
[20:51:24 CEST] <JEEB> but then there were the batshit insane ones
[20:51:26 CEST] <JEEB> 8)
[20:51:41 CEST] <Fenrirthviti> yeah where you had to pay for just being in the same room as an HEVC signal, yours or not.
[20:53:36 CEST] <DHE> don't suppose vp9 is an alternative... I assume not if you're going for hardware encoding.
[20:53:46 CEST] <Fenrirthviti> It's for NVENC
[20:53:49 CEST] <Fenrirthviti> so yes, hardware
[20:54:22 CEST] <Fenrirthviti> full context is for OBS, we've been asked a few times to implement native NVENC HEVC since using our ffmpeg output option is a bit of a mess
[20:54:46 CEST] <Fenrirthviti> we typically just cite "licensing concerns" as a reason not to do it, but trying to educate myself to have a better conversation around it
[20:55:05 CEST] <Fenrirthviti> So was curious how you guys approached it
[20:55:16 CEST] <JEEB> FFmpeg generally takes no comment on patent licensing
[20:55:22 CEST] <JEEB> and we do not officially distribute binaries
[20:55:30 CEST] <Fenrirthviti> Yeah, that's true.
[21:15:05 CEST] <Thomas_J> ITrying to get a stream working with Facebook. I just discovered that the quotes in front of "rtmps:// is actually not a typo but things actually start happening. all-be-it not what I need happening, if it is used.
[21:17:00 CEST] <Thomas_J> Does anyone have any idea sa to how the Quote should be used to make TLS:// work properly?
[21:17:26 CEST] <DHE> that's a commandline thing. if you just write "http://whatever.com/" on a shell, the quotes don't matter.
[21:18:04 CEST] <Thomas_J> I talking rtmps, not http.
[21:19:00 CEST] <Thomas_J> rtmp just works but rtmps hands off to the tls handler and things here do not work.
[21:23:49 CEST] <kepstin> Thomas_J: are you on windows? iirc the windows shell has really weird quoting behaviour - most of the docs you'll find for ffmpeg assume linux shell style quoting
[21:23:59 CEST] <Thomas_J> Ubuntu
[21:24:49 CEST] <kepstin> one thing to note on linux is that the & character which can appear in urls has special meaning to the shell and must be quoted
[21:25:03 CEST] <kepstin> this one hits me all the time when I'm trying to wget stuff :)
[21:26:47 CEST] <Thomas_J> The closest I have gotten is that I can get a message back "Resource temporarily unavailable". I understand that special chars usually have to be excapped but how to od that with gnotls handling the command string?
[21:26:54 CEST] <xantoz> kepstin: better quoted than sorry
[21:27:26 CEST] <furq> kepstin: wouldn't it be cool if some popular service decided to put ! in their urls
[21:27:27 CEST] <Thomas_J> Never had problems with wget.
[21:27:46 CEST] <furq> perhaps based in new zealand and operated by a fat egomaniac
[21:27:51 CEST] <furq> we can only dream though
[21:28:26 CEST] <Thomas_J> File names with spaces are allowed but you have to delimit them with quotes when loading.
[21:28:43 CEST] <xantoz> furq: more fun if they'd put single or double quotes in there
[21:28:56 CEST] <kepstin> Thomas_J: the tls library doesn't see or deal with urls at all, so i don't think that's really your problem
[21:28:59 CEST] <furq> well ! gets interpreted as job control stuff in doublequotes
[21:29:02 CEST] <furq> so you have to singlequote it
[21:29:02 CEST] <xantoz> maybe a combination of $ and single quotes?
[21:29:03 CEST] <Thomas_J> Those 2 mean different things.
[21:29:05 CEST] <furq> that's great fun
[21:29:28 CEST] <xantoz> then you'll have to escape stuff manually no matter what
[21:29:29 CEST] <furq> also it's job control stuff so it doesn't go in your history if you forget
[21:32:47 CEST] <Thomas_J> The thing is that when interpreting the ffmpeg string, the module that the following part of the string is now being parsed by that module and has it's own set of rules as to how to parse the command line. You just hope that common conventions are being observed.
[21:38:57 CEST] <ak22> How do I mix 7 mono inputs (FL, FR, FC, BL, BR, SL, SR) to stereo?
[21:39:28 CEST] <Thomas_J> Wow, I am getting to old. That last line made sense to me while I was writing it.
[21:41:59 CEST] <durandal_1707> ak22: with pan filter, or if you want binaural with headphone/sofalizer/afir/... filters
[21:42:39 CEST] <durandal_1707> using amerge/join with pan, more correctly
[21:43:22 CEST] <Thomas_J> Is there anywhere on the Internet where I can find help with writing a ffmpeg command string for rtmps'ing to Facebook?
[21:48:54 CEST] <Fenrirthviti> Thomas_J: Getting the output and errors so that people can review the issue fully is probably more helpful
[21:49:18 CEST] <Fenrirthviti> There's a good chance that the quotations don't really have anything to do with your issue
[21:50:12 CEST] <Fenrirthviti> If you're trying to run a command, paste the output with errors to a gist or similar and link it so people can view it and see what's going on
[22:03:03 CEST] <Thomas_J> I have been trying to get this working for over a month without success. The Quotes, I just tried today for the first time even though it doesn't make any sense. When I did, I was surprised that I actually got something besides just staring at a running ffmpeg line without anything happening
[22:04:30 CEST] <Thomas_J> I can make things work with rtmp streaming but rtmps will not cooperate.
[22:07:18 CEST] <Thomas_J> I have no other way other than streaming my tests directly to Facebook. I have nothing that takes a rtmps input to check my work with. nginx is not equipped for rtmps.
[22:18:39 CEST] <Thomas_J> Fenrirthviti> When I run ffmpeg with rtmps:// without a quote, the process just sits there idle until I hit the enter key that ends the exec.When I use a d-quote before the rtmps:// it gives me a prompt">" like it is waiting for more input. When I use d-quote before the rtmps:// and at the end of the uri string, that's when I get the error "Resource temporarily unavailable".
[22:19:17 CEST] <Fenrirthviti> I can't really help without seeing the full command and output.
[22:19:32 CEST] <Fenrirthviti> Which is why I asked for it
[22:19:51 CEST] <Thomas_J> let me pastebin
[22:37:30 CEST] <plspgnl> Is anyone know if there is an option to not decode frame if these have error in it with H264 codec. To comparison VP9 codec display by default the last frame without error.
[22:38:58 CEST] <plspgnl> This is to not display glitches while decoding
[22:41:26 CEST] <Thomas_J> Here are my tests. https://pastebin.com/Re628Wu8
[23:38:18 CEST] <Thomas_J> Has anyone had a chance to look at my pastebin yet? https://pastebin.com/Re628Wu8
[00:00:00 CEST] --- Tue Jul 9 2019
More information about the Ffmpeg-devel-irc
mailing list