After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 640569 - vp8enc bitrate property doesn't work
vp8enc bitrate property doesn't work
Status: RESOLVED INVALID
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-01-25 19:38 UTC by Luciana Fujii
Modified: 2011-02-04 10:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Luciana Fujii 2011-01-25 19:38:26 UTC 
When I encode video with vp8enc and set bitrate, the resulting file doesn't have fixed bitrate at all. I'm not setting quality at the same time, just to be clear.

I'm using a gst-launch command like: gst-launch v4l2src num-buffers=100 ! vp8enc bitrate=300 ! webmmux ! filesink location= video.webm
Comment 1 Tim-Philipp Müller 2011-01-25 19:49:56 UTC 
> v4l2src num-buffers=100 ! vp8enc bitrate=300 ! webmmux ! ...

The bitrate property is most likely in bits per second, not kbps. Have you tried 300000?
Comment 2 Luciana Fujii 2011-01-25 20:25:56 UTC 
Thanks for your answer. I hadn't tried. It actually works, the quality is much better and the file size is bigger setting it like that. Totem still doesn't show the bitrate for the video as it does with theoraenc, though. I don't know if this is still a vp8enc issue.

Anyway, this solves my problem, thanks!
Comment 3 Tim-Philipp Müller 2011-02-04 10:54:04 UTC 
The property documentation has been fixed now:

 commit 2b4c85414632fd4538ab135414fb227be46f80bd
 Author: Alexey Fisher <bug-track@fisher-privat.net>
 Date:   Fri Feb 4 09:08:26 2011 +0100

    vp8enc: Add description for bitrate units.


The situation with the different units for "bitrate" properties for different elements is a bit unfortunate, but there are open bugs for that already, so will close this one. (I think in future/0.11 everything will be standardised to bits per second.)