[gstreamer-bugs] [Bug 620323] New: mp3 playback does not respect lame gapless tags

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=620323
  GStreamer | gst-plugins-ugly | 0.10.15

           Summary: mp3 playback does not respect lame gapless tags
    Classification: Desktop
           Product: GStreamer
           Version: 0.10.15
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-ugly
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: nyall at zombiepigs.net
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


Currently, gstreamer is ignoring the lame tags in mp3s during gapless playback.
These tags contain information about the padding at the start and end of the
files, which should be skipped to get perfect gapless playback of these files.
Without using these tags, there'll always be a tiny silence or glitch between
songs. 


Here's an example of the lame tags in a file which should play back gaplessly:

$eyeD3 --lametag Track01.mp3

Track01.mp3 [ 3.77 MB ]

Encoder Version : LAME3.98r
LAME Tag Revision : 0
VBR Method : Variable Bitrate method2 (mtrh)
Lowpass Filter : 18500
Radio Replay Gain : -2.0 dB (Set automatically)
Encoding Flags : --nspsytune --nssafejoint
ATH Type : 4
Bitrate (Minimum) : 192
Encoder Delay : 576 samples
Encoder Padding : 960 samples
Noise Shaping : 1
Stereo Mode : Joint
Unwise Settings : False
Sample Frequency : 44.1 kHz
MP3 Gain : 0 (+0.0 dB)
Preset : V2
Surround Info : None
Music Length : 3.77 MB
Music CRC-16 : 07F9
LAME Tag CRC-16 : E5BF


The encoder delay and encoder padding tags describe how many samples were added
at the start and end of the audio to complete the frames. Some more information
is available on this page: http://gabriel.mp3-tech.org/mp3infotag.html

-- 
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.