your config is really good for MAME. You can try the following; make a backup of the mame ini and delete it from the mame folder and make a new config. The default is already to work without any bugs.
Can I please buy you a beer or something? lol I'm being serious.
I'm a bit scared to just replace my mame.ini with the one in the groovymame.zip. Unless you meant "creating" the mame.ini by running groovymame.exe -cc? Is there a difference between doing that and using the one that's already in the groovymame.zip download?
Also I got a text comparison program and am looking at my current mame.ini and the one in the groovymame.zip and here's the only differences I see:
in CORE PERFORMANCE OPTIONS, my current ini has "autosync 1". This line is not in the mame.ini from the groovymame.zip at all
In my current ini, OSD OUTPUT OPTIONS has "output windows" and the mame.ini in the groovymame.zip has "output auto".
In my current ini, OSD PER-WINDOW VIDEO OPTIONS has "aspect 4:3" and the mame.ini in the groovymame.zip has "aspect auto".
In my current ini, OSD FULL SCREEN OPTIONS has "monitor custom" and the mame.ini in the groovymame.zip has "monitor generic_15"
In my current ini, crt_range0 has "15625-16200, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 192, 288, 448, 576" and the mame.ini in the groovymame.zip has "auto"
I also have "video" set to "d3d" instead of "auto".
And finally, in my current ini, under FRONTEND COMMAND OPTIONS, it has "orientation horizontal" and the mame.ini in the groovymame.zip does not have this line at all.
Could any of these be causing my issue?
edit: for testing I removed "autosync 1" from CORE PERFORMANCE OPTIONS since "autosync 1" was already somewhere else in the ini file. I also changed OSD OUTPUT OPTIONS from "output windows" to "output auto" and neither of those made a difference. I even put in "-priority 1" as part of the command line in LaunchBox because it's supposed to make MAME use more of the CPU. I am still getting audio that's all warped all over the place, even in something as basic as VS Super Mario Bros.
This literally was not happening a week ago. The only things I've done since then was update from 0.235 to 0.236, and messed with CRT Emudriver a bit. I have absolutely no idea why this is happening after those two things.