Wine and spotify used to work. Now it doesn't, and I don't know why. Main problem is that Wine doesn't give any information back regarding why audio fails, only that it fails. When using winecfg, opening the Audio tag, choosing Alsa Driver and pressing "Test sound", a pop up reports "Audio test failed!". Nothing more. Choosing OSS, switching to emulation, same error message. But I have to mention that I do get a couple of "disabling mixer" debug messages. I have browsed the documentation, and used google, but not been able to find any information about how to find out what the problem is. Alsa is of course working in other programs. Aplayworks. Mplayer works. KDE configuration test works. So, how do I start figuring out what's wrong?
Hi alte, you don't by chance have other audio applications open, when trying to use wine, do you??? - this would also include your web-browser (which often grabs the audio). - are you using pulseaudio? I wil have the same problem, if another app is grabbing the soundcard. jordan
Hi jordan. I have three computers in daily use, on two of them Wine works fine. And on the two which are working, I am able to use wine with sound at the same time as I am using Firefox and playing youtube Flash videos. And this is without pulse audio. I am no expert on linux sound, so I don't know why this works, or why it shouldn't work. I've read the FAQ's and man pages of Wine, and /dev/dsp is mentioned. Also testing write access to /dev/dsp to check if some other application is blocking the device. But as far as I understand, /dev/dsp is OSS related, and is not relevant for ALSA. So my obvious question is: - does ALSA really also have the "only one access at a time" limitation mentioned? - if so, what trick allows me to play sound from multiple applications, including Wine, at the same time on two of my machines? And as I mentioned, I am pretty sure I'm not using pulse audio.
I tested with lsof, and the only open sound related device was /dev/snd/controlC1 opened by kmix. Killing kmix of course changed nothing.
No, speaker-test is a native Linux program. http://manpages.ubuntu.com/manpages/lucid/man1/speaker-test.1.html If winecfg's sound test works, of course, you don't need to do a native speaker-test.
>Ya, I don't use KDE, i just naturally assume it plays a similar roleto Pulseaudio (which also can set sound). Sorry, bad description on my part. kmix is an alsamixer equivalent for KDE. It doesn't play anything, or mix sound streams like dmix.>That's kind of what i would expect to see.I wouldn't. Where is gstreamer finding a default ALSA device that aplay can't find? This is linked to the previous question, why can't aplay -L or KDE4/phonon/gstreamer find the devices I create in asound.conf? I wish there would be some more consistency here.>Have you tried a fresh install of Wine??? you can do this simply byrenaming your .wine folder (as to not lose anything), then try uninstalling Wine. I'll try that. I have only tried removing .wine to recreate settings.>For you to not have changed anything, andit just stopped working. I didn't say that. I upgrade gentoo all the time. I even upgrade kernel now and then. Also I've changed from a ATI47** to an ATI56**. But these are steps that cannot easily be reversed. Also, sound is working. It's just wine doing something strange. But I'll try reinstalling it tonight. What I miss is something like what was used in the old ~/.wine/config: [ALSA] "PlaybackDevice" = "default" (Ref: http://wiki.jswindle.com/index.php/Wine_Config_File) If I found a way to do the same in the new .reg files, I'd be happy.
And as I posted the previous, I checked my next opened tab, and found: Code: I got this working finally! I wrote it up in my blog here: http://meandubuntu.wordpress.com/200...dio-from-wine/ But basically it involved setting the following in the registry for Wine: [Software\\Wine\\Alsa Driver] ?AutoScanCards?=?N? ?DeviceCount?=?13 ?DeviceCTL13=?default? ?DevicePCM13=?default? ?UseDirectHW?=?N? Will try, and report back. [/code]
Miss the possibility to edit posts. The above post came from the Ubuntu forum here: http://ubuntuforums.org/showthread.php?t=700231
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.
I use an old XP SP2 on my stationary for games (but more and more my PS3), and the odd device I can't connect to Linux (for example my Garmin Forerunner 405.) My wife connects her XP laptop to the wireless though. But sometimes friends and family visits with their Vista machines? Windows is for games, and Linux for work and everything else, that's what I've always said.