sound-juicer tags mp3 files with incorrect musicbrainz ids
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://
UserTextFrame: [Description: MusicBrainz Album Id]
http://
UserTextFrame: [Description: musicbrainz_
http://
UserTextFrame: [Description: MusicBrainz Album Artist Id]
http://
UserTextFrame: [Description: musicbrainz_
http://
UserTextFrame: [Description: MusicBrainz Artist Id]
http://
UserTextFrame: [Description: musicbrainz_
http://
banshee:
Unique File ID: [http://
UserTextFrame: [Description: MusicBrainz Artist Id]
67930b3e-
UserTextFrame: [Description: musicbrainz_
67930b3e-
UserTextFrame: [Description: MusicBrainz Album Id]
fa1db2dc-
UserTextFrame: [Description: musicbrainz_
fa1db2dc-
The URL-Version leads to picard being unable to load the album information.
Changed in sound-juicer: | |
status: | Unknown → New |
Changed in sound-juicer: | |
status: | New → Confirmed |
Changed in picard: | |
status: | Unknown → Confirmed |
Changed in picard: | |
status: | Confirmed → Fix Released |
Changed in sound-juicer (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in sound-juicer: | |
importance: | Unknown → Medium |
status: | Confirmed → Fix Released |
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.