Sound Juicer should remember modifications to titles/artists after exiting

is there any point to keep these changes ? You change the track/artist, extract
the CD and the job is done, isn't it ?

My use cases were:

1. I entered all the CD data for a CD (the default download was completely
wrong) before realising that I hadn't installed gstreamer0.8-lame in order to
rip to mp3, so I had to exit Sound Juicer, installed gstreamer0.8-lame restarted
Sound Juicer and then discovered I needed to reenter all the data.

2. I occasionally need to rip a CD twice, usually because I want to store it in
ogg for my Free Software using house to listen to, but also want it on mp3 so
that I can listen to it on my proprietry solid state mp3 player. I usually don't
do these rips at the same time.

The third one I haven't encountered:

3. In the event of a crash of either Sound Juicer, X, or my computer, I'd rather
not do that data entry again if it can be avoided.

Ok. In fact there is a bug open upstream about caching the datas:
http://bugzilla.gnome.org/show_bug.cgi?id=121479

let me add a ditto, I tried sound juicer once, found that it produced <<< less
usable directories than the carefully configured GRip I use, and that I had to
re-correct bad cd data every time I wanted to retry.... so I gave up on it.

Isn't the idea that, if it is incorrect, you go to the MusicBrainz site (the latest S-J have an option to go direct to the CD you have in the drive) and fix them up for everyone's benefit?

I filed this bug against Sound Juicer in Ubuntu 4.10, which I don't recall exposing any such option. I haven't used it since then so I can't comment on what "the idea" is in recent releases. It sounds like a reasonable solution on the face of it.

In the case where you go to the MB site and fix the data for everyone, S-J needs to have a way to reload that data instead of using the cached data. I suggest that the "Re-read disc" function do this.

Also, It's still useful to be able to retain your own changes, as (at least for me) it is not uncommon to disagree with the MusicBrainz metadata.

Personally I advocate making it as easy as possible to correct the central database as opposed to every user having a separate cache. The difficulty with a cache is that if the database has been changed by someone in the interim then the user doesn't get the benefit of the changes. At the moment if there are things that are wrong, I change the database, re-read the disc and it is correct.

As I say, if I disagree with the MB data I usually fix it or find that I am wrong ;). I also usually only rip my CDs once and so, were there any changes I wanted to make, I wouldn't be concerned that those changes weren't kept.

That is just my opinion.

One example I've found where I disagree irreconcilably with Musicbrainz, is the Marilyn Manson track known as "Spade" or "♠".

I prefer the "♠" spelling, while MB prefers the "Spade" spelling because they don't like to use Unicode in tags where it can be avoided. Thus I prefer to use my info for myself, rather than theirs, and a local cache is the way to do this. In this case, neither of us are "wrong", we just have a different perspective on it.

I also tend to rip my CDs more than once, as I generally rip to OGG but sometimes want something in MP3 or FLAC for some reason. Sometimes rips screw up because I have the wrong settings, or random other reasons. I prefer not to have to make my changes over and over.

I've encountered this the few times that I've used S-J. It's frustrating - as a user - to have carefully entered all the track information only to have my computer "forget" when I have to re-run S-J (in my case, it was working around another bug). Loss of user-entered information is uncool and perhaps worse than not having them propagate it to the central database. After all, if their carefully-entered information is lost when S-J crashes/restarts, no one benefits.

I would not consider having S-J forget my information to be a feature, even if the intent is to get users to update the central database. What about an option - upon closing - that asks if they wish to "save" or "save and share"?

Another point to consider: Even if the user goes through the process of updating/correcting the MB database, that process takes several weeks before the results appear in the MB results. In the meantime, the old/incorrect results will be returned.

Other ripping software save the changes made by the user into .cddb (local copy of the FreeDB). I think sound juicer should do the same.

Any news? Version 2.26.1 still forgets all the info I have entered. It is annoying, I use to rip CDs with Kaudiocreator, but now I am using GNOME. I'll keep searching for another program, but it would be nice to reconsider keeping the user data locally.