Software Support > GroovyMAME
Groovyarcade installed to disk = No ALSA?
Ansa89:
Everybody should use ALSA, since OSS is deprecated; but you also must remember you are on gentoo...(yes, is a flame/ironic comment because I don't like very much gentoo).
What I can tell you is that on slackware ALSA works fine, so I think there is something wrong with gentoo scripts/sound management.
Calamity:
--- Quote from: Ansa89 on March 04, 2012, 04:47:40 am ---Everybody should use ALSA, since OSS is deprecated; but you also must remember you are on gentoo...(yes, is a flame/ironic comment because I don't like very much gentoo).
--- End quote ---
BTW, in case you want to give it a try, Ves has realeased a new GroovyArcade iso based on ArchLinux: http://www.retrovicio.org/foro/showthread.php?14969-GroovyArcade-Por-fin-100-Pixel-Perfect-y-mucho-mas&p=184957&viewfull=1#post184957
I'm wondering if the sound latency option could remove the latency issue you were experiencing, Ansa89, since then I've seen it repored by other people too, including Ves.
Ansa89:
--- Quote from: Calamity on March 04, 2012, 05:17:35 am ---I'm wondering if the sound latency option could remove the latency issue you were experiencing, Ansa89, since then I've seen it repored by other people too, including Ves.
--- End quote ---
I'll check, but is also important understand why of this behavior (maybe is related to your groovymame changes in sound core?).
Calamity:
--- Quote from: Ansa89 on March 04, 2012, 07:32:17 am ---I'll check, but is also important understand why of this behavior (maybe is related to your groovymame changes in sound core?).
--- End quote ---
Yes, definitely. But the interesting part is that I didn't change anything in the sound core. What this patch does is to adjust the emulation speed to the one forced by the refresh rate of our video card. This is performed by updating m_speed with the current speed percent value, dynamically (this is done in \emu\video.c). On its own side, the sound core uses this m_speed value to adjust the sound output to the current emulation speed, but I didn't add this feature, it was already built-in in MAME, though only used by the almost useless -refreshspeed option. So, I'm guessing the issue is that at some point during normal game execution, some speed percent values are read that when translated into m_speed values somewhat corrupt the sound buffer from there on, causing lag or even worse stuff (if you pause the game the sound gets noise on resume). For some reason, this only happens in Linux. So that's where we need to look for, I believe.
Ansa89:
Just a couple of guesses:
- the m_speed value change too rapidly to let sound be setted correctly
- the m_speed is casted in some obscure way with precision loss.
- the mame sound core driver on linux is bugged (but I think mame uses sdl libraries also for sound)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version