Main > Monitor/Video Forum
Soft-15KHz - slim new tool for 15KHz on normal vga cards
bent98:
http://community.arcadeinfo.de/showthread.php?t=9555
there is link for cabmame.
You can use the .diff file and compile your own build of mame if you just want to apply the sound hack. I use hack plus hi.diff to remove nag screens. Headkaze made a simple GUI FE to recompile mame source.
Question for sailor. I see you removed the neogeo.diff. Can you tell me what is the specific .diff files I need just to apply the soundsync fix to mame.
SailorSat:
@bent98: emuspeed and soundsync should do the job
@silver: autoframeskip 0, throttle 0, tripplebuffer (or vsync) 1 - scrolling smooth as butter.
base mame is aiming for perfect emulation, and fiddling with the sound speed to match the video speed is not perfect ;)
Ummon:
--- Quote from: Silver on February 04, 2008, 01:15:18 pm ---Oh, I agree there is always a tradeoff...
...It's just that it currently sounds like soft15Khz+ATI card allows for unlimited number of custom modelines. Which is basically what advancemame offers, except that advancemame calculates the perfect one for each game. Simply creating a few at varying frequencies, alongside the 60Hz ones, should be a pain free way of removing both the jerky issue and the sound issue in one go?
--- End quote ---
It might be. I had the idea of adding a modeline in Advancemame using the data from a soft15 modeline. Advancemame displayed it at slightly higher refresh - something like, 16.4khz (and a little lower or higher than 60hz). For some reason, it doesn't display all it's modes at 15khz, as the arcade vga and soft15 do. Mame just does what you tell it. Advancemame does something with it. Not necessarily one way or the other, but it is interesting.
I also noticed some difference in behavior between my Geforce Ti200 + soft15 and the arcade vga. For example, I have polepos set to 256x240 and I get a 'user mode' with the arcade vga but the Ti200 ends up doing 640x224 on the same monitor. Also with the Ti200 + soft15, I put on triplebuffer on Mappy (or any 224x288 game), and it was smooth. Not so on the arcade vga.
SailorSat: what is the limiting factor on Nvidia cards?
SailorSat:
--- Quote from: Ummon on February 05, 2008, 01:22:13 am ---SailorSat: what is the limiting factor on Nvidia cards?
--- End quote ---
A "bug" in the ForceWare.
They read/write from/to the CUST_MODE registry key with a 3000 byte buffer, while one mode is 92 bytes.
32 Modes * 92 Byte = 2944 Bytes = fine.
33 Modes * 92 Byte = 3036 Bytes = buffer overrun.
If you add more modes via the default NVidia controls you'll end up with garbage in the registry the first way.
If you add more modes via Soft-15kHz the data in the registry is fine.
However, on bootup, the driver reads only those 3000 bytes, which cuts off the 33rd mode and anthing behind it, causing the whole CUST_MODE string getting detected as "faulty" and droped, hence the card generates the modes itself IN 31kHz.
*EDIT*
It may be possible to "hack" the driver to increase the buffer size, however I'm not that good in disasembling drivers :)
If anyone does, please also take a look on the Intel Driver ;D
Silver:
--- Quote from: SailorSat on February 05, 2008, 12:51:50 am ---@silver: autoframeskip 0, throttle 0, tripplebuffer (or vsync) 1 - scrolling smooth as butter.
base mame is aiming for perfect emulation, and fiddling with the sound speed to match the video speed is not perfect ;)
--- End quote ---
Ok thanks. sounds like a reasonable workaround, as speedup/slowdown and pitch shift will be quite small for most games, although I'll still look at custom resolutions at varying frequencies.