I have Ubuntu Studio Karmic with the real-time kernel.
I run Dragon NaturallySpeaking through wine, so I am most concerned with clear,
low-latency, incoming ("recording") sound.
I have edited /etc/alsa/client.conf to stop pulseaudio from re-spawning, and
killall pulseaudio after I log on.
Under winecfg:
If I select OSS the results are pretty good. It works. Sound quality seems a bit
worse than under ALSA (which used to work, pre-pulseaudio) but it's not bad.
If I select ALSA, the results are not good. No mixer shows up unless I install
esound (which uninstalls pulseaudio-esound-compat and ubuntu-studio-desktop).
Then a mixer shows up and my program shows an audio system present, but freezes
at the first incoming sound.
Sometimes after an update sound does not work.
Updates do not take kindly to tinkering.
This could be because of something to do with esound, it could be because I
tried to update without ubuntu-studio-desktop, or it could be because I set the
default soundcard using asoundconf.
As you probably know, Ubuntu has dropped asoundconf from Karmic, and I use the
one from Jaunty. (I put it under /usr/local/bin.)
To make sound work again, I must re-install the settings from pulseaudio, which
I do as follows:
sudo apt-get --purge remove pulseaudio
sudo apt-get install pulseaudio (and, if you want, all the other programs that
the above command uses; not all of them are re-installed)
Then it works.
This could be useful in case you sound suddenly goes out after an update, as
mine does.
As I said, I'm just documenting this as my experience. Comments? Anyone else
need really good incoming sound?
Do you use OSSv4? and if so what are your experiences with it so far? I've heard that it's much better then pulse audio. On Mon, Sep 21, 2009 at 6:04 PM, Susan Cragin <susancragin at earthlink.net> wrote:> I have Ubuntu Studio Karmic with the real-time kernel. > I run Dragon NaturallySpeaking through wine, so I am most concerned with clear, low-latency, incoming ("recording") sound. > > I have edited /etc/alsa/client.conf to stop pulseaudio from re-spawning, and killall pulseaudio after I log on. > > Under winecfg: > If I select OSS the results are pretty good. It works. Sound quality seems a bit worse than under ALSA (which used to work, pre-pulseaudio) but it's not bad. > If I select ALSA, the results are not good. No mixer shows up unless I install esound (which uninstalls pulseaudio-esound-compat and ubuntu-studio-desktop). > Then a mixer shows up and my program shows an audio system present, but freezes at the first incoming sound. > > Sometimes after an update sound does not work. > Updates do not take kindly to tinkering. > This could be because of something to do with esound, it could be because I tried to update without ubuntu-studio-desktop, or it could be because I set the default soundcard using asoundconf. > As you probably know, Ubuntu has dropped asoundconf from Karmic, and I use the one from Jaunty. (I put it under /usr/local/bin.) > To make sound work again, I must re-install the settings from pulseaudio, which I do as follows: > > sudo apt-get --purge remove pulseaudio > sudo apt-get install pulseaudio (and, if you want, all the other programs that the above command uses; not all of them are re-installed) > > Then it works. > This could be useful in case you sound suddenly goes out after an update, as mine does. > > As I said, I'm just documenting this as my experience. Comments? Anyone else need really good incoming sound? > > > > >
>Do you use OSSv4? and if so what are your experiences with it so far? >I've heard that it's much better then pulse audio.No. I just use alsa-oss emulation. My one effort to install OSSv4 under UbuntuStudio Karmic ended in a broken system. I'd like to re-try, when I have time. It looks so simple, but I'm so worried because Ubuntu has the sound so tightly bound up with Desktop and Metacity. I HATE pulseaudio being mandatory and non-removeable.
>>>Do you use OSSv4? and if so what are your experiences with it so far? >>>I've heard that it's much better then pulse audio. >> >> No. I just use alsa-oss emulation. >> My one effort to install OSSv4 under UbuntuStudio Karmic ended in a broken system. >> I'd like to re-try, when I have time. It looks so simple, but I'm so worried because Ubuntu has the sound so tightly bound up with Desktop and Metacity. >> I HATE pulseaudio being mandatory and non-removeable. > >Tell me about it. I have been using OSSv4 quite happily on Jaunty. I >have been holding out from upgrading to Karmic because I have working >sound and understand Ubuntu have gone with PulseAudio at the exclusion >of everything else. > >I would like to easily switch between different sound systems without >breaking the system I have. > >Have you tried switching to a KDE version of Ubuntu (do they support a >KubuntuStudio)? As I understand it, KDE has its own sound system, and >last I tried I had working sound through it. > >- ReeceThere is no kubuntu studio. I understand KDE uses aRTs and alsa. I've never tried it. I don't like KDE because there are too many applications that I don't want, and the interface is klunky. (The joke used to be... Gnome is for people who think they're running a Mac; KDE is for people who think they're running Windows.) Lots of people have suggested Xubuntu because that's lighter weight with the Xfce desktop and no pulseaudio. But I hate the look. And I don't use the default applications. But why not just add apps? Studio is mostly about a clean look and default packages. Why not install your own packages? You know what you want. When it's off the ground, I'm going for the fastest system possible, which I think will be Lubuntu, based on LXDE. Then just install the apps I need (including the realtime kernel), and remove the ones I don't. It has a taskbar (I hope it's moveable, since it's on the bottom). And I run many of my apps using ALT-F2 anyway. Why do I wait for Ubuntu's rather than just going with the current LXDE Debian version? Well... that's for another time... but there's some news going around that I think I'll repeat... what I remember of it. So I guess consider this mostly gossip. Ubuntu Lucid Lynx has just been announced. Well, some linux kernel developer whose name I forget wrote some patches to make the desktop run much faster, but at the expense of non-desktop services. The linux-kernel team rejected the patches, but Ubuntu may have them as an install option in Lucid. Sound latency is supposed to improve dramatically. Rumor has it, these patches are not incompatible with the existing real-time kernel, but I don't think anyone's tried it. I'm very excited.
>Well, some linux kernel developer whose name I forget wrote some patches to make the desktop run much faster, but at the expense of non-desktop services. The linux-kernel team rejected the patches, but Ubuntu may have them as an install option in Lucid. >Sound latency is supposed to improve dramatically. >Rumor has it, these patches are not incompatible with the existing real-time kernel, but I don't think anyone's tried it.The above refers to Con Kolivas' BFS scheduler. Google has a lot of information about it, if anyone is interested. I was probably wrong about it not being incompatible with the existing real-time kernel. Both use changes to the scheduler. S
You might consider leaving pulseaudio installed and installing aoss from synaptic. This causes alsa/oss emulation to behave well with pulseaudio. I've been using it for years and it works well enough. Just put aoss before any command you want to run using wine. It also works from desktop launcher icons and the like. Good luck.
vitamin wrote:> > jorl17 wrote: > > And that's usually all I need to do :) This is why I don't like Pulseaudio/Ubuntu hatred... > > I wonder what all you run under Wine? And what is your sound hardware. Don't forget different programs do different things.Well, yes, that's pretty much why many of us fail to have something run: Because of different hardware and conditions. In short, while I have never had issues, I probably have always had decent hardware and modules over here... I do recall one issue on a machine which I don't own anymore. It randomly crashed D3D with pulse, but I think it was something I did when I started using Wine and went all whacko with winetricks directx hehe. tparker: I have also never had issues with the microphone ;) On the contrary, under Wine, it works great! Skype, though, tends to go nuts with desyncs, which is why I have to give it direct hw access.