Open GoogleCodeExporter opened 9 years ago
Hi.
Maybe use x264 if you can as it does a better job at preserving bloom with the
settings on the wiki. I might look into some better settings for Webm at some
point - or you could do some research into that if you like.
My guess is that it just seems like the video is accelerated. It's probably
just what it looks like at true 60fps instead of whatever it normally runs at.
Cheers
Andrew
Original comment by acaudw...@gmail.com
on 17 Mar 2013 at 10:07
Thanks for your answer.
I prefer webm (free as in free speech, you know ? XD) but I will try x264 with
the same presets (it's not the wiki's ones, I use -b:v 30,000K).
I personaly prefer this speed, maybe because my project has not a big history
(1 year of really non-intensive commits, with 3 commiters). At true 60 fps it
will be too short.
Yamakaky
Original comment by Yamakaky
on 18 Mar 2013 at 7:47
I searched on the net and found a *better* command for dooing that :
ffmpeg -y -threads 0 -r 40 -f image2pipe -vcodec ppm -i $< -vcodec libvpx -vb 1000k -minrate 100k
-maxrate 30000k -bufsize 1000K -qmin 3 -qmax 30 -rc_lookahead 16 -keyint_min 0 -g 360
-skip_threshold 0 -level 116 -preset veryslow -ab 192k $@
After that, the video has a pretty good quality. I don't understand all the
options (some are not in the man), I'm working on optimizing this.
Do you want my Makefile for the wiki ?
Original comment by Yamakaky
on 18 Mar 2013 at 1:36
Thanks. I might look into what those options do and figure out a better command
line for the wiki.
Original comment by acaudw...@gmail.com
on 19 Mar 2013 at 8:49
Original issue reported on code.google.com by
Yamakaky
on 17 Mar 2013 at 12:44