what I am saying is that on Linux there are two
output modules, portaudio (default) and alsa; if you run
csound with -+rtaudio=alsa you will use the alsa
module. The code for the latter is in InOut/rtalsa.c
and is pretty efficient IMHO.

Victgor

>
> Sorry about that - the message wasn't meant to go to the
> list. :(
>
> The ALSA specific code was written to circumvent the need
> for   PortAudio.  You're saying there's an easy way to
> access the methods   for using ALSA via the API without
> using a Csound Instance?  (I'm   summing a group of
> instances and sending that summed set of samples   out to
> the DAC)
>
> greg
>
> On Aug 25, 2007, at 2:01 PM, Victor Lazzarini wrote:
>
> > But what about Istvan's alsa module; we were never
> > dependent on portaudio, in fact I never use portaudio
> > on Linux; Istvan's module is way faster.
> > Isn't this a bit of reinventing-wheel kind of thing?
> >
> > Victor
> >>
> >>
> >> So last night and this morning I wrote a simple ALSA
> >> specific audio I/  O module for the server.  I think
> its a >> bit of a speed improvement,   but mainly it means
> we're >> not dependent on PortAudio for the XO which   is
> a problem >> because they haven't updated to the latest
> port audio >> release which means none of my code can be
> built (easily) >> on the XO   without manually installing
> portaudio.  Now my >> server should be   compile-able on
> any XO with the >> following command and assuming they
> have my sources in a >> folder (and gcc and
> alsa-lib-devel.i386 yum   installed): >>
> >> gcc main.c -o csoundserver -I ./include -I/usr/include/
> >> -I/usr/  include/csound/ -DLINUX -lm ./src/*.c
> >> /src/Sequencer/*.c -lasound  /
> usr/lib/libcsound.so.5.1 >> /usr/lib/libsndfile.so.1
> >>
> >> Anyway - Ive been running a few more tests .. I have
> the >> 16k   "02GMGSBank1.sf2" fluid example running
> beet5.mid >> and it does pretty   well most of the time -
> but it >> definitely hits sections of the piece   that
> spike the cpu >> to 100% which does cause occasional
> dropouts. >>
> >> My new code will be posted up on the dev.laptop.org
> site >> by the end   of the day.  So we can at least
> inform the >> TamTam group about it and   maybe they can
> even install >> and test the server.
> >>
> >> greg
> >>
> >>
> >>
> ----------------------------------------------------------
> >> --------------- This SF.net email is sponsored by:
> Splunk >> Inc. Still grepping through log files to find
> problems? >> Stop. Now Search log events and configuration
> files using >> AJAX and a browser. Download your FREE copy
> of Splunk now >>>>  http://get.splunk.com/
> >>
> >>
> >> _______________________________________________
> >> Csound-devel mailing list
> >> Csound-devel@lists.sourceforge.net
> >>
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >> >
> >
> ----------------------------------------------------------
> > ------------  ---
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?
> > Stop. Now Search log events and configuration files
> > using AJAX and a   browser.
> > Download your FREE copy of Splunk now >>
> > http://get.splunk.com/
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Right - I know about the rtaudio modules.  I'm mixing multiple  
instances of Csound in my server.  I wasn't sure if you were  
suggesting that I use the API somehow.  If I was just using one  
instance, I could pass that in with the command line settings to the  
instance, but since I'm using multiple instances I can't imagine how  
it could be done

OR  if you're suggesting I rip the code out of rtalsa.c, that might  
work, but I have a working version now .. seems to be mildly  
efficient, so ... I'll post a link to the code as soon as the git  
repo starts behaving.

greg


On Aug 25, 2007, at 6:06 PM, Victor Lazzarini wrote:

> what I am saying is that on Linux there are two
> output modules, portaudio (default) and alsa; if you run
> csound with -+rtaudio=alsa you will use the alsa
> module. The code for the latter is in InOut/rtalsa.c
> and is pretty efficient IMHO.
>
> Victgor
>
>>
>> Sorry about that - the message wasn't meant to go to the
>> list. :(
>>
>> The ALSA specific code was written to circumvent the need
>> for   PortAudio.  You're saying there's an easy way to
>> access the methods   for using ALSA via the API without
>> using a Csound Instance?  (I'm   summing a group of
>> instances and sending that summed set of samples   out to
>> the DAC)
>>
>> greg
>>
>> On Aug 25, 2007, at 2:01 PM, Victor Lazzarini wrote:
>>
>>> But what about Istvan's alsa module; we were never
>>> dependent on portaudio, in fact I never use portaudio
>>> on Linux; Istvan's module is way faster.
>>> Isn't this a bit of reinventing-wheel kind of thing?
>>>
>>> Victor
>>>>
>>>>
>>>> So last night and this morning I wrote a simple ALSA
>>>> specific audio I/  O module for the server.  I think
>> its a >> bit of a speed improvement,   but mainly it means
>> we're >> not dependent on PortAudio for the XO which   is
>> a problem >> because they haven't updated to the latest
>> port audio >> release which means none of my code can be
>> built (easily) >> on the XO   without manually installing
>> portaudio.  Now my >> server should be   compile-able on
>> any XO with the >> following command and assuming they
>> have my sources in a >> folder (and gcc and
>> alsa-lib-devel.i386 yum   installed): >>
>>>> gcc main.c -o csoundserver -I ./include -I/usr/include/
>>>> -I/usr/  include/csound/ -DLINUX -lm ./src/*.c
>>>> /src/Sequencer/*.c -lasound  /
>> usr/lib/libcsound.so.5.1 >> /usr/lib/libsndfile.so.1
>>>>
>>>> Anyway - Ive been running a few more tests .. I have
>> the >> 16k   "02GMGSBank1.sf2" fluid example running
>> beet5.mid >> and it does pretty   well most of the time -
>> but it >> definitely hits sections of the piece   that
>> spike the cpu >> to 100% which does cause occasional
>> dropouts. >>
>>>> My new code will be posted up on the dev.laptop.org
>> site >> by the end   of the day.  So we can at least
>> inform the >> TamTam group about it and   maybe they can
>> even install >> and test the server.
>>>>
>>>> greg
>>>>
>>>>
>>>>
>> ----------------------------------------------------------
>>>> --------------- This SF.net email is sponsored by:
>> Splunk >> Inc. Still grepping through log files to find
>> problems? >> Stop. Now Search log events and configuration
>> files using >> AJAX and a browser. Download your FREE copy
>> of Splunk now >>>>  http://get.splunk.com/
>>>>
>>>>
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>>
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>
>> ----------------------------------------------------------
>>> ------------  ---
>>> This SF.net email is sponsored by: Splunk Inc.
>>> Still grepping through log files to find problems?
>>> Stop. Now Search log events and configuration files
>>> using AJAX and a   browser.
>>> Download your FREE copy of Splunk now >>
>>> http://get.splunk.com/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi greg,

I don't know if I'm getting you, but you can use alsa from the API, just 
like you use portaudio, you need to pass rtaudio=alsa as options (e.g. 
in the CsOptions tag of the csd file).

Cheers,
Andres


Greg Thompson escribió:
> Right - I know about the rtaudio modules.  I'm mixing multiple  
> instances of Csound in my server.  I wasn't sure if you were  
> suggesting that I use the API somehow.  If I was just using one  
> instance, I could pass that in with the command line settings to the  
> instance, but since I'm using multiple instances I can't imagine how  
> it could be done
>
> OR  if you're suggesting I rip the code out of rtalsa.c, that might  
> work, but I have a working version now .. seems to be mildly  
> efficient, so ... I'll post a link to the code as soon as the git  
> repo starts behaving.
>
> greg
>
>
> On Aug 25, 2007, at 6:06 PM, Victor Lazzarini wrote:
>
>   
>> what I am saying is that on Linux there are two
>> output modules, portaudio (default) and alsa; if you run
>> csound with -+rtaudio=alsa you will use the alsa
>> module. The code for the latter is in InOut/rtalsa.c
>> and is pretty efficient IMHO.
>>
>> Victgor
>>
>>     
>>> Sorry about that - the message wasn't meant to go to the
>>> list. :(
>>>
>>> The ALSA specific code was written to circumvent the need
>>> for   PortAudio.  You're saying there's an easy way to
>>> access the methods   for using ALSA via the API without
>>> using a Csound Instance?  (I'm   summing a group of
>>> instances and sending that summed set of samples   out to
>>> the DAC)
>>>
>>> greg
>>>
>>> On Aug 25, 2007, at 2:01 PM, Victor Lazzarini wrote:
>>>
>>>       
>>>> But what about Istvan's alsa module; we were never
>>>> dependent on portaudio, in fact I never use portaudio
>>>> on Linux; Istvan's module is way faster.
>>>> Isn't this a bit of reinventing-wheel kind of thing?
>>>>
>>>> Victor
>>>>         
>>>>> So last night and this morning I wrote a simple ALSA
>>>>> specific audio I/  O module for the server.  I think
>>>>>           
>>> its a >> bit of a speed improvement,   but mainly it means
>>> we're >> not dependent on PortAudio for the XO which   is
>>> a problem >> because they haven't updated to the latest
>>> port audio >> release which means none of my code can be
>>> built (easily) >> on the XO   without manually installing
>>> portaudio.  Now my >> server should be   compile-able on
>>> any XO with the >> following command and assuming they
>>> have my sources in a >> folder (and gcc and
>>> alsa-lib-devel.i386 yum   installed): >>
>>>       
>>>>> gcc main.c -o csoundserver -I ./include -I/usr/include/
>>>>> -I/usr/  include/csound/ -DLINUX -lm ./src/*.c
>>>>> /src/Sequencer/*.c -lasound  /
>>>>>           
>>> usr/lib/libcsound.so.5.1 >> /usr/lib/libsndfile.so.1
>>>       
>>>>> Anyway - Ive been running a few more tests .. I have
>>>>>           
>>> the >> 16k   "02GMGSBank1.sf2" fluid example running
>>> beet5.mid >> and it does pretty   well most of the time -
>>> but it >> definitely hits sections of the piece   that
>>> spike the cpu >> to 100% which does cause occasional
>>> dropouts. >>
>>>       
>>>>> My new code will be posted up on the dev.laptop.org
>>>>>           
>>> site >> by the end   of the day.  So we can at least
>>> inform the >> TamTam group about it and   maybe they can
>>> even install >> and test the server.
>>>       
>>>>> greg
>>>>>
>>>>>
>>>>>
>>>>>           
>>> ----------------------------------------------------------
>>>       
>>>>> --------------- This SF.net email is sponsored by:
>>>>>           
>>> Splunk >> Inc. Still grepping through log files to find
>>> problems? >> Stop. Now Search log events and configuration
>>> files using >> AJAX and a browser. Download your FREE copy
>>> of Splunk now >>>>  http://get.splunk.com/
>>>       
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>>
>>>>>           
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>       
>>> ----------------------------------------------------------
>>>       
>>>> ------------  ---
>>>> This SF.net email is sponsored by: Splunk Inc.
>>>> Still grepping through log files to find problems?
>>>> Stop. Now Search log events and configuration files
>>>> using AJAX and a   browser.
>>>> Download your FREE copy of Splunk now >>
>>>> http://get.splunk.com/
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>>         
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>       
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>   

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net