With last Wine the sound stutters. With last from Ubuntu repository (old) 1.0.1, work near the flawless! I use alsa (pulseaudio -> default -> alsa). ... But sometime wow crash. Now I've tried 1.1.10 and 1.1.11 and the the sound stutters. Please fix this problem :( Ubuntu 8.10 x86_64 Q6600 at 3.2GHz X-Meridian 7.1 nVidia 8800 GT 512Mb Zotac AMP!
psychok9 wrote:> With last Wine the sound stutters. > With last from Ubuntu repository (old) 1.0.1, work near the flawless! > I use alsa (pulseaudio -> default -> alsa). > ... But sometime wow crash. > Now I've tried 1.1.10 and 1.1.11 and the the sound stutters. > Please fix this problem :( > > Ubuntu 8.10 x86_64 > Q6600 at 3.2GHz > X-Meridian 7.1 > nVidia 8800 GT 512Mb Zotac AMP! > >Sad to say, but there are no official efforts to support PulseAudio. You will have to disable it and enable ALSA or OSS. James McKenzie
:( I use pulseaudio for great audio software mixing (often I play with music on background)... and I don't understand how can work flawless with 1.0.1 and broken with 1.1.11. I get a new crash just after my post... nVidia 180.18 driver. When 1.10.11 don't seem fix crashs problems. Can I map only 3Gb of my memory only on Wine?
Solved! Driver emulation flag on winecfg fix my problem! :o This option slow seriously my wow performance? Thank you!
psychok9 wrote:> > jeffz wrote: > > This is not true. There are active efforts to fix PulseAudio issues. > > Great news! Can you answer my performance question? If you know it :P > > ...and sorry for my english :DThe stutter problem is known (bug 16607) either go back to 1.1.10 or wait for the problem to be fixed.
Hi, for all pulseaudio issues to be fixed - as far as I know (see bug 15559), you need the latest git (i.e. post 1.1.11) to pull in my fix. This needs the patch in bug 1607 to correct an issue with that patch. After that, sound should be good.
Be aware that 1.1.x line is development line so defects do happen. 1.0.1 includes a pulseaudio patch. "With padsp & Virtual OSS work... but pulse crash often on long game session (nosound -> console -> and i type pulseaudio for get back the sound)." That failure is not wine related. That is a pulse internal defect. So I would recommend disabling pulseaudio completely. Also be aware if your card has hardware sound mixing you are for sure better off without pulseaudio reason pulseaudio uses your cpu for audio mixing that take cpu time away from your game. Also dmix from alsa is also lighter on cpu usage. Yes less features. I prefer less features and my games running stable than most features and glitches due to internal defects in pulseaudio. Not exactly on the 3gb map issue. Another work around is to use a Linux cgroup to limit the memory wine sees so you can use all of memory normally. Issue here is a funny one. Wine says 4 gb to application wow does not know how to handle it. Something wow users miss enable PAE mode on there Windows XP and it will spit chips the same way. PAE mode allowed 4 gb of user space and kernel space of 32 bit windows in a different memory zone. Yes also allow 32 bit windows xp to take advantage of 8 gb or ram or more. There is a reason why Wow is not designed for PAE mode a lot of Windows drivers also spit chips in PAE mode. Basically tell wow it has 4 gb of ram to use it goes nuts and trys to allocate more than that. Yes 4096MB is not the max for a 32 bit system. Max for a 32 bit system with PAE enabled is 64 GB.
Last Wine source 1.1.11 compiled & installed. I still have game crash, but the sound works again correctly!
Das Letzte Einhorn
2009-Jan-02 14:45 UTC
[Wine] Re: Last Wine 1.1.10/11 = pulse sound stuttering
If you are willing to test WINE-Pulse development.. http://art.ified.ca/?page_id=40
oiaohm wrote:> Sorry I forget wine must have around 4GB. I gave instructions based on how to deal with normal programs under Linux being hogs using ulimit. > > Now of course more than 4GB equals problems for some problems. Bare min ulimit I have found to get winecfg to kick up is ulimit -v 3707585. So a ulimits between 3707585 to 4194304 would be recommend range. Note going for the high side would be better than going too low. > > Thinking ulimit virtual memory limit when hit causes to wine to respond with Cannot allocate memory. Should not break well coded applications instead trigger them to release memory and reuse. > > For some of those memory bugs trying ulimit would be highly recommended. It might be all that is required to prevent.Thanks. I've tried ulimit -m 3145728 with no results but with -v 3145728 Wine don't start. Can fix it I only with the setup the kernel and Linux for only 3Gbyte of memory? Or Wine will fix the bug in the future?