| |||||||||||||
GStreamer: Past, present, and futureGStreamer: Past, present, and futurePosted Oct 27, 2010 17:49 UTC (Wed) by baldridgeec (guest, #55283)In reply to: GStreamer: Past, present, and future by gmaxwell Parent article: GStreamer: Past, present, and future
Ever done live mixdowns of 16-channel audio with separate effects pipelines running per channel? Some people do real audio work with Linux, and it is quite capable if set up properly.
The issues you're talking about are somewhat annoying for desktop audio, but that's not the only use case that has to be considered. Pulseaudio has been getting better - I like that it knows enough to get out of the way of JACK-enabled applications now.
(Log in to post comments)
GStreamer: Past, present, and future Posted Oct 27, 2010 18:09 UTC (Wed) by drag (subscriber, #31333) [Link]
Another example is if your using it for something like VoIP.
If you want to be able to do voicemail, conferences, transfer phones, put people on hold, work with multiple protocols, hook into a T1 or POTS and all that then your VoIP system is going to require a backend that can handle manipulating audio and transcoding between different formats.
Sure most of the audio formats used in VoIP are uncomplicated, to say the least, but if your handling a call center with a 100 phones with the multiple voice bridges and all that stuff then it adds up pretty quick.
Then another issue is the sound cards itself. Sounds cards only support certain audio formats and your going to have to be able to support a multitude if your going have a efficient way of outputting to the real world.
|
|||||||||||||