I thought the FID suffixes and the file types had a 1:1 correspondence in the code..

No, it's like this:

The *0 file stores the data for the particular item. In the case of tunes, it's the MP3 data. In the case of playlists, it's a list of the FIDs contained within that playlist. The FIDs are stored as a simple sequence of unsigned 4-byte quantities (little-endian). They also store the low 4 bits (one hex digit) of the child FIDs, although these are always set to zero.

The *1 file stores the tags for an item. This is the stuff that you edit in emplode. It's a simple tag=value format. One of the important tags is 'type'. Currently, we use 'playlist' and 'tune'.

The root playlist is stored in FID 0x100, i.e. /driveN/fids/100. Its tags are in /driveN/fids/101.

If you change the type to something other than 'tune' or 'playlist', the player should ignore it.

So, to summarise: Put your data in the *0 file, and then describe it in the *1 file, making sure to set type to something other than 'tune' or 'playlist'.


Roger - not necessarily speaking for empeg