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

[burek]

[00:01:13 CEST] <AleXoundOS> I have several tmux panes with ffmpeg running in each. And these additional several characters from new ffmpeg version make "info" line printing new lines, because it doesn't fit inside tmux pane anymore.
[00:01:38 CEST] <JEEB> and if you are a carebear enough, feel free to add an option or whatever for it if you really, really want to limit what ffmpeg.c's print_report() does, but as far as I know the output of ffmpeg.c onto the terminal has never been exactly stable
[00:02:49 CEST] <AleXoundOS> ok, I understand, thank you for the info
[00:04:01 CEST] <llogan> -nostats will omit that last line, but not what you want as far as i can tell
[00:05:09 CEST] <AleXoundOS> yeah, -nostats removes the "info" line completely
[00:05:27 CEST] <AleXoundOS> I need "info" line, but without "speed" field
[00:40:06 CEST] <explodes> av_probe_input_format fails from time to time, has anyone seen this?
[00:43:14 CEST] <explodes> It does work sometimes, but other times it causes a SIGSEGV
[00:43:23 CEST] <explodes> ..which is bad for us
[00:44:07 CEST] <pzich> do you have an error message or stack or something?
[00:47:13 CEST] <explodes> :/ I really wish I did
[00:47:29 CEST] <explodes> Just a libvsp.so+399
[00:49:40 CEST] <J_Darnley> If you have the input as a file then what does ffmpeg manage to do with it?
[00:50:34 CEST] <explodes> I think the problem was that I was omitting AVPROBE_PADDING_SIZE bytes at the end of the buffer ..
[00:50:54 CEST] <explodes> Tests are running to completion now, so far.. knockonwood
[00:51:03 CEST] <J_Darnley> ah, yes an overread could cause that
[04:13:26 CEST] <spiritbro> hi all
[04:13:44 CEST] <spiritbro> i want to ask about rtsp streaming in ffserver
[04:19:15 CEST] <J_Darnley> My answer to all streaming questions: don't do it.
[04:22:17 CEST] <J_Darnley> Damn, missed him.
[05:17:58 CEST] <gusto> hey, does here anyone know how to tell ffmpeg with its x11grab which password it should take for a vnc session? I want to open that VNC viewer output
[05:36:01 CEST] <DHE> x11grab doesn't use VNC
[05:36:08 CEST] <gusto> yes
[05:36:17 CEST] <gusto> but it works, I want to grab from another computer
[05:36:30 CEST] <gusto> locally it does work, when I start a vncserver, it connects
[05:36:31 CEST] <DHE> otherwise it would be called vncgrab
[05:41:53 CEST] <gusto> or I could try xnest
[05:41:57 CEST] <gusto> maybe a better idea
[05:42:36 CEST] <gusto> I mean more like XDMCP, that should work, or not?
[05:46:38 CEST] <DHE> for optimal performance you really need ffmpeg running on the same host as the X server to make use of the shared memory extension
[05:46:53 CEST] <DHE> if you're doing remote VNC, you might as well use a VNC viewer locally and have ffmpeg record the VNC viewer window
[05:47:08 CEST] <DHE> in either case, ffmpeg doesn't get involved in the VNC password
[05:47:11 CEST] <gusto> well
[05:47:36 CEST] <gusto> ok, that one with the window is not a bad idea, but how do I tell ffmpeg to record a window? VLC can do it, but ffmpeg?
[05:49:30 CEST] <DHE> yeah the manual doesn't suggest how you would do it without specifying exact pixel offsets
[05:50:09 CEST] <gusto> pixel offsets are not useful, because when you draw another window over it or you change the virtual desktops, it goes somewhere else
[09:36:36 CEST] <AleXoundOS> Hi. I user several instances of ffmpeg running at the same time. Which type of build will use less RAM in my case: static or shared? Maybe with shared type shared libraries will be loaded in memory only once? Or it doesn't matter?
[09:36:40 CEST] <AleXoundOS> use*
[09:37:04 CEST] <scoofy> probably
[09:37:08 CEST] <AleXoundOS> (I use linux)
[09:38:14 CEST] <scoofy> in static, each instance would load its copy of the libs
[09:38:20 CEST] <scoofy> try dinamic / shared lib
[09:38:32 CEST] <AleXoundOS> ok, thank you
[12:25:13 CEST] <Gegsite> hello
[12:25:22 CEST] <Gegsite> would like to convert an mkv to avi
[12:26:03 CEST] <Gegsite> ffmpeg did it with -i input.mkv output.avi but the quality is pretty bad
[12:26:32 CEST] <Gegsite> it made 300 Mb avi from an 1,5 GB mkv
[12:32:48 CEST] <Gegsite> it say bitrate=  226 kbits/s
[12:32:57 CEST] <Gegsite> should be 1500.... how?
[12:33:41 CEST] <Mavrik> pass the video bitrate parameter :)
[12:34:30 CEST] <Gegsite> -b:v 2000 does nothing
[12:34:53 CEST] <Mavrik> 2000k
[12:34:58 CEST] <Mavrik> It's in bits/s
[12:35:10 CEST] <Mavrik> So if you want 2000kbits/s you need to set -b:v 2000k
[12:35:20 CEST] <Gegsite> oh.. :P thanks Mavrik
[13:09:07 CEST] <VVelox> -threads 0  is the same as -threads auto?
[13:10:01 CEST] <J_Darnley> No.
[13:10:21 CEST] <J_Darnley> 0 is used by libx264 to mean "auto"
[13:10:33 CEST] <J_Darnley> other codecs may not autodetect
[13:11:06 CEST] <VVelox> So if I want to use auto there, I would need to specify auto?
[13:11:11 CEST] <J_Darnley> no
[13:11:19 CEST] <furq> is there even an auto option
[13:11:21 CEST] <J_Darnley> it has an integer argument
[13:11:43 CEST] <VVelox> furq: If I am reading -h full right there seems to be
[13:11:58 CEST] <furq>   -threads           <int>        ED.VA... (from 0 to INT_MAX) (default 1)
[13:11:58 CEST] <furq>      auto                         ED.V.... autodetect a suitable number of threads to use
[13:12:01 CEST] <furq> so there is
[13:12:40 CEST] <J_Darnley> Nice, "just" a special case in option parsing
[13:13:24 CEST] <furq> i don't know whether that works anywhere that 0 doesn't
[13:13:34 CEST] <furq> i assume it must do
[14:29:36 CEST] <satinder___> Hi , my question is very simple , Can we integrate complete ffmpeg with our C program I mean can we create single binary of my C program with including ffmpeg source
[14:29:37 CEST] <satinder___> any can please help
[14:33:12 CEST] <VVelox> Sounds like you are looking for info on libav.
[14:34:37 CEST] <c_14> satinder___: so long as you follow the requirements set by the (L)GPL and don't link against a non-free build of FFmpeg it should be fine. (note, I am not a lawyer)
[14:35:25 CEST] <ln-> my crystall ball tells me following the requirements of (L)GPL is not an option in satinder___'s case
[14:36:26 CEST] <Mavrik> It's possible to statically link LGPL with non-GPL code, but it's fun to keep compliant :)
[14:40:27 CEST] <JEEB> Mavrik: you usually say it the other way :D you're opening a can of worms with saying it that way
[14:40:38 CEST] <JEEB> you have a closed source thing and you link LGPL to it
[14:40:48 CEST] <Mavrik> Oh yes, that's what I meant :)
[14:41:35 CEST] <JEEB> basically there was a discussion about linking against nonfree libs for an LGPL configuration but I don't think we got j-b or his lawyer army to comment
[14:45:36 CEST] <Mavrik> Mhm, last time I checked you'd have to provide object files so people could relink the binary with another set of libav libs.
[14:47:19 CEST] <JEEB> yes, that is how it goes with a closed source thing linking LGPL statically
[14:47:37 CEST] <JEEB> this is regarding LGPL libav* linking against closed source stuff
[14:47:47 CEST] <JEEB> which comes from f.ex. drivers
[14:55:05 CEST] <satinder___> ok
[15:01:57 CEST] <satinder___> Actually I am trying but there is some api issues undefined errors
[15:02:29 CEST] <satinder___> I change ffmpeg main function to ffmpeg_emb_main and call it from my c program
[15:02:47 CEST] <satinder___> so I what I am doing wrong
[15:14:35 CEST] <BtbN> ffmpeg.c is not designed to work as a library, because it isn't one.
[15:20:40 CEST] <satinder___> ok
[15:21:14 CEST] <satinder___> BtbN : then how I can use ffmpeg in my c program
[15:21:30 CEST] <JEEB> use the actual public APIs
[15:21:49 CEST] <JEEB> libavformat|libavcodec etc
[15:21:58 CEST] <JEEB> or you just call the ffmpeg application itself :P
[15:22:11 CEST] <JEEB> if you want all the quirks and ugh related to ffmpeg.c
[15:22:30 CEST] <BtbN> also avoids a lot of licensing issues if you just ship a ffmpeg executable binary.
[15:22:41 CEST] <BtbN> If that's enough for your usecase
[15:29:42 CEST] <satinder___> BtbN : no sir I want single binary of my program including ffmpeg
[15:30:20 CEST] <BtbN> use the official APIs then, and link staticaly.
[15:32:21 CEST] <satinder___> BtbN : but their have not ffmpeg functionality
[15:32:36 CEST] <satinder___> I want add whole ffmpeg
[15:32:52 CEST] <BtbN> Good luck with turning ffmpeg.c in a library then.
[15:33:26 CEST] <satinder___> ok
[15:33:30 CEST] <satinder___> sir
[15:33:36 CEST] <satinder___> thanks
[15:36:52 CEST] <J_Darnley> Oh I forgot I had that guy on my ignore list.  Suddenly this sequence of messages makes a little more sense.
[16:32:50 CEST] <satinder___> how we can pass command line arguments to ffmpeg.c
[16:32:55 CEST] <satinder___> from c program
[16:33:37 CEST] <J_Darnley> system()
[16:33:47 CEST] <satinder___> I change the name of ffmpeg.c main function main to emb_main
[16:33:57 CEST] <JEEB> J_Darnley: put him back on your ignore list, simpler that way :P
[16:34:01 CEST] <satinder___> and calling it from my c program
[16:34:12 CEST] <JEEB> if he wants to do this and it doesn't work, it is not our responsibility to help
[16:34:18 CEST] <JEEB> he can keep both sides
[16:34:21 CEST] <TD-Linux> satinder___, it's not a supported way of using ffmpeg. you won't get any help with that method here
[16:34:30 CEST] <satinder___> ok sir
[16:34:43 CEST] <satinder___> thanks
[19:36:05 CEST] <agrathwohl> Hello, I am testing out the 3.0 release of FFmpeg and am interested in trying out the Common Encryption MP4 support. However, when looking over the manual on ffmpeg.org I was unable to find any documentation on how to get started. Is there any resource out there that shows how to encode MP4s with CENC? Thank you!
[19:36:38 CEST] <JEEB> there are movenc options for that
[19:37:22 CEST] <JEEB> hmm
[19:37:30 CEST] <JEEB> wonder why it's not listed in ffmpeg-all.html
[19:38:00 CEST] <JEEB> I have tried using it through the API earlier, and it seemed to succeed
[19:38:27 CEST] <c_14> Probably nobody wrote docs for it, they're listed in ffmpeg -h muxer=mov though (-encryption_scheme etc)
[19:38:41 CEST] <JEEB> right
[19:39:10 CEST] <JEEB> I would have thought the doc creation thing looks at all of the defined options :)
[19:39:22 CEST] <c_14> It doesn't, only the internal help does
[19:39:31 CEST] <JEEB> aye
[19:42:20 CEST] <agrathwohl> Oh, I see now. Thank you for the help c_14 and JEEB
[00:00:00 CEST] --- Sun Apr  3 2016