Re: [Mixxx-devel] attn to our German speakers...
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. --- Kind regards, Daniel Am 29.08.2014 um 14:25 schrieb Tuukka Pasanen: > Hello, > I've though how about using XSPF or similar playlist style abroach > because SQLite databases are not promised to be byte compatible > (allthougth they have been for ages and will be like for evermore) and > XSPF can be expanded with extensions (just lighter abroach). > > workflow can be like down but with extensions to have file named >/media/external/exported/.mixxx/database.xspf > > So when you import some path you check for and parse > .mixxx/database.xspf or open if to VLC if you are in hurry :P. I also > think should it be like you > can export those playbags so it would make sense so they appear as new > playbag (or what ever it's in English) when you import it and when it's gone > playbag is gone so no need new abstraction. > > Sincerely, > Tuukka > > On 29.08.2014 11:42, Ilkka Tuohela wrote: >> Hi, >> >> I think these two bugs should be implemented with a workflow like this: >> >> - select a folder to export files to (‘create external mixxx library’ for >> example), let’s say >>/media/external/exported >> >> - mixxx creates empty database to the location, for example >>/media/external/exported/.mixxx/mixxx.sqlite >> >> - if successful, the exported library is shown in the mixxx sidebar with >> ‘unmount' icon >> >> - user drags tracks from the library to the folder in sidebar, just like to >> a playlist >>-> mixxx copies the tracks to the folder and updates database in external >> directory >> -> the external DB must contain path in internal DB to match the >> tracks later >> -> tag changes must be timestamped to allow merging of changes back >>-> user can create folders, which are folders in the export directory, >> and mixxx has >>relative paths to the tracks in the exported directory >> >> - user unmount the external library from sidebar >>-> exported database is closed and the entry disappears from mixxx sidebar >> >> - on another (or same) mixxx machine, user chooses ‘import external library’ >>-> the library is shown in mixxx sidebar, and changes can be imported >> (but maybe not >>automatically? Maybe option in sidebar context menu or in import >> dialog?) >>-> tracks can be played normally from the sidebar external library folder >> >> I see no point exporting cue info or waveforms in json or xml formats, >> because the data is internal to mixxx. >> >> *hile* >> >> >> On 2014-08-29, at 11:28 , Tuukka Pasanen wrote: >> >>> Hello, >>> Just thinking should it be JSON, XML or Sqlite file? JSON and XML is >>> supported by QT but config is XML so should it be like that? >>> >>> Thanks, >>> Tuukka >>> >>> On 21.08.2014 18:35, Daniel Schürmann wrote: This might be solved after implementing https://bugs.launchpad.net/mixxx/+bug/1001299 and https://bugs.launchpad.net/mixxx/+bug/918233 Any takers? Am 20.08.2014 19:50, schrieb Musikpirat: > Am 20.08.2014 um 14:48 schrieb Owen Williams: >> persisting on the same machine or is he moving to another machine? >> Obviously it won't work if he's moving to different computers, but they >> should persist if they are on the same machine. > Think he wants to copy the files from one hdd onto another. A common > usecase would be to prepare a set on your workstati
Re: [Mixxx-devel] attn to our German speakers...
Hello, I've though how about using XSPF or similar playlist style abroach because SQLite databases are not promised to be byte compatible (allthougth they have been for ages and will be like for evermore) and XSPF can be expanded with extensions (just lighter abroach). workflow can be like down but with extensions to have file named /media/external/exported/.mixxx/database.xspf So when you import some path you check for and parse .mixxx/database.xspf or open if to VLC if you are in hurry :P. I also think should it be like you can export those playbags so it would make sense so they appear as new playbag (or what ever it's in English) when you import it and when it's gone playbag is gone so no need new abstraction. Sincerely, Tuukka On 29.08.2014 11:42, Ilkka Tuohela wrote: > Hi, > > I think these two bugs should be implemented with a workflow like this: > > - select a folder to export files to (‘create external mixxx library’ for > example), let’s say >/media/external/exported > > - mixxx creates empty database to the location, for example >/media/external/exported/.mixxx/mixxx.sqlite > > - if successful, the exported library is shown in the mixxx sidebar with > ‘unmount' icon > > - user drags tracks from the library to the folder in sidebar, just like to a > playlist >-> mixxx copies the tracks to the folder and updates database in external > directory > -> the external DB must contain path in internal DB to match the tracks > later > -> tag changes must be timestamped to allow merging of changes back >-> user can create folders, which are folders in the export directory, and > mixxx has >relative paths to the tracks in the exported directory > > - user unmount the external library from sidebar >-> exported database is closed and the entry disappears from mixxx sidebar > > - on another (or same) mixxx machine, user chooses ‘import external library’ >-> the library is shown in mixxx sidebar, and changes can be imported (but > maybe not >automatically? Maybe option in sidebar context menu or in import > dialog?) >-> tracks can be played normally from the sidebar external library folder > > I see no point exporting cue info or waveforms in json or xml formats, > because the data is internal to mixxx. > > *hile* > > > On 2014-08-29, at 11:28 , Tuukka Pasanen wrote: > >> Hello, >> Just thinking should it be JSON, XML or Sqlite file? JSON and XML is >> supported by QT but config is XML so should it be like that? >> >> Thanks, >> Tuukka >> >> On 21.08.2014 18:35, Daniel Schürmann wrote: >>> This might be solved after implementing >>> https://bugs.launchpad.net/mixxx/+bug/1001299 >>> and >>> https://bugs.launchpad.net/mixxx/+bug/918233 >>> >>> Any takers? >>> >>> >>> Am 20.08.2014 19:50, schrieb Musikpirat: Am 20.08.2014 um 14:48 schrieb Owen Williams: > persisting on the same machine or is he moving to another machine? > Obviously it won't work if he's moving to different computers, but they > should persist if they are on the same machine. Think he wants to copy the files from one hdd onto another. A common usecase would be to prepare a set on your workstation and than copy it (plus some additional files) to your laptop. Christian -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel >>> -- >>> Slashdot TV. >>> Video for Nerds. Stuff that matters. >>> http://tv.slashdot.org/ >>> ___ >>> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >>> http://mixxx.org >>> >>> >>> Mixxx-devel mailing list >>> Mixxx-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/mixxx-devel >>> >> >> -- >> Slashdot TV. >> Video for Nerds. Stuff that matters. >> http://tv.slashdot.org/ >> ___ >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> http://mixxx.org >> >> >> Mixxx-devel mailing list >> Mixxx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel > -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.source
Re: [Mixxx-devel] attn to our German speakers...
Hi, I think these two bugs should be implemented with a workflow like this: - select a folder to export files to (‘create external mixxx library’ for example), let’s say /media/external/exported - mixxx creates empty database to the location, for example /media/external/exported/.mixxx/mixxx.sqlite - if successful, the exported library is shown in the mixxx sidebar with ‘unmount' icon - user drags tracks from the library to the folder in sidebar, just like to a playlist -> mixxx copies the tracks to the folder and updates database in external directory -> the external DB must contain path in internal DB to match the tracks later -> tag changes must be timestamped to allow merging of changes back -> user can create folders, which are folders in the export directory, and mixxx has relative paths to the tracks in the exported directory - user unmount the external library from sidebar -> exported database is closed and the entry disappears from mixxx sidebar - on another (or same) mixxx machine, user chooses ‘import external library’ -> the library is shown in mixxx sidebar, and changes can be imported (but maybe not automatically? Maybe option in sidebar context menu or in import dialog?) -> tracks can be played normally from the sidebar external library folder I see no point exporting cue info or waveforms in json or xml formats, because the data is internal to mixxx. *hile* On 2014-08-29, at 11:28 , Tuukka Pasanen wrote: > Hello, > Just thinking should it be JSON, XML or Sqlite file? JSON and XML is > supported by QT but config is XML so should it be like that? > > Thanks, > Tuukka > > On 21.08.2014 18:35, Daniel Schürmann wrote: >> This might be solved after implementing >> https://bugs.launchpad.net/mixxx/+bug/1001299 >> and >> https://bugs.launchpad.net/mixxx/+bug/918233 >> >> Any takers? >> >> >> Am 20.08.2014 19:50, schrieb Musikpirat: >>> Am 20.08.2014 um 14:48 schrieb Owen Williams: persisting on the same machine or is he moving to another machine? Obviously it won't work if he's moving to different computers, but they should persist if they are on the same machine. >>> Think he wants to copy the files from one hdd onto another. A common >>> usecase would be to prepare a set on your workstation and than copy it >>> (plus some additional files) to your laptop. >>> >>> Christian >>> >>> >>> -- >>> Slashdot TV. >>> Video for Nerds. Stuff that matters. >>> http://tv.slashdot.org/ >>> ___ >>> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >>> http://mixxx.org >>> >>> >>> Mixxx-devel mailing list >>> Mixxx-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/mixxx-devel >> >> -- >> Slashdot TV. >> Video for Nerds. Stuff that matters. >> http://tv.slashdot.org/ >> ___ >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> http://mixxx.org >> >> >> Mixxx-devel mailing list >> Mixxx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel >> > > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org > > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
Re: [Mixxx-devel] attn to our German speakers...
Hello, Just thinking should it be JSON, XML or Sqlite file? JSON and XML is supported by QT but config is XML so should it be like that? Thanks, Tuukka On 21.08.2014 18:35, Daniel Schürmann wrote: > This might be solved after implementing > https://bugs.launchpad.net/mixxx/+bug/1001299 > and > https://bugs.launchpad.net/mixxx/+bug/918233 > > Any takers? > > > Am 20.08.2014 19:50, schrieb Musikpirat: >> Am 20.08.2014 um 14:48 schrieb Owen Williams: >>> persisting on the same machine or is he moving to another machine? >>> Obviously it won't work if he's moving to different computers, but they >>> should persist if they are on the same machine. >> Think he wants to copy the files from one hdd onto another. A common >> usecase would be to prepare a set on your workstation and than copy it >> (plus some additional files) to your laptop. >> >> Christian >> >> >> -- >> Slashdot TV. >> Video for Nerds. Stuff that matters. >> http://tv.slashdot.org/ >> ___ >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> http://mixxx.org >> >> >> Mixxx-devel mailing list >> Mixxx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org > > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel > -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
