[Bug 647659] New: mp3parse / mpegaudioparse fails to detect VBRI header in mpeg1 mono and mpeg2 files
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Wed Apr 13 07:16:58 PDT 2011
https://bugzilla.gnome.org/show_bug.cgi?id=647659
GStreamer | gst-plugins-ugly | git
Summary: mp3parse / mpegaudioparse fails to detect VBRI header
in mpeg1 mono and mpeg2 files
Classification: Platform
Product: GStreamer
Version: git
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gst-plugins-ugly
AssignedTo: gstreamer-bugs at lists.freedesktop.org
ReportedBy: jonas.larsson at hiq.se
QAContact: gstreamer-bugs at lists.freedesktop.org
GNOME version: ---
Created an attachment (id=185872)
--> (https://bugzilla.gnome.org/attachment.cgi?id=185872)
A (cut) sample mp3 file with VBRI header
When parsing a single channel mpeg 1 or mono/stereo mpeg2 mp3 file, mp3parse
fails to detect VBRI header. VBRI header should always be at offset 0x20
regardless of mpegversion and channels. The offset currently varies between
0x09, 0x11 and 0x20 depending on mpegversion and channels. This is fine for
Xing and Info headers but not for VBRI.
Please see http://www.codeproject.com/audio/MPEGAudioInfo.asp which is
referenced in gstmpegaudioparse.c.
A (cut) sample mp3 file with VBRI header attached.
gst_mp3parse_handle_first_frame:<mpegaudioparse0> Xing, LAME or VBRI header not
found in first frame
At http://www.getid3.org/samples/index.php?dir=/mp3/vbri you can find a mpeg2
VBRI file (VBRI_22S.mp3) that has VBRI at offset 0x20 as well. Detecting the
header fails (partly) for the same reason with this one.
I believe this applies to mpegaudioparse as well, not just mp3parse.
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list