Getting files in the intended order in folders
Beantwortet
I posted the original comment here, and it is clear this is still an issue. Workarounds should not be necessary, because the intended logic of sorting files just by quality escapes me. This is one of those "features" people sitting around a table somewhere thought would be helpful, but actually -- few people think this way about files in folders.
The issue really is why file type or quality trumps internal track numbers. Makes no sense. Over time, I have solved this **almost** always by being thorough about editing the tags. Generally, I 1) order the track numbers in integers only, like "3", no "3/12". 2) Get rid of the disc number entirely or make sure it is "1/1". 3) Delete years. 4) Delete double listings of artists or album artists. 5) Sometimes, when a mixed playlist, use :"Various Artists" for album artist, or when not, make sure the album artist is listed the same way throughout.
Once in awhile, rarely, I just convert the mp3 to a flac, after giving up using the other methods.
Hello, Bluesound, you have a good program here, pay attention to this strange anomaly.
-
Offizieller Kommentar
Hi Blair
Please select Help, Send Support Request in the App so we can get some more details here and arrange for sample content to see where the issue is occurring.
-
Yes, I get this too.
Only thing that works for me is using Audacity to convert MP3 files to FLAC.
PITA
0 -
I had also reported this problem a long time ago. It has not been taken into consideration at all
0 -
I find it absurd that if I have a folder with different file types I cannot have the order I want. The first criterion is the extension of the file and only then the track number in the id tag is taken into account.
0 -
I would like to point out this is not an error or a bug, but it is the behavior of the bluos system.
we don't need help in order to solve a problem. Bluos' sorting priorities would simply have to be changed
0 -
An example
The numbers on the left are the track number id that I edited in the tags.
I would expect the player to sort the tracks in that order
0 -
Francesco,
This is a good example of the problem. I notice that sometimes -- randomly -- it DOES sort by track number in the tags, even if differing formats, and sometimes it doesn't. I have tried to figure out the difference, but all I can say is that ALL fields have to be similarly formatted across all songs in that folder. Silly details like listing disc number as "1" vs. "1/1" seem to make a difference. If a track number says "8/12", meaning 8 of 12, that also can screw it up. I edit it all down to the simplest form....and it still doesn't work sometimes.
Notice in your example something I saw as well. In the first six tracks, one is mixed (Credence) that is in fact a different format than the "CD" level formats of the other five. Total mystery. But maybe there is a clue in that one file vs. the last four, some difference in their tags maybe?
1 -
Hi Blair
You beat me to the punch... your track order and disc order tags MUST be in the same format which can affect the problem. Keep in mind if your CD files are WAV and not FLAC - doubly so as there is no standard for WAV meta (one of many reasons why FLAC was invented).
Francesco Look at Kid3 as a metatag editor to fix WAV files (and other brute force tag fixes). If you are still having issues, please select Help, Send Support Request in the App so we may arrange for a sample of the content to show you where the tags are incorrect...
That being said, when ripping a CD, one should rip it all at the same resolution and format.1 -
The response from Tony corresponds to my experience, but one thing: those non-CD files are often just mp3 files bought online, and there is no choice. Since so many vendors sell FLAC formatted files, it does help to rip CD's (What are those anyway?) to FLAC....:)
1 -
Credence is an acc file.
As highlighted in another thread, the problem is that some files (aiff, m4a) get an "hidden" "leading zero" before the track number id by default while others not (mp3). So the 1 idtag "track number" becomes 01, 2 become 02 etc. For mp3s it doesn't happen; 1 remains 1. Bluos cannot handle these leading zeros properly. So tracks 02, 04 (for example) are listed before 1 and 3. I have just tested a workaround and it is working. You must insert the tag "disc number". For example 1 on all songs. In this way, the order inexplicably works regardless of the "leading zeros".
0 -
I raised this as a support issue a couple of years ago, on an album with mixed .wav and .mp3 files. I documented the issue extensively. https://support1.bluesound.com/hc/en-us/requests/170244
I use Kid3 and MP3tag extensively, and the files were all very clean - no unneeded tags; consistent numbering, etc.
Got lots of platitudes, but as you can tell, no action. I finally used Audacity (a bit of a learning curve, but VERY highly recommended) to convert the .mp3 files to .flac. That worked, but what a kludge!
We are always developing the app, continuing to expand on the features and deliver the best possible listening experience to those who are living with us in our HiFi Family.
Please understand that no version of the app is the final version and we are always working to improve the experience based on customer feedback. The app itself is always being worked on and updated.
Rest assured that we will be taking this purposed request and will be forwarding this request to our Quality Assurance Team as well as the BluOS Development Lab for their consideration for a future update.
In the meantime, if there is anything we can help you with please let us know, we are here to help!
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
11 Kommentare