Software Support > GroovyMAME
Groovy Arcade Linux Live-CD, based on Arch Linux (official update)
Ansa89:
--- Quote from: Calamity on August 23, 2012, 12:05:06 pm ---Please Ves and Ansa and others try this patch out and see if it fixes the issue for you too.
--- End quote ---
Is there a known way to reproduce the "fuzzy sound" issue?
Calamity:
--- Quote from: Ansa89 on August 24, 2012, 09:04:18 am ---
--- Quote from: Calamity on August 23, 2012, 12:05:06 pm ---Please Ves and Ansa and others try this patch out and see if it fixes the issue for you too.
--- End quote ---
Is there a known way to reproduce the "fuzzy sound" issue?
--- End quote ---
Yes, actually the bug is in vanilla MAME (SDL). Just use the option -speed with any factor different from 1.0, say 0.9. Then pause/resume, pause/resume a few times and the sound will go corrupt.
Calamity:
--- Quote from: danger on August 24, 2012, 04:48:08 am ---hi...
I have download GroovyArcade-Arch2012.06.09-i686.iso and after install to disk it gives me an error booting "unable to find root device"
the grub boot line as root=/dev/disk/by-label/GA
anyone can help me ?
--- End quote ---
What shows the first line in grub? (hd0,0) etc
Ansa89:
--- Quote from: Calamity on August 24, 2012, 09:10:11 am ---the bug is in vanilla MAME (SDL).
--- End quote ---
Groovymame is aware of this bug?
Nobody reported it under groovymame?
Calamity:
--- Quote from: Ansa89 on August 24, 2012, 09:25:42 am ---
--- Quote from: Calamity on August 24, 2012, 09:10:11 am ---the bug is in vanilla MAME (SDL).
--- End quote ---
Groovymame is aware of this bug?
Nobody reported it under groovymame?
--- End quote ---
Well if I remind right you did report it! :)
Some Linux users have been experiencing sound problems like static noise since the new soundsync patch was added to GM. What I found is that the soundsync patch is just exposing a previous bug in vanilla MAME SDL sound code.
In GM the bug happens when pausing/resuming, or in some games it just happens spontaneously.
But in vanilla MAME you need to explicitly use the option -speed with a factor different from 1.0 and then pause/resume in order to expose the bug.
In other words, GM is using the -speed feature internally to adjust the sound to the current video speed, that's why it automatically makes the problem appear.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version