Anyone knows how to fix the bug in double wings？

[jsjyqz]

The game has strange sound bug that no one knows about this,the full describe in here:http://mametesters.org/view.php?id=5941

[ProjectAKo]

MAME sound is freakin horrible. I had to manually rewrite the sound engine in my sonic wings 2 rom so it would stop crashing. I explained what the problem was on mametesters, but they didn't care and still haven't fixed it and probably never will. I hope you know how to debug in assembly whatever chipset double wings uses.

[jsjyqz]

MAME sound is freakin horrible. I had to manually rewrite the sound engine in my sonic wings 2 rom so it would stop crashing. I explained what the problem was on mametesters, but they didn't care and still haven't fixed it and probably never will. I hope you know how to debug in assembly whatever chipset double wings uses.

the game Sound Chips : Yamaha YM2151 (@ 3.58 Mhz), OKI6295 (@ 7.627 Khz) ,but don't know how to debug it

[ProjectAKo]

MAME sound is freakin horrible. I had to manually rewrite the sound engine in my sonic wings 2 rom so it would stop crashing. I explained what the problem was on mametesters, but they didn't care and still haven't fixed it and probably never will. I hope you know how to debug in assembly whatever chipset double wings uses.

the game Sound Chips : Yamaha YM2151 (@ 3.58 Mhz), OKI6295 (@ 7.627 Khz) ,but don't know how to debug it

Well I know there's sound timing issues in MAME because it's not properly emulating wait delays after interrupts, so it can do a NMI and by luck instantly do a regular interrupt right after, possibly causing a sound crash. But that's all I know.

[IseeThings]

MAME sound is freakin horrible. I had to manually rewrite the sound engine in my sonic wings 2 rom so it would stop crashing. I explained what the problem was on mametesters, but they didn't care and still haven't fixed it and probably never will. I hope you know how to debug in assembly whatever chipset double wings uses.

We do care, and have acknowledged it.

Any kind of fix would have a wide impact and need *extensive* testing on things well beyond the humble NeoGeo, there is currently nobody in a position to do that. Once you get into subtle timing nuances you're in deep, improving the timing in one place can break much more than it fixes due to exposing other bugs (for example if in another CPU core some of the opcode / frame / whatever timing is incorrect and as a result it actually expects writes to go through during the busy period you've opened up a whole bunch of other bugs that need fixing.

One day it will get done, but just because you have a bug that bothers you don't expect the team to leap up and fix it, for the cores in question the devs who have done most work on them aren't really even active at the moment, so they might actually need new maintainers.

As for jasd, he seems to have resorted to spamming forums asking people to fix the bug he wants fixing.