John Eckman's dashboard

Thanks for your reply. Someone else had also responded actually pointing to the songbird.metadata.enableWriting pointer as well.

Unfortunately, when I tried to import my library after doing that Songbird crashed - out of memory I believe (this was on a Windows XP box, but the library is quite large).

Haven't had a chance to try it again (or on Linux or Mac OS) since then.

The point of not allowing changes to the file is just that I've used too many systems which wrote bad metadata - changed album art, consolidated albums which should be kept apart, "updated" years in accurately, etc.

Also, I backup my entire music library, and would prefer to only incrementally backup changed files - updating metadata makes the files "changed" and means they get backed up again.

I guess it is just philosophical - I don't think of my player application as "managing" my library, just knowing about it to be able to play it - if I find I actually use the app to edit meta data, then I'd be happy to re-enable the preference - but once I set meta data accurately, I see little reason to update it.

Thanks pvh - that rocks. I will take a look at about:config.

Songbird is fantastic, and I'm promoting every chance I get - thanks for the good work

@Boris - thanks. It just seems odd to have a "player" app require write access upfront - I've had other "library organizing" type apps go in and make unexpected meta-data changes before and I'd like to avoid that . . .

I'm with Jason - why does Songbird need write-access to metadata for my files? I'm reluctant to let it "touch" my carefully managed library without knowing what data it might update

How can you add multiple stops to an existing trip? I see the answers here related to the "new trips" flow but not how to edit an existing trip.

Thanks Scott - I agree there's potential for ongoing collaboration, just want to make sure we don't end up with two unnecessarily competing orgs (FSF/OSI round 2?) – John Eckman, on July 24, 2008 18:53