So I used to use the winepulse patch for wine. (Yes I like pulse). But since 1.3.25+ uses mmdevapi for audio, that patch no longer works. That author points to a wine multimedia git, however, after installing that I have no more sound in any wine application, and the winecfg test audio says audio failed. How do I get this new sound server working in wine? -- Sincerely, MacNean C. Tyrrell -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winehq.org/pipermail/wine-users/attachments/20110819/05716c5a/attachment.htm>
So I tried the multimedia wine git, the openal-soft git, and the alsa-plugin patch for pulse. I got sound in WoW.exe but not in Steam Games (steam has sound but when it launches a game I don't have sound anymore). On Fri, Aug 19, 2011 at 8:08 AM, MacNean Tyrrell <dardack at gmail.com> wrote:> So I used to use the winepulse patch for wine. (Yes I like pulse). But > since 1.3.25+ uses mmdevapi for audio, that patch no longer works. That > author points to a wine multimedia git, however, after installing that I > have no more sound in any wine application, and the winecfg test audio says > audio failed. How do I get this new sound server working in wine? > > > -- > Sincerely, > > MacNean C. Tyrrell >-- Sincerely, MacNean C. Tyrrell -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winehq.org/pipermail/wine-users/attachments/20110819/df2715fc/attachment.htm>
Sorry I clicked send too early. SO I've dropped back to 1.3.24 for now with the pulse patch. I may try this again in a month or two to see if the sound has come along farther for those of us who dont' want to uninstall pulse and install alsa. On Fri, Aug 19, 2011 at 10:37 AM, MacNean Tyrrell <dardack at gmail.com> wrote:> So I tried the multimedia wine git, the openal-soft git, and the > alsa-plugin patch for pulse. I got sound in WoW.exe but not in Steam Games > (steam has sound but when it launches a game I don't have sound anymore). > > > On Fri, Aug 19, 2011 at 8:08 AM, MacNean Tyrrell <dardack at gmail.com>wrote: > >> So I used to use the winepulse patch for wine. (Yes I like pulse). But >> since 1.3.25+ uses mmdevapi for audio, that patch no longer works. That >> author points to a wine multimedia git, however, after installing that I >> have no more sound in any wine application, and the winecfg test audio says >> audio failed. How do I get this new sound server working in wine? >> >> >> -- >> Sincerely, >> >> MacNean C. Tyrrell >> > > > > -- > Sincerely, > > MacNean C. Tyrrell >-- Sincerely, MacNean C. Tyrrell -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winehq.org/pipermail/wine-users/attachments/20110819/17fd5ae4/attachment.htm>
winepulse patch we do not provide support for. Please try alsa with hardware acceleration set to emulation. Installing the winepulse patch breaks things.
oiaohm wrote:> winepulse patch we do not provide support for. > > Please try alsa with hardware acceleration set to emulation. > > Installing the winepulse patch breaks things.What do you mean by "hardware acceleration set to emulation"? Is such asoundrc not sufficient (it works for gst-launch-0.10 audiotestsrc ! alsasink but not wine): Code: pcm.dsp0 { type pulse } pcm.dsp { type pulse } pcm.!default { type pulse } ctl.!default { type pulse } pcm.pulse { type pulse } ctl.pulse { type pulse } ctl.mixer0 { type pulse }
> Please try alsa with hardware acceleration set to emulation. >This is referring to winecfg audio settings. Wine alsa interface has two options full and emulation. Set on the winecfg audio tab. Yes lot of pulseaudio hell is coming from the fact people are not changing that from default of full
jorl17 emulated mode sound quality as such no difference as long as it does not break up. But there is a performance difference. More dependance on CPU for processing in emulated than full. Full uses a few extra options in alsa to improve odds perfect audio under load. Basically emulation is running without a safety net. uzytkownik is wine putting any messages out on terminal also make sure alsaplay or otherwise equal native alsa using program can make sound.
oiaohm wrote:> jorl17 emulated mode sound quality as such no difference as long as it does not break up. > > But there is a performance difference. More dependance on CPU for processing in emulated than full. Full uses a few extra options in alsa to improve odds perfect audio under load. > > Basically emulation is running without a safety net. > > uzytkownik is wine putting any messages out on terminal also make sure alsaplay or otherwise equal native alsa using program can make sound.Code: ALSA lib pcm_pulse.c:995:(_snd_pcm_pulse_open) Unknown field handle_underrun ALSA lib pcm_pulse.c:995:(_snd_pcm_pulse_open) Unknown field handle_underrun ALSA lib pcm_pulse.c:995:(_snd_pcm_pulse_open) Unknown field handle_underrun ALSA lib pcm_pulse.c:995:(_snd_pcm_pulse_open) Unknown field handle_underrun ALSA lib pcm_pulse.c:995:(_snd_pcm_pulse_open) Unknown field handle_underrun err:winmm:WINMM_OpenDevice Activate failed: 80004005 ALSA lib pcm_pulse.c:995:(_snd_pcm_pulse_open) Unknown field handle_underrun err:winmm:WINMM_OpenDevice Activate failed: 80004005 aplay is working.
uzytkownik I did miss a step. winecfg audio set hardware to emulation. Next ok exit winecfg run wineserver -k to shut wine fully down. then re run and test. "ALSA lib pcm_pulse.c:995:(_snd_pcm_pulse_open) Unknown field handle_underrun" This is something you should not be seeing. This is like you Alsa pulse is not built right. There should be a underrun handler otherwise its not up to grade to run wine. Since underruns naturally happen all the time. Basically there should be a underrun error not Unknown field handle_underrun. dmix does in fact provide a underrun handler. Wine does particularly request alsa support for underrun correction. Note I run without pulse audio "ALSA lib ../../../src/pcm/pcm.c:7316:(snd_pcm_recover) underrun occurred" is basically status normal. Audio should come out with under runs Basically uzytkownik there is something major-ally wrong in your audio stack and this is why wine is not putting out sound. Now if this is incompetence in the pulseaudio side they need their tails kicked.
> ALSA lib pcm_pulse.c:1008:(_snd_pcm_pulse_open) Unknown field > handle_underrunThis is why. output streem will have failed to open because of that. So its the "multimedia-git" where this is coming from. People developer branches for testing out future forms has some nasty requirements. Like the git version of pulseaudio as well. That supports the handle_under-run feature. Emulation is the required state to use pulseaudio if you have a working version of it. MacNean Tyrrell basically nice sweet spot wine has to ask for that feature since windows applications believe it perfectly fine to under run a audio buffer. Why is wine requesting the feature. It stops wine from crashing the complete pulseaudio server due to it not handling underruns. Yes its better to be pulseaudio incompadible until it underrun in it get more common.
MacNean Tyrrell You might be walking into a trap. Setting emulation in winecfg does not happen instanty. wineserver -k is require after winecfg to get the new audio state loaded. Yes I have had people be caught that after a reboot they are in emulation then change to full have it work and think the setting was full when it worked. Its a evil binary lock that can get you.
MacNean Tyrrell problem we have here is it sometimes not wine. Sometimes is pulseaudio it self alsa emulation failing. few minutes death is a common one from pulseaudio alsa interface and pulse server being different versions. Since I don't normally use pulseaudio version of pulse and making sure you pulse install is correctly matched up would be the next wise things to check. ALSA lib pcm_pulse.c:1008:(_snd_pcm_pulse_open) Unknown field If this is appearing on console still you version of pulse is not wine compadible. Ie too old.
MacNean Tyrrell don't know ubuntu versioning. Pulse versions in those might enable someone to answer if it contains that feature or not.
There is a particular reason for setting emulation. MacNean Tyrrell To prevent wine from calling real-time features of alsa. That pulseaudio simply does not support. Full tells wine to use every feature alsa offers. This is why I am saying emulation if emulation mode does not work then we have something to worry about. If full fails could be simply using features pulseaudio does not support very well at wrong times leading to sound failure. So we don't bother debugging full on anything bar standard alsa.
err:alsa:wine_snd_pcm_recover underrun occurred Yep confirmation of a pulseaudio shot gun if running in full. Since at or near the fail a underrun happens. This is enough to crash or cause pulseaudio to stop putting out audio on everything. Reason why seeing this. "ALSA lib pcm_pulse.c:1008:(_snd_pcm_pulse_open) Unknown field handle_underrun" Tells us that pulseaudio will not recover from a underrun event and the err above confirms the exist of that problem. Is basically a o that is why full is not working moment. "err:d3d:device_resource_released Buffer 0x2ea93b70 is still in use by stateblock 0x1ba608 as index buffer. " That is a strange error. Next item really requires running with pasuspender with wine set emulation. Ok wine is going to hog the audio doing this due to no mixer in most cases. But this does remove pulseaudio from mix. If wine is still failing in pasuspender mode with wine set emulation then its 100 percent a bug in wine alsa with the programs you are using. pasuspender mode cannot have full either because you most likely not have a mixer. So is a wine bug report. If it works with pasuspender something from pulseaudio is messing with us. So it is a bug report to pulseaudio due to there alsa emulation being faulty for some reason. Yes I had to get you using emulation before I could ask you todo the next test. Full in pasuspender mode also fails in bad ways due to missing mixer. Also some programs just switching on emulation make the problem with pulseaudio disappear.
On Mon, Sep 5, 2011 at 8:54 AM, MacNean Tyrrell <dardack at gmail.com> wrote:> > > On Mon, Sep 5, 2011 at 8:42 AM, tparker <tparker at etherstorm.net> wrote: > >> On 09/04/2011 08:03 PM, MacNean Tyrrell wrote: >> >>> >>> OK, obviously compiling my own pulse/alsa doesn't work. I get sound in >>> all >>> applications except wine. >>> >> >> I don't have pulse installed and I have sound everywhere except in wine >> since wine version 1.3.25. Is it possible that part of your problem is the >> in-progress-but-not-completed changes to sound in wine? I haven't had any >> luck tracking an answer down for that in my case am an not sure how we would >> tell if that applied to your issue. >> >> > If I upgrade to 11.04 Ubuntu (which has a newer Pulse server) I can get > sound for 30-40 minutes. However, there is a bug in libasound2-plugins > (basically alsa-plugins) that causes the alsa plugin to fail after awhile. > It's fixed in 11.10. I really hate unity, but like the simplicity of > ubuntu. So not sure what i'm gonna do right now. > >Hmm sorry last one went to personal instead of wine-users. Also, I think without pulse and straight up alsa, wine .25+ is supposed to just work.> -- > Sincerely, > > MacNean C. Tyrrell >-- Sincerely, MacNean C. Tyrrell -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winehq.org/pipermail/wine-users/attachments/20110905/2dc1b298/attachment.html>
MacNean Tyrrell wrote:> On Mon, Sep 5, 2011 at 8:54 AM, MacNean Tyrrell <dardack at gmail.com> wrote: > > > > > > > > On Mon, Sep 5, 2011 at 8:42 AM, tparker <tparker at etherstorm.net> wrote: > > > > > > > On 09/04/2011 08:03 PM, MacNean Tyrrell wrote: > > > > > > > > > > > > > > OK, obviously compiling my own pulse/alsa doesn't work. I get sound in > > > > all > > > > applications except wine. > > > > > > > > > > > > > > I don't have pulse installed and I have sound everywhere except in wine > > > since wine version 1.3.25. Is it possible that part of your problem is the > > > in-progress-but-not-completed changes to sound in wine? I haven't had any > > > luck tracking an answer down for that in my case am an not sure how we would > > > tell if that applied to your issue. > > > > > > > > > > > If I upgrade to 11.04 Ubuntu (which has a newer Pulse server) I can get > > sound for 30-40 minutes. However, there is a bug in libasound2-plugins > > (basically alsa-plugins) that causes the alsa plugin to fail after awhile. > > It's fixed in 11.10. I really hate unity, but like the simplicity of > > ubuntu. So not sure what i'm gonna do right now. > > > > > > > Hmm sorry last one went to personal instead of wine-users. Also, I think > without pulse and straight up alsa, wine .25+ is supposed to just work. > > > > -- > > Sincerely, > > > > MacNean C. Tyrrell > > > > > > > > -- > Sincerely, > > MacNean C. Tyrrell > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://www.winehq.org/pipermail/wine-users/attachments/20110905/2dc1b298/attachment.html>Can't you configure Pulseaudio to go through an ALSA device that uses dmix instead of talking to the hardware? Then you could have Wine use that device as well, bypassing pulse. You'd also setup the environment so that all the other apps would use the "pulse" device, which would lead to Pulse, which would lead to the dmix device, but with the advantages of Pulse. Cheers, Jorl17
Let me try to make this clear. Pulseaudio talks to ALSA. However, it is usually setup to talk to the ALSA device hw:0, which is the hardware. So, Pulseaudio hogs the hardware device and no other app can access it. This is ok, because ALSA is setup to route every other application (if that app is well configured) to another ALSA "device" called pulse, which, in turn, sends it to Pulseaudio. So when an application that uses ALSA directly runs, it goes like this: App -> ALSA -> ALSA pulse device -> Pulseaudio -> ALSA hw:0 device (hardware). Before Pulseaudio, as you may know, people used dmix to do software mixing. Sure, Pulseaudio offers a range of other features, but you can still use dmix today. The idea here is to have Wine "bypass" Pulseaudio completely, and talk to ALSA directly. To do this, Pulseaudio must stop "hogging" the hw:0 device, so it must go through another device we create called, for instance, dmixed. This dmixed device supports software mixing through dmix and, thus, can be accessed by Pulseaudio and other applications as well. It would still default to sending applications to Pulseaudio, but if you configured your application to request the dmixed device, you'd be bypassing the whole Pulseaudio "mess". So this is what would happen: Regular App -> ALSA -> ALSA pulse device -> Pulseaudio -> ALSA dmixed -> hw:0 device (hardware). Wine -> ALSA -> ALSA dmixed device -> hw:0 device (hardware) Wine can be configured to do this with registry keys. The devices can be fairly easy created by editing the $HOME/.asoundrc file. The question here is how to redirect Pulseaudio to the ALSA dmixed device instead of the hw:0 one. To be honest, since I moved to Gentoo I've left Pulseaudio completely. The only feature I missed was recording the PC sound and I've fixed that on my own with plain ALSA. However, I still remember doing something similar to this in ubuntu, so if it hasn't changed, you can change the default Pulseaudio alsa device from hw:0 by editing the /etc/pulse/default.pa file and adding the following at the end: load-module module-alsa-source device=dsnoop:0 load-module module-alsa-sink device=dmixed:0 Of course this assumes that you have created a dsnoop device and a dmix device (in $HOME/.asoundrc). dsnoop allows for record software mixing and dmix for playback software mixing. If you'd like to try this, do say, as it *might* help you solve your problems...let's just hope it doesn't add any other. Cheers, Jorl17
If you need help, don't mind asking!
Hmmm using [/code] in email doesn't work as well as posting on the forums I see. Anyways I see the forum got my email, but I guess there's discussion about splitting the two, guess I'll have to add this to one of my startup tabs.
Hi. You .asoundrc seems fine. Note that applying asoundrc changes doesn't mean pulseaudio also applied its changes. ALSA can be restarted via a service, I'm sure. Pulseaudio I don't know. In my ubuntu days I just killed pulseaudio and manually typed pulseaudio. If you say it complains it's probably because it doesn't want to run as root. (which service probably does). I don't think you have to/should uncomment those two lines, because they are there to help pulseaudio detect the underlying hardware (the udev one) and the other one is just plain useless unless you want to save energy. Once you've tried it out, be sure to tell us if it worked! Jorl17 P.S: the last [/code] got in the message by mistake. Code tags do work, but you obviously have to open them before closing them ^^
Laptop:~$ aplay -D duplex_for_pulse Miley_Cyrus-Party_In_The_USAshort.wav Playing WAVE 'Miley_Cyrus-Party_In_The_USAshort.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo ^CAborted by signal Interrupt... That works, the abort was me cutting it short.
dardack wrote:> On Tue, Sep 6, 2011 at 10:00 PM, dardack <wineforum-user at winehq.org> 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
jorl17 you missed important instruction wineserver -k before editing ~/.wine/user.reg directly. Reason otherwise wineserver might simply nuke you edit. Yes its safer to use regedit or reg commands and import a proper reg file. Now of course what would make us all happy is if Pulseaudio alsa support just worked out the box. Not having to bend 12 ways from sunday so it behaves itself.
So Ok I think I have it, but it's wierd. First, I compiled pulseaudio 0.9.93 following: http://colin.guthr.ie/2010/09/compiling-and-running-pulseaudio-from-git/ (If on ubuntu don't try to install this, you will F your sound so much, you'll prolly have to reinstall (yeah happened to me)). Then I do: echo "autospawn=no" >> ~/.pulse/client.conf pulseaudio -k Then using those directions, after each reboot I execute the: export LD_LIBRARY_PATH=~/Programs/pulseaudio-src/build/src/.libs then I do: ~/Programs/pulseaudio-src/build/src/pulseaudio -n -F src/default.pa -p $(pwd)/src/.libs/ -vvvv Then I run something using pulse (ussually a mp3 with totem) pause the mp3 so it stays in pulse use. Then I open youtube in chrome that uses alsa direct. Then I kill that pulseaudio, and do: pulseaudio Then all sound works. As long as something stays in pulse it works. What makes this work I suspect is the updated .23, but linked to .21 for ubuntu to not break. padevchooser (the pulse manager) says: ServerVersion: 0.9.23-rebootstrapped Linked to Library Version: 0.9.21-63-gd3efa-dirty So yea. Pain the the but, but so far perfect sound in all applications. On Wed, Sep 7, 2011 at 1:51 PM, MacNean Tyrrell <dardack at gmail.com> wrote:> > > On Wed, Sep 7, 2011 at 1:46 PM, ryan woodsmall <rwoodsmall at mac.com> wrote: > >> >>> > I don't know, I may give up >>>> >>>> Yeah, give up if it keeps you from replying to yourself over and over >>>> and over. >>>> >>> >>> Wow really? Was updating because jorl17 was helping me alot. Just >>> putting out there where it was at and stuff. You don't gotta read it if you >>> don't want to. >>> >>> >>> >>> I'm eating a crumb cake, what are you doing? >>> >> >> OH cake, thought you was trollin. Banging my head against pulse/alsa wall >> for past 3 days. >> >> >> Totes trawlin. But I've had good luck with OSS4 even though it pretty much >> replaces ALSA+Pulseaudio. >> >> The cake was delicious BTW. >> > > I personally like pulse for everthing buy wine (even liked it in wine pre > 1.3.24 and below with the winepules patches). Eh who knows what i'll do at > this time. > > -- > Sincerely, > > MacNean C. Tyrrell >-- Sincerely, MacNean C. Tyrrell -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winehq.org/pipermail/wine-users/attachments/20110907/56b49a97/attachment.html>
OK posting this in case someone else wants to do this. This is for people on Ubuntu mainly, and who don't want to upgrade to 11.10 (fixes the pulse alsa plugin) on wine 1.3.27 (wine may fix it'self with the sound server rewrite, ubuntu has stated the plugin fix will not be backported because of new pulse API). First create a ~/.asoundrc that has this: (Edit the hw, or other options as needed for your card) Code: pcm.dsnooped { type dsnoop ipc_key 2048 #Any value at random. Really, any value. slave { pcm "hw:0" #Or whatever your card # is } } pcm.dmixed { type dmix ipc_key 5678293 #Any value at random. Really, any value. slave { pcm "hw:0" #Or whatever your card # is } } ctl.dmixed { type hw card 0 device 0 } pcm.duplex_for_pulse { type plug slave { pcm { type asym playback.pcm "dmixed" capture.pcm "dsnooped" } } } ctl.duplex_for_pulse { type hw card 0 } next edit /etc/pulse/default.pa find the Code: load-module module-udev-detect line and comment it out: Code: #load-module module-udev-detect then scroll to bottom of the file and add: Code: load-module module-alsa-sink device=duplex_for_pulse load-module module-alsa-source device=duplex_for_pulse then make a alsareg.reg file (or manually edit the registry of your wineprefix): Code: REGEDIT4 [HKEY_CURRENT_USER\Software\Wine\Alsa Driver] 1315011634 "AutoScanCards"="N" "AutoScanDevices"="N" "DeviceCount"="1" "DeviceCTL1"="duplex_for_pulse" "DevicePCM1"="duplex_for_pulse" "UseDirectHW"="Y" then in terminal: Code: WINEPREFIX="your prefix path here" regedit alsareg.reg Open winecfg go to audio tab and make sure Alsa is checked and Emulation is selected. now the next part are a few ways you can do. You want updated alsa-plugins/alsa-lib but not alsa-driver/alsa-utils/linux-sound-base. I used the ppa from these guys: https://launchpad.net/~team-iquik/+archive/alsa updated everything but alsa-base/alsa-utils/linux-sound-base, then removed the ppa. You can also download the source code, compile/install it. I rebooted at this point. If your using 1.3.24 at least (I tested that), wine should use alsa directly, and regular apps should use pulse now. 1.3.27 will not get sound if something is using pulse, and if wine is using the soundcard pulse apps won't get sound. So now comes the hackish part. Follow the steps to compiling pulseaudio here: http://colin.guthr.ie/2010/09/compiling-and-running-pulseaudio-from-git/ DO NOT DO sudo make install , you will probably mess up your whole sound if you do, and will prolly have to reinstall OS (happened to me, no amount of purges/reinstalls got my sound back). Once you have it compilled, I rebooted. I then have 3 scripts: pulseAudiolib.sh Code: ! /bin/bash export LD_LIBRARY_PATH=/home/macnean/Programs/pulseaudio-0.9.23/build/src/.libs I open terminal and run: Code: . pulseAudiolib.sh Be mindful of the .<space> it allows the exported path to escape the single session pulseSecondlib.sh Code: rm /home/macnean/.pulse/client.conf echo "autospawn=no" >> /home/macnean/.pulse/client.conf pulseaudio -k ~/Programs/pulseaudio-0.9.23/build/src/pulseaudio -n -F ~/Programs/pulseaudio-0.9.23/build/src/default.pa -p $LD_LIBRARY_PATH -vvv run this script, and now you need to run something that uses pulse (vlc/totem/mumble/whatever) and pause it. in that terminal hit CTRL C to end this local pulse pulseThirdlib.sh Code: #! /bin/bash rm /home/macnean/.pulse/client.conf pulseaudio And that's it. 1.3.27 will now use ALSA straight up, and all pulse items can use the sound card. Not sure anyone else cares, but posting it here for documentation sake incase my HD crashes or something.[
dardack wrote:> The reg will if Pulse doesn't want to grab sound later. Maybe with 2 sound > cards it works better. But on mine if Pulse has grabed the Soundcard at > this point, wine won't be able to use it for some reason. (at least 1.3.27 > wine, 1.3.24 worked fine at this point). >I am not having this issue on 1.3.27. There's no conflict between wine and pulse that I have seen. I could just be lucky though. I don't think I was having near as many issues with sound after 1.3.25 came out as some other people though. dardack wrote:> > Did you change the name pcm.dmixed/mixin for the second card, they can't > have the same name, you also have to change the HW#. It could be why you're > having sound go across multiple sound cards. Then create duplex2 or > something. >I suffixed everything with 0 or 1 depending if it was hw:0 or hw:1. Works great except in the few circumstances I noted. dardack wrote:> > BTW you using 1.3.27 wine? >Yup. I had to download the 1.3.27 deb from the natty repo though since there is no 1.3.27 build for lucid yet. Also many thanks for putting that little guide together!