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

[burek]

[00:27] <tpd> hey, all im going through the source looking for the amr narrow band code
[00:28] <tpd> there is wide band c source, but i cant find them
[00:29] <tpd> i see a ffmpeg/libavcoded/amrnbdec.c
[00:29] <burek> Megapixar, yes you can
[00:30] <tpd> oh shit, im tarded
[00:33] <burek> raptor67682, http://ffmpeg.gusari.org/viewtopic.php?f=25&t=39
[00:33] <juanmabc> .oO(MegaPixal would be a cool nick)
[00:36] <burek> "using the built-in segmentation feature" :D I already thought of segmentation faults that were recently discovered and connected the statement with that and loled for a couple of seconds :D
[00:37] <burek> drno_, why dont you simply name your output files with current date
[00:37] <burek> like ffmpeg -i ... output-`date "+Hms"`.avi
[00:38] <lsb> hey all, im looking for a amr narrow band encoder in libavcodec, im looking at the source, and all i see is a decoder,
[00:39] <burek> that should have been: ffmpeg -i ... output-`date +"%H-%i-%s"`.avi
[00:39] <burek> or just use %F (full date)
[00:39] <juanmabc> then if you are lucky it's work in progress, lsb
[00:40] <lsb> hah, well aparently ffmpeg can encode to amr
[00:40] <durandal_1707> lsb: via libopencore-amr
[00:44] <lsb> so its not apart libavcodec?
[00:44] <lsb> a part of
[00:44] <JEEBsv> it's a library that then can be used via libavcodec
[00:44] <JEEBsv> just like libx264 for H.264 encoding
[00:51] <lsb> well here is what i have gathered
[00:51] <lsb> do you knw about audacity
[02:12] <drno_> burek: Sorry for the delay. =)  Thanks for your reply.  I have tried that actually.  With the built-in segmenter, the filename is interpreted ONCE, and only once.
[03:49] <Sashmo> Can anyone help me out here.  I am getting tons and tons of errors while decoding a multicast stream.  If use a none DVB source, just an IP source from a professional encoder, it works amaizng, but if I use a DVB source from satalite, I get tons of errors ->, http://pastebin.com/nm8Zt3HR
[04:24] <lolfrenz> when using libmp3lame to convert to mp3, how can I make it use the best quality it can? (i.e. supply no bitrate)
[04:25] <lolfrenz> I'm converting a flv to an mp3 using ffmpeg -i file.flv -acodec libmp3lame file.mp3
[06:00] <brocatz> i need to capture from dshow to disk then i need to use avisynth to edit the file, then i need to output it to x264
[06:00] <brocatz> what format should i use for the initial capture
[06:00] <brocatz> audio and video
[06:00] <teratorn> anything wrong with x264, high quality?
[06:01] <brocatz> i don't think i need to actually encode it first time through
[06:01] <brocatz> i was thinking yuv or whatever
[06:01] <teratorn> what
[06:01] <teratorn> format and how long?
[06:02] <brocatz> 1280x720 @ 25 for a few minutes, but i can put a 500gig ssd into the machine easy enough
[06:02] <brocatz> it's recording people give interviews
[06:02] <brocatz> then automatically editing them afterward
[06:02] <teratorn> you want to trust RAM to that?
[06:02] <teratorn> :)
[06:02] <brocatz> third generation intel ssds should be suitable
[06:02] <teratorn> i guess
[06:03] <teratorn> what's this for, if you don't mind me asking?
[06:03] <brocatz> letting people give their impressions during a trade show, like a photobooth but for video
[06:04] <brocatz> friend just finished building the booth shell this week
[06:04] <teratorn> commercial or just personal stuff?
[06:04] <brocatz> i'd say prototype
[06:04] <teratorn> its funny i work in that space
[06:04] <brocatz> we're just a couple of freelancers
[06:04] <teratorn> well not that funny
[06:04] <teratorn> cool
[06:04] <teratorn> http://catturavideo.com that is where i work
[06:05] <brocatz> oh cool, yeah i see what you mean
[06:06] <teratorn> yeah :)
[06:06] <teratorn> it's interesting
[06:07] <teratorn> have you been to any shows lately?
[06:09] <brocatz> what kind of shows
[06:09] <brocatz> i'm in new zealand
[08:24] <brocatz> hey, i'm trying to use ffmpeg with avisynth, i've done that before but now i'm getting the same problem as this guy is having http://ffmpeg.org/trac/ffmpeg/ticket/1410
[08:28] <TACPILOT> I am using avisynth with ffmpeg. Is there a way to use a piped stream as the input in an avs file ??
[08:40] <brocatz> hum looks like the ffmpeg build
[09:41] <o]> I need to change the mp3 audio codec from a video to any other that my tv supports.
[09:41] <o]> how can I do that with ffmpeg?
[10:06] <brocatz> so my ffmpeg from 2010 runs avisynth fine, but the newer versions i have, including the one i compiled a few days ago, don't want to run it
[11:18] <phoenixson> I have general question on video formats. What are the safest formats to go for in terms on web video atm?
[11:19] <zap0> teh web is a transport medium. video is a file.   they are different things.
[11:20] <phoenixson> well I was thinking in terms of compability its tricky btw webm, mp4, ogg, flv
[11:20] <Tjoppen> phoenixson: at work we're using mp4/h264/mp3, ogg/theora/vorbis and webm/vpx/vorbis
[11:21] <Tjoppen> for container/video/audio
[11:21] <phoenixson> and thats overs IE, Mozilla, Chrome, Safari and Opera?
[11:21] <phoenixson> covers*
[11:21] <Tjoppen> dunno. works in firefox and chrome at least
[11:22] <phoenixson> ha its something
[11:22] <Tjoppen> should work in recent versions of ei too, since win7 does mp4
[11:22] <phoenixson> but then the whole Mac army is using Safari and Opera
[11:22] <Tjoppen> I'd be surprised if mac didn't do mp4
[11:23] <phoenixson> well I am will try the ones you suggested.
[11:23] <phoenixson> content is going to be delivered to me and then I will do testing
[11:23] <Tjoppen> of course there's plenty of pitfalls with what profiles etc. you choose (esp. for h264)
[11:23] <Tjoppen> just fuck around and search the web a bit - you'll figure it out
[11:24] <phoenixson> thats true...thats for your help tho
[12:04] <HerbertPumpkin> Will ffmpeg use DPX sequences as input these days? Could I get it to mux in a soundtrack at the same time? If so, how? I've googled, but DPX-related stuff seems a bit obscure.
[12:05] <HerbertPumpkin> Best I can find is something like ffmpeg -f image2 -i "Movie_Frame_%04d.dpx" but I'm not sure if that's correct.
[12:05] <Tjoppen> dpx works, as long as they're named in a way you can use the percent syntax for
[12:05] <Tjoppen> like any other image sequence
[12:05] <HerbertPumpkin> what's the whole "image2" thing
[12:06] <Tjoppen> magic. I'm not sure if it's required in this case
[12:06] <burek> o], ffmpeg -i input.avi -vcodec copy -acodec ... output.avi
[12:07] <HerbertPumpkin> so, perhaps something like:
[12:07] <gavlig> hi. i'm using libav(codec, format and utils) from my application to cut videos. i'm doing that by copying the frames i need from one stream to the new one. It works most of the time but not with videos which have parser in their streams. If they have parser, output video doesn't contain framerate, fps, tps and bitrate info. Any thoughts what could cause that?
[12:07] <HerbertPumpkin> ffmpeg -f image2 -i "movie_%04.dpx" -r 24 -acodec libx264 -b 5000k
[12:07] <HerbertPumpkin> ...maybe?
[12:07] <Tjoppen> -r 24 before -i
[12:08] <Tjoppen> -vcodec libx264
[12:08] <HerbertPumpkin> oh.
[12:08] <HerbertPumpkin> of course, that was more a slip of the fingers :)
[12:08] <Tjoppen> use CRF mode instead of specifying a bitrate, like -crf 24
[12:08] <HerbertPumpkin> I find it's very hard to make ffmpeg stick to any particular bitrate anyway
[12:08] <HerbertPumpkin> tends to do what it wants
[12:08] <HerbertPumpkin> god knows how you're supposed to actually tell it how many bits per second you want\
[12:09] <HerbertPumpkin> what would 24 give me?
[12:09] <Tjoppen> you wouldn't - you tell it what quality you want
[12:09] <Tjoppen> 24 is x264's (the CLI) default
[12:09] <Tjoppen> lower is better
[12:09] <burek> gavlig, you can always read ffmpeg's source code to figure out some things
[12:09] <HerbertPumpkin> I want about 5mbps
[12:10] <Tjoppen> just run it and see what you get
[12:10] <HerbertPumpkin> That's ridiculous; can't I specify numerically?
[12:10] <Tjoppen> aiming for some bitrate only makes sense if you're broadcasting or need to stick the file on some limited size media
[12:10] <burek> HerbertPumpkin, yes you can
[12:10] <HerbertPumpkin> It makes sense if that's what I've been asked for.
[12:11] <Tjoppen> -b should work fine then
[12:11] <HerbertPumpkin> Why is CRF recommended?
[12:11] <Tjoppen> let me turn that around: why would you want CBR?
[12:11] <gavlig> burek: i knew you'd say so :) but i can't find the solution of my problem there. I'm copying everything to the new context as it is done in ffmpeg.c but that doesn't help. I think there is something less obvious than copying info from one context to another, but i have no idea what is it
[12:12] <HerbertPumpkin> Tjoppen: I have no idea. That's what I've been asked for. Mine is not to reason why.
[12:12] <HerbertPumpkin> The documentation is pretty poor, by the way. I looked at it to figure out how to set frame rate, for instance.
[12:12] <Tjoppen> well, there you go then. I care about apparent quality, not bitrate
[12:12] <HerbertPumpkin> It tells you what valid options are (things like 24000/1001), but not what the actual option is called, "-r".
[12:12] <HerbertPumpkin> Which is crazy.
[12:13] <HerbertPumpkin> What if I wanted to mux in a soundtrack too?
[12:13] <Tjoppen> an extra -i and maybe use -map. I don't recall the syntax
[12:14] <burek> gavlig|food, http://ffmpeg.org/developer.html
[12:14] <HerbertPumpkin> Is there a -crop as well as -s for scale?
[12:15] <burek> it is possible to use VBR (-crf) with defined max bit rate
[12:15] <burek> i.e. to tell FFmpeg to make VBR but not to go too far with bit rate
[12:16] <HerbertPumpkin> I assume it won't read the framerate in DPX headers
[12:16] <HerbertPumpkin> so I'll need to give it -r 24000/1001 etc
[12:16] <burek> HerbertPumpkin, from which url did you read the docs?
[12:16] <HerbertPumpkin> Several.
[12:16] <burek> did you read official docs?
[12:16] <HerbertPumpkin> Exactly what constitutes "official docs" tends to change depending on who you talk to.
[12:17] <burek> http://ffmpeg.org/ffmpeg.html#Video-Options
[12:17] <HerbertPumpkin> if I specify -s 1920x1080 it'll scale the input to fit, as opposed to scale and crop, right?
[12:17] <burek> and it doesn't depend on anything but the official domain name :)
[12:17] <burek> first read that link
[12:17] <burek> and then tell me what do you see
[12:18] <HerbertPumpkin> How would I go about cropping, say, 100 pixels top and bottom
[12:18] <burek> do you see -r on that page
[12:18] <burek> ‘-r[:stream_specifier] fps (input/output,per-stream)’
[12:18] <burek> Set frame rate (Hz value, fraction or abbreviation).
[12:18] <burek> etc
[12:19] <HerbertPumpkin> Yes we've worked out the rate thing, burek
[12:19] <HerbertPumpkin> I'm trying to figure out cropping
[12:19] <burek> you can read that same document
[12:19] <burek> for any option you need
[12:19] <HerbertPumpkin> Personally I have no idea what "`r[:stream_specifier]" means
[12:20] <burek> nobody does at the first read
[12:20] <burek> that's normal
[12:20] <burek> for such a complex and useful tool like ffmpeg is, it is normal that the documentation will be somehow harder to understand if you are new to all that
[12:20] <HerbertPumpkin> I'm trying to figure out how I'd go about cropping it down.
[12:20] <burek> HerbertPumpkin, read that document and you'll find out
[12:21] <burek> for example, try CTRL+F 'crop'
[12:21] <HerbertPumpkin> OK, that's very nice, but that document doesn't seem to contain any examples and would appear to be a reference for software engineers, not users.
[12:21] <burek> would you just RTFM?
[12:21] <HerbertPumpkin> I found http://ffmpeg.org/trac/ffmpeg/wiki/FilteringGuide but it doesn't include much more information
[12:22] <HerbertPumpkin> it's far from obvious what "crop=width:height:x:y" means
[13:10] <brocatz> hey guys, i just compiled ffmpeg with the mingw package so that i could apply a patch and everything works fine, but now when i try to use avisynth it fails, it says permission denied, but i think that error is a side effect of another error, my other version of ffmpeg from 2010 (when i last used avisynth with it) works fine
[13:10] <brocatz> wondering if there are any obvious things i should check
[13:12] <Mavrik> hmm
[13:12] <Mavrik> brocatz: haven't seen that error on my mingw builds yet
[13:13] <Mavrik> maybe the binary can't find .dll files
[13:13] <brocatz> well actually
[13:13] <brocatz> i got another prebuilt ffmpeg
[13:13] <brocatz> and it wont run it either
[13:13] <Mavrik> brocatz: try running this: http://technet.microsoft.com/en-us/sysinternals/bb896645
[13:13] <Mavrik> filtering on the ffmpeg.exe
[13:13] <brocatz> [avs @ 00000000016cf320] AVIFileOpen failed with error -2147221164
[13:13] <brocatz> C:/temp/output.mp4.1.avs: Operation not permitted
[13:13] <Mavrik> and see which file it's trying to open
[13:14] <brocatz> oh yep i have that already
[13:14] <brocatz> ok
[13:15] <Mavrik> usually those errors can come from different sources :)
[13:15] <brocatz> yep
[13:15] <brocatz> that's what i figured
[13:16] <brocatz> i was wondering if my ffmpeg binary is inadvertently 64bit
[13:16] <Mavrik> you'd get a "binary not supported" error on start
[13:16] <Mavrik> plus, you need to try really hard to build a 64bit binary with mingw -_-
[13:17] <brocatz> binary not supported from avs?
[13:17] <brocatz> i guess avs is already sending a meaningful error
[13:17] <brocatz> so it's been entered
[13:17] <Mavrik> oh, sorry, forgot you're running through avs
[13:21] <brocatz> how do i track what it tries to open
[13:21] <brocatz> it closes too fast
[13:32] <murali> i'm trying to install ffmpeg with x264 support in my linux fedora 14 machine. but couldn't locate the libx264.so file even though it's installed in my /usr/lib directory. please help.
[13:33] <brocatz> murali: are they both 32bit?
[13:33] <murali> yes. my machine by itself is 32-bit.
[13:34] <murali> [root at SS59-MAA ffmpeg-0.11.1]# ./configure --enable-gpl --enable-libmp3lame --enable-libx264 --enable-shared  ERROR: libx264 not found
[13:34] <murali> [root at SS59-MAA ffmpeg-0.11.1]# ls /usr/lib/libx264.so* /usr/lib/libx264.so  /usr/lib/libx264.so.102
[13:35] <sacarasc> murali: What does the config.log say?
[13:36] <murali> gcc -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -std=c99 -fomit-frame-pointer -pthread -E -o /tmp/ffconf.gChSmshI.o /tmp/ffconf.vlAAMhUb.c /tmp/ffconf.vlAAMhUb.c:1:18: fatal error: x264.h: No such file or directory
[13:36] <murali> compilation terminated.
[13:36] <murali> ERROR: libx264 not found
[13:36] <microchip_> murali: install libx264-dev or similar
[13:36] <brocatz> yeah
[13:36] <sacarasc> You might have to upgrade x264, too...
[13:37] <brocatz> it looks pretty planely like it wants x264.h which will be in the dev package
[13:37] <juanmabc> if you manually placed the /usr/lib, the problem is /usr/inclucde
[13:37] <murali> ok. i'm installing now. gimme 5 mins.
[13:37] <juanmabc> do not put lib there
[13:37] <juanmabc> its for headers
[13:38] <juanmabc> ah, -dev, ok
[13:39] <murali> it worked i guess, but some version conflict . it requires ERROR: libx264 version must be >= 0.118
[13:40] <murali> i'll compile it from source.
[13:40] <sacarasc> Uninstall the package one first.
[13:41] <murali> ok.
[13:53] <burek> murali, type ldconfig
[13:56] <murali> i compiled it from source. but the x264.h like similar header files are not copied to /usr/include
[13:56] <murali> so i copied some 4 .h files to /usr/include.
[13:56] <burek> /usr/local/include
[13:56] <burek> don't copy anything manually man
[13:56] <murali> the libx264 enabled is yes after configure script is run.
[13:56] <burek> compile x264 from source and after that type ldconfig
[13:57] <burek> then configure your ffmpeg
[13:57] <murali> but it shows a compilation error.
[13:57] <burek> http://ffmpeg.gusari.org/viewtopic.php?f=25&t=38
[13:57] <burek> just skip the libaacplus part
[13:58] <burek> i.e. configure with: ./configure --enable-shared --enable-gpl --enable-libmp3lame --enable-libx264
[13:59] <murali> it's already skipped.
[14:00] <burek> did you compile x264?
[14:00] <murali> yeah. i compiled. make and make install.
[14:00] <burek> and ldconfig
[14:00] <murali> but make install didn't work as expected.
[14:01] <murali> ./configure --enable-static --enable-shared --enable-gpl --enable-nonfree --enable-libmp3lame --enable-libaacplus --enable-libx264
[14:01] <murali> [root at SS59-MAA x264-snapshot-20120624-2245]# make install install -d /usr/local/bin install x264 /usr/local/bin
[14:02] <juanmabc> the x264 you build, uses/should use ./configure ... --prefix=/usr, or ffmpeg would need --with-libx264=/usr/local or whatever (ffmpeg part not checked ./configure --help | grep -i x264)
[14:02] <murali> sorry, ingore my previous paste.
[14:03] <murali> i've changed my configure script input as suggested by burek and it's compiling.
[14:03] <sanderj> Can ffmpeg handle live video?
[14:03] <burek> ok
[14:03] <burek> sanderj, yes
[14:04] <sanderj> burek, do you got an example of it?
[14:04] <burek> sanderj, it's too wide topic
[14:04] <murali> no use. it's same. libavcodec/libavcodec.so: undefined reference to `x264_bit_depth' libavcodec/libavcodec.so: undefined reference to `x264_encoder_open_125' collect2: ld returned 1 exit status make: *** [ffmpeg_g] Error 1
[14:04] <burek> can you give some more specifics on what's your live video
[14:04] <burek> murali, type dpkg -l | grep x264
[14:04] <burek> or yum
[14:05] <sanderj> burek, to make a web video confreance system?
[14:05] <sanderj> with multiple people..
[14:05] <burek> well I guess it's possible
[14:05] <burek> but I never tried it in such configuration
[14:05] <burek> I always used sip server for that
[14:06] <sanderj> But how do I recive a stream as input, and sends it as output?
[14:06] <sanderj> in ffmpeg.
[14:06] <burek> ffmpeg -i input -vcodec copy -acodec copy output
[14:09] <sanderj> And then I have to make a wrapper which recives it on a port, and sends it to stdin?
[14:09] <burek> no
[14:09] <burek> ffmpeg -i http://blabla:port/stream.flv -vcodec copy -acodec copy udp://blabla:port/
[14:11] <murali> burek, it's a fedora. it's yum. i'll try anyway? but tell me what should i find?
[14:11] <burek> x264-dev
[14:11] <burek> and x264
[14:11] <burek> and uninstall those
[14:11] <sanderj> burek, How do I get a webbrowser to send data to ffmpeg?
[14:11] <burek> because you are compiling the latest anyway
[14:11] <burek> sanderj, why on earth would you do that?
[14:12] <sanderj> Because I want to capture it from the web camera. and send it to ffmpeg.
[14:12] <burek> where does webbrowser appear in that scenario?
[14:13] <murali> burek, will this installer script help me?
[14:13] <murali> or atleast, will it help sanderj. he he.. :-)
[14:13] <burek> murali, what installer script?
[14:14] <sanderj> burek, Because it will be an web video conferance app.. Just like google+ hangout.
[14:14] <murali> http://www.ffmpeginstaller.com/
[14:14] <burek> murali, no need for that
[14:14] <burek> just compile things regularly
[14:14] <sanderj> burek, I don't see how ffmpeg gets the input from another machine.
[14:15] <burek> sanderj, you need a webbrowser plugin that will capture the video, encode it and send it over the web to your ffmpeg
[14:15] <murali> ok. fine. i'll do that compilation by myself.
[14:15] <burek> at least that is how googla talk does it
[14:15] <burek> sanderj, ffmpeg -i http://anothermachine:port/bla.asf
[14:16] <burek> or ffmpeg -i udp://localhost:port
[14:16] <burek> if you send udp traffic to ffmpeg
[14:16] <sanderj> burek, but with that ffmpeg -i command.. it require that the webbrowser plugin have an open port I belive..?
[14:17] <sanderj> I want ffmpeg to listen to a port for incoming video.
[14:19] <burek> ffmpeg -i udp://localhost:incomingport
[14:19] <sanderj> Cool.
[14:21] <sanderj> burek, do you know about any such video webbrowser plugin?
[14:22] <sanderj> Wondring how google hangout makes it without a plugin.
[14:22] <burek> it uses plugin
[14:25] <murali> burek, i did a ./configure --enable-satic --enable-shared --system-libx264 and all the header files are copied into their apropriate directories i guess. now i'm compiling ffmpeg again with ./congfiure options you suggested.
[14:25] <murali> but still, the same error libavcodec/libavcodec.so: undefined reference to `x264_bit_depth' libavcodec/libavcodec.so: undefined reference to `x264_encoder_open_125' collect2: ld returned 1 exit status make: *** [ffmpeg_g] Error 1
[14:26] <sacarasc> murali: You didn't uninstall the old x264, did you?
[14:26] <burek> why --system-libx264 ?
[14:26] <burek> I thought the post on that forum was really straight forward
[14:26] <murali> i was just trying my luck. sorry.
[14:27] <murali> ok. will read it again. and get back to u .
[14:27] <burek> uninstall all x264* you have
[14:27] <burek> in your package manager (google how to do that properly on your os)
[14:27] <burek> and then compile libx264 and then ffmpeg
[14:27] <burek> it's a 4-5 minute of work
[14:28] <xero-exez> Hi All, First things first "thnxz for ffmpeg"
[14:28] <AlRazi> ffmpeg aac+ output file duration is 789:57:13 on itunes
[14:29] <xero-exez> I can not find the answer to the following question:
[14:30] <sanderj> burek, do I have to have a certain version of ffmpeg to make streaming possible?
[14:30] <xero-exez> "Why is (using H264) only the baseline profile suported/accepted as a parameter for -vprofile"
[14:31] <burek> sanderj, I don't know, usually I use the latest :)
[14:31] <AlRazi> burek, ffmpeg aac+ output file duration is 789:57:13 on itunes
[14:32] <burek> xero-exez, where did you read that?
[14:32] <burek> AlRazi, that's cool :)
[14:32] <AlRazi> lool
[14:32] <AlRazi> yeah but when trying to stream it from our web app, it downloads the whole file first then start playing it
[14:33] <AlRazi> the duration tag doesn't add up to the player i reckon
[14:33] <xero-exez> @burek I did not read that, ffmpeg doesnt accept it
[14:33] <burek> xero-exez, why would you use -vprofile?
[14:33] <burek> xero-exez, can you please use pastebin.com, to show your command line and its output?
[14:33] <sacarasc> AlRazi: To get around that, run `qt-faststart` on the MP4 file.
[14:34] <burek> either that, or if your app is ffmpeg, tell it to use -flags +global_header
[14:34] <xero-exez> @burek since -profile isn't compatable any more...thanks I will paste just a minute
[14:34] <burek> (for AlRazi)
[14:34] <burek> xero-exez, most probably you are using an old ffmpeg.. you should stick to native x264's -profile (mapped option in ffmpeg)
[14:35] <AlRazi> if my app is ffmpeg ? excuse my ignorance here .. what happens is that when the user uploads an mp3 a background job initiates an ffmpeg process for conversion and then upload the resulting file to an S3 bucket
[14:35] <AlRazi> do i add -flags +global_header to the ffmpeg process command ?
[14:36] <xero-exez> ffmpeg version git-2012-05-23-7a0d00d built on May 23 2012 16:47:13 with gcc 4.6.1  Thank you for the hint I will check it out
[14:36] <xero-exez> @burek
[14:37] <burek> xero-exez, can you please use pastebin.com, to show your command line and its output?
[14:38] <burek> AlRazi can you show your ffmpeg encoding command
[14:38] <burek> use pastebin
[14:38] <AlRazi> http://pastebin.com/YutdQ98d
[14:38] <xero-exez> @burek I'm on it. Just a sec...and thanks
[14:39] <AlRazi> and here is the configurations
[14:39] <AlRazi> http://pastebin.com/E1hUjnMD
[14:40] <AlRazi> the m4apath variable ends with  (.m4a) should I try it with (.acc) ?
[14:41] <sanderj> burek, This one got an "Unable to find a suitable output format for 'udp://localhost:4444'": ffmpeg -i udp://localhost:4444 -vcodec copy -acodec copy test-output.flv& ffmpeg -i test-input.flv -vcodec copy -acodec copy udp://localhost:4444
[14:43] <sanderj> The format is Video: flv, yuv420p Audio: mp3, 44100 Hz
[14:43] <sanderj> Seems stream 0 codec frame rate differs from container frame rate: 1000.00 (1000/1) -> 29.92 (359/12)
[14:43] <sanderj> HMM..
[14:44] <burek> oh I see..
[14:44] <burek> AlRazi, now, you would like to stream that mp4, right?
[14:44] <AlRazi> yes sir
[14:44] <burek> well, you'll either have to use qt-faststart as sacarasc suggested
[14:44] <burek> or don't save as mp4, but instead use .aac or .flv
[14:45] <AlRazi> i already download the python version
[14:45] <AlRazi> hmm let me try changing to aac quick and i'll let you know
[14:45] <burek> sanderj, can you please use pastebin.com, to show your command line and its output?
[14:45] <AlRazi> but if you don't mind explaining why would .aac solve it ?
[14:46] <burek> different format/container
[14:46] <burek> that is more suitable for streaming
[14:46] <burek> instead of mp4 which is more suitable as a file storage
[14:46] <burek> (keeps some important info at the end of file, that's why you need to download a whole file before playing it)
[14:46] <AlRazi> but what i use is m4a not mp4
[14:46] <AlRazi> if that makes any difference
[14:46] <xero-exez> @burek You helped me out ;) Had a question earlier about profiles (baseline,main, high)Thnxz
[14:46] <burek> qt-faststart fixes that by moving that data to the front of the file
[14:46] <AlRazi> oh
[14:47] <burek> xero-exez, :beer: :)
[14:49] Action: xero-exez is handing over a :beer: to burek
[14:51] <sanderj> burek, http://pastebin.com/HymxXXZt
[14:52] <AlRazi> burek, aac requires flash player as opposed to my html5 player, and qtfaststart output is still giving those false readings on itunes : /
[14:52] <burek> html5 player also requires things (like installed codecs on your OS) so it's pretty much the same trouble both ways
[14:53] <burek> oh iOS :)
[14:53] <burek> good luck with that :)
[14:54] <burek> sanderj, your ffmpeg is ancient
[14:54] <burek> you really need to update it
[14:54] <Nedwada> 'm having a problem, using ffmpeg version 0.10.2.git.   If i open an m3u8, and this is redirected inside its stream, i get a segfault error | http://privatepaste.com/2374deb5f0 |
[14:55] <Nedwada> can someone help?
[14:55] <burek> Nedwada, this is probably a bug, can you report it please: http://ffmpeg.org/bugreports.html
[14:56] <Nedwada> i'm not very good at those things
[14:56] <Nedwada> but i will try
[14:57] <burek> thanks :)
[15:00] <burek> just testing :)
[15:02] <AlRazi> is the qtfaststart python version accredited ?
[15:02] <AlRazi> or should i use the c library ?
[15:03] <burek> ask google?
[15:03] <AlRazi> ok thanks
[15:08] <swkide> Greetings! Can someone please point me to documentation how to rewrite a program, which still uses AVFormatParameters?
[15:09] <HerbertPumpkin> fsvo "documentation"
[15:10] <swkide> Ok I did dig this source but without success - I wil try again - thnks
[15:11] <swkide> Ok I did dig this source but without success - I will try again - thanks
[15:11] <HerbertPumpkin> Someone should write a basic user's guide to ffmpeg, but it would be a bitch to keep up to date, and you'd never get the developers to endorse it.
[15:13] <saste> swkide: check doc/examples
[15:14] <saste> in case something is outdated you are welcome to send a patch!
[15:14] <burek> HerbertPumpkin, yes, VLC has solved that pretty simple
[15:15] <burek> they installed wiki software and allowed simple users to edit the docs and contribute in that way
[15:15] <burek> not everyone knows how to make a patch :)
[15:16] <swkide> @saste will do thanks
[15:17] <HerbertPumpkin> burek: I was thinking from a "conversion" point of view, not just a viewing thing.
[15:17] <HerbertPumpkin> I use VLC for viewing, but I often need to convert
[15:19] <burek> HerbertPumpkin, well I started this: http://ffmpeg.gusari.org/viewforum.php?f=25
[15:19] <burek> based on issues from this channel
[15:19] <HerbertPumpkin> Really it needs to be at ffmpeg.org
[15:19] <burek> I agree, but there is always something that stands in the way :)
[15:19] <burek> so it's best to leave things as they are now :)
[15:20] <HerbertPumpkin> I mean, if you go there and hit the "general documentation" button, the very first thing you get is "ffmpeg can be hooked up with a number of external libraries... by passing appropriate flags to ./configire"
[15:20] <HerbertPumpkin> that's not general documentation
[15:20] <HerbertPumpkin> that's engineering information
[15:20] <burek> :D
[15:21] <burek> I think I know what answer you'll get most probably :) patch welcome :)
[15:21] <HerbertPumpkin> I'd be perfectly happy to write it
[15:21] <HerbertPumpkin> but they'd never want to endorse documentation
[15:21] <burek> what do you mean
[15:22] <HerbertPumpkin> I've found ffmpeg developers to be, well, openly hostile to non-coders.
[15:22] <burek> it's a professional deformation I guess :) we all don't have patience sometimes, especially when we are always crowded with a ton of work..
[15:23] <HerbertPumpkin> You're not the only ones.
[15:23] <ubitux> ?
[15:24] <ubitux> HerbertPumpkin: i agree the documentation is not perfect, but we are working on it quite often
[15:24] <HerbertPumpkin> I suspect the real problem is that ffmpeg changes its behaviour every three hours so keeping documentation up to date would be quite the task.
[15:24] <burek> HerbertPumpkin, do you have any suggestion how to overcome it?
[15:24] <AlRazi> okay this is strange .. outputting m4a directly won't play, but outputting wav, and then using faac to convert to m4a, it's playable
[15:24] <ubitux> HerbertPumpkin: if you want to add some examples, feel free to add some in http://ffmpeg.org/ffmpeg.html#Examples-2
[15:24] <saste> HerbertPumpkin: i agree "general documentation" for that is a retarded name
[15:25] <burek> AlRazi, maybe your ffmpeg is outdated?
[15:25] <ubitux> saste: documentation page need to be reworked :(
[15:25] <ubitux> the "index" is not really good (http://ffmpeg.org/documentation.html)
[15:25] <AlRazi> Sun May 20 15:20:47 2012
[15:25] <AlRazi> my latest ffmpeg commit
[15:26] <burek> AlRazi, then it might be a bug.. can you please report it?
[15:26] <HerbertPumpkin> I can't even find where the basics are discussed - "ffmpeg -i [input file] [options] [output file]"
[15:26] <burek> HerbertPumpkin, at ffmpeg docs
[15:26] <burek> "FFmpeg Documentation"
[15:27] <ubitux> http://ffmpeg.org/ffmpeg.html#Synopsis
[15:27] <ubitux> first section
[15:27] <HerbertPumpkin> Yes, but the problem is not that it isn't there (it IS there), it's just too hard to find.
[15:28] <ubitux> yeah, the ffmpeg.org/documentation page need to be re-organized
[15:28] <saste> the first part of ffmpeg.texi is really generic, not ffmpeg-specific
[15:28] <burek> while we are at it, would it be better to move "General Documentation" section (with those 7 links) below the "Command Line Interface (CLI) and Related Usage Documentation"
[15:28] <burek> because, after all, ffmpeg is the main thing in this project
[15:28] <saste> that could be moved to a generic file
[15:28] <HerbertPumpkin> I mean, the "synopsis" section is a little, er, bald.
[15:28] <ubitux> i'd move the CLI documentation links above the general one
[15:28] <burek> and docs for ffmpeg could be the first link in docs
[15:29] <saste> burek: it's confusing and wrong to pretend that "ffmpeg" the tool is somehow special with the regards to the other tools
[15:29] <ubitux> and rename "General documentation" into "Supported stuff" or sth like that
[15:29] <burek> or just "other" :)
[15:30] <saste> unfortunately many devs have this feeling that ffmpeg/avconv is special and implement all sort of ad-hoc hacks into it
[15:30] <ubitux> :)
[15:30] <HerbertPumpkin> Personally I have been extremely unimpressed with the way ffmpeg developers engage with non-developers.
[15:30] <HerbertPumpkin> Chip on shoulder, etc.
[15:30] <burek> saste, I do think it's special, otherwise an entire domain wouldn't be named ffmpeg.org :)
[15:30] <HerbertPumpkin> This may explain why the documentation is so dire.
[15:31] <burek> at least that's the impression I get, as an ordinary user
[15:31] <saste> burek: i mean "ffmpeg" the tool and FFmpeg are two distinct thing
[15:31] <saste> ffmpeg is just a facet of a more generic entity
[15:31] <burek> I just say it would be logical (to me) that ffmpeg docs are the first link at docs link, that's all
[15:31] <burek> or CLI section, for that matter
[15:31] <ubitux> 15:28:43 <@ubitux> i'd move the CLI documentation links above the general one
[15:31] <ubitux> 15:29:02 <@ubitux> and rename "General documentation" into "Supported stuff" or sth like that
[15:32] <saste> indeed i hope it will be possible to transcode with ffplay or ffprobe some (not very remote) day
[15:32] <ubitux> anyone wants to send a patch for this? :)
[15:32] <burek> yes exactly ubitux :)
[15:32] <saste> or in other words every tools just emphasize a specific aspect, but functionality should reside in the library
[15:32] <saste> (and application should tend to be as lean as possible)
[15:33] <burek> saste, that's not the issue here :)
[15:33] <burek> HerbertPumpkin, has got a point :) the first group of links in docs is somehow wrongly positioned at the top
[15:33] <burek> when in reality most people are really interested in CLI section of links
[15:34] <HerbertPumpkin> YEs.
[15:35] <burek> for the reference, I'm talking about this page: http://www.ffmpeg.org/documentation.html
[15:35] <saste> ubitux: all for the supported stuff, it would be cool to write a script which parses the souce and detects which formats are supported
[15:35] <saste> that page naturally tend to be outdated and require continuous babysitting
[15:35] <saste> well actually some people love to do that kind of work...
[15:36] <ubitux> :)
[15:37] <ubitux> saste: i would actually print the support and all the options on the same page
[15:37] <ubitux> ideally with some nasty js to show/hide them
[15:38] <ubitux> but i don't want to do that
[15:38] <ubitux> and i don't want to become the website maintainer :)
[15:39] <HerbertPumpkin> Well, I think you're right
[15:39] <HerbertPumpkin> the amount of work it would take to keep a comprehensive ffmpeg user guide up to date is enormous.
[15:39] <HerbertPumpkin> That being the case, perhaps it would be nice if every answer in this channel wasn't "RTFM", eh?
[15:39] <burek> :)
[15:40] <saste> HerbertPumpkin: they are called links to documentation, and apparently many users don't know that there is a manual apparently
[15:40] <HerbertPumpkin> If you can't find it, there effectively isn't.
[15:40] <ubitux> HerbertPumpkin: it looks like you are willing to improve things, that's great! Will you join us and contribute by helping the users? :)
[15:40] <saste> i wrote much part of it (e.g. filters documentation) and i don't feel like i want to rewrite it (again) on the ML
[15:40] <HerbertPumpkin> No. ffmpeg developers tend to be asshats, and I'm not willing to work with those people.
[15:41] <ubitux> HerbertPumpkin: well, that's not that hard, clic documentation, and then ffmpeg
[15:41] <ubitux> HerbertPumpkin: ok :(
[15:41] <HerbertPumpkin> Sorry, but they brought it on themselves.
[15:41] <saste> HerbertPumpkin: give it a try, otherwise your claims are injustified (and unfair)
[15:41] Action: HerbertPumpkin enjoys a slice of pie
[15:42] <ubitux> i think a bad or incomplete documentation will just bring more user complains
[15:42] <HerbertPumpkin> So do I.
[15:42] <ubitux> i think we should drop completely the documentation
[15:42] <burek> btw, regarding the documentation, why there is no interest in creating a wiki docs?
[15:42] <burek> it's much easier to maintain it
[15:42] <ubitux> because it would split the work
[15:43] <ubitux> the wiki is nice for examples though
[15:43] <saste> burek: we have it on trac
[15:43] <HerbertPumpkin> Most of the time when I google I tend to find that I get information from forum posts and the like, not ffmpeg.org
[15:43] <saste> but we need: 1. to publicize it better (no links from the website??)
[15:43] <burek> saste, ok, but why don't you inforce it for docs? why .texi and all that stuff?
[15:43] <saste> 2. to have more people working on it
[15:43] <burek> ubitux, how would it split the work?
[15:44] <ubitux> burek: we like file-versionned documentation
[15:44] <saste> burek: problem is that code and documentation are not different things
[15:44] <HerbertPumpkin> Mainly you would need to get the developers to at least mark parts dirty where they've made changes
[15:44] <saste> when i extend a component i update the documentation as well
[15:44] <HerbertPumpkin> and you'll never get them to do that
[15:44] <burek> ubitux, wiki is all about versioning
[15:44] <ubitux> it's not file oriented
[15:44] <saste> and the documentation is specific of the version that you're using
[15:44] <burek> at least mediawiki, I don't know about ffmpeg's trac wiki
[15:44] <ubitux> burek: and you can't duplicate it easily
[15:44] <burek> its not wikimeda
[15:44] <burek> mediawiki*
[15:44] <ubitux> burek: i like working offline with the doc
[15:45] <ubitux> and know there are some backups everywhere
[15:45] <saste> when we ship ffmpeg version x.xx we want to provide bundled documentation, rather than a link to a website
[15:45] <ubitux> also, by having them in the git, we can follow the changes easily
[15:45] <HerbertPumpkin> ffmpeg doesn't ship versions.
[15:45] <ubitux> (mail notice, git log, etc.)
[15:45] <HerbertPumpkin> you can only claim to be "shipping versions" if you're releasing binaries, which you aren't.
[15:45] <ubitux> HerbertPumpkin: http://ffmpeg.org/download.html#releases
[15:45] <saste> HerbertPumpkin: that's another prejudice, ffmpeg has versions since 3 years at least
[15:45] <HerbertPumpkin> That's source code.
[15:45] <ubitux> HerbertPumpkin: look for "builds" on the same page
[15:46] <HerbertPumpkin> The behaviour of that source code can change wildly depending on how it's compiled.
[15:46] <burek> can't follow all of your arguments, but "ubitux> burek: and you can't duplicate it easily" -> yes you can
[15:46] <burek> ubitux, also offline work is possible too, just update the online version when you are done
[15:46] <ubitux> i can't duplicate the whole wiki content and history
[15:46] <ubitux> easily.
[15:46] <saste> burek: what is makes sense, is keeping "official" and unofficial documentation split
[15:46] <ubitux> also, i like the plain text doc :)
[15:46] <burek> also, it is not difficult to make wiki for x.x version of ffmpeg
[15:47] <burek> and update it accordingly
[15:47] <saste> that is official documentation - shipped with ffmpeg, and wiki for user-guides
[15:47] <burek> (several wikis)
[15:47] <ubitux> really, feel free to update the trac burek :)
[15:48] <burek> ubitux, well trac is not mediawiki
[15:48] <ubitux> so what? :)
[15:48] <burek> and doesn't have all the options to ease the work
[15:48] <burek> so it takes more time to work on it
[15:48] <ubitux> saste: didn't you say you would add an example to https://ffmpeg.org/trac/ffmpeg/wiki/FancyFilteringExamples ?
[15:48] <burek> compare the features and you'll see
[15:49] <saste> ubitux: no you did (the mirror effect)
[15:49] <burek> the point of wiki is that a lot of people can contribute on it, fixing typos, adding additional usage examples, etc
[15:49] <saste> and i have a ton of todo with highest priority right now
[15:49] <saste> like chatting on irc
[15:49] <ubitux> burek: we already have 2 official incomplete sources of documentation, i don't think adding a third will solve anything
[15:49] <ubitux> saste: oh this one, ok
[15:49] <burek> ubitux, not the 3rd, but the combined and one
[15:50] <HerbertPumpkin> I'm with burek, for what it's worth
[15:50] <HerbertPumpkin> not that anyone in charge of ffmpeg will ever take any notice
[15:50] <ubitux> that's the problem
[15:50] <HerbertPumpkin> this conversation is a waste of time; no ffmpeg developer will ever agree to a big change that wasn't his idea
[15:50] <HerbertPumpkin> especially if it came from a non-dev
[15:51] <burek> I'm just saying it from the perspective of an ffmpeg user (not developer) that it's a lot easier to contribute in this way then to learn all the git/patch/texi stuff and practically loose time learning it, which would push me away from wanting to help at all
[15:51] <ubitux> i don't get what's complicated and so painful with the trac wiki
[15:51] <HerbertPumpkin> burek: I assumed that's the idea.
[15:51] <HerbertPumpkin> The last thing developers want is non-developers getting involved.
[15:51] <HerbertPumpkin> They might have to listen to them!
[15:52] <burek> ubitux, I think I already answered that.. check diffs for features of mediawiki and trac wiki
[15:52] <ubitux> also, despite the "sync" issue, it will be yet another source of documentation, so users will likely never know where to look for
[15:52] <HerbertPumpkin> ubitux, the thing to understand is that there really isn't any documentation as it is.
[15:52] <HerbertPumpkin> Other than google.
[15:52] <ubitux> burek: you have to show me it's an issue, because i don't believe so; so you need to raise some specific issues :p
[15:53] <HerbertPumpkin> What's on ffmpeg.org is outdated, fragmentary, disorganised, and hard to find.
[15:53] <burek> ubitux, again.. I don't know why are you bringing same issues again, when I argued them previously.. it won't be "yet another source of docs" it will be one and only
[15:53] <burek> like in VLC
[15:53] <ubitux> the page referencing the documentation isn't perfect and need just some small rework
[15:53] <burek> they joined all the docs and put them to wiki
[15:53] <burek> and look how big the docs are and still well organized
[15:53] <ubitux> the overall documentation is heterogeneous because we focused on the documentation only recently
[15:53] <burek> why not learn from others success?
[15:54] <HerbertPumpkin> There's a focus on the documentation?! Well, you can't tell!
[15:54] <ubitux> HerbertPumpkin: http://git.videolan.org/?p=ffmpeg.git;a=history;f=doc;h=3d84ebf5add3bac99c3624493de84faf7d8e5ecd;hb=HEAD
[15:54] <saste> HerbertPumpkin: i consider your attitude a bit arrogant, considering the amount of my *free time* i dedicated to it
[15:54] <ubitux> all of this affect what's in doc/ directory
[15:55] <HerbertPumpkin> saste: I'm being blunt, I admit.
[15:55] <HerbertPumpkin> But frankly this isn't really about points for effort.
[15:55] <HerbertPumpkin> A lot of effort in open source is wasted for this reason.
[15:55] <ubitux> are you helping in any way?
[15:55] <saste> HerbertPumpkin: it's not like we got a company, money or whatever else backing us
[15:55] <HerbertPumpkin> It doesn't matter how good ffmpeg is; people will still use Compressor or the inbuilt exporter in their NLE because they can't figure out how to use ffmpeg.
[15:55] <HerbertPumpkin> At which point you have to ask why ffmpeg exists.
[15:56] <HerbertPumpkin> If it exists to be useful to people, it needs good documentation.
[15:56] <HerbertPumpkin> If it's just a science project, an experiment, a toy... well, do as you wish, but I don't think that's what you want.
[15:56] <ubitux> burek: again, i'm personally against moving the documentation out the git source tree, but i'm ok splitting them in two: one from the dev, and one from/for the users (and the current trac)
[15:56] <saste> HerbertPumpkin: it is useful on its own, and don't forget that it is the engine of most multimedia apps/services out there
[15:56] <HerbertPumpkin> wtf is a "git source tree"
[15:56] <saste> so at least someone is able to deal with it
[15:56] <ubitux> s/and the current trac/the current trac/
[15:57] <HerbertPumpkin> is that something I need to know in order to understand documentation changes?
[15:57] <ubitux> it's the history of the changes in the project
[15:57] <ubitux> affecting source code, and documentation
[15:57] <burek> ubitux, why the docs need to be in git anyway if mediawiki supports its own versioning of all the content there?
[15:57] <ubitux> i already gave a few arguments for that
[15:58] <HerbertPumpkin> I think the wiki idea is sensible.
[15:58] <HerbertPumpkin> It's easy to contribute, and would spread the workload.
[15:58] <ubitux> we have a wiki
[15:58] <ubitux> and you can contribute
[15:59] <burek> ok, all in all, the idea of wiki had one good thing in mind, to split the need of regular user to know advanced stuff, like git/patch/texi/etc
[15:59] <burek> they just need to log in, use the cool html editor and contribute
[15:59] <HerbertPumpkin> Yes.
[15:59] <ubitux> we should add an url to the wiki in the documentation page btw.
[15:59] <burek> even a person who is not that familiar with computers can contribute.. isn't that valuable?
[15:59] <HerbertPumpkin> One of the ways you make people contribute is to make it easy for people to contribute
[15:59] <ubitux> burek: https://ffmpeg.org/trac/ffmpeg/wiki/FilteringGuide?action=history
[16:00] <HerbertPumpkin> I would probably have tried to write patches for ffmpeg itself (though obviously they would be rejected) if it could be compiled in MSVCC.
[16:00] <ubitux> various ppl contributed here
[16:00] <HerbertPumpkin> They're making it very, very hard to contribute (intentionally, of course).
[16:00] <ubitux> ok i think i'm wasting my time here
[16:00] <ubitux> feel free to keep complaining
[16:00] Action: ubitux &
[16:01] <burek> ubitux, that's cool :) but, let me just point out one really bad thing of that trac.. at least the one that I was embarrassed to realize..
[16:01] <burek> when you go to the home page of it https://ffmpeg.org/trac/ffmpeg/
[16:01] <burek> where is the register button?
[16:01] <burek> to create a new account?
[16:02] <ubitux> login ’ register?
[16:02] <saste> ubitux, burek: i don't like that as well
[16:02] <burek> I know, but come on.. 2 clicks?
[16:02] <burek> why?
[16:02] <ubitux> because it sucks
[16:02] <burek> simple things that irritate people.. :/
[16:02] <saste> don't know if it has to deal with trac defaults
[16:02] <HerbertPumpkin> What's "trac"
[16:02] <burek> :)
[16:03] <HerbertPumpkin> Why someone would use anything other than mediawiki for collaborative docs I have no idea.
[16:03] <HerbertPumpkin> No, wait, I do have an idea - so they can keep out everyone except their little in-group :/
[16:04] <ubitux> because mediawiki doesn't handle issues
[16:04] <HerbertPumpkin> Be more specific?
[16:04] <ubitux> bug tracker
[16:04] <burek> anyway, let's forget the trac/wiki/patches :) the thing is there is a problem for non-advanced users to help contribute to ffmpeg.. that was especially noticeable when Google Summer of Code was actual
[16:04] <burek> we didn't have a way to give tasks to people because everything needed some basic knowledge just in order to start contributing
[16:05] <ubitux> HerbertPumpkin: we want to limit the number of different services (load, consistency, security, ...)
[16:05] <saste> burek: how is that different from "real world"?
[16:05] <HerbertPumpkin> I would attempt to write code for ffmpeg.
[16:05] <HerbertPumpkin> But I can't even compile it.
[16:05] <burek> so I had to convert all those contribs for the docs into patches (had to learn how to do that of course)
[16:05] <ubitux> HerbertPumpkin: and since we're using a bug tracker that does wiki, we use that feature
[16:05] <burek> instead of just giving them link to the wiki and tell them "go there, edit what you find erroneous"
[16:06] <ubitux> burek: then I might have a solution
[16:06] <ubitux> go to the github mirror, and if you have an account, you might be able to directly edit from the web interface
[16:06] <ubitux> and then request a merge etc
[16:06] <saste> ubitux: program an AI will assist users with using ffmpeg, or contributing to it
[16:06] <HerbertPumpkin> Just use bloody mediawiki
[16:06] <HerbertPumpkin> what possible problem is there with it
[16:07] <ubitux> 16:05:01 <@ubitux> HerbertPumpkin: we want to limit the number of different services (load, consistency, security, ...)
[16:07] <HerbertPumpkin> not techy enough for you? too easy for your little linux heads?
[16:07] <ubitux> 16:05:11 <@ubitux> HerbertPumpkin: and since we're using a bug tracker that does wiki, we use that feature
[16:07] <burek> ubitux, and how exactly is that easier in comparison of "just giving them link to the wiki and tell them "go there, edit what you find erroneous""
[16:07] <ubitux> also, we already have some content in the wiki
[16:07] <ubitux> burek: then just give them the link to the wiki
[16:08] <ubitux> anyway, i think it's ok to report typo or error on the devel channel
[16:08] <saste> HerbertPumpkin: "your little linux heads?" - that's offensive, are you aware of it?
[16:08] <burek> ubitux, there is nothing in the wiki!
[16:08] <ubitux> then fill it
[16:08] <burek> because you split it
[16:08] <ubitux> adding another wiki won't fill it
[16:08] <burek> into texi and wiki..
[16:09] <ubitux> it's the third time i explained that git versionning for the documentation is IMHO way better
[16:09] <saste> burek: i agree with ubitux, official and non-official docs should be kept separate
[16:09] <HerbertPumpkin> Yes, ubitux, but you have to be an expert software engineer for that.
[16:09] <saste> no need to keep them together, because they appeal to different kind of users
[16:10] <saste> and... who does the work decide how to do it, especially when he's volunteering his/her own time
[16:10] <saste> there are technical and social reasons for the choice of the wiki and for the use of texi in ffmpeg
[16:10] <ubitux> main doc on git ’ because it is decentralized (we have copies of it), doesn't require stupid web shit (plain text read & edit), it's versionned with tools we can make use of, we can track the changes, etc.
[16:11] <ubitux> user doc on trac (use cases, etc)
[16:11] <HerbertPumpkin> It may be versioned with tools YOU can make use of, but you're a linux-based software engineer.
[16:11] <HerbertPumpkin> It's hopeless.
[16:11] <ubitux> exactly
[16:11] <ubitux> then just report typo issues by opening an issue in the trac
[16:11] <ubitux> and complete the doc in the wiki
[16:12] <HerbertPumpkin> what's a trac?
[16:12] <ubitux> it's a facebook group
[16:12] <ubitux> join it
[16:12] <ubitux> and shut up forever
[16:12] <ubitux> thx
[16:12] <HerbertPumpkin> ..and that is why open source software is so poorly documented.
[16:12] <burek> ubitux, http://www.mediawiki.org/wiki/Git/Workflow
[16:13] <burek> it's not the best wiki software for nothing
[16:13] <ubitux> burek: that's interesting
[16:13] <ubitux> can you generate the manpages out of it?
[16:14] <ubitux> will it be able to handle the generation & installation of them?
[16:14] <ubitux> also, how do you control the users are not trashing the whole documentation?
[16:14] <burek> ubitux, did you know that texi2html can also generate wiki code?
[16:15] <HerbertPumpkin> Same was wikipedia does.
[16:15] <HerbertPumpkin> IE it doesn't really happen.
[16:15] <ubitux> it happens, they have moderators for this
[16:15] <ubitux> and we have reviews.
[16:15] <HerbertPumpkin> Although I suspect that in open source world, writing simple, understandable instructions that are useful to the layperson would be considered "trashing the whole documentation".
[16:15] <burek> I'm just saying there is a need for better documentation.. One way of solving that problem is to open the way for non-advanced users who have free time and will to contribute the text for docs
[16:15] <ubitux> burek: possible, so?
[16:16] <burek> otherwise, because of all the restrictions and requirements present now, the developers are the only one who can do that
[16:16] <burek> and we all know they lack free time always
[16:16] <burek> so.. what's the point of our conversation then..
[16:16] <saste> burek: let's try to avoid to go in circles, we have already a wiki at zero cost, what we lack is people working on it
[16:17] <HerbertPumpkin> burek, in open source world, the reaction to documentation improvement is generally "possible, so?"
[16:17] <saste> one problem is that people don't know how to reach it
[16:17] <HerbertPumpkin> M
[16:17] <HerbertPumpkin> Nobody cares.
[16:17] <HerbertPumpkin> Open source developers don't care.
[16:17] <ubitux> yep
[16:17] <ubitux> OTOH, microsoft let you edit msdn documentation
[16:17] <burek> <saste> one problem is that people don't know how to reach it
[16:17] <burek> true
[16:17] <burek> but also nobody used that before
[16:18] <burek> and it doesn't have a cool html editor, etc etc..
[16:18] <saste> so... either you post a patch, or you open a ticket, or you write a mail on the ML or you just tell it
[16:18] <burek> that way you developers loose free time
[16:18] <saste> if i do it myself, i'll never get rid of it, it is important that users which care do it themselves
[16:18] <burek> and docs suffer.. all users suffer
[16:19] <saste> or they will always rely on other people (especially people which has already a huge workload)
[16:19] <burek> exactly my point
[16:19] <burek> it doesn't have to be wiki
[16:19] <burek> mediawiki*
[16:19] <saste> that said i'll note it on my todo list, and i'll get to do some real work right now...
[16:19] <ubitux> same for me...
[16:19] <burek> it just needs to be something simple that other non-advanced users can easily use.. that's it
[16:19] <HerbertPumpkin> I cant imagine why you wouldn't use mediawiki.
[16:19] <saste> burek: the principle is that we don't have mediawiki, we have trac and is already up and working
[16:20] <burek> saste, ok, let's use ti
[16:20] <burek> it*
[16:20] <saste> it may be not the best, but it's already there and imho good enough
[16:20] <HerbertPumpkin> saste, the documentation is crap; whatever "trac" is, it is NOT working
[16:20] <burek> no, really, let's use it
[16:20] <ubitux> thank you.
[16:20] <burek> if it suits both devels and ordinary users
[16:20] <HerbertPumpkin> It might be technically doing what it's supposed to do, but it is NOT creating good docs, so it is not working.
[16:20] <burek> then its perfect
[16:20] <saste> if there is some interest and someone wanting to do the work, that's welcome (but again it needs some discussion, there is the risk of splitting resources and work, we can't afford that)
[16:20] <ubitux> burek: i'll rework the documentation page tonight
[16:20] <HerbertPumpkin> and you can afford bad docs?
[16:21] <ubitux> burek: i'll add a trac URL, and re-organize a bit the links
[16:21] <burek> cool thanks :)
[16:21] Action: HerbertPumpkin bounces his head off the wall
[16:21] <HerbertPumpkin> Just. Use. Mediawiki. It's free!
[16:21] <ubitux> burek: if you have a minute, please open a trac issue to add a "register" link on the main page
[16:21] <burek> one more thing that needs to be done is that all texi thing is either moved to wiki or wiki is linked to it or something
[16:21] <burek> what ever devels write through texi files, ordinary users need to be able to edit through the wiki
[16:21] <ubitux> no, texi files will stay on git
[16:22] <ubitux> for the reasons i mentionned
[16:22] <burek> otherwise we have a split work, which is bad
[16:22] <HerbertPumpkin> "texi files?"
[16:22] <ubitux> wiki should document different thinbgs
[16:22] <ubitux> HerbertPumpkin: the files used to generate the documentation, they are on git
[16:23] <HerbertPumpkin> *what* documentation!?
[16:23] <burek> did we ever bother to take a look how did guys from videolan solve all their issues using mediawiki
[16:23] <burek> because they have great docs
[16:23] <burek> how did they do that?
[16:23] <burek> why not just copy the idea?
[16:23] <ubitux> HerbertPumpkin: http://git.videolan.org/?p=ffmpeg.git;a=tree;f=doc;hb=HEAD  these files are used to generate pages like http://ffmpeg.org/ffmpeg.html
[16:23] <burek> if it's good of course
[16:23] <HerbertPumpkin> You're trying to tell me that you want to autogenerate a man page that describes the use of ffmpeg in detail?!
[16:23] <HerbertPumpkin> That's crazy!
[16:23] <saste> burek: different kind of users, different *number* of users
[16:23] <ubitux> HerbertPumpkin: that's what we do...
[16:23] <ubitux> HerbertPumpkin: these texi are used to generate the manpages we deploy
[16:24] <ubitux> as well as the official documentation on the website
[16:24] <ubitux> but we also have a user-editable wiki: https://ffmpeg.org/trac/ffmpeg
[16:24] <HerbertPumpkin> bear in mind on windows I don't even see a man page.
[16:24] <ubitux> which need to be completed.
[16:24] <HerbertPumpkin> Oh fer chrissake
[16:24] <HerbertPumpkin> Once again, user documentation for an open source project obsesses over merely compiling it.
[16:24] <HerbertPumpkin> That's not documentation! Tell me how to USE it!
[16:25] <ubitux> ?
[16:25] <ubitux> wth are you talking about?
[16:26] <HerbertPumpkin> Compiling software is not something users should have to do, and it isn't usually something they CAN do.
[16:26] <burek> http://doc-book.sourceforge.net/homepage/
[16:26] <burek> DocBookWiki can also be used to edit a DocBook document online, from the web. Editing is done one section at a time, so the editor selects first the section that he wants to edit, and then edits it. He can edit it in several modes: text (like wiki), xml (the original format), html, latex, texi, etc.
[16:26] <HerbertPumpkin> burek: No. Just use mediawiki.
[16:26] <HerbertPumpkin> Everyone knows it, everyone's comfortable with it.
[16:26] <HerbertPumpkin> Ain't broke, don't fix,
[16:26] <burek> well HerbertPumpkin we need to respect the need of developers too..
[16:26] <burek> if we don't there won't be any anymore..
[16:26] <burek> :/
[16:27] <ubitux> the problem is not with mediawiki or any other service
[16:27] <ubitux> it's what saste and i already stated several times
[16:29] <ubitux> and btw if the documentation gets outside the repository, be assured that when adding new stuff, the documentation won't be updated by developers anymore
[16:29] <HerbertPumpkin> Developers can go hang
[16:29] <HerbertPumpkin> They write code once
[16:29] <HerbertPumpkin> We use it a million million times
[16:29] <sacarasc> Because developers never use their own code. :(
[16:29] <burek> I don't know.. I understand the need for texinfo but this docbook wiki uses xml file to store the content and produces html, texi, latex, anything.. and what's most important it allows online editing of the content which bridges two worlds of devels and regular users
[16:29] <HerbertPumpkin> Coder ease and comfort is massively less important than user ease and comfort.
[16:30] <HerbertPumpkin> God almighty just USE MEDIAWIKI.
[16:30] <HerbertPumpkin> What possible problem is there
[16:30] <ubitux> install it, do your shit with it, and please stop complaining
[16:30] <ubitux> we have more serious problem do deal with
[16:30] <HerbertPumpkin> I don't think you do.
[16:31] <HerbertPumpkin> I think you fail to understand how important good docs are.
[16:31] <ubitux> now please stop being insultant or you won't stay long here
[16:31] <burek> HerbertPumpkin, you can't have an attitude like that
[16:31] <saste> ubitux: don't get your day spoiled ;-)
[16:31] <burek> why is developer's comfort and ease less important
[16:31] <burek> they are not payed for what they do
[16:31] <HerbertPumpkin> Because they have what's called a "single task involvement"
[16:31] <burek> if they were that would be completely different story
[16:31] <HerbertPumpkin> Well, there's a mechanism for software engineers to get paid for what they do, it's called "commercial software"
[16:31] <HerbertPumpkin> if they want to do that fine.
[16:31] <HerbertPumpkin> If they don't, then this is the deal.
[16:32] <burek> they do this because they like it and have free time to help contribute it.. if we make it so they dont like it anymore, there wont be any more devels and project will die
[16:32] <HerbertPumpkin> So what? I can't make it do anything useful anyway, because the documentation is so bad.
[16:32] <HerbertPumpkin> (slight exaggeration but you see what I mean)
[16:32] <burek> no, my point is that you would talk differently if you were one of developers
[16:32] <burek> if you would realize problems observed from their perspective
[16:33] <burek> if we can't join/merge these 2 worlds, then we didn't help
[16:33] <ubitux> saste: yeah, i'm going away :)
[16:33] <HerbertPumpkin> I appreciate the issues
[16:33] <HerbertPumpkin> I just think that writing good docs is part of being a software engineer.
[16:34] <HerbertPumpkin> If the developers don't agree then I would say they are missing the point of what they're doing.
[16:34] <brocatz> it's not literally
[16:34] <brocatz> that's why there is a career in technical writing
[16:34] <brocatz> the matter of documentation is an endless argument amongst programmers
[16:34] <HerbertPumpkin> I know, I make quite a lot of money out of technical writing.
[16:34] <HerbertPumpkin> :)
[16:34] <burek> it's just too bad docs haven't been written in XML or some other more general format.. that way developers would be able to edit them in text editors and there are a lot of html editors able to edit XML content
[16:34] <brocatz> a lot of purists believe there should be very little as it discourages writing readable code
[16:34] <burek> that would be ideal IMHO
[16:34] <brocatz> but you're coming at it from an end users perspective
[16:35] <brocatz> and i would say a technical writer is more the kind of person you want
[16:35] <HerbertPumpkin> There are a lot more end users than there are developers.
[16:35] <brocatz> not a software engineer
[16:35] <HerbertPumpkin> This means the end users' concerns are much, much more important.
[16:35] <HerbertPumpkin> Sorry if that sucks.
[16:35] <brocatz> the kind of documentation programmers write for each other would be of very little value to you
[16:35] <HerbertPumpkin> But it's life.
[16:35] <HerbertPumpkin> Oh, I know.
[16:35] <HerbertPumpkin> I write code too.
[16:36] <brocatz> so anyway, you want a technical writer
[16:36] <HerbertPumpkin> But if that's the case, what's wrong with just having a wiki?
[16:36] <brocatz> don't make out like that's a software engineers obligation
[16:36] <HerbertPumpkin> You can't tell me that the docs on the current website are used by the engineers.
[16:36] <brocatz> my problem with the recent documentation change is that they canged the selection color and now find is basically worthless in chrome
[16:36] <brocatz> and for such a dense document that's unhelpful
[16:37] <burek> brocatz, how?
[16:37] <burek> it works for me
[16:37] <brocatz> i didn't say it didn't work
[16:37] <brocatz> i said the selection color changed
[16:37] <brocatz> looks like it's changed again, or chrome was being a jackass, it's bright orange now
[16:38] <brocatz> which is good
[16:38] <burek> ?
[16:38] <burek> i dont understand your issue..
[16:38] <HerbertPumpkin> If certain text colours are set wrongly, the find hilight becomes invisible.
[16:39] <brocatz> ^
[16:40] <burek> select color is blue
[16:40] <HerbertPumpkin> You could argue that's really Chrome's bug, but either way if it's easily fixable (and it is), it should be fixed.
[16:40] <burek> find color is something yellowish orange something
[16:46] <HerbertPumpkin> burek: it is possible to cause collisions, though.
[16:46] <HerbertPumpkin> Possibly it shouldn't be, but it is, and web authors need to bear that in mind or you do gimp the browser rather.
[16:48] <burek> well I don't see collisions, that's why I ask :)
[16:48] <HerbertPumpkin> link me, I use chrome
[16:48] <burek> link me? :)
[16:49] <HerbertPumpkin> "provide me with a URL to the offending page"
[16:49] <burek> oh, well I don't have an offending page :) ask brocatz :))
[16:53] <HerbertPumpkin> OK, must dash, dinner with a beautiful woman
[17:04] <swkide> After this very interesting discussion I would like to ask where I could find information about deprecated functions in avformat. the program segmenter.c does compile with ffmpeg 0.8.3 but no longer with ffmpeg 0.11.3, because of not longer exsisting functions. Looks to me, taht you have changed the media handling (open/close) completely. I simply don't find a place to really open this...
[17:04] <swkide> ...Gordian knot - which it is to me ...
[17:07] <ubitux> < burek> it's just too bad docs haven't been written in XML or some other more general format.. // XML sucks and is not editable
[17:07] <ubitux> i mean it's a pain.
[17:08] <ubitux> texi is generic enough, though i have a preference for markdown and restructuredtext
[17:09] <brocatz> yeah xml is a terrible markup format
[17:17] <saste> swkide: but again i suggest to rely on the internal segmenter instead
[17:27] <swkide> @saste I got the internal segmenter up and running. We have tons of flv movies, which should be transcoded to apple format. Segmenting works, but all audios are clipping .
[17:28] <saste> swkide: i know audio segmentation is borken
[17:28] <swkide> when transcoded and segmented from a flv format - other formats work without any problem
[17:28] <swkide> ok thanks
[17:28] <saste> try this one: http://gitorious.org/~saste/ffmpeg/sastes-ffmpeg/commits/misc-segment-fixes-20120206
[17:28] <saste> yes i'm aware i should integrate it, postponing since months...
[17:30] <swkide> ok will try this
[17:30] <swkide> thanks
[17:49] <varaderoguy> hello all
[17:49] <varaderoguy> I wanted to ask some advice out metadata in flv files
[17:50] <varaderoguy> I am trying to add some metadata to an existing FLV file using ffmpeg 0.6.5 (Centos 5.7) and the metadata is not being written
[17:51] <varaderoguy> command I typed was: ffmpeg -i PM_PL_11_12_NOR_STO-00.flv -map_meta_data 0:0 -vcodec copy -acodec copy -metadata canSeekToEnd="true" PM_PL_11_12_NOR_STO-00-fixed2.fl
[17:51] <varaderoguy> unfortunely, 'canSeekToEnd' is not written to the file:
[17:53] <varaderoguy> Output is shown at: http://fpaste.org/j8nq/
[17:55] <varaderoguy> However, I know it is NOT working, because when you use ffplay:
[17:56] <varaderoguy> http://fpaste.org/OcVN/
[17:56] <varaderoguy> Thoughts Chaps????
[18:02] <varaderoguy> [coughs]....
[18:04] <sacarasc> That last paste didn't seem to work.
[18:06] <varaderoguy> arh - hello there sacarasc....let me repaste...
[18:07] <varaderoguy> http://fpaste.org/KLbG/
[18:08] <varaderoguy> I notice that the DAG repos has an v.old version of FFMPEG - only 0.6.5....when you guys are running 0.11.1
[18:09] <varaderoguy> I'm on Centos 5.7
[18:09] <varaderoguy> I suppose I ~could~ try and roll my own....
[18:10] <varaderoguy> :-(
[18:10] <sacarasc> To do that, you'd probably have to update a bunch of dependencies too.
[18:10] <varaderoguy> joy....
[18:11] <varaderoguy> I'll see whether the static ffmpeg might work....
[18:11] <varaderoguy> maybe see whether I can get DAG to update his repos
[18:12] <swkide> perhaps http://yamdi.sourceforge.net/ is an option?
[18:14] <varaderoguy> okay - this might be a goer....
[18:15] <swkide> MIght throw some problems compiling in CentOS
[18:15] <varaderoguy> Is it worth me placing a bugzilla report in for this...or am I going to laughed out of court?
[18:17] <Mavrik> rolling your own is pretty much the only choice if you're doing anything that relies on ffmpeg
[18:17] <Mavrik> the repo versions are just too old
[18:18] <varaderoguy> okay - I wonder whether I have to do this myself....
[18:19] <varaderoguy> IF....and this is a BIG IF....I can get the distro to roll its own and get a buildfile to work; would you be interested?
[18:19] <varaderoguy> I work in the media industry, so I suppose it is in my interest anyway
[18:22] <sweb> http://superuser.com/questions/441361/ffmpeg-strip-all-metadata-from-all-formats
[18:23] <varaderoguy> arh - good news - Yamdi has produced better results that b4
[18:25] <varaderoguy> sweb: Sorry, but I'm not stripping data; I'm adding it.....
[18:26] <varaderoguy> sweb: oddly enough - yamdi can strip all metadata
[18:26] <varaderoguy> using its -M flag
[18:27] <varaderoguy> right - gotta be off now....I think I'll be back here....you guys are so lovely!
[18:27] <varaderoguy> Thanks for the pointers....
[18:27] <varaderoguy> Chou
[19:18] <sweb> i have an error
[19:18] <sweb> ffmpeg -i audio.mp3 -map_meta_data -1 -c:v copy -c:a copy out.mp3
[19:18] <sweb> Unrecognized option 'c:v'
[19:19] <sweb> FFmpeg version SVN-r26402, Copyright (c) 2000-2011 the FFmpeg developers
[19:19] <JEEB> it's just old
[19:19] <JEEB> -vcodec for older versions
[19:19] <sacarasc> SVN hasn't been used with ffmpeg since January of last year.
[19:19] <JEEB> yeah
[19:19] <sweb> so i must move to github for latest version ?
[19:20] <sweb> i think it's a mirror
[19:20] <JEEB> http://git.videolan.org/?p=ffmpeg.git
[19:29] <sweb> during compile ... ERROR: vfw32 not found
[19:29] <sweb> what package required ?
[19:29] <sweb> debian 64 .... 6.0.5
[19:29] <JEEB> don't try to enable everything, that's a windows only feature
[19:31] <sweb> whitch --enable ?
[19:31] <sweb> http://pastie.org/private/6f78yksmah8wk8y62depbg
[19:32] <sweb> JEEB: ^
[19:33] <JEEB> enable what you're using
[19:33] <sweb> so i want to know vfw32 ?
[19:35] <sweb> find out
[19:35] <sweb> --enable-avisynth
[20:00] <sweb> make: *** [libavdevice/libcdio.o] Error 1
[20:14] <sweb> ffmpeg: error while loading shared libraries: libavdevice.so.54: cannot open shared object file: No such file or directory
[20:14] <sweb> after compile
[20:15] <durandal_1707> you will need to be more verbose to get any useful help
[20:16] <alyawn> I'm attempting to run the muxing.c example changing the format to "mpegts" but I get: Requested output format 'mpegts' is not a suitable output format. Is there an additional step to output a ts?
[20:18] <sweb> durandal_1707: this is my configure : http://pastie.org/private/aiier6dfcvw5smxq3tmxnw
[20:18] <sweb> debian 64 ... 6.0.4 fully upgrated
[20:19] <durandal_1707> sweb: perhaps you enabled stuff that fails to compile
[20:20] <sweb> durandal_1707: which one ... during make i have no error
[20:22] <beastd> sweb: Where do you get that error? Is it in the build directory or after installation?
[20:22] <sweb> beastd: after make install in /usr/local/bin/ffmpeg
[20:22] <sweb> after run ffmpeg
[20:24] <beastd> sweb: Did you check that the libraries were created in the build directory?
[20:24] <sweb> beastd: how can i check it ? after make ?
[20:25] <sweb> in making source dir ?
[20:25] <beastd> Just check if the files are present in the source dir after you successfully executed make.
[20:30] <sweb> beastd: i get latest from 0.11 of github
[20:34] <beastd> sweb:  does "ls libavcodec/libavcodec.*" in the build directory list the library file?
[20:36] <sweb> beastd: http://pastebin.com/0b0hgq0k
[20:40] <beastd> sweb: Seems like the libraries were not build. So you should have some errors at "make" and probably at "make install" too.
[20:42] <sweb> i will paste all operion during configure make and make install w8
[20:51] <sweb> beastd: http://pastebin.com/nrdUD95C
[20:56] <ShinyObjects> Hey everyone. I'm comparing the data in my non-working h264 stream to a working one. I've noticed that the NALU header for the working one is 67 while mine is 27.
[20:56] <ShinyObjects> That would mean that the working one has "3" for nal_ref_idc, while my stream has "1"
[20:56] <ShinyObjects> I can't seem to find what on earth nal_ref_idc is, however.
[20:56] <ShinyObjects> Does anyone know what nal_ref_idc is?
[20:57] <ShinyObjects> And of course, after searching for about 20 minutes I finally find my answer after I break down and ask here.
[20:57] <ShinyObjects> http://lists.mpegif.org/pipermail/mp4-tech/2006-June/006615.html
[20:58] <ShinyObjects> Looks like the only difference between 1 and 3 for a nal_ref_idc is that 3 gets higher priority
[20:59] <Mavrik> ^^
[20:59] <Mavrik> The Murphy's law of software development.
[20:59] <ShinyObjects> Yep, totally.
[21:50] <beastd> sweb: May it be that "ldd /usr/local/bin/ffmpeg" shows you that it finds none of the libav* libraries? If so you need to adjust your runtime linkers library search path.
[21:51] <beastd> est
[22:03] <beastd> sweb: May it be that "ldd /usr/local/bin/ffmpeg" shows you that it finds none of the libav* libraries? If so you need to adjust your runtime linkers library search path to also find stuff in /usr/local/lib.
[22:40] <pisto> hello. I think that mp3 is one of the formats that supports raw concatenation. but unfortunately my mp3s have id3 tags. Is there a way to tell ffmpeg to strip them before concatenating?
[23:10] <relaxed> pisto: look at -map_metadata and -metadata in the man page.
[23:10] <burek> pisto, can you type ffmpeg -i a.mp3
[23:10] <burek> and use pastebin.com to show the output
[00:00] --- Tue Jun 26 2012