To end a command-line session, use ctl-C. In the GUI, either
'pause' or 'reset'. The Coreaudio module has problems with
MIDI in the GUI, but works perfectly in the command-line.
Portaudio works anywhere.

It's important to suppress display messages, because they
are
very costly on OSX (the graphics are very heavy on Macs). So
for
any MIDI RT performance that's a must. The GUI has the
advantage
that the messages can be turned ON/OFF during performance,
so
if you want to check for any problems, you can turn it on.
And when
they are off, they are actually pumped to the console (you
can open
it from 'utilities'), so you can always open it to see what
is going on.

Anyway, I am glad it's working for you.

Victor

>
>
> Victor, Istavan, Matt, and David,
> Thanks all for answering my question. I receive the Digest
> so that is   why it has taken me so long to respond.  I
> have tried all of your   suggestions and below are the
> answers to the various questions/  scenarios.
>
> > Is this with the GUI app or with command-line Csound?
> It clicks the same way from the GUI and from the
> command-line.  BTW,   when you run a real time csound file
> from the command line, how do   you terminate the
> playback.  My SCO runs for 8888 seconds.  Tried CTRL  +X
> but that did not work.  I ended up running "ps" and then
> using   "kill+id#".  I know that is not correct but could
> not figure out an   other way.   Is CTRL+C the correct
> way?
>
> > What happens if you don't use MIDI input with the
> > everything else the same (but without the MIDI opcodes)?
> It still clicks from the GUI and from the command line.
>
>
> > What happens if you read a MIDI file instead of real
> > time MIDI input, using the -F flag ?
> Still breaks up in the GUI and from the command line.
>
> > However, with portaudio, there seems to be no
> > problems, so instead of saying -+rtaudio=coreaudio, just
> > don't say anything.
> Yes, portaudio seems to help.
>
> > Also it helps to do -m0 (or uncheck
> > the messages box in the GUI) and -d.
> Including -m0 and -d really helps a great deal
>
> I've ended up using -odac --midi-device=1 -m0 -d -B512
> -b256  this   seems to work well.
>
> > you might want to try my csound5 front end, "CsoundX"
> >
> > http://sonomatics.com/CsoundXalpha1.dmg
> Matt, was not able to get things working with
> CsoundXalpha1.  Not   sure I see how to set the flags on
> this.  The interface looks great,   esp. the drop down
> sliders, etc.  Can't wait to see this develop. I   tried
> your test.csd and could get no sound from it.  I'm sure
> that I   am overlooking something very simple.
>
> Thanks again to all who helped out on this.
> Mitch
>
>
>
>
>
>
>
> On Feb 11, 2006, at 1:56 PM, csound-help@lists.bath.ac.uk
> wrote:
>
> > From: Victor Lazzarini 
> > Date: February 10, 2006 4:12:49 PM EST
> > To: csound@lists.bath.ac.uk
> > Subject: Re: Csound5 OSX MIDI performance
> > Reply-To: Victor.Lazzarini@nuim.ie
> >
> >
> > What happens if you don't use MIDI input with the
> > everything else the same (but without the MIDI opcodes)?
> >
> > Is this with the GUI app or with command-line Csound? I
> > must confess I have not really tested MIDI extensively
> > on OSX apart from checking it works. But others, I
> > presume have (David Akbari?).
> >
> > I'll check.
> >
> > Victor
> >>
> >>
> >
> > From: Istvan Varga 
> > Date: February 10, 2006 4:18:07 PM EST
> > To: csound@lists.bath.ac.uk
> > Subject: Re: Csound5 OSX MIDI performance
> > Reply-To: csound@lists.bath.ac.uk
> >
> >
> > On Friday 10 February 2006 21:48, Mitchell Turner wrote:
> >
> >> I am using the following flags with Csound5:
> >> -odac -iadc -+rtaudio=coreaudio --midi-device=1 -B128
> -b64 >>
> >> This same set of flags works perfectly (with no
> glitches) when >> sending an audio signal through a
> Csound5, so I do not believe that I >> have a problem with
> -B128 -b64. >
> > What happens if you read a MIDI file instead of real
> > time MIDI input, using the -F flag ?
> >
> >
> >
> > From: Victor Lazzarini 
> > Date: February 10, 2006 4:54:30 PM EST
> > To: csound@lists.bath.ac.uk
> > Subject: Re: Csound5 OSX MIDI performance
> > Reply-To: Victor.Lazzarini@nuim.ie
> >
> >
> > I ran some tests and what I found was that indeed with
> > MIDI and coreaudio, the GUI csound outputs a stream of
> > clicks. That I reckon has to do with the way the GUI
> > runs csound. However, with portaudio, there seems to be
> > no problems, so instead of saying -+rtaudio=coreaudio,
> > just don't say anything. Also it helps to do -m0 (or
> > uncheck the messages box in the GUI) and -d.
> >
> > So the bottom line is, with the GUI frontend, use
> > portaudio if you are doing MIDI.
> >
> > With Csound on the commandline, it doesn't matter as the
> > problem doesn't happen.
> >
> > Victor
> >
> >>
> >>
> >
> > From: "Matt J. Ingalls" 
> > Date: February 10, 2006 7:23:48 PM EST
> > To: csound@lists.bath.ac.uk
> > Subject: Re: Csound5 OSX MIDI performance
> > Reply-To: csound@lists.bath.ac.uk
> >
> >
> > you might want to try my csound5 front end, "CsoundX"
> >
> > http://sonomatics.com/CsoundXalpha1.dmg
> >
> >
> > From: David Akbari 
> > Date: February 10, 2006 10:47:34 PM EST
> > To: csound@lists.bath.ac.uk
> > Subject: Re: Csound5 OSX MIDI performance
> > Reply-To: csound@lists.bath.ac.uk
> >
> >
> > Running the attached file out of the box "as is" results
> > in no   errors; I'm able to play 5-6 voice polyphony
> > without breakups. On   OS 10.3.9 still, using the Csound
> > commandline built from CVS this   morning. (10 Feb 2006)
> >
> > Flags used were:
> > csound -odac:1 -idevaudio:1 -+noninterleaved=1
> > -+rtaudio=CoreAudio -  b1024 -B1024 -M0 -d ${FILENAME}
> >
> > * noninterleaved and explicit buffer-size are because of
> > using digi   mbox hardware.
> >
> > -David
> >
> > On Feb 10, 2006, at 4:12 PM, Victor Lazzarini wrote:
> >
> >
> > From: Victor Lazzarini 
> > Date: February 11, 2006 4:39:46 AM EST
> > To: csound@lists.bath.ac.uk
> > Subject: Re: Csound5 OSX MIDI performance
> > Reply-To: Victor.Lazzarini@nuim.ie
> >
> >
> > And perhaps when you're ready, you might like to add
> > it to Csound5 CVS. It's possible to use the command-line
> > xcode tool to build it from Sconstruct. Then we can
> > distribute
> > it with the binaries. What do you think?
> >
> > Victor
>
>

Victor,
Thanks for all the tips, they are much appreciated.
Mitch


On Feb 12, 2006, at 4:57 AM, Victor Lazzarini wrote:

> To end a command-line session, use ctl-C. In the GUI, either
> 'pause' or 'reset'. The Coreaudio module has problems with
> MIDI in the GUI, but works perfectly in the command-line.
> Portaudio works anywhere.
>
> It's important to suppress display messages, because they
> are
> very costly on OSX (the graphics are very heavy on Macs). So
> for
> any MIDI RT performance that's a must. The GUI has the
> advantage
> that the messages can be turned ON/OFF during performance,
> so
> if you want to check for any problems, you can turn it on.
> And when
> they are off, they are actually pumped to the console (you
> can open
> it from 'utilities'), so you can always open it to see what
> is going on.
>
> Anyway, I am glad it's working for you.
>
> Victor
>
>>
>>
>> Victor, Istavan, Matt, and David,
>> Thanks all for answering my question. I receive the Digest
>> so that is   why it has taken me so long to respond.  I
>> have tried all of your   suggestions and below are the
>> answers to the various questions/  scenarios.
>>
>>> Is this with the GUI app or with command-line Csound?
>> It clicks the same way from the GUI and from the
>> command-line.  BTW,   when you run a real time csound file
>> from the command line, how do   you terminate the
>> playback.  My SCO runs for 8888 seconds.  Tried CTRL  +X
>> but that did not work.  I ended up running "ps" and then
>> using   "kill+id#".  I know that is not correct but could
>> not figure out an   other way.   Is CTRL+C the correct
>> way?
>>
>>> What happens if you don't use MIDI input with the
>>> everything else the same (but without the MIDI opcodes)?
>> It still clicks from the GUI and from the command line.
>>
>>
>>> What happens if you read a MIDI file instead of real
>>> time MIDI input, using the -F flag ?
>> Still breaks up in the GUI and from the command line.
>>
>>> However, with portaudio, there seems to be no
>>> problems, so instead of saying -+rtaudio=coreaudio, just
>>> don't say anything.
>> Yes, portaudio seems to help.
>>
>>> Also it helps to do -m0 (or uncheck
>>> the messages box in the GUI) and -d.
>> Including -m0 and -d really helps a great deal
>>
>> I've ended up using -odac --midi-device=1 -m0 -d -B512
>> -b256  this   seems to work well.
>>
>>> you might want to try my csound5 front end, "CsoundX"
>>>
>>> http://sonomatics.com/CsoundXalpha1.dmg
>> Matt, was not able to get things working with
>> CsoundXalpha1.  Not   sure I see how to set the flags on
>> this.  The interface looks great,   esp. the drop down
>> sliders, etc.  Can't wait to see this develop. I   tried
>> your test.csd and could get no sound from it.  I'm sure
>> that I   am overlooking something very simple.
>>
>> Thanks again to all who helped out on this.
>> Mitch
>>
>>
>>
>>
>>
>>
>>
>> On Feb 11, 2006, at 1:56 PM, csound-help@lists.bath.ac.uk
>> wrote:
>>
>>> From: Victor Lazzarini 
>>> Date: February 10, 2006 4:12:49 PM EST
>>> To: csound@lists.bath.ac.uk
>>> Subject: Re: Csound5 OSX MIDI performance
>>> Reply-To: Victor.Lazzarini@nuim.ie
>>>
>>>
>>> What happens if you don't use MIDI input with the
>>> everything else the same (but without the MIDI opcodes)?
>>>
>>> Is this with the GUI app or with command-line Csound? I
>>> must confess I have not really tested MIDI extensively
>>> on OSX apart from checking it works. But others, I
>>> presume have (David Akbari?).
>>>
>>> I'll check.
>>>
>>> Victor
>>>>
>>>>
>>>
>>> From: Istvan Varga 
>>> Date: February 10, 2006 4:18:07 PM EST
>>> To: csound@lists.bath.ac.uk
>>> Subject: Re: Csound5 OSX MIDI performance
>>> Reply-To: csound@lists.bath.ac.uk
>>>
>>>
>>> On Friday 10 February 2006 21:48, Mitchell Turner wrote:
>>>
>>>> I am using the following flags with Csound5:
>>>> -odac -iadc -+rtaudio=coreaudio --midi-device=1 -B128
>> -b64 >>
>>>> This same set of flags works perfectly (with no
>> glitches) when >> sending an audio signal through a
>> Csound5, so I do not believe that I >> have a problem with
>> -B128 -b64. >
>>> What happens if you read a MIDI file instead of real
>>> time MIDI input, using the -F flag ?
>>>
>>>
>>>
>>> From: Victor Lazzarini 
>>> Date: February 10, 2006 4:54:30 PM EST
>>> To: csound@lists.bath.ac.uk
>>> Subject: Re: Csound5 OSX MIDI performance
>>> Reply-To: Victor.Lazzarini@nuim.ie
>>>
>>>
>>> I ran some tests and what I found was that indeed with
>>> MIDI and coreaudio, the GUI csound outputs a stream of
>>> clicks. That I reckon has to do with the way the GUI
>>> runs csound. However, with portaudio, there seems to be
>>> no problems, so instead of saying -+rtaudio=coreaudio,
>>> just don't say anything. Also it helps to do -m0 (or
>>> uncheck the messages box in the GUI) and -d.
>>>
>>> So the bottom line is, with the GUI frontend, use
>>> portaudio if you are doing MIDI.
>>>
>>> With Csound on the commandline, it doesn't matter as the
>>> problem doesn't happen.
>>>
>>> Victor
>>>
>>>>
>>>>
>>>
>>> From: "Matt J. Ingalls" 
>>> Date: February 10, 2006 7:23:48 PM EST
>>> To: csound@lists.bath.ac.uk
>>> Subject: Re: Csound5 OSX MIDI performance
>>> Reply-To: csound@lists.bath.ac.uk
>>>
>>>
>>> you might want to try my csound5 front end, "CsoundX"
>>>
>>> http://sonomatics.com/CsoundXalpha1.dmg
>>>
>>>
>>> From: David Akbari 
>>> Date: February 10, 2006 10:47:34 PM EST
>>> To: csound@lists.bath.ac.uk
>>> Subject: Re: Csound5 OSX MIDI performance
>>> Reply-To: csound@lists.bath.ac.uk
>>>
>>>
>>> Running the attached file out of the box "as is" results
>>> in no   errors; I'm able to play 5-6 voice polyphony
>>> without breakups. On   OS 10.3.9 still, using the Csound
>>> commandline built from CVS this   morning. (10 Feb 2006)
>>>
>>> Flags used were:
>>> csound -odac:1 -idevaudio:1 -+noninterleaved=1
>>> -+rtaudio=CoreAudio -  b1024 -B1024 -M0 -d ${FILENAME}
>>>
>>> * noninterleaved and explicit buffer-size are because of
>>> using digi   mbox hardware.
>>>
>>> -David
>>>
>>> On Feb 10, 2006, at 4:12 PM, Victor Lazzarini wrote:
>>>
>>>
>>> From: Victor Lazzarini 
>>> Date: February 11, 2006 4:39:46 AM EST
>>> To: csound@lists.bath.ac.uk
>>> Subject: Re: Csound5 OSX MIDI performance
>>> Reply-To: Victor.Lazzarini@nuim.ie
>>>
>>>
>>> And perhaps when you're ready, you might like to add
>>> it to Csound5 CVS. It's possible to use the command-line
>>> xcode tool to build it from Sconstruct. Then we can
>>> distribute
>>> it with the binaries. What do you think?
>>>
>>> Victor
>>
>>
> -- 
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk