dardack wrote: > On Tue, Sep 6, 2011 at 10:00 PM, dardack <wineforum-user@xxxxxxxxxx> wrote: > > > > OK, so I had to comment out the udev part, but not the idle part. > > > > However, wine is still creating alsa-plugins in pulse. I don't think it's > > communicating directly to alsa hw. How do i make it choose alsa hw over > > pulse. > > > > I did find an update alsa-driver/plugin ppa for 10.04. Trying it out, but > > still it's a alsa plugin into pulse with wine, would like to skin this. > > > > > > > > > > > > Ok the ppa was working until i rebooted. Now whatever grabs the sound > > > first has sound. If a reg app grabs it, wine doesn't, if wine grabs it, > reg apps don't get it. They show up (reg apps) in applications under sound > pref's, but now sound, until wine releases. > > > -- > Sincerely, > > MacNean C. Tyrrell > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://www.winehq.org/pipermail/wine-users/attachments/20110906/c0062326/attachment.html> Ok. Now this may be some kind of Wine-Pulseaudio incompatibility again. So what we're going to do is use Wine's settings to force it to use the duplex_for_pulse device, instead of the default one, which points to pulse. This is farily easy, according to the ALSA keys in http://wiki.winehq.org/UsefulRegistryKeys For instance here's an example: [Software\\Wine\\Alsa Driver] 1315011634 "AutoScanCards"="N" "AutoScanDevices"="N" "DeviceCount"="1" "DeviceCTL1"="duplex_for_pulse" "DevicePCM1"="duplex_for_pulse" "UseDirectHW"="N" However, I think you might run into an issue due to not having defined a ctl.duplex_for_pulse, but we'll get there. For now just create those entries so that they match this. BTW, it isn't advised, but you can paste that snippet in the ~/.wine/user.reg file at the end (be sure to back it up first!) and it should work. To make sure you're testing wine's sound, do a wineserver -k and then open up winecfg to test the sound. Cheers, Jorl17
