Your browser does not support javascript (or it is disabled.) Please use a browser with javascript or enable it.We need javascript to function properly otherwise some things won't work.
Another example with 3 digitshttps://imgur.com/F3vwqdV
Quote from: mrbenn on April 20, 2021, 10:00:38 PMAnother example with 3 digitshttps://imgur.com/F3vwqdVThat seems to go well? First vol.1, then 10, then 100.What's wrong there?
Is there a way of doing this via virtual tags? eg: If I have a set of compilations with volume numbers, it currently sorts 1, 10, 11, 2, 3, etcIf I sort by path it gets it in the natural order.
It's not a bug.https://getmusicbee.com/forum/index.php?topic=19870.0
It is called smart sorting.Musicbee can do it but a bit inconsequentialThe listbox on the left does the alpha numerical thing (BWV.1080, BWV.12, etc)The listbox on the right does it the right way (BWV.12, BWV.147, etc) it sort by number.
You are right, it's not a bug, but maybe a feature request for an oversight. I think it would be a very useful improvement as many of us have compilations with volume numbers in the album title. Neutron, a music player I use on Android is able to correctly sort numbers in album names. So numbers can be sorted correctly by the value of the whole number, not just the first digit from a tag's text field.
No.Simply because I didn't configure anything.Some boxes do sort "smart", others don't
Are you opposed to replacing single digit numbers in your tags with padded numbers?The other available options if not would be sorting with a Virtual Tag or sorting using <Path> as an option.
The Path option works for me, as I've said. It was just an observation that I thought worth mentioning here. Quite honestly I was quite surprised to have noticed it, seems like something too significant to have slipped through the cracks unchanged for so long.