Re: [Musicpd-dev-team] Database backend
Max once thought about using SQLite as backend. He even was clear that, if done right, there shouldnt be ANY regression in speed. Not sure what the plans are for now. I guess there are more important things :) Fair enough. :) In the meantime, is there any way of selectively removing songs/albums/etc from the MPD database? Or is the best way to delete the database files or make MPD recreate it via --createdb and repopulate from scratch? -- Jonny Tyers -- ___ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
Re: [Musicpd-dev-team] Database backend
I agree that it's sometimes awkward that the update is modification time based - for example, if you add replaygain tags to your whole library you don't really want it all to end up with the same modification date. Perhaps it's worth looking into adding a feature there, since something a lot simpler than implementing SQLite would be possible. For now, I've never actually done this but I expect you could edit the database by hand, since it's stored as text. In particular, you could delete references to songs you want to update, or reset their mtime to something old and let mpd handle the rest. And of course, for move/delete cases the update path mechanism should be sufficient, with enough care in picking the path so that it doesn't have to scan all 100GB. Jeffrey On Wed, Jul 1, 2009 at 3:24 AM, Jonny jonnyt...@gmail.com wrote: In the meantime, is there any way of selectively removing songs/albums/etc from the MPD database? Or is the best way to delete the database files or make MPD recreate it via --createdb and repopulate from scratch? -- Jonny Tyers -- ___ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
Re: [Musicpd-dev-team] Database backend
On Wed, Jul 01, 2009 at 09:31:43AM -0500, Jeffrey Middleton wrote: if you add replaygain tags to your whole library you don't really want it all to end up with the same modification date. Why not? If all files were modified at the same time, they should all have the same modification time. Tracking file changes is really the only reason the modification time is stored at all. Not updating it breaks more than just mpd too. For example, rsync uses the same technique to determine which files have changed. Of course it checks file size too, but that doesn't really help when doing things like editing ID3 tags, since doing so rarely changes the file size. On Wed, Jul 1, 2009 at 3:24 AM, Jonny jonnyt...@gmail.com wrote: In the meantime, is there any way of selectively removing songs/albums/etc from the MPD database? What I do is use a fake music directory, with symlinks to my actual music. My real music directory has only a few directories, plus a todo directory with music that still needs to be sorted. In my fake music directory, I have symlinks to everything in there *except* the todo directory, keeping it out of my database. It might be a bit hard to manage if you want to keep out, say, specific albums or songs, and not just one out of a few top level directories. But it wouldn't be too difficult to write a script to create symlinks to everything in a given directory, excluding a subset of it's contents. pgpzyOZp93AUS.pgp Description: PGP signature -- ___ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
Re: [Musicpd-dev-team] Database backend
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Why dont you just move the files to a non-mpd directory and do a database update? Jonny wrote: Max once thought about using SQLite as backend. He even was clear that, if done right, there shouldnt be ANY regression in speed. Not sure what the plans are for now. I guess there are more important things :) Fair enough. :) In the meantime, is there any way of selectively removing songs/albums/etc from the MPD database? Or is the best way to delete the database files or make MPD recreate it via --createdb and repopulate from scratch? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpLyboACgkQswz/d6k9dsWFawCeJzEYf30250z9UBbU82I3vza+ M6QAn0ZjPEMykAY6+3egyFO/3bc+KgEV =erk+ -END PGP SIGNATURE- -- ___ Musicpd-dev-team mailing list Musicpd-dev-team@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
