Peke wrote: ↑Sat Jul 09, 2022 1:50 pm
Custom fields are Alpha numerical sorted fields (String based not Number based).
Custom fields are not alpha sorted.
There is some logic in there to sort them numerically.
See here.
I know this because I asked for it to be added during the alpha phase of MM5.
PoopertonThePious wrote: ↑Sun Jul 10, 2022 5:45 pm
Thanks Peke! Is there any way to designate a custom field as number based instead of string based? I can definitely try zero padding the numbers, although I'm not exactly looking forward to doing it for 700+ files
Hi Pious
Are your Custom tags sorted "correctly" in a List View, like in my picture above?
Maybe the special numeric logic hasn't been implemented inside a playlist. This is something that they could look at .. Ludek .. ?
Pious, do you use the BPM tag?
This is a proper numeric tag, and it is a tag the MM5 does not update.
You could transfer your number into the BPM column.
Does the BPM column sort "correctly" in your Playlists?
If that achieves what you want, you could transfer your number into the BPM tag with a single SQL query.
If you don't know SQL I could send it to you ... but first you should test if your number in the BPM tag is going to achieve what you want for your playlists
BUT THE REAL FIX is if they give us some proper numeric Custom tags.
This is needed so that we can use the arithmetic operators with custom tags ... ie Custom01
<= 10
That kind of thing is impossible at the moment; a limitation which sux.
This request is being "monitored", but isn't receiving any love.