Welcome to the Rockbox Technical Forums!
is the path you showed the complete path on the player?
FAT has a limitation of 255 characters for the filename including the complete path. Linux can create files that violate this limitation so maybe this is your cause?
If the files on the source computer use a funny encoding (like storing UTF-8 chars in the FAT long name), the strange chars can get corrupted in Rockbox.
If you play the 3rd track, does it play properly and is it labelled properly?
Linux isn't too strict following the FAT specs, but from the file names you posted I can't see any characters that would be invalid in UCS-2. Maybe you can run chkdsk /f on a windows box and / or check the filenames on windows?
But it seems like there's something else going on: These files weren't playing at all, so I renamed the album folder they were in (in hopes of fixing the combining problem). Now the files will play, but the albums are still combined (so it seems like that's a limit of the database itself).
Ah, so you're using the database for playing the files? Do they work correctly if you play them from the file browser?
Quote from: bluebrother on February 15, 2008, 03:36:25 AMLinux isn't too strict following the FAT specs, but from the file names you posted I can't see any characters that would be invalid in UCS-2. Maybe you can run chkdsk /f on a windows box and / or check the filenames on windows?Yeah, these filenames were posted from Windows (I was at work). They seem OK.
I just renamed these files to get rid of the ä character and it still skips tracks 3 and 4.
Did you follow through on my suggestions at all? Â Try playing the third and last tracks from other folders and see if you notice any similar behavior.
I replied above a few days ago: http://forums.rockbox.org/index.php?topic=15457.msg115288#msg115288Other folders are fine, it's just with this folder that I notice this problem.
The only thing I can think of suggesting at this point is to examine the ID3 tags and make sure they're not excessively long (I forgot what the limit is, probably 255 characters) or corrupted or... who knows.
Page created in 0.09 seconds with 15 queries.