PinSound not working in 10.8x64

[kapter316]

Hello,
I am hoping you can assist. I saw another post where it looks like the issue was resolved, but I'm still experiencing it. I downloaded the latest: sc-3.6-720-e4df859-win-x86.zip and sc-3.6-720-e4df859-win-x64.zip. When running x64 test, PinSound works with no problems; you cannot get it to load with VPX10.8.8 32bits launcher. However, when I run x86 through a test or VPX10.8.8 64bits launcher, I always get the following error: "unsupported pinball sound system." I have tried to run as admin and not as admin for all the programs above, and I still have the same issue. Is there a version of pinmame that runs PinSound in VPX10.8 64bits launcher? If so can you direct me to that version, or is this a bug?
One last piece of information, the 10.7 32bits launcher will load and does play PinSound.
I appreciate everything you do for us.

Thank you,
Brian

[5cutters]

Not sure if this is the same issue as noted here -
" I'm all 64-bit with my setup and all Bally/Williams pins work perfectly with altsound=2. However, if I attempt the same process with Data East / Sega / Stern games then I get the "unsupported pinball sound system" error in PinSound Studio."

Some Pinsound mixes can work with x64, but some don't?

[kapter316]

Not sure if this is the same issue as noted here - " I'm all 64-bit with my setup and all Bally/Williams pins work perfectly with altsound=2. However, if I attempt the same process with Data East / Sega / Stern games then I get the "unsupported pinball sound system" error in PinSound Studio."

Some Pinsound mixes can work with x64, but some don't?

Thank you for the comment. I retested, and you are correct; Pinsound now only works with Bally/Williams tables in 64-bit and works on almost all the others in 32-bit. I'm still hoping this can be corrected as all new tables and a lot of updated tables are being converted to 64bit, which means Pinsound cannot be used on those tables going forward that are not Bally/Williams.

[timdeporte]

Yes, this is not a problem caused by vpx but caused by vpinmame. I hope a fix will be available in the near future.