Hi, I'm using MIXO to update VirtualDJ lib from Rekordbox. I did several complete backups from RekordBox to VirtualDJ - and I loose de prepared stems - thats a shame.
I did partial update - using only changed playlists and I noticed something even worse: Mixo is mixing '/' and '' of windows. On VirtualDJ side, the database is not aware of '' and writes duplicates when updating index. At the end I had plenty of duplicates that make the library confused and may trigger twice the stem analysis. I took half a day to write a script in Python to resolve all the mess that makes Mixo - I did it but it was very very touchy - with a lots of backup - restroe. Now I think I have a tool to resolve to possible problems but still a little bit anxious using Mixo. If you want to have a look to my script you can ask I can send it to your developers - to get an eye on it

cannot update my entry - so sorry for mistakes...

mixo is mixing '/' and '\' - Virtual DJ seems using only '/'

Hi there,

Thanks for reporting this issue. I think MIXO is expecting backslash filepath separators for windows but n your case your system has forward slash separators.

This is a fairly new issue since historically windows always uses backslashes but now it’s started to adopt forward slash in many cases.

I will review the logic we have for other exports and make sure that VDJ uses the same logic to correctly identify the separator type.

Thanks again for letting us know! I’ll let you know as soon as this is fixed.

This issue is a little more complicated than I thought. It's not what I wrote in my previous message.

Having tested further, my Virtual DJ database on Windows contains filePaths with backslash '\' separators. There are no forward slash separators for my tracks.

This means that the data you imported from Rekordbox contained tracks with backslash separators - you should also see this in MIXO under the FilePath column (you can add this column by right-clicking the track list column headers). It must also mean that the existing tracks in Virtual DJ were for some known reason added with forward slash separators rather than backslash. This would cause duplication.

In my tests, dragging and dropping tracks into VDJ always results in backslash separated paths on Windows, so I'm not sure how to replicate this.

How were your tracks were added to VDJ? If you can shed any light into the situation that would be great.

Or it could be the other way around - your Rekordbox import contained forward slash separators and VDJ has backslash separators. That would make more sense based on what I'm seeing.

Hi I’m not sure about who uses backslashes , but the fact is duplicates in VDJ after different imports
Problem with duplicates is that VDJ has to analyse twice / preparing stems is very time consuming .
I imported via mixo - different Rekordbox 7+ versions , different Mixo versions (2 years ago for the oldest) , different ways of import (db , diff , or collection.xml)

rekordbox collection has a long history from v5 through v7 / latest)
I Never changed manually collection.xml nor database,xml until I had this issue with mixo

Now I wrote a python script that fixed the duplicates in vdj database.xml - was very touchy many iterations - but now I’m ok with the result.

Ok nice work for fixing the paths! I'll look into ways to handle this somehow but so far I don't know the answer because VDJ should be using backslash separators on Windows!