Quoted from Ashram56:robotworkshop
One suggestion I would have to determine whether TiltAudio interprets things differently with regards to altsound format parsing is simply to run VPX with the same table, with PinMame sound mode set to 1 (if I recall correctly, might be set to 2).
If it's identical you can then proceed to look at Pinmame source code
Maybe I'm missing something but does VPX and PinMame emulate the Tilt Audio board? If so I can see where that can provide some insight.
Even if it does that still only would cover how VPX and PinMame work with the soundsets. The actual implementation could vary and be slightly different in the Tilit Audio firmware.
I deal with this kind of issue all the time. Hitting the same API's and retrieving the same data sets yet iOS and Android developers have their own thoughts on how to parse and process that payload. Everyone thinks they are doing it the same yet there are occasional slight differences to track down and resolve. Too many times have I run into projects and there ends us being a difference in what everything thinks it is doing vs what it is actually doing. Whether is is a mobile app parsing the data or an emulator or firmware it comes down to ensuring everyone handles the same data the same way.
What I am trying to find out is explicitly how the Tilt Audio firmware implements and parse the soundset data from an altsound csv file. Unless I am totally off base it can only come from the Tilt Audio code to verify how it is doing it.