Comment 16 for bug 1084759

And from Daniel at the mailing list:

"Hi Tuukka, Hi Ilkka,

thank you for picking up this topic.

Here some unsorted comments:

---

XSPF:
It looks like this is extensible and because of this a good candidate to store Mixxx database info in a standard format. We may start by offering a simple xspf playlist export similar to what we do with m3u right now.
This may expand later with additional meta informations.

The next step is to allow to copy the tracks along with these playlists/crates. This way most use-cases are covered. I am just worrying that export might be pretty easy but not re-import.

---

/media/external/exported/.mixxx/mixxx.sqlite:
I like this idea very much, because it is exactly my current workflow using the --settingsPath Option.

I have all my tracks on my desktop PC and on a external HDD, big enough to carry the entire database.
Before I go to a gig, I just do:
rsync -av ~/Musik /media/Musik --delete
Since I use clementine for tagging, I search for tracks changed since last Gig, Put them in a Playlist and
Select "Reload Metadata"
After the gig I do
rsync -av /media/Musik ~/Musik

All changes that will streamline this work flow are very welcome :-)

Since there is a high risk of a corrupt sqlite DB when you remove
accidentally the USB cable. I put the whole .mixxx folder under git
control.
This means: the working sqlite DB should allways be on a fixed mounted
drive.

I am not scared about the possible bit incompatibility. We must Fix the
Mixxx version anyway, and if it turn out sqlite breaks the compatibility.
We may distribute the sqlite.so along with Mixxx.

---

"