Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: knightrdrx on November 12, 2014, 09:41:20 pm
-
Dont 'know if this is the place to post this...
I haven't checked all my games but I know already Tempest 's sound is corrupt on mame .155 vs. mame .120 when it was working fine.
Anyone else experience this?
This one glitch is a good reason for me not to upgrade.
well..i do see some improvements...trivia whiz color...pole position shows gear shift....still....what happened to Tempest??? Do I just have a bad rom?
-
MAME will inform you if your ROM has an incorrect CRC if you didn't apply any unofficial patches.
I just fired up 0.155 and ran *mame64 tempest* and everything is sounding very good here.
Seems to be very close to a video of an actual Arcade machine --> http://youtu.be/AMto2HJJSSA?t=55s (http://youtu.be/AMto2HJJSSA?t=55s)
-
Maybe I don't have a good version of Mame?
I am using MAMEUIFX64 0.155
Is there a more common version I should use?
-
I took a video..does this help show what I mean?
https://www.youtube.com/watch?v=73vPLeoUN_w&feature=youtu.be (https://www.youtube.com/watch?v=73vPLeoUN_w&feature=youtu.be)
-
There are no known sound regressions with Tempest, maybe your PC isn't fast enough to run it in 0.155, the emulation should be more accurate now, but also more demanding.
Also if you have a decent video card you can enable the vector HLSL and make the vector games look MUCH nicer in 0.155, that simply wasn't possible in 0.120.
-
Dont 'know if this is the place to post this...
I haven't checked all my games but I know already Tempest 's sound is corrupt on mame .155 vs. mame .120 when it was working fine.
Anyone else experience this?
This one glitch is a good reason for me not to upgrade.
well..i do see some improvements...trivia whiz color...pole position shows gear shift....still....what happened to Tempest??? Do I just have a bad rom?
I may have missed it, but did you get the 0155 roms set or are you trying to use your 0120 roms with the 0155 exe? Also, you might try MAME instead of MAMEUI. I don't know all the differences, but, when in doubt, try the "baseline" MAME.
I'm pretty sure Tempest works with 0155 otherwise there would be a lot of people making noise about it (assuming they know how to get into the MameWorld forums now).
As with all things MAME, the devs have made some good progress, but some things do break. So, it's best to keep several versions around, just in case.
-
I'm pretty sure Tempest works with 0155 otherwise there would be a lot of people making noise about it (assuming they know how to get into the MameWorld forums now).
AFAIK nobody's mentioned having problems with Tempest in the MAMEUIFX forum (http://mame32fx.altervista.org/forum.htm).
Scott
-
Another idea might be to go in your mame.ini and find the sound option. If it's set to auto change it to dsound
-
Another idea might be to go in your mame.ini and find the sound option. If it's set to auto change it to dsound
hey just wondering, is this a recommendation for everyone
ie. whats up with using 'auto'.. was wondering what problems can that introduce?
-
Thank you all. I don't know what dsound is either. I will leave it on auto since that didn't solve my problem and I don't know the difference.
I did just figure out the problem. Under slider options the sound level was too high.... the speaker mono volume was over 1 (around 1.28 for each)
I brought it down to 1 each and it sounds fine!
I'm happy now and continue configuring. I'm glad I have experts here for help.
-
Another idea might be to go in your mame.ini and find the sound option. If it's set to auto change it to dsound
hey just wondering, is this a recommendation for everyone
ie. whats up with using 'auto'.. was wondering what problems can that introduce?
I'm not 100% sure, but I thought "auto" was "dsound" now..? Or is that only for SDL Builds?
-
I think it's better to just put dsound or insert it at the command line for both windows and SDL builds. I've read elsewhere that even SDL builds do not use dsound when auto is in the .ini
Maybe Haze or someone else more knowledgeable can comment on that.
I use dsound for the official windows binary as well as SDL builds and there's no problems that I can hear AFAIK.
I'm not sure if it's correct on windows though.
-
on a regular windows build 'auto' is the same as 'dsound' and the recommended setting
on an SDL / SDL2 build 'auto' defaults to something else (xaudio2 or sdl I think) which has some audio breakup issues if the framerate drops <100% or your refresh rate isn't dead on, so selecting 'dsound' instead of auto is preferable.
btw, if you're on XP + older nVidia and want to avoid the BSOD with newer nVidia drivers then the SDL builds don't suffer from that problem without having to resort to the GDI / ddraw video output.