Hi Jim,<br><br>The reason the GUI is not mentioned there is that the GUI is not part of csound, it is afront end, an independent graphical interface. There are many front ends, but Csound5GUI is one of the GUI s distributed with csound. There are better ones, like WinXsound for windows and MacCsound for Mac. What might be a good idea is explaining better in the getting started section that the front end calls csound, and each front end gas different ways of exposing the options available in csound.<br>
I also haven&#39;t included any specific information about csound5GUI, because I don&#39;t like it. It&#39;s very awkward. I&#39;m working on another (yet another front end...) which is cross-platform, which I hope supercedes csound5GUI, but it&#39;s still untested in Mac and OSX and there&#39;s still some work to be done before it&#39;s released.<br>
<br>Cheers,<br>Andres<br><br><div class="gmail_quote">On Wed, Jun 4, 2008 at 9:16 PM, Jim Aikin &lt;<a href="mailto:midiguru23@sbcglobal.net">midiguru23@sbcglobal.net</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br></div>
Also, I&#39;m sensitive on this subject because I&#39;ve been writing and editing<br>
how-to material for musicians who use synthesizers for the past 30 years.<br>
When I look at the Csound manual&#39;s page on Real-time MIDI Support, for<br>
instance: (a) It never mentions using the GUI as an option, only the command<br>
line, and (b) the words &quot;buffer&quot; and &quot;latency&quot; are never used. That being<br>
the case, I would not characterize this page as providing a sufficient<br>
discussion of the topic. I&#39;m speaking not as a baffled musician (though I&#39;m<br>
sometimes in that category) but as a professional editor.<br>
</blockquote><div><br>&nbsp;</div></div><br>