Missing tracks in Serato (special characters)
Solved
Some tracks don't export in Serato and all the tracks seems to have special characters in their file path like apostrophe, €™, 甲 or #.
Some tracks don't export in Serato and all the tracks seems to have special characters in their file path like apostrophe, €™, 甲 or #.
Hi Patrick,
Apostrophes should be absolutely fine. I will of course check everything is working correctly and confirm back to you.
In the meantime, which Version of MIXO are you using?
Remko
Hi Patrick,
Apostrophes should be absolutely fine. I will of course check everything is working correctly and confirm back to you.
In the meantime, which Version of MIXO are you using?
Remko
Ha! Magic ;)
Ha! Magic ;)
MIXO v1.27 is now live with a fix that allows single quotes in track filePaths when exporting to Serato!
https://www.mixo.dj/versions
MIXO v1.27 is now live with a fix that allows single quotes in track filePaths when exporting to Serato!
https://www.mixo.dj/versions
Thanks a lot! My cuepoints are now there and all the tracks with quotes are now recognized! Great job!
Other than two tracks with slavic characters, I have only one missing track in Serato with a backslash in the path : Axwel /\ Ingrosso
In Serato the folder is like this : Axwell E Ingrosso
Thanks a lot! My cuepoints are now there and all the tracks with quotes are now recognized! Great job!
Other than two tracks with slavic characters, I have only one missing track in Serato with a backslash in the path : Axwel /\ Ingrosso
In Serato the folder is like this : Axwell E Ingrosso
Ok thanks, I'll take a look and see what can be done with that.
Ok thanks, I'll take a look and see what can be done with that.
Ok I think I've fixed the issue with backslashes for the next release! It affects only Mac and Linux, because Windows file names can't contain forward or back slashes.
Support for the Cyrillic alphabet when exporting to Serato might be a little longer though, due to low demand.
Anyway, thanks again for your help. Much appreciated!
Remko
Ok I think I've fixed the issue with backslashes for the next release! It affects only Mac and Linux, because Windows file names can't contain forward or back slashes.
Support for the Cyrillic alphabet when exporting to Serato might be a little longer though, due to low demand.
Anyway, thanks again for your help. Much appreciated!
Remko
Interesting. That shouldn't be happening so I'll look into that.
Great idea about the existence checker - I'll get that added as a context menu option in the track list.
Remko
Interesting. That shouldn't be happening so I'll look into that.
Great idea about the existence checker - I'll get that added as a context menu option in the track list.
Remko
Hey Patrick,
I've added a new feature to quickly highlight missing tracks from the track list context menu, whereby missing tracks become greyed-out and show 'YES' in the 'Missing' column.
I've also fixed the HTML code for apostrophes when importing XML and NML files. It's strange because normally iTunes produces the name type "& apos;" but in your case it was the code type "& #39;"!
And finally I've added support for the Latin upturned V (lower and upper case) when exporting to Serato (the Greek version is in fact supported).
The changes will be in the next release!
Remko
Hey Patrick,
I've added a new feature to quickly highlight missing tracks from the track list context menu, whereby missing tracks become greyed-out and show 'YES' in the 'Missing' column.
I've also fixed the HTML code for apostrophes when importing XML and NML files. It's strange because normally iTunes produces the name type "& apos;" but in your case it was the code type "& #39;"!
And finally I've added support for the Latin upturned V (lower and upper case) when exporting to Serato (the Greek version is in fact supported).
The changes will be in the next release!
Remko
Do you have any recommendations or best practices for DJs to avoid or mitigate problems caused by special characters in track file paths when organizing their music libraries? Tel U
Do you have any recommendations or best practices for DJs to avoid or mitigate problems caused by special characters in track file paths when organizing their music libraries? Tel U
Replies have been locked on this page!