similar to: Anyone else having trouble with inbound audio start/stop/start?

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 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

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

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

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

>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

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

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

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

Pulseaudio works great in wine using the modified wine from the Neill Aldur ppa. Tried everything else (padsp, pasuspender, blah) and nothing would work reliably. Some crashes when another application outputs sound, sometimes the sound does not work at all, sometimes it is awfully slow or with latency varying while recording, leading to unpredictable offsets in recorded files. Using pulseaudio

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

>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

Updated git last night (been compiling fine for years), and now get: ../../tools/widl/widl -I. -I. -I../../include -I../../include -D__WINESRC__ -h -H ../../include/wtypes.h ../../include/wtypes.idl make[2]: ../../tools/widl/widl: Command not found make[2]: *** [../../include/wtypes.h] Error 127 Made

My apologies beforehand if this is a common issue, but I have next to no experience with Ubuntu. I have a regular microphone hooked into my MoBo onboard sound and it works fine in Ubuntu (tested using a sound recorder). When I launch Steam, and any game within, I cannot get my microphone to work. I haven't tested this in other programs in WINE since I don't have anything else installed

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'm using wine 1.1.18 on Ubuntu Intrepid 32 bit and cannot access the "Drive" folder in winecfg while using ".wine" folder created with this release. while creating it, the terminal shows the error: err:process:__wine_kernel_init boot event wait timed out and when accessing the Drive Tab it says: err:winecfg:open_mountmgr failed to open mount manager err 2 after i

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

And to get it all, use it like this : sudo make 2>&1 &>somelogfile or even better sudo make 2>&1 |tee somelogfile to see the messages and have them recorded at the same time. Kind regards,Sylvain Petreolle (aka Usurp) Support artists, not multinationals - http://Iwouldntsteal.net Supportez les artistes, pas les multinationales - http://Iwouldntsteal.net ----- Message

Note to admins: Please, read through my whole post this time before deleting it. You will be surprised to find out that I have already tried all solutions detailed in the stickies. If you still think that this topic should be deleted, please be kind enough to notify me why, so that I would know how to proceed about getting help with my problem. Thank you. I have 64-bit OpenSUSE 12.1 and I have