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

>
> 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 ?
> --
> Send bugs reports to this list.
> To unsubscribe, send email to
> csound-unsubscribe@lists.bath.ac.uk