>Having first copied the original Fusion.ini file to my desktop, I tried ALSADeviceName=pulse and saved the file. Run Kega Fusion (with no other programs), enabled the sound and it froze. Tried your other suggestion, that is ALSADeviceName=default and again, Kega Fusion froze.
You're either stumbling upon a Kega Fusion bug, or possibly the alsa- plugins bug which I fixed a while ago (install alsa-plugins from my ppa to test if the latter is true: https://launchpad.net/~diwic/+archive/ppa ) > All these problems I've been describing have one thing in common: some programs won't work with sound unless you close ALL other programs. I don't think all these different programs have the same bug. Most of them do, PulseAudios entrance into the ALSA world was quite recently and before that, whether you were using "plughw" or "default" didn't matter as much as it does now. Not all other apps have adjusted since. If you use the the "plughw" device, you're locking all other apps away from the soundcard. Before PulseAudio, it was somewhat standard to do so. >I don't know "who" writes the Linux sound systems or if you could contact them about this problem. It's a critical problem! I don't know if I qualify as a "Linux sound system writer", but at least Daniel T Chen does. And believe me, we're trying to do the best we can, many of us in our spare time. But to get a stable sound system, we need things to be fixed the right way. And the right way for Kega Fusion is to use the device name "default" . Should that cause other bugs, we need to fix them as well. -- Sound problems. https://bugs.launchpad.net/bugs/512612 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
