URBI Forum

The function speaker.play("beep.wav" works, but:
(if, of course, the "b eep.wav" file was copied at the root of the memory stick, as a compatible wav file.
I didn't see anywhere in the doc' that these files weren't allowed to have any space in the name. Perhaps it's something to add somewhere, it would prevent people from spending a lot of time trying to find where the error comes from (as trying to convert their wav file in another bitrate, ...).
Found on URBI for AIBO ERS-7, may be present for other robots.

It's the underlying FAT32 file system on the memorystick that limitates you. URBI merely uses the Sony Aperios API to access files.

Sorry we didn't mention that in the doc, but there are thousands of implicit knowledge like this that we haven't yet integrated.

JCB

The underlying system is FAT (probably 12 or 16), not FAT32.
& I am perfectly able to put a file with a name like "a b.c" with my computer, so the file system allows it.
It's only the API that is to blame, not the file system.
implicit knowledge I don't see any implicit knowledge in this. Is it so obvious that files can't contain spaces in their name? Is it so common on all operating systems?

The problem is the relationship between hardware and software. The hardware-- in this case, the AIBO programming stick-- uses an FAT16 structure. FAT16 is compatible with all operating systems except the Apple System # series and MS-DOS, so it's pretty much safe to call it platform-independent. However, it's up to the operating system and/or its drivers to determine how compatible it is with FAT16.
Long filenames (ones that are more than 8 characters long with up to 3 characters as an extension) are stored in a second file structure which is normally used for backup purposes. Some APIs/OSes aren't aware of the second table and use only the first, which has the 8.3 filenames only. Aperios, the AIBO's native OS, uses the 8.3 table only, so it won't recognize files unless you address them by their 8.3 name. However, it should be noted that FAT16 does allow spaces and periods in the 8.3 format. However, this causes issues with APIs and programs that assume you don't use spaces. It appears that Aperios is one of those operating systems that balks at spaces, so you have to limit yourself to strict 8.3 rules. Alternatively, you could make a long filename in Windows or Linux, then access it using the short 8.3 version that it created (usually <first 6 letters minus spaces>~1.<first 3 chars in extension>). This should also fix the problem.
In other words, you can use filenames as long as you want when saving them onto the memory card from a computer. However, when using URBI or anything that connects to the AIBO, you must refer to these files using their short 8.3 versions. If you have a space in the 8.3 version, then you must remove it prior to using it in the AIBO. There's no way around it without hacking into the AIBO's operating system.

HI MNGoldenEagle,

Thanks for this precise explanation,
Cheers,
JC

PS: however, URBI could easily issue a warning when you use filename not compatible with the Aperios API. We will do that in future versions.