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

[burek]

[00:43] <troker> Hey all, looking for an older copy of ffmpeg (version .60 to be exact) for some research.  Anyone know where I might be able to find it?
[01:32] <miguel_> is there a way to suppress the output from ffmpeg?
[01:32] <miguel_> all the information about the process its doing
[01:32] <miguel_> or pipe it to a file
[01:33] <llogan> "-loglevel quiet" as a global option
[01:35] <miguel_> thx
[01:36] <llogan> or "ffmpeg -y -i input output 2> log.txt"
[01:55] <whateverman> howdy
[01:55] <whateverman> got some pretty vanilla issues, I think, this time
[01:55] <whateverman> installing ffmpeg from source on amazon linux (since no repos are available for it that work well with amazon linux)
[01:55] <whateverman> and I get to the point where I'm configuring ffmpeg - it says that it can't find libx264, though I installed that one from source
[02:04] <whateverman> it might just be that x264 didn't build... bleh
[02:06] <llogan> whateverman: how did you configure x264?
[02:08] <whateverman> well, I've got /usr/local/lib/libx264.a
[02:09] <whateverman> and it was configured with just "--enable-static"
[02:13] <Zeranoe> I'm trying to do a screen capture using FFmpeg on Windows, but the audio is lagging the video behind. What audio codecs are very fast at encoding?
[02:14] <llogan> maybe you can just stream copy it.
[02:14] <Zeranoe> llogan: I don't think my hard drive is fast enough for raw pcm. What is the bitrate of pcm?
[02:15] <sacarasc> 1440k.
[02:15] <sacarasc> I think.
[02:17] <whateverman> llogan: does that sound like I configured x264 correctly?
[02:19] <llogan> patience. i have a million terminals open and i'm working on three servers at once.
[02:19] <llogan> i mean 4.
[02:20] <whateverman> no worries
[02:20] <llogan> whateverman: add "--extra-libs=-ldl" to your ffmpeg configure
[02:20] <whateverman> I'm only on 3 vOv
[02:20] <whateverman> will try
[02:21] <llogan> also see https://ffmpeg.org/trac/ffmpeg/wiki/CentosCompilationGuide
[02:21] <whateverman> ah, tyty
[02:21] <llogan> what distro is the amazon linux most like anyway?
[02:22] <whateverman> centos
[02:22] <whateverman> it's an RHEL-alike kinda like centos, but the repos don't quite line up
[02:22] <llogan> maybe i should mention the amazon whatever on the centos guide then.
[02:23] <bparker> how can I generate a video stream that's very difficult to encode? for example I'd think /dev/urandom would be a good source... but it seems I can't read from it fast enough for 1080p60 which is my requirement
[02:23] <llogan> although i plan on merging them to make a general guide for linux, but i haven't arranged it so it is not too confusing for copy-n-paste users.
[02:24] <whateverman> interesting - I had a script that worked unattended on some of our amazon linux servers, but I may have been taking a few things for granted that were already in place
[02:24] <whateverman> that seems to have done it, llogan
[02:31] <whateverman> again, thanks
[02:34] <llogan> Zeranoe: maybe flac will fit your needs then
[03:26] <whateverman> oh... and the reason I was re-compiling ffmpeg today
[03:26] <whateverman> http://hastebin.com/fojigasixa.bash
[03:26] <whateverman> this script
[03:26] <whateverman> lol
[03:26] <whateverman> one of my co-workers wrote it, then my boss ran it w/o options
[03:26] <whateverman> if rm -rf / doesn't kill your server
[03:26] <whateverman> chmod 777 /
[03:26] <whateverman> will
[06:06] <anshul> is it neccassory to do avcodec_close and avcodec_open if i want to mux video.
[06:38] <RigidWig> is there a way to verbosely, one by one, declare the images to create a video? ie: ffmpeg -blahblahblah -i '1.jpg', '1234_abd.jpg', 'ZZX%^2.jpg'  etc etc, rather than globing or sequencing....?
[07:05] <Lyude> I have a Happauge Colossus capture card, and it happens to have a hardware x264 hardware encoder on it. There isn't any way I could have ffmpeg offload x264 encoding to that so that the CPU wouldn't have to do it, is there?
[07:21] <vulture> Lyude: if it has a directshow driver you can probably hardware encode with directshow
[07:22] <Lyude> This is on a Linux system
[07:23] <vulture> does your hardware encoder have a linux driver? :P
[07:23] <Lyude> Pretty sure it does, I'm not entirely sure though. I'm just wondering if ffmpeg has the ability to do this at all, since I know it can't do GPU encoding yet
[07:24] <vulture> no idea
[07:24] <vulture> most people I imagine dont bother with hardware encoding, it's usually lower quality
[07:24] <vulture> and x264 is pretty fast these days
[07:24] <Lyude> Streaming while gaming takes power though
[07:24] <vulture> thats why you have multiple cpus
[07:25] <Lyude> I've got a Q9550 overclocked
[07:25] <Lyude> It still takes a lot of power no matter what :P, unless you're using hardware encoding, which I'd love to be able to do
[07:26] <Lyude> I've gotta go for now, so I'll be back some other time, bai
[07:27] <vulture> some hardware encoders probably can only even encode from their video capture ports too
[07:36] <ilove11ven> Lyude: video encoder card is very cheap
[07:36] <vulture> aaaaaaand that wasnt even his question
[07:38] <ilove11ven> yes, he wants to stream his gaming. I suggest using video encoder card instead of GPU encoding
[10:46] <anshul__>  is there any spevific format. to send an patch, i feel mine patch is ignored  on ffmpeg-devl mailing list
[11:27] <rjek> Hi.  Does anybody know if ffmpeg has a test suite of media files (specifically, broken media files) that's publically available?
[11:36] <t4nk001> hi
[11:37] <t4nk001> is it possible to skip frame in ffserver if the remote client can not receive data since tcp window size is zero
[11:38] <t4nk001> when I use vlc to connect ffserver with the url http://192.168.1.254:8090/test.asf
[11:38] <t4nk001> then vlc can not receive any data if tcp zero window is occur
[11:38] <sine``> guys for windows, what would be the best codec pack to download
[11:38] <t4nk001> is it possible to skip the frame if tcp zero window occur?
[11:39] <t4nk001> in ffserver?
[11:51] <t4nk001> any ideas?
[12:41] <anshul__> cant run fate server, it is giving slote name as command not found
[13:10] <kode54> is it me, or is ffmpeg.org incredibly slow right now?
[13:12] <tsjiller> it's fast here
[13:12] <tsjiller> 2013-06-27 13:12:03 (5,72 MB/s) - ffmpeg-1.2.1.tar.bz2 saved [5968378/5968378]
[15:53] <mark4o> rjek: http://samples.ffmpeg.org/
[15:54] <rjek> mark4o: Does that include broken files, too?  If so, you're my hero.
[15:56] <mark4o> there are broken files in there
[15:57] <rjek> :D
[16:21] <ElInvitado1> hablan castellano?
[16:22] <joltman> trying to do a screen capture with FFMPEG on Windows.  using the dshow filter and the screen-capture-recorder app.  The capture worked fine as x264 mkv.  However, the machine i was capturing on rebooted last night to do windows updates.  The capture stopped.  I'm viewing the video now, but in VLC i can't fast forward.  Is there a switch on the command line I need to add in order for FF to work?  Let me find the command line I used to do this capture
[16:25] <joltman> ffmpeg -f dshow -i video="screen-capture-recorder" -r 10 -threads 0 -t 28805 outfile.mkv
[16:26] <joltman> i also am not getting a time length on the video when it plays in VLC.  I'm wondering if this is because the FFMPEG process was killed by Windows
[16:26] <joltman> oops...the frame rate was 15...not 10
[16:27] <Mavrik> hmm, not setting the encoding parameters usually isn't a wise idea :P
[16:28] <Mavrik> but yeah, it seems ffmpeg didn't get the chance to write file trailer and set metadata
[16:28] <Mavrik> so remux it and it should be ok
[16:28] <Mavrik> basically just do
[16:28] <Mavrik> ffmpeg -i your.mkv -codec copy new.mkv
[16:31] <ElInvitado1> |-)
[16:31] <ElInvitado1> the option -target ntsc-vcd does not work, always gives me VBR and has an unacceptable flashing Gibbs effect
[16:32] <ElInvitado1> is there any solution?
[16:32] <ElInvitado1> or I have to use TMPGEnc
[16:33] <joltman> Mavrik: Thanks!
[16:33] <joltman> i'm gonaa try this again
[16:33] <joltman> thanks much!
[16:36] <ElInvitado1> será  TMPGEnc entonces
[16:36] <ElInvitado1> chao
[16:54] <mrAlmond> Hi everyone
[16:54] <joltman> Mavrik: you were right, doing the -codec copy thing worked perfectly
[16:54] <joltman> thanks for the help. Now I know what to do if Winderz decides to reboot again.
[16:56] <mrAlmond> I've encoded an h264 using Android 4.2 encoder and then I've muxed it with ffmpeg to mp4
[16:57] <mrAlmond> it plays fine with vlc and mplayer in linux
[16:57] <mrAlmond> but with windows media player it gives me error
[16:57] <mrAlmond> this is the mp4box info of that file
[16:57] <mrAlmond> http://pastebin.com/meP2Dfw8
[16:57] <mrAlmond> do you see something wrong?
[16:59] <mrAlmond> this file has no audio track, only video
[17:09] <xlinkz0> how do i check if a file was created with -movflags faststart?
[17:15] <JEEB> xlinkz0, you can use for example L-SMASH's boxdumper and see how far in the file the moov atom is in
[17:15] <JEEB> if it's in the beginning
[17:15] <JEEB> it has the index moved into the beginning
[17:16] <xlinkz0> is that a debian package?
[17:16] <JEEB> dunno
[17:16] <JEEB> not that compiling L-SMASH is hard :D
[17:16] <JEEB> because it has literally no dependencies
[17:16] <JEEB> other than a C99 compiler
[17:30] <xlinkz0> JEEB: so moov: Movie Box] position = 32 means it is at the begining, right?
[17:30] <JEEB> I think so
[17:30] <xlinkz0> thanks
[17:44] <mrAlmond> can someone give me some help?
[17:44] <mrAlmond> http://pastebin.com/meP2Dfw8
[17:45] <mrAlmond> this file plays well on vlc but not on windows media player
[20:02] <Maverick|MSG> does ffmpeg support encoding a file that is currently being written to?
[20:02] <t4nk172> I am observing a weird behavior while using the H.264 Encoder (libx264). If I monotonically increase the pts "frame->pts++" before the avcodec_encode_video2() function, the encoder crashes randomly after encoding some 300 /350 odd pictures. However, if I implement PTs as a mod 128 counter i.e. frame->pts++; frame->pts %= 128, the encoder works fine. Any idea what could this be because of?
[20:13] <llogan> Maverick|MSG: it's working for me (but first output/second input is DV)
[20:19] <Maverick|MSG> llogan, so you have an input movie that is continuing to grow as the user is creating their movie and ffmpeg will encode it to x264 on the fly (and wait if it reaches the end of the file)?
[20:21] <llogan> Maverick|MSG: i just ran: "ffmpeg -i input.dv -target ntsc-dv out.dv" and "ffmpeg -i out.dv out.mp4", but I didn't wait until the end since i'm currently encoding other stuff.
[20:24] <Maverick|MSG> llogan I think the problem I'm running into is that ffmpeg is encoding the output file faster than the user is creating the avi
[20:25] <Maverick|MSG> so I'm not sure if ffmpeg is going to stop encoding when it hits the end of the file, or pause at eof and check at a set interval if the avi is larger and then continue encoding, etc
[20:26] <klaxa> i'm rather sure it will stop encoding at the point where the file ended when ffmpeg opened it
[20:27] <Maverick|MSG> so no way to tell ffmpeg to just wait a little bit?
[20:27] <Maverick|MSG> or recheck the source file?
[21:25] <blink> is prores_kostya included by default in a windows build?
[21:30] <llogan> blink: yes, probably as prores_ks
[21:30] <llogan> see "ffmpeg -encoders"
[21:30] <llogan> assuming you're using builds from Zeranoe
[21:31] <llogan> and not some graybeard build
[21:35] <blink> yes, I did. thanks, I was using a wiki page that stated prores_kostya.
[22:31] <llogan> blink: was it a page on ffmpeg.org?
[22:45] <blink> llogan: http://ffmpeg.org/trac/ffmpeg/wiki/vfxEncodingGuide#ProRes
[22:52] <llogan> quite verbose
[22:55] <blink> the specific incantation I was looking at was prefaced by "An example command line for generating a 2K mono clip with Prores is: "
[23:06] <llogan> blink: thanks. i updated the guide to include both the new and older names.
[23:07] <blink> thank you
[23:07] <llogan> although that guide could use some cleanup/lowered verbosity.
[23:08] <blink> I like the verbosity, as long as it's factual :)
[23:16] <brontosaurusrex> so whats the difference between prores and prores_ks?
[23:19] <llogan> brontosaurusrex: see "ffmpeg -h encoder=prores" and "ffmpeg -h encoder=prores_ks"
[00:00] --- Fri Jun 28 2013