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

[burek]

[00:04:21 CEST] <t4nk336> Agh. I told ffmpeg to build x64 and it built x86. Who does that?!
[00:08:31 CEST] <BtbN> It will build as whatever msvc shell you used.
[00:11:21 CEST] <t4nk336> Ah, thanks BtbN; that solved it, I think.
[00:20:02 CEST] <t4nk336> Now it seems to be building x64... Except for things built by yasm...
[00:24:17 CEST] <t4nk336> Maybe I just need to reconfigure
[00:43:54 CEST] <t4nk336> Wowee - I finally compiled and got exes with pdbs
[00:44:31 CEST] <t4nk336> And it only took almost 2 hours. A new record perhaps?
[00:51:06 CEST] <klaxa> t4nk336: no
[00:51:38 CEST] <t4nk336> And debugging, it looks like the issue is that the parser uses a different H264Context than the codec context for some reason...
[00:51:39 CEST] <klaxa> i can assure you people (including me) have spent way waaaaay more time trying to get a sofware to run
[00:51:57 CEST] <t4nk336> I meant record in the other direction ;)
[00:52:27 CEST] <t4nk336> As the parser sets its H264Context's is_avc, but the codec context's H264Context's is_avc remains cleared
[00:54:01 CEST] <t4nk336> In fact, I think that's a libavcodec bug
[00:54:17 CEST] <t4nk336> So I guess it's a good thing I have the source so I can workaround it locally
[00:55:42 CEST] <t4nk336> Oh or maybe I need to set the decoder's "is_avc" field myself or something.
[00:57:49 CEST] <t4nk336> Ohh - I needed to set the extradata/extradata_size *before* I opened the codec, not after
[00:58:04 CEST] <t4nk336> Now it works fine.
[00:59:29 CEST] <t4nk336> Gotta love struct-based APIs
[01:01:14 CEST] <BtbN> you don't even want to know what the libav* apis would look like if everything were function parameters.
[01:06:06 CEST] <t4nk336> True, but I do want to know what the libav* apis would look like if everything were APIs that operated on the AVContext/Codec/etc. objects - setters, getters, etc.
[01:36:21 CEST] <klaxa> C has no objects and that is good
[01:36:24 CEST] <klaxa> but that's just my opinion
[01:39:17 CEST] <t4nk336> Just look at something like libpng (modern)
[01:39:46 CEST] <t4nk336> it's c code, but it's object-oriented rather than requiring the user to poke around in a struct
[01:40:17 CEST] <t4nk336> And it just reduces a good amount of user mistakes as well as allows for better binary/source compatibility
[02:04:04 CEST] <chungy> glib is also object-oriented and plain C. GTK/GNOME are built from it :P
[02:04:23 CEST] <chungy> (those devs have actively expressed hatred towards C++, haha)
[02:10:35 CEST] <gnfz> I'm having trouble finding much information on creating chapters using ffmpeg (command line).  Can someone point me in the right direction?  Something along the lines of -metadata:c:# key=value is spitting out an error message that the chapter index is invalid.  (with # an int and key an element name from looking at matroska's section on chapter element name's)
[02:13:13 CEST] <gnfz> I'm just blindly guessing though as I couldn't find any specific examples in the documentation.
[02:53:37 CEST] <gnfz> I ended up just dumping the metadata from a file I knew had chapters and used map_metadata.  If there's a way to create chapters without using a separate metadata configuration file, I'm still interested.
[03:53:17 CEST] <MINIMAN10000> Alright so I was looking for the lowest bitrate I could get my video and then ran the encode. This is what I ended up when trying to find the lowest bitrate. ffmpeg -i input.mkv -preset slowest -c:v libvpx-vp9 -c:a libvorbis -q:a 0 -b:a 0k -b:v 1k output.webm
[03:54:37 CEST] <MINIMAN10000> are there any other things that can make it smaller while still having both video and audio?
[05:42:11 CEST] <cehoyos> MINIMAN10000: Generally, to get the lowest bitrate, choose the highest quantiser supported by a codec (don't know if this is also true for libvpx)
[05:42:48 CEST] <MINIMAN10000> cehoyos, on libvpx the if I remember correctly ended up being around 50% larger
[05:43:58 CEST] <MINIMAN10000> oh wait nvm
[05:44:00 CEST] <MINIMAN10000> i used crf
[05:44:09 CEST] <MINIMAN10000> unless crf is the quantizer?
[05:49:32 CEST] <cehoyos> It is not exactly the same iirc, but choosing the worst possible quality with crf should produce the smallest possible files.
[06:39:13 CEST] <MINIMAN10000> cehoyos, your right setting min and max quantizer does produce the smallest thanks
[06:39:26 CEST] <MINIMAN10000> but now my audio is larger than my video lol
[06:41:54 CEST] <MINIMAN10000> got ogg vorbis set to quality of 0... as low as it goes jeeze
[06:49:51 CEST] <MINIMAN10000> alright manually set it to 96 kb by punching in smaller numbers til one worked and its smaller than q 0
[06:51:47 CEST] <MINIMAN10000> Alright the new smallest output command line is. ffmpeg -i input.mkv -preset slowest -c:v libvpx-vp9 -c:a libvorbis -ab 96k -qmin 63 -qmax 63 output.webm
[06:57:31 CEST] <MINIMAN10000> huh according to opus own codec chart they have higher quality at what looks to be 128 kb/s
[07:04:49 CEST] <MINIMAN10000> not entirely sure why 48 or 64 k didnt work with vorbis but it may be worth a shot to try opus after this finishes
[07:13:18 CEST] <MINIMAN10000> ... now that im on the wiki and went down further
[07:13:36 CEST] <MINIMAN10000> they also have 80 64 45 officially
[07:14:39 CEST] <rjp421> http://www.streamingmedia.com/ConferenceVideos
[09:45:47 CEST] <asimas> Hello. I've found this command http://pastebin.com/9irnTLPe that uses a complex filter to concat and then scale a video. Is there any way I could first scale the videos and then concat then? I'd still like to do it in a single command.
[09:47:39 CEST] <Mavrik> asimas, switch the order?
[09:47:58 CEST] <asimas> Right
[09:51:05 CEST] <asimas> Also the input files might need to be scaled differently, so the question is how can I refer to specific input's video stream and use it for the scale filter
[09:53:52 CEST] <Mavrik> you can't afaik
[09:53:57 CEST] <Mavrik> but that shouldn't matter
[09:54:03 CEST] <Mavrik> since you need to get them all to the same size right?
[09:56:35 CEST] <asimas> Mavrik, couldn't I do something like this? http://pastebin.com/B3iw8KjP
[09:58:11 CEST] <asimas> Mavrik, I need them all at the same size but I want to scale them without losing aspect ratio and adding padding where necessary. That's why I think I need to use separate filters for each input before concatenating.
[09:59:09 CEST] <Mavrik> ah
[09:59:29 CEST] <Mavrik> yes, you'll have to do it for each stream first and then concat, but I don't know the syntax for that I'm afraid :/
[10:01:26 CEST] <asimas> Mavrik, that's ok. Thanks for your help :) I'll try to come up with something myself.
[10:30:49 CEST] <asimas> Well if anyone's interested here's how I managed to scale first and then concat in a single command: http://pastebin.com/xdTKrkw7
[11:19:39 CEST] <hendry> anyone know how to capture the fullscreen with -f x11grab ? it seems to require "-i :0.0" now, but that doesn't capture whole screen
[14:50:17 CEST] <MINIMAN10001> alright im back
[14:51:53 CEST] <cehoyos> hendry: Command line and complete, uncut console output missing. If this is a regression (if a command line used to work with an older version of FFmpeg but does not work anynore), I am especially interested. Please don't forget to test current FFmpeg git head before reporting issues / asking questions.
[14:52:17 CEST] <MINIMAN10001> so by changing from bitrate a target of 1kb to a quantizer setting of 63 and to opus 96kbps im hitting just under 20 MB from the previous 26 MB
[14:54:19 CEST] <MINIMAN10001> with an input of 1.09 GB
[14:57:10 CEST] <cehoyos> 96kb sounds a lot for opus if you use quantizer 63...
[14:57:25 CEST] <MINIMAN10001> i tried 48 and it sounded like it was missing the hightones
[14:57:34 CEST] <cehoyos> And how did it look like??
[14:57:36 CEST] <MINIMAN10001> it was extremely distracting from the original
[14:57:46 CEST] <MINIMAN10001> honestly better than i thought considering its the worst it can get
[14:57:47 CEST] <cehoyos> I mean the video.
[14:58:11 CEST] <cehoyos> 96kb is still a (very) high bitrate if you are trying to get as low as possible.
[14:58:20 CEST] <cehoyos> But opus is said to beat aac
[14:59:04 CEST] <MINIMAN10001> http://puu.sh/iexOf/1adb9c3065.jpg this vs original http://puu.sh/iexQ0/17cce1fcb7.jpg
[15:00:30 CEST] <MINIMAN10001> but yeah now id like to make another one that aims to have higher quality video. Last used command. ffmpeg -i input.mkv -preset slowest -c:v libvpx-vp9 -c:a libopus -b:a 96k -qmin 63 -qmax 63 output.webm
[15:00:58 CEST] <MINIMAN10001> so just up the qmin and that should do it?
[15:03:31 CEST] <cehoyos> Why are qmin and qmax necessary?
[15:03:43 CEST] <cehoyos> Did you try -q:v 63 ?
[15:03:51 CEST] <MINIMAN10001> qmax wasnt nessassary but i didnt want to leave it open to interpretation at least.
[15:03:59 CEST] <c_14> You know, if you want to make the video smaller, just downscale?
[15:04:01 CEST] <MINIMAN10001> i thought q:v was presets
[15:04:25 CEST] <MINIMAN10001> i wasnt sure if a downscaled would result in higher quality
[15:04:31 CEST] <MINIMAN10001> for the same datarates
[15:05:56 CEST] <cehoyos> Is there a difference (md5sum-wise) if you use -q:v 63 or qmin and qmax?
[15:06:39 CEST] <MINIMAN10001> not sure how to obtain the md5 but i have no idea which is why i set both qmin and max
[15:08:05 CEST] <cehoyos> Is there a difference with the output filesize if you use -q:v or qmin/qmax?
[15:08:27 CEST] <MINIMAN10001> encoding a 10 second segment on qmin/qmax atm
[15:08:53 CEST] Action: c_14 got a 3byte difference over 5 seconds
[15:09:28 CEST] <MINIMAN10001> i swear if its 3 bytes smaller for q:v imma throw a fit lol
[15:09:29 CEST] <c_14> Eh, 3kilobyte that is
[15:09:34 CEST] <MINIMAN10001> kb*
[15:09:43 CEST] <MINIMAN10001> which is quite significant for the sizes on a 5 sec i imagine
[15:10:35 CEST] <c_14> Nah, it is bytes. or blocks whatever `ls -l' outputs
[15:10:42 CEST] <MINIMAN10001> q:v was around 100% larger
[15:11:50 CEST] <MINIMAN10001> was the difference between 100 kb and 200 kb for qmin/max and q:v respectively
[15:12:43 CEST] <cehoyos> Sorry, it is -crf 63
[15:13:30 CEST] <cehoyos> There is a kind of stress field between "q:v" and "crf" and qmin/qmax seem to be unable to decide on which side they are;-)
[15:14:40 CEST] <cehoyos> (Some codecs like vpx ignore -q:v but accept -crf,, others like mpeg4 don't know crf but respect -q:v and the fact that qmin maps to both in different codecs makes the issue worse.)
[15:15:18 CEST] <MINIMAN10001> crf is 50% larger than min/max
[15:18:27 CEST] <JEEBsv> cehoyos: i think the funniest part is that only libx264 and libx265 actually have crf
[15:18:54 CEST] <JEEBsv> libvpx's thing is different iirc, but somehow was mapped to it
[15:18:58 CEST] <cehoyos> The given report (and the source code) indicates that libvpx also has it...
[15:19:18 CEST] <cehoyos> I am not talking about semantics, only command line usage.
[15:19:55 CEST] <cehoyos> And I still don't think that any user cares about "lamda" in this context.
[15:20:57 CEST] <JEEBsv> dunno, all I remember is that libvpx's thing to which -crf was mapped was different. might have even been different between vp8 and vp9
[15:21:28 CEST] <JEEBsv> as in, how that libvpx option works
[15:21:43 CEST] <JEEBsv> but I don't remember the details :)
[15:24:50 CEST] <MINIMAN10001> alright
[15:25:14 CEST] <MINIMAN10001> im no longer interested in minimizng the file size, like i did with opus id like to meet a certain quality level... how should i do that.
[15:29:47 CEST] <MINIMAN10001> lol dangit sounds like a pain according to this
[15:30:11 CEST] <MINIMAN10001> says you should use crf in conjunction with bitrate in order to manipulate quality
[15:30:24 CEST] <c_14> just use crf
[15:30:27 CEST] <c_14> What are you reading?
[15:30:43 CEST] <MINIMAN10001> ffmpeg vp8 encode wiki
[15:30:47 CEST] <MINIMAN10001> https://trac.ffmpeg.org/wiki/Encode/VP8
[15:31:01 CEST] <Mavrik> *sigh*
[15:31:05 CEST] <c_14> Aren't you using vp9? Read https://trac.ffmpeg.org/wiki/Encode/VP9
[15:31:09 CEST] <Mavrik> I don't think there's a way of making VP8 not crap.
[15:31:16 CEST] <MINIMAN10001> " Note that you shouldn't leave out the -b:v option as the default settings will produce mediocre quality output."
[15:31:36 CEST] <MINIMAN10001> eh thought the vp9 page wasnt complete
[15:31:40 CEST] <MINIMAN10001> guess that isnt the case lol
[15:32:02 CEST] <MINIMAN10001> oh says set b:v 0
[15:32:04 CEST] <c_14> It's been complete for 2 month
[15:33:08 CEST] <c_14> +s
[15:33:33 CEST] <MINIMAN10001> welp
[15:33:45 CEST] <MINIMAN10001> crf 10 might have been higher than i wanted lol
[15:35:01 CEST] <MINIMAN10001> its practically the same bitrate as the original with a newer encoder... sounds like a recipe for wasted space
[15:35:06 CEST] <c_14> crf might be a bit high, I usually use 31 or so for short clips
[15:35:22 CEST] <c_14> Not sure why I wrote a crf of 10 there
[15:35:40 CEST] <MINIMAN10001> crf 10 is used in all the examples on the libvpx pages
[15:39:13 CEST] <c_14> Oh well, not like it really matter.s
[15:42:02 CEST] <MINIMAN10001> so i was reading on streaming ealier and it said a iframe was sent every 250 frames and nolatenecy mode makes every frame an iframe. does that mean the point between iframe is considered latency?
[15:44:25 CEST] <MINIMAN10001> i became interested in latency when i heard it can be adjuted from 5 to 120 ms in opus
[15:44:31 CEST] <MINIMAN10001> adjusted*
[15:45:06 CEST] <c_14> https://web.archive.org/web/20141118095252/http://mewiki.project357.com/wiki/X264_Encoding_Suggestions#Encoder_latency
[15:45:09 CEST] <c_14> that's for x264 though
[15:46:07 CEST] <MINIMAN10001> oh
[16:01:03 CEST] <doki_pen> I'm trying to cut a video, and for the most part it's working, but I get a few seconds of grey screen at the begining of the output: ffmpeg -i cut.avi -ss 10 -t 00:06:25 -c copy final.avi
[16:01:20 CEST] <doki_pen> any ideas on how to fix?
[16:20:07 CEST] <MINIMAN10001> for me using -ss in conjunction with -t works just fine
[16:22:17 CEST] <doki_pen> yeah, must have something to do with the encoding. no matter where I clip from, the first few seconds are grey screen. audio is fine
[16:44:17 CEST] <klaxa> doki_pen: it might be related to the types of frames in the video, you are probably trying to start from a non-i-frame
[16:45:35 CEST] <klaxa> an i-frame is a full frame that can be decoded without referencing earlier or later frames
[16:45:53 CEST] <klaxa> you can try to re-encode (which will reduce quality) or cut at i-frames
[16:57:40 CEST] <zhanshan> hi
[16:58:11 CEST] <zhanshan> is there an option in ffmpeg to reorder massive JPG files to render them properly to video?
[16:58:59 CEST] <zhanshan> I made the big mistake to name the files '002_wild0001.jpg' - '002_wild32465.jpg'
[16:59:23 CEST] <zhanshan> so in the end it is one more digit than in the beginning
[17:01:06 CEST] <c_14> Not in ffmpeg, but you can use something like `perl-rename 's/([0-9]{4})/0$1/' *'
[17:03:15 CEST] <zhanshan> c_14 thanks but I don't know how to use this
[17:04:33 CEST] <intracube> hi, is '*.jpg' in: ffmpeg -f image2 -i *.jpg -c:v ... expanded by the shell (on linux) or handled directly by ffmpeg?
[17:06:07 CEST] <jarainf> intracube, it's handled by the shell
[17:07:08 CEST] <intracube> jarainf: thanks
[17:09:40 CEST] <c_14> zhanshan: the command I gave you should work (assuming you have perl-rename installed). You might want to add -n for testing though (that'll just tell you what it'll rename).
[17:16:05 CEST] <zhanshan> ok thanks!
[17:20:11 CEST] <zhanshan> I don't get it, is the command 'rename' or 'perl-rename'?
[17:20:18 CEST] <zhanshan> I only have rename installed
[17:22:04 CEST] <zhanshan> $ rename 's/([0-9]{4})/0$1/' *' -n
[17:22:12 CEST] <zhanshan> there's one ' missing I guess
[17:22:20 CEST] <zhanshan> the command doesn't work like this
[17:24:07 CEST] <zhanshan> ok I got it
[17:24:26 CEST] <zhanshan> but there are still files with different digit-length 002_wild002389.jpg  002_wild0023899.jpg
[17:24:49 CEST] <zhanshan> the command seems to just add one '0' in front after '002_wild'
[17:25:07 CEST] <zhanshan> I actually performed the command twice already :P
[17:56:29 CEST] <spectromas> is there anything unusual about this file? https://bpaste.net/show/46c40c13e59f my tv is having problems with it but I can't see anything that might be a problem
[18:02:31 CEST] <Mavrik> does your TV handle MKVs?
[18:03:34 CEST] <spectromas> Mavrik: it does usually yes
[18:03:41 CEST] <dsl420> spectralsun, DAR looks a bit weird, but i could be wrong though
[18:04:17 CEST] <Mavrik> is it perhaps concatenated from multiple files?
[18:05:09 CEST] <spectromas> it's possible, i don't know the source of the file
[18:06:02 CEST] <spectromas> it plays fine on my computer with mpv though, that's the annoying thing
[18:18:03 CEST] <c_14> zhanshan: eeeh, right. The regex wasn't entirely correct. it should have been s/[^0-9]([0-9]{4}/0$1/. Now you'll have to update the {4} to whatever the shortest digit length is
[18:37:28 CEST] <MINIMAN10001> alright figured it out
[18:37:36 CEST] <MINIMAN10001> the reason why audio sucked is it's 5.1 channel
[18:39:11 CEST] <MINIMAN10001> weird a cfr of 63 is relatively high quality
[18:39:26 CEST] <MINIMAN10001> crf*
[18:40:27 CEST] <MINIMAN10001> some significant artifacting
[19:17:21 CEST] <zhanshan> pls see https://gist.github.com/zhanshan/b72fd3a750830dbe9520
[19:17:30 CEST] <zhanshan> a new error from ffmpeg
[19:20:55 CEST] <zhanshan> c_14 about the issue before: in 002_wild000001.jpg the digit length would be 6 or 1?
[19:21:56 CEST] <zhanshan> 002_wild001650.jpg, 002_wild0016509.jpg -> 6, 7?
[19:22:02 CEST] <zhanshan> so I'd go for 6
[19:22:05 CEST] <zhanshan> I guess
[19:39:45 CEST] <zhanshan> [image2 @ 0x40c2c60] Could find no file with path '*.jpg' and index in the range 0-4
[19:39:46 CEST] <zhanshan> *.jpg: No such file or directory
[19:39:48 CEST] <zhanshan> :P
[19:41:55 CEST] <zhanshan> with '-pattern_type glob' it seems to work now
[19:42:00 CEST] <klaxa> i remember having troubls with long numbers too. maybe making a subdirectory and creating symlinks like 000001.jpg -> ../002_wild000001.jpg would make it easier?
[19:44:18 CEST] <klaxa> and if all fails try: cat some/dir/*.jpg | ffmpeg -f image2pipe -i - [options] out.mkv
[19:46:04 CEST] <zhanshan> klaxa I think the problem seems to be that ffmpeg accepts only four digit-numbering 0000?
[19:46:13 CEST] <zhanshan> more than that causes problems?
[19:46:43 CEST] <klaxa> i have an ffmpeg command in my history with %05d
[19:46:52 CEST] <klaxa> so i guess 5 works at least
[19:46:53 CEST] <intracube> zhanshan: if the file sequence starts at 00000001.jpg onwards you should be able to do: -i $08d.jpg
[19:46:57 CEST] <intracube> for example
[19:47:51 CEST] <zhanshan> alright
[19:48:36 CEST] <klaxa> just tested it and %06d works too for me
[19:49:12 CEST] <zhanshan> ok, thanks!
[21:50:38 CEST] <feliwir> hey, is there any official FindFFMPEG.cmake script?
[21:52:39 CEST] <feliwir> everytime i use a script from the web i get linker errors -.-
[22:26:31 CEST] <Emmanuel_Chanel> Hello!
[22:27:31 CEST] <Emmanuel_Chanel> I'm seeking how to add Track2.acc to Version1.mkv with 1 video track and 1 audio track. Do you know where I should see?
[22:28:59 CEST] <c_14> ffmpeg -i Track2.acc -i Version1.mkv -map 0 -map 1 -c copy out.mkv
[22:33:48 CEST] <Emmanuel_Chanel> c_14: It says Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument
[22:47:47 CEST] <anoop_r> hi i got error Past duration 0.904747 too large
[22:47:48 CEST] <anoop_r> while using x265 to encode
[22:47:48 CEST] <anoop_r> x265 10bit with ffmpeg
[22:53:31 CEST] <anoop_r> please see this http://pastebin.com/9L60nhYi
[23:17:00 CEST] <MINIMAN10001> hmm
[23:17:13 CEST] <MINIMAN10001> not sure how to run x265
[23:18:06 CEST] <c_14> The binary or encode to H.265 using ffmpeg?
[23:18:35 CEST] <MINIMAN10001> playing a video encoded using ffmpeg to use h.265
[23:18:49 CEST] <c_14> what?
[23:19:41 CEST] <MINIMAN10001> i create a h265. i have no idea how to play it
[23:19:56 CEST] <c_14> ffplay file
[23:19:56 CEST] <c_14> mplayer file
[23:19:56 CEST] <c_14> mpv file
[23:19:57 CEST] <c_14> vlc file
[23:20:02 CEST] <MINIMAN10001> ooh
[23:20:05 CEST] <MINIMAN10001> i used mp4
[23:20:33 CEST] <MINIMAN10001> vlc sounds promising
[23:20:58 CEST] <MINIMAN10001> oh... vlc not suitable for libx265
[23:21:11 CEST] <MINIMAN10001> either is mpv
[23:22:35 CEST] <iive> libx265 is only encoder. ffmpeg libavcodec has the decoder and that is what everything uses.
[23:23:33 CEST] <MINIMAN10001> for example i encoded using libx264 and decoded using google chrome
[23:23:54 CEST] <MINIMAN10001> i encoded with libx265 but google chrome and windows media player is unable to decode it.
[23:24:14 CEST] <MINIMAN10001> the file was a .mp4
[23:28:48 CEST] <JEEBsv> so do you want to play back or encode?
[23:28:52 CEST] <JEEBsv> you sound confused
[23:30:22 CEST] <MINIMAN10001> i want to play back
[23:30:33 CEST] <MINIMAN10001> h265
[23:30:52 CEST] <JEEBsv> then I'd just grab VLC 2.2 or newer, or mpv from https://mpv.srsfckn.biz/
[23:30:58 CEST] <JEEBsv> both should support HEVC :P
[23:31:11 CEST] <JEEBsv> latter you drag and drop stuff on top of the exe
[23:34:57 CEST] <MINIMAN10001> alright vlc works fine
[23:41:34 CEST] <MINIMAN10001> hmm i give up that task lol
[23:42:07 CEST] <MINIMAN10001> i wanted to try and get a bitrate that would playable realtime by a 56k modem
[23:42:26 CEST] <MINIMAN10001> but at low bitrates video quality jumps off a cliff
[23:43:12 CEST] <MINIMAN10001> hmm yeah
[23:43:18 CEST] <MINIMAN10001> problem is probably the resolution
[23:43:59 CEST] <JEEBsv> and frame rate, since every picture has to have its headers etc
[23:44:23 CEST] <MINIMAN10001> i was running 4 fps 1920x1080 and 265 only created 2 frames at 50 kbps
[23:44:34 CEST] <MINIMAN10001> 264 just sorta did its best
[23:45:59 CEST] <JEEBsv> uhh
[23:46:10 CEST] <JEEBsv> I'm really not sure what exactly you're trying to say
[23:46:30 CEST] <MINIMAN10001> that 264 had 4 fps they just looked unrecognizable
[23:46:41 CEST] <MINIMAN10001> 265 only created 2 frames.
[23:46:47 CEST] <MINIMAN10001> over 10 seconds
[23:46:52 CEST] <JEEBsv> uhh
[23:47:11 CEST] <JEEBsv> are you talking about it being slower or are you talking about either encoder dropping frames?
[23:47:22 CEST] <JEEBsv> because yes, it's lol slow
[23:47:24 CEST] <MINIMAN10001> encoder dropped frames on 265
[23:47:30 CEST] <MINIMAN10001> all of them but 2
[23:47:31 CEST] <JEEBsv> ok, did it tell you about it
[23:47:53 CEST] <MINIMAN10001> dropped frames some odd 260 yeah
[23:48:03 CEST] <JEEBsv> can you post a log?
[23:48:08 CEST] <JEEBsv> on pastebin
[23:48:17 CEST] <MINIMAN10001> it appears out of habbit i closed the cmd prompt lol
[23:48:45 CEST] <JEEBsv> because I was trying to make sure you're just not having an issue between the chair and the keyboard
[23:49:16 CEST] <JEEBsv> (of course it is possible that libx265 drops frames but that would be rather anticlimatic due to libx264 specifically being made so that it doesn't drop anything)
[23:49:31 CEST] <JEEBsv> (and I would be surprised if libx265 dropped that design)
[23:49:40 CEST] <JEEBsv> (although... it's made by MCW so the fuck I know :V)
[23:50:03 CEST] <MINIMAN10001> so
[23:50:08 CEST] <MINIMAN10001> how do i even give you he console output anyways
[23:50:40 CEST] <MINIMAN10001> ah
[23:50:42 CEST] <MINIMAN10001> select all enter
[23:50:45 CEST] <MINIMAN10001> didnt know that existed
[23:50:55 CEST] <MINIMAN10001> for some reason i always assume you can't highlight in cmd prompt lol
[23:51:15 CEST] <JEEBsv> also if you want to just redirect an app's standard output/error stuff into a file that's also possible
[23:51:32 CEST] <JEEBsv> ffmpeg uses stderr so you add " 2> file.txt" to the end of your command
[23:51:37 CEST] <JEEBsv> without the ""
[23:51:58 CEST] <JEEBsv> 2 is "standard error, please", > is redirect and then you have the file name :P
[23:52:41 CEST] <JEEBsv> default is 1 and you get it with just a >, but ffmpeg doesn't use it when encoding so you can use it for output purposes
[23:53:10 CEST] <MINIMAN10001> http://pastebin.com/ZbzpZKMd
[23:53:21 CEST] <MINIMAN10001> i forgot the bitrate limits this time but it replicated either way
[23:57:56 CEST] <JEEBsv> that drop is funky, esp. since you didn't even set a bit rate limit there
[23:58:06 CEST] <rafael2k> People, which codec do you recommend for squeezing a HD-SDI 1.5Gb signal thru 1Gb ethernet without losing quality?
[23:58:10 CEST] <JEEBsv> so it wouldn't be the lack of emergency mode, either
[23:58:28 CEST] <JEEBsv> rafael2k: if it fits through something lossless, that
[23:58:34 CEST] <JEEBsv> what kind of image is it?
[23:58:46 CEST] <JEEBsv> as in, pixel format and bit depth
[23:58:47 CEST] <rafael2k> It's for TV contribution
[23:59:00 CEST] <rafael2k> I'm trying to save some money using 1Gb ethernet
[23:59:02 CEST] <rafael2k> ; )
[23:59:14 CEST] <rafael2k> 10bit 422
[23:59:19 CEST] <JEEBsv> ok
[23:59:40 CEST] <JEEBsv> your best bet is probably -q:v 0 -c:v libx264 with a 10bit libx264 linked in
[23:59:46 CEST] <rafael2k> I was thinking about using huffman or something very simple
[00:00:00 CEST] --- Sun Jun  7 2015