It's certainly an RTFM thing, but last time I didn't know how to get PulseAudio to go away. I wrote a shell script to keep killing it in a loop (since it restarts itself) long enough to get JACK to take over. I know there must be better ways...
Then inevitably once I've got JACK setup, I'll want to play some background music or watch some Flash video online without tearing down my JACK setup. Oops, does that audio player support JACK natively? Do I have that plugin installed? Can I run Pulse and have it direct output into JACK? None of this has worked smoothly in my experience.
> users of JACK generally buy high-end hardware specifically for that purpose and know what they're doing
This has not been my experience. I love to dabble, but apparently don't know what I'm doing.
Two weeks ago, I spent 20 minutes with 3 KXStudio Laptops and a master KXStudio workstation, and got all the laptops acting as input slaves to pipe live instruments and mics to Ardour running on the workstation using Opus as the transferring codec. all it took was loading the network module into JACK, and making sure there was gigE/cat6 for networking. we had mp3's and FLAC's of the concert ready for the band to review before their roadies were done packing up the gear.
As for high-end hardware, the laptops are using M-Audio Fast Track Pros and 10/10's. None of the hardware goes for more than $150, and we're using ultra-cheap AMD Fusion laptop slaves sourced from alibaba with an AMD A10-based workstation as master. We're at $2800, including 3 monitors.
Because an AMD A10 with 12GB of RAM is stupid overpowered for audio production, we installed MacOS X via KVM and routed that output through JACK as well. WINE loads quite a few professional digital audio workstation packages, and a ton of VSTs, and wineasio makes them all work with JACK. Running all this emulation doesn't make the system feel sluggish at all.
the main website is http://kxstudio.sourceforge.net, but the LiveCD downloadable there is based on Ubuntu 12.04. I installed raring, added the PPA's, and then installed packages. I like bleeding edge. but the official livecd is _very_ painless to install if you're having headaches configuring.
Thanks for the link!
In case anyone is interested: I'm using them on Arch, they are available through the AUR.
* Turning off auto-respawn (from 2010, not sure if it's entirely accurate): http://www.linuxplanet.com/linuxplanet/tutorials/7130/2
* Script I used to use to get Skype and PulseAudio to play nice in the early days of PA: http://ubuntuforums.org/showthread.php?t=790889
[1] http://en.wikipedia.org/wiki/Zero_configuration_networking
> It's certainly an RTFM thing, but last time I didn't know how to get PulseAudio to go away
`pulseaudio -k`Typically when I want a quick-and-dirty "kill PulseAudio for real" solution I move /usr/bin/pulseaudio to /usr/bin/pulse-dead, issue pkill pulseaudio, and proceed until I want PA to come back to life, at which time I mv the binary back.
pasuspender paususpender while true
do
done pasuspender catSo, in other words, it really is. All you said was just rephrasing the problem as solved.
For one, what's "exceedingly rare" is not getting any sound at all. That doesn't mean you get to enjoy all the features of your soundcard (from mixing panels to 3D audio and such). Or that it work without tinkering in ALL programs and across desktop environments.
There's also the issue of more professional sound work, which will be a world of pain. Getting any pro, multi-channel soundcards to work and such.
For anything else than basic sound playing, from recording a podcast, to streaming, to using a DAW etc, here be dragons.
This legacy hampers Android too, which is a joke when it comes to multimedia APIs compared to the oligarchic iOS.
In many ways, OS X has shown us the ideal distribution. It's based on open technology and continually adopts new technology as it proves itself, but Apple is not afraid to integrate tightly and replace components with well-engineered, well-tested replacements as necessary (the origination of the divergence between X11 and Quartz), as long as it means a solid, unified, consistent and functional experience for their users.
We need that now. Canonical fancies themselves after that pattern but I don't believe they take the needed organization seriously enough and I don't believe they have the technical expertise necessary to really make the tough calls and implement a technically-sound user-centric system (see: Mir). They need to get some new leadership in there.
My needs are simple: I want sound from my audio player (MOC), from my browser (f.e. Youtube), from games and they shouldn't interfere. So my audio player shouldn't have exclusive access to the device and prevent me from hearing Youtube at the same time.
JACK does all this, is easy to configure and doesn't get in the way.
edit: I should mention I run Debian Testing and prefer to stay away from big desktop environment like Gnome (do we see a trend here?).
I think the last time I ever had this problem was literally around 12 years ago, and it was caused by me fiddling with my alsa conf file. I haven't touched any ALSA related settings or done anything special in the last ~8 years, and I never have a problem with things like playing music and having a browser flash plugin using audio at the same time.
Not saying it doesn't happen to other people. Just genuinely curious and baffled.
I thought the way it was supposed to work was, when testing gets re-tagged as stable, there's no 'testing' for a brief period (month?) until the next planned distro release is named.
For a moment of time (we're talking hours), testing and stable have the same set of packages. Britney, the software which migrates packages from unstable to testing, runs four times a day. During a freeze, it is configured to need "unblock exceptions" to migrate packages. When this is option is disabled, the following britney run will make the first difference between testing and stable.
testing is testing. it points to the version that is on testing, be it 7-wheezy, or 8-whatever.
the only exception to the rule is 'sid'. debian sid is always the bleeding edge, it never becomes a proper version.
btw, i hate every versioning alias scheme that does not force the number to appear. such as debian, ubuntu, android... it's all just idiotic.
Now consider trying to make similar determinations if you know you're running "Gingerbread" but the latest version is "Jelly Bean", or if you're on "Intrepid Ibex" and the latest version is "Raring Ringtail".
It's even worse on Ubuntu, where they've chosen a reasonable, useful numerical versioning system (year.month), but then obscure it with stupid codenames.
IMO it's also much more difficult to remember the codenames. I had to verify that Android 4.2 was still called Jelly Bean and though I knew the latest Ubuntu was 13.04, I had to look up its codename altogether.
The fact that these projects continue to have underlying "developer use only"-type numerical versions only further emphasizes the utility of these. The codenames feel like a poorly-conceived marketing thing. I don't think most people have trouble remembering a coupled software package with a version number, like "Windows 7". I don't think they often say, "Oh crap, I know I had version 4 of something ... was it Android or Windows?"
"debian 7"
with the quote marks fix that issue?If they really wanted to improve UI, it would also be in the 'system settings' link under the username on the desktop panel- for users that run desktops.
Now, this phone runs android Diabetes, and you want a feature introduced in android Cavity. Should I buy this one? I don't f#&$%#& know!
There are actually 2 low level audio stacks that apps can use in Linux, OSS and ALSA. Only OSS offers great sound and low latency,[2] but the kernel developers have refused to add the free GPL'd OSSv4 updates into the kernel, so we are all stuck with OSSv3 legacy and ALSA's latency and poor design decisions. Using the PA layer only makes the latency situation worse and added another layer for things to go wrong.
[1]http://www.phoronix.com/scan.php?page=news_item&px=MTEyO...
[2]http://insanecoding.blogspot.hk/2009/06/state-of-sound-in-li...
Is the problem people trying to play sounds for games over the network with pulseaudio? Is that use-case really something that needs to be worried about?
My condolences. I also have that one and solved the problem by shoving a cheap second hand Creative SB Audigy in the PCI slot. And It still crackles and pops and messes up every time skype makes a sound.
Edit: to clarify, using a PCI soundcard solved the crackling and popping in every application except skype, which I find acceptable for now, since I don't usually talk on skype. I might experiment with using JACK and somehow routing pulse through that.
>Is it possible to use/set environment variables to change the default ALSA device?
>you can use ALSA_PCM_CARD or ALSA_CARD to set the default card, either by name or by number. If both are set, ALSA_PCM_CARD takes precedence. The device on the card can be set in the variable ALSA_PCM_DEVICE.
Anyway, no pulseaudio, simple usb soundcard/dac based on Burr-Brown from TI[1] - and now (software) mixing of audio works across youtube/html5 audio in iceweasel (21.0~b6-1 from "deb http://mozilla.debian.net/ experimental iceweasel-beta"), vlc and flash audio in chromium[2]. All that was needed in the end, was the following ~/.asoundrc:
# Aliases for the devices. I don't use the onboard audio -
# terribly noisy. The names (after card) come from
# /proc/asound/cards - see [1]
pcm.nvidia { type hw; card NVidia; }
ctl.nvidia { type hw; card NVidia; }
pcm.usb { type hw; card DAC; }
ctl.usb { type hw; card DAC; }
# If all you want is use usb as default,
# uncomment this, and ignore the rest.
#pcm.!default pcm.usb
ctl.!default ctl.usb
# For software mixing - allowing several programs to play audio
# at the same time:
#dmix for software mixing - http://alsa.opensrc.org/Dmix
pcm.!default {
type plug
slave.pcm "dmixer"
}
pcm.dmixer {
type dmix
ipc_key 1024 # must be unique!
slave {
pcm "hw:DAC"
}
}
Now, I've also realized that the main reason I started fighting with
this, was the delay introduced by pulsaudio, which is only a problem for
me in vlc -- and that could've been fixed (probably) by using the
tools->Track synchronization menu options. Just in case anyone else has
synchronization issues.I currently don't do any gaming (except for Angband...) -- or other synchronization-sensitive multimedia.
[1] according to /proc/asound/cards: 0 [DAC ]: USB-Audio - USB Audio DAC Burr-Brown from TI USB Audio DAC at usb-0000:00:0b.0-3, full speed
[2] Apparently html5 audio (at least in videostreams) is broken in chromiumr. Flash video (from eg regular non-html5-youtube) works fine for me with this set up. Some more details at: http://code.google.com/p/chromium/issues/detail?id=178626
[edit: minor corrections]
I believe you are mistaken. The BSDs have always avoided all the freakish audio framework nonsense from linux land. They provide an API that is somewhat compatible with OSS to allow software with linuxisms like assuming OSS to function. That API is a wrapper around the real audio system: http://www.openbsd.org/cgi-bin/man.cgi?query=ossaudio&ap...
So there are three major components for different purposes. Core audio support is the domain of ALSA itself and Linux does a good job with it. PulseAudio provides advanced capabilities on top of the more basic/hardware-oriented functionality in ALSA, and JACK provides low-latency audio for realtime applications that need it (not games, only really audio processing equipment). With large amounts of work the partial redundancy between these components could be removed, but it's really not a big issue; for desktop or professional use getting things to work right isn't too hard.