That makes sense. I have another unrelated suggestion for further improvement of the manual. It is the part about the Rekordbox xml.
What i really like about the manual, is how it describes how the xml is uncoupeld from the actual internal Rekordbox database. What could be improved, is describing how to utilize the xml in relation to Rekord Buddy. The part that was missing for me, is to explain how the underlying system is working. By looking at edit-timestamps of the different xml’s while performing actions in Rekord Buddy, i was able to backtrace the mechanism of action.
- Make an one-time export of your Rekordbox database into a xml file.
- Import this one-time export xml file into Rekord Buddy
- Attention: any changes made by the end-user in Rekord Buddy for the Rekordbox collection, are written back into another xml file. In other words: Rekord Buddy will from now onwards completely ignore the imported xml-file as described in step 1 and 2. Instead, Rekord Buddy is assuming that a second xml file is in the default folder of Rekordbox. Therefore, alwyas check that you Rekordbox settings are appointing to this default location. In this way, Rekordbox already has created such an “import” xml for the end-user.
- Reimporting changes back into Rekordbox: Rekordbox is using the xml file in the default folder of Rekordbox, not the xml file used to make the one-time export in step 1.
The fact that Rekord Buddy is using two different xml files (one to import, one to export) made it very confusing for me to understand. It would help a lot if the default behaviour could be explained graphicaly in the manual.
Instead of using this confusing setup, i did it in another way. I am using only 1 xml file.
- Make an export of your Rekordbox database into a xml file on any location you like.
- Import this export xml file into Rekord Buddy, but in the alternative way: by drag-dropping it all the way in the bottom of the list (rekordbox user location). In this way, you are forcing Rekord Buddy to write any changes done by the end-user into the very same xml file
- Within the Rekordbox application, change the settings: make sure that you are reading from the same xml file as the one you created in step 1 during the first export.
The above alternative method is much more intuitive for me. For this alternative method, it would help a lot as well to explain it graphicaly in the manual.
I think by describing these mechanisms in a way that people really understand the mechanisms behind it, you could reduce the number of questions/tickets on the forums. I’m curious what your opinion on this topic is.