Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Webm encoding quality #183

Open
GoogleCodeExporter opened this issue Mar 18, 2016 · 4 comments
Open

Webm encoding quality #183

GoogleCodeExporter opened this issue Mar 18, 2016 · 4 comments

Comments

@GoogleCodeExporter
Copy link

Hi

I use your soft for one of my projects, but the output video has a very bad 
quality, in particular with the bloom. I use this command line :
    gource --user-image-dir faces --hide 'mouse' --multi-sampling -r 60 -1280x720! -a 1 --bloom-multiplier 0.5 -o - $project_dir | ffmpeg -y -threads 0 -r 40 -f image2pipe -vcodec ppm -i $< -vcodec libvpx -b:v 30000K output.webm

I use -r 60 in gource and -r 40 in ffmpeg because otherwise the video is 
accelerated. Any idea ?

Original issue reported on code.google.com by Yamakaky on 17 Mar 2013 at 12:44

@GoogleCodeExporter
Copy link
Author

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 [email protected] on 17 Mar 2013 at 10:07

  • Changed title: Webm encoding quality
  • Added labels: Priority-Low, Type-Other
  • Removed labels: Priority-Medium, Type-Defect

@GoogleCodeExporter
Copy link
Author

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

@GoogleCodeExporter
Copy link
Author

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

@GoogleCodeExporter
Copy link
Author

Thanks. I might look into what those options do and figure out a better command 
line for the wiki.

Original comment by [email protected] on 19 Mar 2013 at 8:49

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant