Also let's be clear about this. On OSX , Csound has three
audio IO modules available:

jack (librtjack.dylib)
portaudio (librtpa.dylib, the default)
coreaudio (librtcoreaudio.dylib)

All three use OSX's underlying audio API, coreaudio. The last one
in the list was written specifically to use it directly, whereas the others
are using libraries that themselves use the coreaudio framework.

I hope this clarifie the issue. Having one module named 'coreaudio'
surely confuses things... (I should have known better).

Note that similar setups exist on Linux (jack, alsa and portaudio, all using
alsa) and Windows (mme and portaudio, both possibly using mme).

Victor

----- Original Message ----- 
From: "DavidW" 
To: "Developer discussions" 
Sent: Monday, March 31, 2008 8:50 PM
Subject: Re: [Cs-dev] Manual redraft: Building Csound: all platforms


If this is the case, as Victor suggests, then let's be specific:

Perhaps:
Real-time audio can use CoreAudio or PortAudio.
To use Jack it must be explicitly set as a Command Option for the
build, irrespective of which real-time option is selected."

I haven't tested the accuracy of this.

David

On 01/04/2008, at 3:21 AM, Andres Cabrera wrote:
> I think the wording implies that Jack even though it goes through
> CoreAudio is a separate interface from Csound's point of view, so I
> think the wording fits. (i.e. you can build the Jack rt module without
> building the CoreAudio module, is this correct?)
>
> Any suggestions?
>
> Cheers,
> Andrés
>
>
> On Mon, Mar 31, 2008 at 7:18 AM, DavidW  wrote:
>> Builds now, thanks Anrés,
>> Small correction:
>> Under OSX heading
>>
>>> Mac OS X
>>> Optional configurations for Mac OS X include the following:
>>>
>>>      • Real-time audio can use CoreAudio (OSX builtin native audio
>>> system) and Jack, appart from PortAudio.
>>
>>
>> Suggest this instead:
>> Mac OS X
>>
>>        • Real-time audio can use CoreAudio (OSX builtin native
>> audio system)
>> or PortAudio
>>        * Jack support requires Portaudio (i.e. will not work with
>> CoreAudio)
>>
>>
>>
>> On 31/03/2008, at 1:57 PM, Andres Cabrera wrote:
>>> My bad, I committed a broken file. It should be fixed now.
>>> Cheers,
>>> Andres
>>>
>>>
>>> On Sun, Mar 30, 2008 at 6:09 AM, DavidW  wrote:
>>>> Hey thanks _very_ much for doing this Anrés, I had intended to do
>>>> it,
>>>> but having to learn docbook etc formats slowed me up.
>>>> You'll notice that the very last row of the table of compile
>>>> options
>>>> "PythonVersion" is out of alphabetic order. I put it there
>>>> because it
>>>> is the only non-boolean.
>>>> Perhaps it should go at the top, outside the table, as follows:
>>>>
>>>> "When building csound, the version of python used to do the build
>>>> can
>>>> be set with the  Custom Variable PythonVersion. For example
>>>> PythonVarable = 2.4. All other Custom Variables are set out in
>>>> Table
>>>> 4, below."
>>>>
>>>> I can't see the latest updates from today's feedback because  I'm
>>>> getting a make error when trying to compile the latest CVS:
>>>> ...
>>

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel 


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Well I'm glad that's been cleared up! I can't test any of it at the mo
  - is SConstruct still broken?
I tried scons SConstruct  (no options) and I get an opcode build error
scons SConstruct2 tells me there's nothing to build!

Anyway, another question about the Buildin Csound man. entry:
The Custom Variable 'generatePDF'
SConstruct says:
>     print 'CONFIGURATION DECISION: Generating Csound API PDF  
> documentation.'
>     refmanTex = commonEnvironment.Command('doc/latex/refman.tex',  
> 'Doxyfile', ['doxygen $SOURCE'])


~scound5/doc/latex/refman.tex dosn't exist. Is that right?

Given that the manual seems to be a separate CVS 'leg'  is there  
anywhere which says where it should be installed wrt csound5 sources?
(I've just been using a completely separate directory to csound5.)

David

On 01/04/2008, at 7:05 AM, victor wrote:
> Also let's be clear about this. On OSX , Csound has three
> audio IO modules available:
>
> jack (librtjack.dylib)
> portaudio (librtpa.dylib, the default)
> coreaudio (librtcoreaudio.dylib)
>
> All three use OSX's underlying audio API, coreaudio. The last one
> in the list was written specifically to use it directly, whereas the  
> others
> are using libraries that themselves use the coreaudio framework.
>
> I hope this clarifie the issue. Having one module named 'coreaudio'
> surely confuses things... (I should have known better).
>
> Note that similar setups exist on Linux (jack, alsa and portaudio,  
> all using
> alsa) and Windows (mme and portaudio, both possibly using mme).
>
> Victor


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net