Did some testing with a buddy and here is what I found out. We are both running the latest shield and pi B. The test was done on a DE Star Wars using the default sound package and the updated config file.
I also did a continuity check on my ribbon connectors and all the chip legs and they are good.
I was going to make an adapter to split the Y cable so you could hook the Raspin up and also listen to the machine at the same time like I did with Apollo 13 and then my buddy came up with a simple solution. We took a WPC cable that had a connector in the middle and hooked each end up to the original boards as you would a normal cable. Then we hooked the Raspin up using the middle connector and now you can run both the machine and the Raspin through a remote speaker and compare sounds in real time.
1. WPC seems to be about 90% correct on both.
2. When running the latest Version 1.17, the attract music never stops and plays over other sounds. With 114, it plays continuously when you turn on the machine but it stops when you start a game. In 117 it doesn't stop so we reverted back to 1.14 to do the rest of the testing. Its not supposed to play continuously.
3. DE is probably 15-20% correct. When you start a game, the shooter lane sounds are all correct so you think to yourself that things are good, but as soon as you launch the ball, most sounds are not correct. Listening to both at the same time helps identify even the smallest sound effects like a laser sound being wrong. The thing is that if you do not know what you are listening for, you may think it sounds pretty good but in reality its not right. Listening to both will make that clear.
4. Now here is the interesting thing. We were using the same config file because I emailed him mine. About 10-20% of our sounds were different. I am not sure how that can happen but it was consistent that each of our setups played the sounds consistently. We even looked at our sound packages and compared some of the numbers of the sounds that were different and everything checked out. Now he did have to replace a chip on his board but for that to just affect a few sounds seems odd to me but maybe it can happen.
5. It still feels to me like this is a config problem in mapping.
The bad news is that I will be spending most of the next 5-6 weeks out of town and will not be able to do any extensive testing. I will be home a day or two here and there so if a new version of the code comes out I will be able to run a quick test and report back but that is about it. I will be following the thread and will provide input if I can help.
Here are a couple of things that I think would be helpful as we go forward.
1. Somebody please test a DE game with the latest shield and original sound package, preferably with the WPC ribbon cable so you can listen to both sounds at once and take the glass off the machine and test as much as you can so we can see if ALL of the sounds are mapped correctly. Like I said, its easy for a game to appear to work correctly but it may not be. If its SW then that is a bonus since me and my buddy both have one we can compare against.
2. Steve, can you test your LW3 with a ribbon cable so you can listen to the entire game simultaneously. Like I said with SW, the first part is correct so I would like to see if any of your sounds are wrong later that may not be obvious. It would also be great if you could try the latest shield just to make sure something didn't go wrong during production or something.