sound-juicer tags mp3 files with incorrect musicbrainz ids

Bug #353389 reported by DSHR
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MusicBrainz Picard
Fix Released
Unknown
Sound Juicer
Fix Released
Medium
sound-juicer (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: sound-juicer

Sound-juicer seems to tag mp3 files with musicbrainz tags incompatible with banshee and picard. I think this did not happen on intrepid. Looking at a file ripped with sound-juicer and the same track ripped with banshee the difference is obvious:

sound-juicer:
Unique File ID: [http://musicbrainz.org] http://musicbrainz.org/track/611703be-4157-4173-886f-b9fa0f2c4a36

UserTextFrame: [Description: MusicBrainz Album Id]
http://musicbrainz.org/release/fa1db2dc-b37e-4d8d-8a96-aca8bd38ea89.html
UserTextFrame: [Description: musicbrainz_albumid]
http://musicbrainz.org/release/fa1db2dc-b37e-4d8d-8a96-aca8bd38ea89.html
UserTextFrame: [Description: MusicBrainz Album Artist Id]
http://musicbrainz.org/artist/67930b3e-e00b-469f-8c74-fd69f20522ec
UserTextFrame: [Description: musicbrainz_albumartistid]
http://musicbrainz.org/artist/67930b3e-e00b-469f-8c74-fd69f20522ec
UserTextFrame: [Description: MusicBrainz Artist Id]
http://musicbrainz.org/artist/67930b3e-e00b-469f-8c74-fd69f20522ec
UserTextFrame: [Description: musicbrainz_artistid]
http://musicbrainz.org/artist/67930b3e-e00b-469f-8c74-fd69f20522ec

banshee:
Unique File ID: [http://musicbrainz.org] 611703be-4157-4173-886f-b9fa0f2c4a36

UserTextFrame: [Description: MusicBrainz Artist Id]
67930b3e-e00b-469f-8c74-fd69f20522ec
UserTextFrame: [Description: musicbrainz_artistid]
67930b3e-e00b-469f-8c74-fd69f20522ec
UserTextFrame: [Description: MusicBrainz Album Id]
fa1db2dc-b37e-4d8d-8a96-aca8bd38ea89
UserTextFrame: [Description: musicbrainz_albumid]
fa1db2dc-b37e-4d8d-8a96-aca8bd38ea89

The URL-Version leads to picard being unable to load the album information.

Revision history for this message
Philipp Wolfer (phw) wrote :

Yes, that's seriously wrong. Sound Juicer did this correctly in Intrepid. I just had a quick look myself, but couldn't find the cause for this behaviour.

Changed in sound-juicer:
status: Unknown → New
Changed in sound-juicer:
status: New → Confirmed
Revision history for this message
Phil Housley (undeconstructed) wrote :

This problem happens with vorbis files as well, so I assume it is general within soundjuicer.

Changed in picard:
status: Unknown → Confirmed
Revision history for this message
DSHR (s-heuer) wrote :

Seems to be fixed with sound-juicer 2.28.0 (karmic beta).

Revision history for this message
Philipp Wolfer (phw) wrote :

I haven't tested this version, but given the source it does not look like it was fixed.

Changed in picard:
status: Confirmed → Fix Released
Revision history for this message
DSHR (s-heuer) wrote :

$ LANG=C apt-cache policy sound-juicer
sound-juicer:
  Installed: 2.28.0-1
  Candidate: 2.28.0-1
  Version table:
 *** 2.28.0-1 0
        500 http://archive.ubuntu.com karmic/universe Packages
        100 /var/lib/dpkg/status

gives

Unique File ID: [http://musicbrainz.org] 777c3e8a-f3aa-41e9-8296-28d09bf42f18

UserTextFrame: [Description: MusicBrainz Album Id]
98862aec-2132-4407-bacc-508dbaddd3d8
UserTextFrame: [Description: musicbrainz_albumid]
98862aec-2132-4407-bacc-508dbaddd3d8
UserTextFrame: [Description: MusicBrainz Album Artist Id]
4bdcee62-4902-4773-8cd1-e252e2e31225
UserTextFrame: [Description: musicbrainz_albumartistid]
4bdcee62-4902-4773-8cd1-e252e2e31225
UserTextFrame: [Description: MusicBrainz Artist Id]
4bdcee62-4902-4773-8cd1-e252e2e31225
UserTextFrame: [Description: musicbrainz_artistid]
4bdcee62-4902-4773-8cd1-e252e2e31225
UserTextFrame: [Description: CDDB DiscID]
880ad70b
UserTextFrame: [Description: discid]
880ad70b
UserTextFrame: [Description: MusicBrainz DiscID]
rjqyEXrqEtGBetOV1A3dor6puHA-
UserTextFrame: [Description: musicbrainz_discid]
rjqyEXrqEtGBetOV1A3dor6puHA-

as reported by eyeD3 - looks OK for me ....

Revision history for this message
Philipp Wolfer (phw) wrote :

I've found the "fix". The package in Karmic uses the deprecated libmusicbrainz version 2 instead of 3 (the package of libmusicbrainz 2 is called libmusicbrainz4 in Ubuntu).

Jaunty switched from version 2 to 3, which introduced this bug. Now Karmic switched back, which "solves" this bug again. I've opened another bug report #455461, which explains why this is even worse than before.

Revision history for this message
Jeff Ebert (jeffrey-ebertland) wrote :

I used Sound Juicer on Jaunty to rip the majority of my CDs, and then Picard to do some tag clean-up, so this bug got me. I wrote a small utility to fix the MusicBrainz tags (attached).

Note that you must have python and python-mutagen installed, and I only tested this code with python2.6.

Changed in sound-juicer (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Changed in sound-juicer:
importance: Unknown → Medium
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.