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 794876 - Opus files are encoded allways in hard-CBR
Opus files are encoded allways in hard-CBR
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: general
HEAD
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-04-01 14:37 UTC by POJAR GEORGE
Modified: 2018-05-24 19:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description POJAR GEORGE 2018-04-01 14:37:29 UTC 
Opusinfo tool shows that OPUS files produced by rhythmbox use hard-CBR mode (instead of VBR).

I did a short investigation and it turns out that the `cbr` option does not exist in GStreamer 1.0; instead the `bitrate-type` option was introduced:

    bitrate-type : Bitrate type
                           flags: readable, writable, changeable in NULL, READY, PAUSED or PLAYING state
                          Enum "GstOpusEncBitrateType" Default: 0, "cbr"
                             (0): cbr - CBR
                             (1): vbr - VBR
                             (2): constrained-vbr - Constrained VBR

Replacing `cbr=false` with `bitrate-type = vbr` resulted in a proper VBR Opus being generated.

Please replace in rhythmbox.gep common encoding profiles for rhythmbox file:

    [rhythmbox-encoding-opusenc-vbr]
    cbr = false
    constrained-vbr = true

    [rhythmbox-encoding-opusenc-cbr]
    cbr = true

with:

    [rhythmbox-encoding-opusenc-vbr]
    bitrate-type = constrained-vbr

    [rhythmbox-encoding-opusenc-cbr]
    bitrate-type = cbr
Comment 1 GNOME Infrastructure Team 2018-05-24 19:43:49 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/1634.