3 ms·

It's as right now as it was 5 years ago, and has a lot of corrolary with other customer-facing, resource-constrained software maintenance environments that you

by mpyne 14y ago

It's as right now as it was 5 years ago, and has a lot of corrolary with other customer-facing, resource-constrained software maintenance environments that you might see from a YC participant. And I say this as a Linux user who doesn't use PulseAudio...

klodolph 14y ago
As a user who avoided Pulse for years, I feel your pain. But since I started writing audio apps for Linux, I realized that the Pulse Audio API is the least broken way to do audio on Linux. It is very comparable to Core Audio and DirectSound in terms of the most relevant features. ALSA should just give hardware access but instead it is bloated with plugins and tries to do everything. There's really no excuse for not doing mixing and sample rate conversion in userspace (not all hardware can do it) and an audio server just makes more sense than plugins for client applications.
- tomrod 14y ago
  I don't mean to threadjack. I'm curious what apps you've put out. I'm a sound neophyte, occasionally play with Audacity, but interested in doing more advanced stuff. I just wanted to point out that I'd love to see any technical blogs/howtos you may have put together, or any top notch stuff you may have come across. Thanks! /threadjack
jebblue 14y ago
>> And I say this as a Linux user who doesn't use PulseAudio... PulseAudio works great in Linux? We can switch easily between a headset mic, web cam mic, builtin mic, etc. I think this is still problematic on Windows.
- shardling 14y ago
  Yeah, I still have problems with OS X not switching to USB speakers easily, when that worked with PulseAudio.
- mpyne 14y ago
  I do literally none of these things though. My speakers have a headphone port which works perfectly 100% of the time without needing an entire new sound server to route all audio through. There's a reason my sound has continued to work properly for years, and that's because I didn't "fix it" when it wasn't broken. ;)

by mpyne 14y ago

klodolph 14y ago

As a user who avoided Pulse for years, I feel your pain. But since I started writing audio apps for Linux, I realized that the Pulse Audio API is the least broken way to do audio on Linux. It is very comparable to Core Audio and DirectSound in terms of the most relevant features. ALSA should just give hardware access but instead it is bloated with plugins and tries to do everything. There's really no excuse for not doing mixing and sample rate conversion in userspace (not all hardware can do it) and an audio server just makes more sense than plugins for client applications.

tomrod 14y ago
I don't mean to threadjack. I'm curious what apps you've put out. I'm a sound neophyte, occasionally play with Audacity, but interested in doing more advanced stuff. I just wanted to point out that I'd love to see any technical blogs/howtos you may have put together, or any top notch stuff you may have come across. Thanks! /threadjack

jebblue 14y ago

>> And I say this as a Linux user who doesn't use PulseAudio... PulseAudio works great in Linux? We can switch easily between a headset mic, web cam mic, builtin mic, etc. I think this is still problematic on Windows.

shardling 14y ago
Yeah, I still have problems with OS X not switching to USB speakers easily, when that worked with PulseAudio.
mpyne 14y ago
I do literally none of these things though. My speakers have a headphone port which works perfectly 100% of the time without needing an entire new sound server to route all audio through. There's a reason my sound has continued to work properly for years, and that's because I didn't "fix it" when it wasn't broken. ;)