Bug 183177 - sound-juicer can't find music data that is artist, album, and title.
Summary: sound-juicer can't find music data that is artist, album, and title.
Alias: None
Product: Fedora
Classification: Fedora
Component: sound-juicer   
(Show other bugs)
Version: 5
Hardware: i386 Linux
Target Milestone: ---
Assignee: John (J5) Palmieri
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-02-27 05:16 UTC by Takaki Hiroshi
Modified: 2013-03-13 04:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-10 23:06:45 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 330464 None None None Never

Description Takaki Hiroshi 2006-02-27 05:16:31 UTC
Description of problem:
sound-juicer can't find music data. Music data of my cdrom, Milk and Honey, is
in musicbrainz.


Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. insert cd into drive
Actual results:
Title: Unknown Title
Artist: Unknown Artist

Expected results:
Title: Milk and Honey
Artist: John Lennon & Yoko Ono

Additional info:
rhythmbox- in FC5 can find this. sound-juicer in FC3 can find this.


Comment 1 John Thacker 2006-03-03 06:39:58 UTC
Check to see if this still happens with sound-juicer-2.13.6.  The upstream
author turned off caching the metadata between 2.13.5, as it was breaking things.

Comment 2 Takaki Hiroshi 2006-03-03 13:27:46 UTC
Thanks for your comment. But sound-juicer-2.13.6-1 in today's rawhide still not
works fine.

Comment 3 John Thacker 2006-03-08 03:43:35 UTC
The album information is in MusicBrainz, but no DiscID exists for it in
MusicBrainz, so lookup won't work.  Try inserting your disc, selecting "Submit
Track Names" from the disc menu, and then looking up the Album in order to add
the DiscID.  You may need to create a MusicBrainz username to do so, I'm not sure.

This is expected behavior because there's a track listing but no DiscID in the
MusicBrainz database, and sound-juicer (and MusicBrainz) uses the DiscID to look
up CDs.  (Sometimes different replication batches of the same CD can have
different IDs, though, depending on how they were pressed.)  If you add the
DiscID, it should work.

Comment 4 John Thacker 2006-03-08 03:57:33 UTC
From http://musicbrainz.org/cd_submission.html:

"However, there is a downside to this as well. Audio CD-ROMs are usually
produced in large batches, that may include thousands if not millions of copies
of one CD. Once a record company is done selling that one batch, or a record
company in another country wants to print up a batch of the same CD, they will
make another batch. There are over 10 different pressings for the album 'The
Dark Side of the Moon' by Pink Floyd, for instance.

If the CDs from the new batch are off by one sector (as mentioned above) they
will have a different unique Disc ID.


Let's say you use one of the CD Submission tools to submit a CD and you find
that MusicBrainz doesn't know about the CD. You then proceed to select the
artist and then MusicBrainz shows you a list of CDs and your CD is right there
is in the list. What's wrong?

There may be a few things going on:

    * MusicBrainz may not have any Disc IDs for this album.
    * MusicBrainz may have a different Disc ID than you have, thus MusicBrainz
already knows about a different pressing of the CD. 

In either case, you should select the matching CD and let MusicBrainz create
another association for you. This means that MusicBrainz will now know about the
new Disc ID that you just reported. The next time you want to look up this CD,
MusicBrainz will gladly deliver the data to you."

Comment 5 Takaki Hiroshi 2006-03-10 23:06:45 UTC
You are right. I got the expected results if I sent DiskID to MusicBrainz by
function of sound-juicer. Thanks!

Note You need to log in before you can comment on or make changes to this bug.