Rockbox

  • Status Closed
  • Percent Complete
    100%
  • Task Type Bugs
  • Category Operating System/Drivers
  • Assigned To No-one
  • Operating System All players
  • Severity Low
  • Priority Very Low
  • Reported Version Daily build (which?)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by rnjacobs - 2007-11-17
Last edited by jdgordon - 2008-06-24

FS#8174 - path length of >= 256 bytes is problematic?

(This is on a Nano 1st Gen)

I have a specific filename that rockbox cannot open. The same file, in any other directory, or with any other name, is openable; any arbitrary file with this name cannot be played or “Properties”ed.

The path that fails is
“Brahms/CUdL+MITCC-Ein_Deutches_Requiem/(Chœur_Universitaire_de_Lausanne,_MIT_Concert_Choir,_Sinfonietta_de_Lausanne,_Jean-Christophe_Aubert_directing-Johannes_Brahms’s_Ein_Deutsches_Requiem)-2-_Denn_alles_Fleisch,_es_ist_wie_Gras_[2006_May_31_&_June_1].ogg”

Rockbox can display the file in the browser (the œ is displayed as the “no glyph” character, whatever).

I discovered this is not a unicode thing (All the other files in the same dir have the same œ; plus the same non-functioning file works if e.g. copied to the root directory)

This seems to be a maximum length thing. Neither this file nor the one that is 5 characters longer (256 and 261 unicode entities long) can be played.

This may be related to the maximum of 255 ucs2 entities for a filename (not path!) on VFAT.

(I probably should use shorter filenames, but…)

Thank you very much for an awesome piece of software!

Closed by  jdgordon
2008-06-24 10:45
Reason for closing:  Not a Bug
Additional comments about closing:   Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407

use shorter filenames…

Project Manager

According to the FAT32 specification, the maximum length of a complete path (including the filename) is 255 characters. In your case, the path including the filename is 256 characters.

Could we get a little warning regarding the problem when the user tries to select a path name that’s too long? It took a while to figure this out, when the only symptoms were “I can’t play it”.

(Looking up the standard, microsoft seems to say “260 bytes, including the [driveletter]:\[nul]”, which is a max of 256, not 255, but that’s just being pedantic)

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing