[00:00] <shambala> yep [00:00] <saste> shambala, the first or the second? [00:00] <shambala> family history [00:00] <saste> ah ok [00:01] <shambala> so, the format needs to be changed, huh? [00:01] <llogan> what are you tryng to do? why do you need the transparency preserved? [00:02] <shambala> this was a sample movie.. there'll be other movies that will have all kinds of zoom effects and black fill looks ugly [00:02] <shambala> doesn't look natural [00:02] <llogan> how about a white fill? [00:03] <shambala> hmm& can try that, do you know the option, by any chance? [00:04] <llogan> see the "color" filter source and "overlay" for one method [00:04] <llogan> although the seems more like work for a video editor or compositor [00:09] <llogan> shambala: as in "ffmpeg -i input -filter_complex color=c=white:s=640x480,overlay output" [01:10] <shambala> llogan: thanks for the help, it didn't work though [01:10] <shambala> had to get into an impromptu meeting, will keep trying [01:14] <llogan> shambala: "it doesn't work" is a common error message. [01:15] <shambala> sorry, I meant it behaves exactly same as before (i.e. fill is still black) [01:21] <llogan> works for me [01:42] <shambala> hmm& will try again tonight, thanks a bunch [04:10] <schtinky> burek, I saw your bug post here: https://ffmpeg.org/trac/ffmpeg/ticket/614?cversion=0&cnum_hist=4 [04:11] <schtinky> I'm experiencing something similar, intermittent failure of the hardware to properly lock and spit out data to ffmpeg [04:11] <schtinky> was your device analog or digital? [07:30] <kristopolous> HI! [07:31] <kristopolous> ffmpeg -i out.mkv -an -vcodec libx264 -vpre slow_firstpass -y -pass 1 -f h264 -y /dev/null && ffmpeg -i out.mkv -vcodec libx264 -vpre slow -pass 2 -f h264 video.mp4 I'm doing that [07:32] <kristopolous> and it doesn't work [07:32] <kristopolous> it's about as simple and supported as it should be [07:32] <kristopolous> but no chance@! [07:34] <drv> you probably don't want to say -f h264, the format will be autodetected from the .mp4 filename [07:35] <drv> (h264 is the raw h264 format, not mp4) [07:35] <kristopolous> ok I will drop that and try again [07:36] <drv> you probably still need something like it in the first pass command since it's outputting to /dev/null, but not in the 2nd pass [07:36] <kristopolous> surely. [07:39] <kristopolous> nope [07:39] <kristopolous> certainly broken [07:39] <kristopolous> "constant rate-factor is incompatible with 2pass." [07:39] <kristopolous> woopdee [07:40] <kristopolous> yeah, this stuff never works for me [07:41] <kristopolous> even when I copy and paste from the manpage [07:44] <drv> i think you need to specify bitrate explicitly, e.g. -b:v 400k [07:44] <drv> the preset probably has crf by default [07:45] <kristopolous> what's with the new colon syntax [07:45] <drv> http://ffmpeg.org/trac/ffmpeg/wiki/x264EncodingGuide#twopass [07:45] <kristopolous> how long has that been around [07:46] <drv> dunno, switched some time ago, more consistent between audio and video now [07:48] <kristopolous> yeah I'm just going to try 1 pass [07:49] <kristopolous> as it turns out, compressing complex math graphs yields a bunch of compression blocks with most ways I approch [07:54] <relaxed> kristopolous: try, ffmpeg -i input -c:v libx264 -crf 18 -preset veryslow -tune grain output [07:56] <kristopolous> ok sure [07:56] <kristopolous> I just can't be passing around a 14GB video [07:58] <relaxed> -preset veryslow will yeild the best compression. [08:00] <relaxed> if it's still too large increase the -crf value until you're happy with the size/quality. [08:01] <kristopolous> oh wow, it's at 7 seconds in [08:01] <kristopolous> this will take a while [08:01] <kristopolous> I'm at -thread 0 [08:02] <kristopolous> is there an mpi or gpu version of ffmpeg? [08:04] <kristopolous> oh, and the bitrate is over 900000kbit/s [08:04] <kristopolous> this won't work [08:10] <relaxed> add -t $seconds to encode some samples and figure out what -crf to use [08:16] <kristopolous> oh good call [08:16] <lentferj> kristopolous: I ususually use -crf in the range of 20 - 23 [08:17] <kristopolous> im trying with 22 right now [08:17] <lentferj> I encountered artifacts when using preset lower than medium on some FullHD content [08:18] <lentferj> so usually I try slow first, if that makes problems revert to medium [08:18] <kristopolous> fullhd? you mean 1920x1080? [08:18] <lentferj> yes [08:18] <kristopolous> oh ok [08:19] <lentferj> relaxed: why "-tune grain"? I usually use film. What's grain doing? [08:20] <kristopolous> these are abstract mathematical graphs ... I think grain is right [08:21] <lentferj> ah... ok [08:21] <lentferj> never came to my mind you could use it for something else than.. well. movies ;) [08:23] <kristopolous> most of my ffmpeg use is generating frames through some C or R program and then stitching them together [08:23] <kristopolous> or doing screencasting [08:24] <kristopolous> I've *heard* of people watching movies on computers ... but I'm far too nerdy for that I think [08:26] <lentferj> kristopolous: haha :) [08:59] <kristopolous> yay, down to 140MB and still watchable [08:59] <kristopolous> good [09:42] <bogdanp> can anyone think of a reason why doing http://pastebin.com/raw.php?i=UMvFQPiW would result in http://i.imgur.com/2EmLbPj.png ? I'm trying to convert RGB32 frames received from a camera to h264 video but this has me stumped. [09:45] <viric> I've the impression that I can't beat the quality/bitrate of youtube webm videos [09:45] <viric> does anybody know their coding settings? [09:45] <viric> I even think that I'm *far* to achieve their quality/bitrate [15:15] <bonana|dlr> Heho! In my application I try to capture an RTSP-stream (audio + video). Following this example http://stackoverflow.com/a/13457773/1228324 I can capture the video. Where do I find information how to write the audio simultaneously into the same file? [15:16] <bonana|dlr> is the muxing-example, coming with the dev-package, the right way to start or is it easier to deal with? [17:21] <lentferj> with this command line [17:21] <lentferj> ffmpeg -probesize 50M -analyzeduration 50M -i 11303_20130409181200.mpg -map_metadata 0 -map 0:v -map 0:a -c:a copy -b:a 384k -c:v libx264 -crf 23 -preset slow -threads 10 -tune film -stats .ffmpeg_tmp_19173/11303_20130409181200.mpg [17:21] <lentferj> I get "This syntax is deprecated. Use '|' to separate the list items." [17:21] <lentferj> on latest ffmpeg from git [17:22] <lentferj> I understood that ',' should not be used anymore [17:22] <lentferj> but I don't have any in this command [17:22] <lentferj> where else should I use '|' ? [17:23] <durandal_1707> lentferj: that warning comes from filter that is auto insterted [17:23] <durandal_1707> there is nothing wrong on your side [17:23] <durandal_1707> this is known problem and will be fixed eventually [17:23] <lentferj> ok, thought something like that :) [17:24] <lentferj> one more regarding this, atm I have something like [17:24] <lentferj> -vf "crop=1276:716:2:2",yadif [17:24] <lentferj> in my scripts [17:25] <lentferj> how should that be written in new syntax? [17:25] <lentferj> -vf "crop=1276:716:2:2"\|yadif [17:25] <lentferj> gives me error [17:25] <durandal_1707> the : is "changed" by fork [17:26] <durandal_1707> so instead of : using to separate options in filter like crop, you use | [17:26] <lentferj> oh, for the values too [17:26] <lentferj> I thought just for lists of options/filters, instead of , use | [17:27] <durandal_1707> nope [17:28] <durandal_1707> but nothing yet changed [17:28] <durandal_1707> because unlike fork we care for backward compatibility [17:29] <lentferj> ;) [17:29] <lentferj> yeah, I see that the old syntax is still working [17:29] <lentferj> but while I upgraded ffmpeg I thought I could also look in to this so it doesnt bite me later :) [17:30] <lentferj> so, ok with -vf "crop=1276\|716\|2\|2" I get "[Parsed_crop_0 @ 0x2ab7400] [Eval @ 0x7ffffa5c3cd0] Invalid chars '|716|2|2' at the end of expression '1276|716|2|2'" [17:31] <durandal_1707> well you could switch to named ones, those will always work, they are still separated by : [17:31] <durandal_1707> even to me its not clear what that warning about | actually means .... [17:31] <ubitux> huh? [17:32] <ubitux> why are you putting '|'? [17:32] <ubitux> no no no there is no reason to put '|' [17:32] <lentferj> ubitux: dunno... trying to "learn" the new syntax [17:32] <ubitux> '|' are used only for list of items [17:32] <durandal_1707> ubitux: you did not notice warning by auto insterted filters that talk about | thin for list of things of same type? [17:33] <lentferj> ubitux: so, what I thought [17:33] <ubitux> yes, for lists, with a few little filters [17:33] <ubitux> durandal_1707: any problem with it? [17:33] <lentferj> ubitux: no problem, just a little confusion [17:33] <durandal_1707> it just spill warning and confusing users, who than gona change all scripts ... [17:34] <ubitux> durandal_1707: with what filtergraph is it warning? [17:34] <lentferj> ubitux: so, when I use e.g. "-vf "crop=1276:716:2:2"\|yadif" I get "Invalid chars '|yadif' at the end of expression '2|yadif'" [17:34] <ubitux> don't use '|' here [17:34] <ubitux> it makes no sense [17:34] <durandal_1707> ubitux: random conversions, aformat [17:34] <ubitux> use a comma, just like before [17:34] <lentferj> oh, ok.. [17:35] <lentferj> then it seems I didn't understand what the warning is about [17:35] <ubitux> lentferj: with what command did you see a warning? [17:35] <lentferj> ubitux: do you have backlog? [17:35] <lentferj> 14 mins ago [17:36] <ubitux> i don't see any filtering info in your cmd line [17:37] <durandal_1707> [audio format for output stream 0:0 @ 0x2984f600] This syntax is deprecated, use '|' to separate sample rate. [17:37] <durandal_1707> when doing simple mp3 encoding [17:37] <ubitux> do we auto insert aformat somewhere? [17:37] <durandal_1707> ffmpeg does [17:38] <lentferj> http://pastie.org/7454670 [17:39] <ubitux> mmh strange [17:39] <ubitux> lentferj: note that we are currently merging such stuff, so it's a bit unstable [17:39] <lentferj> well, it's latest git version .. I can live with that :) [17:40] <lentferj> I just I didn't understand the new synatx right (from the little I could draw from the commit logs) [17:40] <lentferj> thought* [17:40] <ubitux> lentferj: please consider waiting a day or two when the chaos calm down [17:40] <ubitux> it's still a little bit fresh [17:41] <lentferj> ja, I saw like 2 dozen commits of "new synatx".. I pulled last 2 days ago I think :) [17:41] Action: lentferj is a early adopter [17:42] <lentferj> ok, gotta run to pick my kids. If I can test something or the like just ping me. [17:42] <bonana|dlr> Capturing an RTSP-stream how can I write video in audio simultaneously into one file? [17:43] <bonana|dlr> in my custom application. [17:44] <ne555> ¿what should I put in `input' in order to capture the audio output? [17:45] <ne555> (linux) [17:51] <dv-> i'm trying to record my desktop with ffmpeg (libx264 & crf 0) but the result is kind of meh... the colors look noticably washed out and it's not as sharp. is there anything I can do to improve it? [17:52] <ubitux> lentferj: you can try again eventually [17:59] <dv-> this describes the problem pretty well: http://ubuntuforums.org/showthread.php?t=2124591 [17:59] <LithosLaptop> maybe try 4:4:4 chroma format? [18:01] <LithosLaptop> I don'y know the switch [18:01] <LithosLaptop> *dob't [18:02] <LithosLaptop> don't [18:04] <dv-> LithosLaptop: ok, using yuv444p improved it a lot. [18:05] <dv-> anything else I can do? [18:06] <JEEBsv> Just capture in RGB (4:4:4 with RGB coefficients) instead of YCbCr? But to be honest your video will end up being 4:2:0 in the end if you want it to be widely decode'able [18:06] <JEEBsv> 4:4:4 profile is just not supported in most things [18:06] <JEEBsv> (except for libavcodec, naturally) [18:06] <dv-> does youtube support it? [18:07] <JEEBsv> youtube will re-encode your content to 4:2:0, and whether or not it can decode 4:4:4 depends on how old of a libavcodec they're using [18:08] <JEEBsv> If you want to be able to view the thing in flash, you'd have to either host it yourself or use a video hoster that doesn't re-encode, as well as use 4:2:2 YCbCr at most [18:08] <JEEBsv> Flash uses MainConcept's decoder and that surprisingly has support for 4:2:2 as well [18:09] <JEEBsv> most end-user decoders only support 4:2:0 [18:09] <dv-> hm [18:09] <ubitux> lentferj: every unwanted warning should be fixed; if you still have some, please report them [18:10] <dv-> so would it be better in the end to record to 4:2:0 or 4:4:4 and let youtube convert it? [18:12] <dv-> if they do at all. i've had some problems with this in the past [18:12] <LithosLaptop> I think it is best to keep it at 4:2:0 for youtube [18:12] <JEEBsv> Personally I always record in RGB as-is with some fast encoder, and then convert to 4:2:0 with whatever I happen to prefer at that point and upload that in either lossless (youtube etc. that always re-encode), or lossy (non-re-encoding services) [18:12] <LithosLaptop> My video colors are messed up in my computer's media player, or YouTube is only showing gray video. Now what? [18:12] <LithosLaptop> [18:12] <LithosLaptop> Add -pix_fmt yuv420p as an output option. YouTube and most (or perhaps all) non-FFmpeg based players do not support proper decoding of YUV 4:2:2 or YUV 4:4:4. [18:13] <JEEBsv> LithosLaptop: youtube does use libavcodec for decoding, it just means that 'tube uses an old version of it :P [18:13] <JEEBsv> they update very rarely [18:13] <LithosLaptop> oh ok [18:13] <JEEBsv> but yes, in general very, very few decoders support something else but 4:2:0p [18:14] <dv-> that's too bad [18:14] <JEEBsv> MainConcept (Flash) happens to support 4:2:2 as well, but that is closer to being tan exception than the rule [18:14] <dv-> now what about aliasing? is there anything I can tell ffmpeg over -q 0 so that it will keep more detail? [18:14] <JEEBsv> if you are setting a qp of zero for x264, you should already be getting a lossless picture [18:15] <JEEBsv> so if something is happening, it's happening before the picture comes to x264, or after it has been decoded [18:15] <JEEBsv> if you are talking about aliasing between two very different colors [18:16] <JEEBsv> then you can't really do anything 'bout it in general [18:16] <LithosLaptop> what do the html5 browsers vp8 decoders support? [18:16] <JEEBsv> I think VP8 only has a 4:2:0 mode to begin with [18:16] <LithosLaptop> ah ok [18:16] <JEEBsv> since 4:2:0 has full luma ("grayscale"), and a single value for a 2x2 area of chroma (color) [18:17] <JEEBsv> you are bound to get some derpiness that can be more or less apparent depending on the content [18:18] <dv-> even with 4:4:4 it doesn't look as sharp as what I see on screen [18:18] <JEEBsv> first of all try with the RGB encoding mode [18:19] <JEEBsv> I think ffmpeg made that into a separate video codec [18:19] <JEEBsv> although it uses the same x264 in the background [18:20] <JEEBsv> libx264rgb it seems [18:20] <JEEBsv> that should keep the picture in RGB if the input is RGB as well [18:21] <dv-> i assume x11grab is [19:35] <ljudevit> hello, need help with subtitle encoding [19:35] <ubitux> explain your problem [19:36] <ljudevit> works on xubuntu, does not work on red hat. Unable to open iconv context with input character encoding "windows-1250" [19:36] <ljudevit> interesting is, that my own little program that uses icon with 1250 works ok.. [19:36] <ljudevit> ok, will upload [19:37] <ljudevit> command im using: http://pastebin.com/j1ESN9dU [19:39] <ubitux> "and the COMPLETE console output" [19:39] <ljudevit> jep, its here http://pastebin.com/jaznkaRz [19:41] <ubitux> can you try "cp1250" instead? [19:43] <ljudevit> yes, I already did. The same error [19:43] <ubitux> ljudevit: can you pastebin a iconv -l? [19:45] <ljudevit> i can, but it lists all the ever-known-to-man encodings, including the windows-1250 :) [19:45] <ubitux> mmh [19:45] <ubitux> that's strange then [19:45] <ubitux> ljudevit: oh i think i know [19:46] <ubitux> ljudevit: this static build was probably configured with a iconv where these are in a different location [19:47] <ljudevit> that makes sense.. can I somehow help myself without recompiling it on my own? [19:48] <ubitux> burek is building those on ubuntu, so the path where those encodings are is probably different [19:48] <ubitux> i don't know if you can change that at runtime with some magic iconv env variables [19:48] <ubitux> if not, you probably need to build ffmpeg yourself [19:49] <ljudevit> well, that was helpful. thank you very much [19:52] <LithosLaptop> http://www.motobit.com/util/charset-codepage-conversion.asp [19:53] <LithosLaptop> could maybe convert it to utf8? [19:54] <ljudevit> i could, but this is executed as a job and im trying to do everytinh in one process [19:54] <ljudevit> within ffmpeg [19:56] <ubitux> just build it yourself :p [19:57] <ljudevit> will do, using burek's build was a quick shortcut :p [20:27] <Sc0rc3d> Hi folks i got a hopefully smal question for you. :) i wannt to use ffmpeg to stream an local mp4 file to my Red5 Vidoe Server. But i got an error the stream starts 1sec and stops. this my code: ffmpeg -re -i xx.mp4 -vcodec copy -acodec copy -f mp4 rtmp://111.222.333.444:1935/live/ [20:28] <klaxa> hmm... that's a tough one, no idea where it could go wrong [20:28] <klaxa> are you sure red5 is set up correctly? [20:28] <Sc0rc3d> yes i can stream over open broadcast software [20:28] <Sc0rc3d> that works pretty well [20:28] <klaxa> then paste complete console output [20:28] <klaxa> on pastebin [20:28] <klaxa> or a similar site [20:28] <Sc0rc3d> on my way [20:29] <Sc0rc3d> http://pastebin.com/E4w286Cf [20:30] <LithosLaptop> ac3 audio might be a problem? [20:30] <Sc0rc3d> yes i think so too so i tryed with : [20:31] <Sc0rc3d> damn putty closed ^^ [20:31] <LithosLaptop> haha [20:32] <Sc0rc3d> so: ffmpeg -re -i xx.mp4 -vcodec copy -ab 192k -ac 2 -ar 44100 rtmp://xxx.x:1935/live [20:33] <klaxa> you would want to specify an audio codec [20:33] <Sc0rc3d> and then i get an Unable to find a suitable output format for 'rtmp://81.169.184.174:1935/live/test' [20:33] <klaxa> you need -f mp4 or something [20:33] <klaxa> to force an output format [20:33] <Sc0rc3d> yeah tryed that too [20:33] <Sc0rc3d> gave me the same "incorect codec params" error [20:34] <klaxa> well try to specify like... -acodec libmp3lame or something [20:34] <klaxa> you haven't set an audio codec i don't know what the default codec is, you could obtain that info from the log [20:34] <Sc0rc3d> no lame [20:34] <Sc0rc3d> i think i can check by ffmpeg -acodec ? [20:35] <klaxa> would vorbis be okay? [20:35] <Sc0rc3d> quality > * [20:35] <klaxa> ffmpeg -codecs [20:35] <LithosLaptop> -c:a aac -b:a 256k -strict -2 -cutoff 15000 [20:36] <LithosLaptop> or [20:36] <klaxa> mhh >inb4 -c:a is too new of a syntax for his ffmpeg-build [20:36] <LithosLaptop> -acodec aac -ab 256k -strict -2 -cutoff 15000 [20:37] <LithosLaptop> oh ok [20:37] <LithosLaptop> is the experimental aac encoder included in his build? [20:37] <Sc0rc3d> like this? : ffmpeg -re -i xx.mp4 -vcodec copy -acodec aac -ab 256k -strict -2 -cutoff 15000 -f mp4 rtmp://111.222.333.444:1935/live/ [20:37] <klaxa> looking good i guess [20:37] <LithosLaptop> yeah [20:38] <LithosLaptop> oh wait [20:38] <LithosLaptop> how many channels is the ac3 [20:38] <klaxa> 2 [20:39] <klaxa> >Stream #0.1(ger): Audio: ac3, 48000 Hz, 2 channels, s16, 192 kb/s [20:39] <LithosLaptop> ah ok [20:39] <LithosLaptop> thats ok then [20:39] <Sc0rc3d> hmm same error incorect codec params [20:39] <LithosLaptop> paste quickly in pastebin [20:39] <LithosLaptop> does it sy ehich params [20:39] <LithosLaptop> oops [20:39] <LithosLaptop> my wireless keyboard skips letters [20:40] <klaxa> (from the first paste: >Could not write header for output file #0 (incorrect codec parameters ?) ) [20:40] <Sc0rc3d> http://pastebin.com/vrcysnRe [20:42] <klaxa> according to wikipedia mp4 should support ac3 even [20:42] <klaxa> can you as a test write it to a temporary .mkv file? [20:43] <Sc0rc3d> like this: ffmpeg -re -i xx.mp4 -vcodec copy -acodec aac -ab 256k -strict -2 -cutoff 15000 -f mkv test.mkv [20:43] <LithosLaptop> yeah [20:43] <klaxa> not really [20:43] <klaxa> either use -f matroska, or omit -f completely [20:43] <LithosLaptop> wthout -f mkv [20:43] <klaxa> -f mkv will not be recognized [20:44] <Sc0rc3d> he does it [20:44] <Sc0rc3d> with -f matroska [20:44] <Sc0rc3d> writing... [20:44] <LithosLaptop> oo ok [20:45] <Sc0rc3d> i can quit it right? [20:45] <klaxa> yeah [20:45] <Sc0rc3d> last line: frame= 985 fps= 24 q=-1.0 Lsize= 29417kB time=00:00:41.00 bitrate=5877.6kbits ^^ [20:45] <LithosLaptop> and if you try -f mp4 test.mp4 [20:45] <Sc0rc3d> he wirtes too [20:45] <Sc0rc3d> *writes [20:45] <Sc0rc3d> frame= 345 fps= 24 q=-1.0 Lsize= 14423kB time=00:00:14.27 bitrate=8278.8kbits [20:45] <LithosLaptop> hmmm [20:46] <klaxa> hmm.. i can write h264 video with ac3 audio [20:47] <Sc0rc3d> maybee red5 just says that thes support mp4 in some forum threads i just find use flv but i try to convert mkv -> flv it was just a pixelblock at all -.- [20:47] <klaxa> you um... [20:47] <klaxa> you're not supposed to re-encode, also flv only supports certain sample rates [20:47] <klaxa> you'd probably have to resample audio [20:47] <klaxa> but you can try to simply specify -f flv [20:47] <Sc0rc3d> yes i does it with :v copy [20:47] <LithosLaptop> ffmpeg -re -i xx.mp4 -vcodec copy -acodec aac -ab 256k -strict -2 -cutoff 15000 -f flv rtmp://111.222.333.444:1935/live/ [20:48] <Sc0rc3d> omg he does it [20:48] <Sc0rc3d> but it lags ^^ [20:48] <LithosLaptop> haha [20:48] <LithosLaptop> ahh [20:48] <Sc0rc3d> is there a buffer param? [20:49] <Sc0rc3d> awsome :> [20:49] <LithosLaptop> I am not sure, are you streaming over the internet? [20:49] <Sc0rc3d> yep from my qnap nas -> root server [20:49] <Sc0rc3d> t hink not it runs without lag [20:50] <Sc0rc3d> i got enough speed i think http://www.speedtest.net/result/2561684204.png :> [20:50] <LithosLaptop> wow [20:50] <LithosLaptop> want to see mine? [20:51] <LithosLaptop> :) [20:51] <Sc0rc3d> sure :> [20:52] <Sc0rc3d> so there is a -bufsize param expamle "-bufsize 1835k" [20:52] <Sc0rc3d> but cant find on the ffmpeg wiki ^^ [20:52] <LithosLaptop> http://www.speedtest.net/result/2639235177.png [20:53] <Sc0rc3d> uff thats pretty slow bro :) [20:53] <LithosLaptop> hehehe [20:53] <LithosLaptop> mabe I can stream a 160x120, 12fps video :) [20:54] <klaxa> you could stream 1280x720 30 fps video if the bitrate is low enough [20:54] <klaxa> it's not a quesiton of the resolution and framerate :P [20:55] <klaxa> http://x264dev.multimedia.cx/archives/98 [20:55] <uffo> does anyone knows what this means http://pastebin.com/rYM14sRS [20:56] <klaxa> it means "This syntax is deprecated, use '|' to separate sample rate." [20:56] <klaxa> however, if we don't know what you entered to trigger that we can't really help [20:56] <klaxa> (or at least i can't) [20:57] <uffo> ffmpeg.exe -i i.mts -map 0 -map_metadata 0:s:0 -codec:a libfdk_aac -profile:a aac_low -vbr 2 -afterburner 1 -flags +qscale -vn OUTPUT_AAC.m4a [20:57] <uffo> what i should replace here [20:57] <uffo> to lose message [20:59] <klaxa> hmm good question, no idea though... [21:00] <LithosLaptop> yeah, it looks ok [21:00] <klaxa> put the complete console log on pastebin [21:00] <klaxa> that might give more hints [21:01] <durandal_1707> nothing, message is from inserted filter [21:01] <durandal_1707> updating to latest master should silence that nonsense spam [21:01] <uffo> http://pastebin.com/965aGrG0 [21:02] <uffo> even with other codecs it apears [21:02] <durandal_1707> as i already said, nothing is wrong at your side [21:03] <uffo> thanks, then i just ignore it [21:05] <Sc0rc3d> oh i forgot thanks a lot to klaxa and LithosLaptop [21:05] <Sc0rc3d> :) [21:09] <LithosLaptop> no prob :) [21:24] <uffo> looks like my last problem is connected with this [21:24] <uffo> http://permalink.gmane.org/gmane.comp.video.libav.devel/44209 [21:24] <uffo> what this means [21:28] <durandal_1707> uffo: uffo what problem with ffmpeg do you have? [21:29] <uffo> i tried to engode, encoding fine just warning messages http://pastebin.com/965aGrG0 [21:29] <uffo> encode* [21:30] <durandal_1707> uffo: when you compiled ffmpeg from source? [21:31] <uffo> today [21:31] <durandal_1707> why? [21:31] <durandal_1707> anyway you could fetch and recompile again and that warning should dissapear [21:32] <uffo> http://permalink.gmane.org/gmane.comp.video.libav.devel/44209 how this is connected because this has something to do with this i presume [21:32] <uffo> This syntax is deprecated", use '|' to separate channel layout [21:33] <uffo> what layout? i dont see anything similar [21:33] <durandal_1707> uffo: because converions is done in background [21:33] <durandal_1707> see -v debug [21:34] <uffo> so i just should ignore this, that this do not cause anything [21:35] <durandal_1707> is runs this filter for example aformat=sample_fmts=u8,s16p [21:35] <durandal_1707> but now it it is: aformat=sample_fmts=u8|s16p [21:38] <uffo> weird that it displays to me if i do not use this, is this just a todays build bug? [21:40] <durandal_1707> uffo: it is already fixed, (i'm repeating myself several times) [21:40] <uffo> i understood [21:40] <uffo> thanks [21:46] <brontosaurusrex> whats the procedure to get certain file to work in ffmpeg? is that a bug, request or what exactly? mailing list or something else? [22:30] <stefan_> Did anybody see Mans conversation with Mr. Russell King over at the linux mailing lists? [22:30] <ubitux> i did :) [22:31] <stefan_> I felt so remided of the old days on the ffmpeg-devel mailing list. [22:34] <stefan_> http://thread.gmane.org/gmane.linux.ports.arm.kernel/230304/focus%3D230523 for the one interested in doing some reading up [00:00] --- Fri Apr 12 2013