[Interopcast-general][icecast-dev] about translatingdocumentation, but not only documentation.

[Likai Liu]

Michael Smith wrote:

>I'm less sure about 'audiocompress'. Perhaps a general-purpose (possibly using 
>LADSPA, or something else) audio-manipulation pipeline, to which 
>AudioCompress could be one option? 
>  
>
I agree that it would have been better to have audiocompress ported as 
an LADSPA plugin. My initial impression after taking look at their 
source code is that it shouldn't be so much of a trouble other than 
fulfilling LADSPA's formals. But what is stopping me at this moment is 
exactly the problem with dlfn on Mac OS X.

There are two paths towards PortAudio integration. One is to directly 
modify im_oss.c to use the PABLIO (blocking I/O subset of PortAudio) and 
forget about callbacks. This is the easiest method but has the 
disadvantage that the same audio buffer is copied perhaps at least 2-3 
times. The second one is to rewrite IceS based on callbacks, or perhaps, 
based entirely on PortAudio, so we don't have to worry about supporting 
different sound I/O APIs -- this option is probably quite controversial.

I've heard of JACK support on PortAudio, though the recent stable V18.1 
release still doesn't have it. Another problem with PortAudio is that, 
as of V18.1, supports only one host sound I/O method per compilation. 
This means the user can't select which sound I/O to use, should more 
than one is available, other than the one that is compiled in. V19 will 
remedy these issues altogether. It seems wise to wait for PortAudio V19 
to become a stable release.

liulk

--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to 'icecast-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.