Open vext01 opened 2 years ago
Perhaps I should use lowercase for directories, but mixed case for filenames?
I just tried this scheme with a handful of albums and that seems to work so far.
But why?
After investigating more deeply, it seems that OpenBSD and Linux display the case of short filenames differently with the default mount options. This seems to be why Hiby OS can't find files in the playlist, if you generated the playlist on an OpenBSD system.
What I don't understand though, is how Hiby have managed to make a FAT32 filesystem case sensitive. The case of the files in the playlist shouldn't matter if the filesystem of the SD card is FAT 32, right?
With the SD card mounted on my OpenBSD system, there is an album in the directory:
(Where
<sd-root>
is the mount point)And this directory, according to OpenBSD, contains the following files:
Through experimentation (and with the aid of this post) I've figured out that:
a:\
\
. Forward slash will not work.So, you'd have thought that to have the above files in a
m3u
playlist, you'd use a playlist like:If you try to load this playlist, then the R3 won't find the files, but if you lowercase
OGG
toogg
then it does find the files. But why?Further experimentation. If you make a playlist like:
The 2nd and 3rd entries work, but the others don't. However, the album art does load for the 2nd, 3rd, and 4th entry. This suggests that the directory prefix (where it will be searching for cover art) is valid for those, but not the filename within that directory.
I feel like this has something to do with FAT32 filenames and their interaction with Linux's filesystem driver (used by Hiby OS), but I can't figure out the pattern. This makes generating playlists on my computer difficult, as I don't know what case to use in the playlist files.
Perhaps I should use lowercase for directories, but mixed case for filenames? I don't know.