Heya,
so after dozens of Auto-Playlists having gotten messed up column display and sorting (
https://getmusicbee.com/forum/index.php?topic=23561.0 ), this now also seems to affect the exported static m3u playlists for me as well.
Can anyone shed some light (might be only Steven would know) and explain what the "<SortBy Field" in an .xautopf of Musicbee does relate to exactly ?
Are these <SortBy Field codes documented somewhere ?
Are they relative to the columns of the playlist or absolute/global field values ?
I could not find them on the forum and neither in the twiki,
As to the issue - I have now gone through all Auto-Playlists and loaded my custom default column view for each where it wasn't on the same column layout (10-20 or so of 117 Files), and sorted them 'by Rating value' as well for all where this wasn't the case as well. So all should be good now as this was the state they were in before (the 3.2 update I believe) and which I need them to be in for static playlist export (for this trick to work:
https://getmusicbee.com/forum/index.php?topic=20764.msg122920to write out a iTunes xml where all Auto-Playlists have a 'rating sorted' static playlist equivalent. And all non-auto-playlist based ones remain in their 'natural sorting' way...).
Now, even with all Auto-Playlists fixed/aligned by hand, my resulting static playlists of the Auto-Playlists that I need to generate the iTunes xml from, have now taken on all sorts of sorting which I am trying to a) understand, and b) fix...
So, I have switched all auto-Playlists to rating based sorting, and most state:
<SortBy Field="75" Order="Descending" />
Most of the culprits that produce incorrectly sorted static playlists do have other Sortby Field values, such as:
<SortBy Field="2" Order="Ascending" />
<SortBy Field="47" Order="Ascending" />
Now to the real oddity with this - I've double checked the ones in MB that do NOT have:
<SortBy Field="75" Order="Descending" />
in their xautopf file, and even they are sorted 'By Rating' inside of MB as they should (and they even have the same column fields & order - I thought IF they are column relative to the playlists shown columns... this could explain it... but no, based on the breadcrumbs)... so this does not quite compute.
Any explanation here would be much appreciated.
Also - in case anyone else sees something similar, this feels somewhat buggy to me, but have yet no idea if/how to reproduce these.
Churs.
c.