The starting point of this project was the code from https://github.com/Holzhaus/serato-tags
This software is provided as-is without active support and without providing any warranty. If you decide to use it, make sure to back up your files as I take no responsibility for any loss of data. I built & use this software for my own personal use, so I am testing it, however there might be cases that I haven't covered with my testing.
- Make sure you have Python 3.11 installed on your computer
- Export the rekordbox.xml file from Rekordbox
- Rename the
.env.distfile to.env - Edit the
.envfile and theRB_XMLdirective to the place where your Rekordbox XML file is located (for Windows make sure it's the full path)- For Windows make sure it's the full path
- For MacOS you can either use the full path or user the
~sign to replace the/Users/<your_username>from the path
- MAKE A BACKUP OF YOUR MUSIC FILES
- Analyze your files in Serato and add the beatgrid marker labeled 1 at the same position as in Rekordbox
- Run
make install - Run
make
In this case the make commands will probably not work for you, but you can just write the normal commands:
Instead of make install you can do
python3.exe -m venv venv
venv/bin/pip3.exe install -r requirements.txt
and instead of make you have venv/bin/python3.exe import.py
I don't have access to a Windows machine, at the time of the writing, so you may need to adjust the executable path or maybe remove the .exe extension when running the commands.
The application will copy the CUE and LOOPS from Rekordbox v6 to Serato v3. Probably will work with older versions of the software, but I have not tested and I never will.
To prevent doing too much, it's restricted (for now) to only 1 playlist, so you will need to create a playlist with the tracks that you want to have synced, and then you will need to select the playlist from the CLI prompt when it is asked for.
-
HOT CUE points will be overwritten if they are on the same position as in RB:
- if you have a CUE on position 1 in RB as well as in Serato, it will be overwritten in Serato
- if you have a CUE on position 1 in RB but not in Serato, it will be created in Serato
- if you have a CUE on position 1 in RB, a CUE on position 2 in Serato, you will get 2 CUE points: pos 1 from RB and pos 2 will be preserved
-
LOOPS points will be overwritten if they are on the same position as in RB:
- if the LOOP is LOCKED in Serato, it will not be overwritten (not even the name)
- it will be created if the loop does not exist in the given position
-
MEMORY cues will be copied to Serato in the empty cue point locations
- all the memory cues will be prefixed with
M:(notice the "space" after ":") and they will either have the name or a number - IF you have 5 HOT CUEs and 5 MEMORY cues, only the first 3 memory cues will be synced as you can only have 8 HOT CUEs in Serato
- they will have a default color of RED because the XML does not contain color information for them
- all the memory cues will be prefixed with
For the application to properly set the CUEs and LOOPs it's very important to first have the beatgrid setup in Serato as the app will use the beatgrid information to calculate the offsets between the RB beatgrid and the Serato beatgrid.
Actually you don't even need to set the entire beatgrid for Serato. You just need the first marker to match the one from Rekordbox, as the software will use that one to calculate the offset.
NOTE: if the HOT CUE, LOOP or MEMORY CUE has a name, it will be copied over as well
...it's useful to you and you feel that I earned it, feel free to buy me a coffee as I really enjoy them (for real...not just saying it for donations 😅).
As example file I used Perséphone - Retro Funky (SUNDANCE remix), which is licensed under the term of the Creative Commons Attribution 3.0 Unported (CC BY 3.0) license.
The software in the app directory are published under the GPL-3.0 license . Everything else is licensed as described HERE in the original repository