similar to: Anyone having trouble with sound?

Change -- The program I test with is Dragon NaturallySpeaking. Yesterday's Ubuntu updates produced a rash of pulseaudio changes, and suddenly alsa works with wine, without stumbling. Today's secret to making it work: In System/Preferences/Startup applications, uncheck pulseaudio sudo apt-get install esound sudo nano /etc/pulse/client.conf autospawn = no Then every time your computer

I have a USB soundcard that I have tried to run with Dragon NaturallySpeaking. It doesn't work unless I set winecfg to oss instead of alsa. Is this normal? Am I doing something wrong? How do I get alsa over USB? Thanks, Susan Cragin

I have sound problems in Ubuntu Studio, starting yesterday. These may be caused by a Ubuntu bug, but I wanted to run them by wine users and see if anyone else is having a similar problem. My configuration: I use Ubuntu Studio. I installed it clean this morning, with default options. Then I purged pulseaudio (because pulseaudio does not work with wine) asoundconf list shows the following

>Hello, > >PulseAudio is not a problem. You can use the OSS Emulation of PA, it works perfectly. (I saw a test with Dragon NaturallySpeaking, and it seems imply that it's good, isn't it ?) > >I used padsp for a while when a beautiful project was born : WinePulse. I'm actually testing it with the main (and only) developer of this PulseAudio backend for Wine and recently

Wine requires direct access to sound device(s) to make sound. This is true for both ALSA and OSS driver back-ends. However most sound servers are not compatible with neither of these back-ends. This also true about pulse-audio - it is not fully compatible with Wine. If you using new distro (Fedora 8, Ubuntu 8.04, SuSE 11) and do not have sound you should: 1. Report problem to your distro support

Alsa audio started working a couple of days ago with wine and then stopped working yesterday. Here is my experience. Pulseaudio cannot be removed any more. So I reinstalled the system and left it there. I compiled wine git and installed, and then installed DNS 10. Then I re-booted, ran killall pulseaudio in terminal, and started the program with winecfg's sound set to alsa. Everything

Mine doesn't appear to work? It might be just me. Would someone confirm if this is a bug?

Susan Cragin wrote: > When I run Audacity for Windows (the 1.13 beta) under wine, the "default" sound system does not work. > I have to select "MIME" and "Wine Sound Mapper." > > Wine Sound Mapper does work, but isn't wine supposed to use the "default" sound system as primary, and if that has changed, how come winecfg can't find the

Comments? http://insanecoding.blogspot.com/2009/06/state-of-sound-in-linux-not-so-sorry.html

I upgraded to karmic yesterday, and ran winecfg. The list of possible sound systems has shrunk to three: oss, jack and eSound. I tried running winecfg plain, and with padsp and pasuspender prefixes. Susan

I have been having audio trouble lately, for the past week or so. I don't know why. When I turn on sound input, then turn it off, then on again, the program either freezes or just stops working. What I want to know, is if any other wine users have been having troubles like mine recently, and what they have done about it? I have tried with pulseaudio purged, and using pasuspender. Those both

Hello guys, i have a sound problem with Wine 1.0.1 (is the same on every version) on Ubuntu Linux v9.04, when i start play some game for Windows, like Counter-Strike 1.6, in the beginning i have perfect sound, but when i'm playing more than 10-15 minutes and my sound disappeares, when i restart the game, the sound is back, but happens again in 10-15 minutes, any ideas ? :?

>Susan Cragin wrote: >> When I run Audacity for Windows (the 1.13 beta) under wine, the "default" sound system does not work. >> I have to select "MIME" and "Wine Sound Mapper." >> Wine Sound Mapper does work, but isn't wine supposed to use the "default" sound system as primary, and if that has changed, how come winecfg can't

My sound card was working fine until yesterday. Now I get this when I open winecfg. Any ideas? Guesses? Suggestions? ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: Permission denied Susan

Forwarding this to wine-users, I made a mistake while sending. Gardou J?r?me <jgardou at yahoo.fr> a ?crit : Date: Fri, 14 Mar 2008 14:09:42 +0100 (CET) De: Gardou J?r?me <jgardou at yahoo.fr> Objet: RE : [Wine] getting a Creative Soundblaster card to work ?: Susan Cragin <susancragin at earthlink.net> Cc: wine-user at winehq.org Susan Cragin <susancragin at

I use Intrepid Studio, and have all updates as of today (29-Oct). As of a few days ago, my distro does not shut down or start cleanly. It is because I have removed pulseaudio. The same thing happens on shutdown when I have pulseaudio stopped with pactl exit. Has anyone else experienced this? If so, what is the workaround when using wine? pasuspender wine application.exe ?? Thanks. Susan

I have no sound in wine. I open my application (Dragon NaturallySpeaking) and it says the device is not responding. (Neither the mike jack nor the USB pod.) When I run winecfg I get the following message. fixme:wave:ALSA_ComputeCaps Device has a minimum of 2 channels fixme:mixer:ALSA_MixerInit No master control found on ThinkPad Console Audio Control, disabling mixer So it appears that my mixer

I have noticed a significant deterioration in incoming sound quality recently, and was wondering if anyone else had the same experience. (I build git and re-install the programs on a new config daily.) I run Dragon NaturallySpeaking 10, which grades microphone sound on a range of 1 to (I think) 45. I used to get a score of about 26-28 just a couple of weeks ago, but now it's down to about

Yesterday's Ubuntu updates produced a rash of pulseaudio changes, and suddenly alsa works with wine, without stumbling. Today's secret to making it work: In System/Preferences/Startup applications, uncheck pulseaudio sudo apt-get install esound sudo nano /etc/pulse/client.conf autospawn = no Then every time your computer starts, run killall pulseaudio in terminal first. (Because the

This is one of those nasty answers. If you are running pulseaudio switching to emulation for directsound then it works. This is most likely not a bug in wine. But a bug in pulseaudio provided version of alsa interface. If you not running pulseaudio so just alsa direct problem can be wine. But due to varation in quality of alsa drivers it might be an alsa driver bug. Please not pasuspender is