Hi Anthony.
Thanks for the feedback.  I still got some dropouts when I disabled
the mouse callbacks, but usually only when I click a scrollbar.  I
still have to find a way to auto-scroll the score, and perhaps make
that optional.
As far as crashing, there is an option under the File menu to export
Csound; it will create a .csd file identical to what Rationale uses,
with the exception of the instrument that gets called automatically
just to move the cursor.  This is another reason I think I may use rt
events: the only way to line the cursor up with Csound's tempo is to
insert individual notes and have them increment the cursor.  If I work
out the tempo within Rationale, the cursor could be yet another thread
or what not, not dependent on Csound.
Anyway, if you export .csd, you can try it from the command line and,
if that works, let me know and I'll try to get to the bottom of it.

-Chuckk

On Fri, Oct 24, 2008 at 9:19 PM, Anthony Kozar
<mailing-lists-1001@anthonykozar.net> wrote:
> Chuckk,
>
> I was (finally) able to get Rationale running last night and I would guess
> that the playback problem is almost certainly the mouse movement callbacks.
> (Unfortunately, the program crashes when I try to play a CSD though, so I
> haven't observed the problem you described yet).
>
> Many other GUI programs that use Csound have issues when the mouse is
> clicked or held as the GUI event handler takes over completely and sound
> stops.  (i.e. try using FLTK graphs with command-line Csound and clicking in
> or dragging the graph window).  My own Csound 5 front end on OS 9 had the
> same problem.  And these programs don't usually respond to "mouse moved"
> events which are more numerous than "mouse down" events.
>
> So, disabling the mouse callbacks would definitely help but there may be
> other solutions.  Putting the Csound perf loop in another thread may help
> too (although I see from the code that you might be doing that).  I can say
> that I do not expect any difference in performance simply by using real-time
> score events or OSC.  Using a separate Csound process of course would give
> the best performance but then does not allow the same level of integration
> with your host application.
>
> Anthony Kozar
> mailing-lists-1001 AT anthonykozar DOT net
> http://anthonykozar.net/
>
> Chuckk Hubbard wrote on 10/23/08 2:07 AM:
>
>> I have been using Tkinter and the API in Python,
>> assembling a complete csd when ready to audition and running Csound.
>> It's worked well enough for me, but I get lots of static any time I
>> move the cursor over the score, even though I start a separate thread
>> for Csound.
>
>> My dilemma is whether to keep it as it is and disable mouse callbacks
>> during playback, or to switch to an orchestra with no score and send
>> it real-time events (instead of putting all notes into the csd to
>> start), as you suggest here, or to send OSC events at an API-run
>> orchestra, or even to start a separate Csound process instead of using
>> the API.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>



-- 
http://www.badmuthahubbard.com