Missing tracks in Serato (special characters)

Patrick started this chat 3 years ago

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

Replies (22)

R
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

1


P

In reply to Remko

Hi Patrick, Apostrophes should be absolutely fine. I will of course check everything is working cor...
1.25.0

1


P

In reply to Remko

Hi Patrick, Apostrophes should be absolutely fine. I will of course check everything is working cor...
I just installed 1.26.0 and it's working now! I never see a bug been fixed so fast 😅

1


R
Ha! Magic ;)

1


P

In reply to Remko

Ha! Magic ;)
Sorry, I speak too fast 😅 Some have been fixed, but others don't.

I have some tracks that don't export and have slavic characters like глав.

Some with apostrophe, but of another type. This one work -> ' . This one don't -> ’

1


P
Some tracks don't export in Serato and all the tracks seems to have special characters in their file path like apostrophe, €™, 甲 or #.
  • Capture d’écran 2023-08-29 151218.pngScan ok
  • Capture d’écran 2023-08-29 152212_2.pngScan ok

1


R

In reply to Remko

Ha! Magic ;)
Strange, I thought that was working. I've added a conversion for curly apostrophes aka right single quotation marks and also left single quotation marks.



The fix will be in the next release.

Thanks for helping me find this!

Remko

1


R
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

2


P
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

1


R
Ok thanks, I'll take a look and see what can be done with that.

1


R
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

1


P

In reply to Remko

Ok I think I've fixed the issue with backslashes for the next release! It affects only Mac and Linux...
No problem for Cyrillic alphabet, I will change the album folder manually to eleminate this characters.

For Axwell Ingrosso, I was partially wrong. You are right, we can't use slash or backslash as folder name or filename in Windows. So I was curious to check out my folder on my windows PC and finally I find out this is a turned "V" : Ʌ and not a slash/backslash. I didnt even know that character exist 😅 But I have two folders that have exaclty the same name with turned V and only one work in Mixo. I just find why.

There's two types of turned V, latin and greek. They look exactly the same.
More info here : https://qaz.wtf/u/show.cgi?show=ɅΛ&type=string

Turned V in latin work in Mixo but not the greek one.

I will change all my Axwell Ingrosso track with latin turned V in artist name to fix this.

1


R

In reply to Remko

Ok I think I've fixed the issue with backslashes for the next release! It affects only Mac and Linux...
We do actually support most of the Greek alphabet so I'll need to check that one, thanks!

1


P

In reply to Remko

Ok I think I've fixed the issue with backslashes for the next release! It affects only Mac and Linux...
So i did some changes to delete all special characters in my library and re-arrange my folders/filenames automatically with Musicbee.

I reimport all my library in Mixo after in iTunes format to apply all the changes.

There is a little mistake with the new version (1.127) : All the quotes are now displayed like this ' Not just on playlist name, but everywhere (title name, album name ,etc.) after my re-import. I post a screen capture of my import screen.

Outside that, with this process, a lot of files have been moved so I had some difficulties to find old tracks in Mixo to delete them (local and cloud). Maybe a quick "library integrity scan" or something like that could help to show and delete "not found" files easily.
  • Capture d’écran 2023-08-31 142615.pngScan ok

1


P

In reply to Remko

Ok I think I've fixed the issue with backslashes for the next release! It affects only Mac and Linux...
Sorry, the text editor converted the quote automaticaly in my comment.

1


R
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

1


R
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

1


P

In reply to Remko

Hey Patrick, I've added a new feature to quickly highlight missing tracks from the track list conte...
Wow! Thank you for your incredible support!

For the HTML code, I'ts because I use Musicbee and not iTunes directly. Musicbee have an option to export his library in iTunes XML format and the encoding is probably different.

A few years ago I searched for an alternative for iTunes on Windows when Apple announced they will stop the support on it. So I choose Musicbee. It's a very powerful music player, very lightweight and it also have a backup feature. My old process to sync my music was to share the music folder on my DJ laptop as a network folder. On my main PC I use Musicbee to backup my main library on my laptop. Musicbee compare the two libraries and only export de files and playlists that have been changed. After that, I execute Musicbee on my laptop and save the Itunes XML to use it in Serato. It's was a very complicated process, but it always work well.

With Mixo the process is a LOT easier ;) But I still use Musicbee to manage my main library. Moving files, playlist creation and reorder is a lot faster. For now, for example, when I move a playlist or a track in Mixo, it freeze for a moment and the app feel very laggy. I think this is the automatic sync that do that. Maybe a manual push feature could fix that. Like a Git repo :)

1


R

In reply to Remko

Hey Patrick, I've added a new feature to quickly highlight missing tracks from the track list conte...
Ah yes that's probably because MIXO needs to also prepare and push changes to the sync queue and then sync the changes to the cloud. This can cause a slight lag.

It may be slightly faster in the next release.

Anyway, thanks for the info!



Remko

1


P

In reply to Remko

Hey Patrick, I've added a new feature to quickly highlight missing tracks from the track list conte...
You're welcome!

1


R

In reply to Remko

Hey Patrick, I've added a new feature to quickly highlight missing tracks from the track list conte...
Ok v1.28 is live! :)

1


T
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

1