Some info that may be useful...
You'll note that for versions of the interpreter that don't support speech (SQ5), the games tend to come with resource.aud, which is where the digital audio resources are placed (which share the same "number namespace" as the midi sounds).
As best I can tell (and this is what SCI Companion assumes), for interpreters that do support speech, the audio were moved to resource.sfx, and resource.aud becomes the place to put speech (aud36) resources.
In addition to the package files mentioned above (which contain the actual audio data), there are the map resources that tell where in the package files the audio data starts for a particular resource number.
For audio resources, the corresponding map resource is 65535.map (occasionally 0.map in some games). For aud36 resources, the map resource is [nnnnn].map, where nnnnn corresponds to the speech resources for a particular room number. So there are lots of map resources for speech.
There are three possible formats for the 65535.map file (shown as 5 bytes, 6 bytes or 8 bytes in SCI Companion, as that's how large each entry is). For the [nnnnn].map files for the aud36 resources, there are 2 possible formats (shown as Sync map late, or Sync map early).
Sometimes 65535.map is its own file, sometimes its embedded in resource.map/resource.000 like a normal resources (I'm not sure if matters to the interpreter). The [nnnnn].map resources are either found in message.map (most commonly), or sometimes resource.map with the regular resources, or sometimes altres.map.
Now, if you start trying to manipulate the resources in SCI Companion while moving files around and stuff, and the way you have the files set up doesn't match a normal game... s*** can get f***ed up. For instance, while I was initially playing around with this, I hadn't changed resource.aud to resource.sfx, so resource.aud was getting filled with both audio and aud36 resources.
It looks like there bug in SCI Companion in that it doesn't display the correct "audio map format" if 65535.map is not a lone file (i.e. if it's embedded in resource.map/resource.000). However, I will tell you that, from what I can tell, 65535.map is:
- LSL6: 6 bytes
- SQ5: 5 bytes
- KQ6: 6 bytes
- KQ6 CD: 5 bytes
So if digital audio sfx stop working when switching the terp from SQ5 to LSL6, that could be the reason (not sure if later terps can handle various audio map formats or not). If that's indeed the case, then to move the digital audio over, you'd need to export all the audio resources and then add them back in. Of course, when adding them back in, you'd need to start with an audio map that is compatible with the newer interpreter, otherwise Companion will still write the old format.
