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 641858 - mpegaudioparse: Post CBR bitrate as nominal bitrate
mpegaudioparse: Post CBR bitrate as nominal bitrate
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
unspecified
Other All
: Normal normal
: 0.10.22
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-02-08 18:25 UTC by Arun Raghavan
Modified: 2011-02-09 17:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
mpegaudioparse: Post CBR bitrate as nominal bitrate (2.79 KB, patch)
2011-02-08 18:25 UTC, Arun Raghavan
committed Details | Review

Description Arun Raghavan 2011-02-08 18:25:31 UTC
For discoverer, we don't wait for 10 frames to be parsed before collecting available metadata. Attaching a patch to post available bitrate (as nominal) for the we-hope-this-is-a-CBR-stream case.
Comment 1 Arun Raghavan 2011-02-08 18:25:33 UTC
Created attachment 180404 [details] [review]
mpegaudioparse: Post CBR bitrate as nominal bitrate

Even if VBR headers are missing, we can't guarantee that a stream is in
fact a CBR stream, so it's safer to let baseparse calculate the average
bitrate rather than assume a CBR stream. However, in order to make
/some/ metadata available before the requisite number of frames have
been parsed, this posts the bitrate from the non-VBR headers as the
nominal bitrate.
Comment 2 Stefan Sauer (gstreamer, gtkdoc dev) 2011-02-09 13:17:07 UTC
good idea.
Comment 3 Mark Nauwelaerts 2011-02-09 17:35:38 UTC
commit cfc3f5e43bbcc5a9c6437ad83f12e834e7307908
Author: Arun Raghavan <arun.raghavan@collabora.co.uk>
Date:   Tue Feb 8 23:50:13 2011 +0530

    mpegaudioparse: Post CBR bitrate as nominal bitrate
    
    Even if VBR headers are missing, we can't guarantee that a stream is in
    fact a CBR stream, so it's safer to let baseparse calculate the average
    bitrate rather than assume a CBR stream. However, in order to make
    /some/ metadata available before the requisite number of frames have
    been parsed, this posts the bitrate from the non-VBR headers as the
    nominal bitrate.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=641858