Hi,

I’ve run into what looks like a path‑encoding bug when exporting from MIXO to Serato on Windows.

Environment

OS: Windows 11 (user folder: C:\Users\migue...)

Serato: Serato DJ Lite (latest)

Source workflows:

Playlist originally created in DJ.Studio → imported into Rekordbox 7 → imported into MIXO → exported to Serato

Playlist created only in Rekordbox 7 → imported into MIXO → exported to Serato

In both workflows the result is the same.

Issue

MIXO plays all tracks in these playlists without any problem, so the paths inside MIXO are valid.

After exporting to Serato, many tracks appear as “missing” in Serato.

The Serato error bar shows file URLs like: file:///C:/C%3A/Users/migue/Music/DJ.Studio/Exports/pedegee%20cola/...mp3

The actual file on disk is at: C:\Users\migue\Music\DJ.Studio\Exports\pedegee cola...mp3

So the exported path looks like the drive letter C: has been encoded twice, giving C:/C%3A/... instead of a normal C:/Users/... URL. Serato can’t resolve this path and treats the file as missing.

What I’ve tried

Using “Relocate/Find File” in Serato to point to the correct file. This works for that single track, but the same problem exists for other tracks, and it doesn’t fix the underlying crate data.

Re‑exporting from Rekordbox 7 via MIXO with different playlists (including one that never touched DJ.Studio). Same problem.

MIXO continues to play all affected files fine, so it seems specific to the Serato export.

Expected behavior

MIXO should export Serato crates/paths using valid Windows file URLs, e.g.: file:///C:/Users/migue/Music/DJ.Studio/Exports/pedegee%20cola/...mp3

Actual behavior

The exported Serato data uses URLs like file:///C:/C%3A/Users/..., which Serato interprets as an invalid location and marks tracks as missing.

Impact

Large playlists exported from MIXO to Serato require manual relinking track by track, which is not practical for big libraries.

If it helps, I can send you screenshots of:

The Serato error bar showing the file:///C:/C%3A/... path

Windows Explorer showing the real C:\Users... path for the same file.

It would be great if you could check the Serato‑export logic for Windows paths (especially how the drive letter is encoded) and confirm whether this is a known issue.

Thanks a lot for your help!

Best regards,
Miguel
[text rewritten by AI from user own notes]