Re: [Banshee-List] Banshee writing ID3v1 rather than ID3v2 tags when ripping CDs



On 13 April 2014 21:22, "Andrés G. Aragoneses" <knocte gmail com> wrote:
On 12/04/14 15:17, William Furnass wrote:
Can't see an option to write ID3v2 rather than ID3v1 in the 'audio CD'
prefs - am I missing something obvious here?

I ask as my Sansa Fuze MP3 player doesn't interpret ID3v1 track
numbers correctly and so plays album tracks out of sequence.

IIRC this is a known issue, Banshee should write tags via taglib-sharp
when ripping (instead of using GStreamer which is what it might be using
now). It may be easy to fix.

Thanks for the info.  Looks like the bug report re the use of
gstreamer rather than taglib-sharp when ripping hasn't been updated
since it was originally filed in Sept 2011 [1] and gstreamer is still
being used for tagging in the banshee git head [2].

I'm slightly confused though: [2] indicates that 'id3v2mux' should be
used for tagging if available and the Gstreamer 0.10 tagging library
(libgsttaglib.so) on my machine does seem to support this:

$ strings /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgsttaglib.so |
grep id3v2mux
id3v2mux

Yet the MP3 files that I rip and encode using Banshee only have ID3v1
tags.  Also, Banshee still writes only ID3v1 and not ID3v2 tags when I
update file tags _after_ ripping:

~/Music/Unknown Artist/Unknown Album $ id3v2 -l 01.\ Track\ 1.mp3
id3v1 tag info for 01. Track 1.mp3:
Title  : Track 1                         Artist: Aluk Todolo2
Album  : Unknown Album                   Year:     , Genre: Unknown (255)
Comment:                                 Track: 1
01. Track 1.mp3: No ID3v2 tag

[1] https://bugzilla.gnome.org/show_bug.cgi?id=658372
[2] https://git.gnome.org/browse/banshee/tree/data/audio-profiles/mp3-lame.xml.in


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]