jordan wrote: > > Interesting, this makes sense to me now. I believe the default that > wine uses is just to autoscan your soundcard. > It seems it was grabbing the wrong thing and failing. So you had to > specifically tell it what to use via the Registry. > That makes sense because: - Withouth /etc/asound.conf there is no "default" device. This is why I needed asound.conf in the first place. So if wine is scanning the hardware directly, it shouldn't find a default device either. And fail. - And even with asound.conf aplay -L doesn't find the new defined devices. If Wine scans with the same method, it would get the same result. What is strange though, is that this used to work. But maybe an upgrade to Wine has changed the way Wine looks for devices? Or maybe there are some slight differences between my old and new graphics card, or an upgrade to ati-drivers has changed something. I haven't used Wine on a daily basis at home, so it's difficult to say exactly when things broke.
