I should add, that CsoundVST requires noFLTKThreads=1.

----- Original Message ----- 
From: "Michael Gogins" 
To: 
Sent: Tuesday, May 16, 2006 11:26 PM
Subject: Re: [Csnd] [Cs-dev] release date question


> This script can be used to illustrate my problem.
>
> With the following code in place CsoundVST renders the soundfile:
>
> # Create an instance of Csound (actually, CppSound).
>
> csound = csnd.CppSound()
>
> With the following code in place CsoundVST just crashes:
>
> # Create an instance of Csound (actually, CppSound).
>
> # csound = csnd.CppSound()
>
> Previously, that code worked (using the instance of CppSound that is 
> created
> when the csnd module is imported by CsoundVST). Now, the instance is still
> created, and it works with some scripts, but there is a crash with koch.py
> (or, with other scripts, garbled numbers).
>
> Regards,
> Mike
>
> ----- Original Message ----- 
> From: "Michael Gogins" 
> To: 
> Sent: Tuesday, May 16, 2006 1:01 PM
> Subject: Re: [Csnd] [Cs-dev] release date question
>
>
>>I think it should be delayed for all packages. Later I will email you a
>>script that reproduces the error.
>>
>> Regards,
>> Mike
>>
>> -----Original Message-----
>>>From: Istvan Varga 
>>>Sent: May 16, 2006 11:09 AM
>>>To: csound@lists.bath.ac.uk
>>>Subject: Re: [Csnd] [Cs-dev] release date question
>>>
>>>On Tuesday 16 May 2006 15:09, Michael Gogins wrote:
>>>
>>>> Sorry, but I'm experiencing a new problem with CsoundVST.
>>>> Some scripts run fine, others produce non-numbers.
>>>
>>>Is there a simple script that reproduces this error ?
>>>I am not very familiar with CsoundVST, though, but it
>>>may be worth having a look at, particularly if, as you
>>>suggested, the bugs may also have been introduced in
>>>the Csound library.
>>>
>>>> So, I'd like to wait till the end of the month for the release.
>>>
>>>What is the suggested release date now ? Should the release
>>>be delayed on all platforms, or only those packages that
>>>include CsoundVST ?
>>>-- 
>>>Send bugs reports to this list.
>>>To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>>
>>
>>
>> -- 
>> Send bugs reports to this list.
>> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>>
> 

So what does the scons noFLTKThreads=1 do now? How
should we build the binaries (currently I  use =1 on the
Mac and it works for all front-ends)?

At 10:03 23/05/2006, you wrote:
>On Wednesday 17 May 2006 14:27, Michael Gogins wrote:
>
> > I should add, that CsoundVST requires noFLTKThreads=1.
>
>It is actually possible to have the effects of noFLTKThreads=1
>enabled at run-time, rather than compiling the widgets plugin
>with noFLTKThreads=1 (in fact, the csound5gui frontends assumes
>noFLTKThreads=0). To disable the use of a separate thread for
>the widget opcodes, run this code between csoundPreCompile()
>and csoundCompile():
>
>   csoundCreateGlobalVariable(csound, "FLTK_Flags", sizeof(int));
>   *((int*) csoundQueryGlobalVariable(csound, "FLTK_Flags")) = 28;
>
>Replace the 28 with 30 to disable the FLTK graphs, or 3 to get
>rid of both the widgets and the graphs.
>
>Additionally, if using 274 instead of 28, then as long as
>csoundCompile() is called from the same thread that also calls
>Fl::wait(), it is possible to get the widgets working regardless
>of what thread is used for performing.
>
>Here is the complete list of flags:
>
>/**
>  * FLTK flags is the sum of any of the following values:
>  *   1 (input):  disable widget opcodes by setting up dummy opcodes instead
>  *   2 (input):  disable FLTK graphs
>  *   4 (input):  disable the use of a separate thread for widget opcodes
>  *   8 (input):  disable the use of Fl::lock() and Fl::unlock()
>  *  16 (input):  disable the use of Fl::awake()
>  *  32 (output): widget opcodes are used
>  *  64 (output): FLTK graphs are used
>  * 128 (input):  disable widget opcodes by not registering any opcodes
>  * 256 (input):  disable the use of Fl::wait() (implies no widget thread)
>  */
>--
>Send bugs reports to this list.
>To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 

So, in that case, did you set the default for OSX for fltk
to run in the main thread? This is necessary for the csound
'classic' frontend and the OSX frontend (as well as tclcsound).

Victor

At 10:55 23/05/2006, you wrote:
>On Tuesday 23 May 2006 12:39, Victor Lazzarini wrote:
>
> > So what does the scons noFLTKThreads=1 do now? How
> > should we build the binaries (currently I  use =1 on the
> > Mac and it works for all front-ends)?
>
>noFLTKThreads=1 is now only needed if you have an FLTK library
>that was not compiled with --enable-threads. Otherwise, the
>correct threading mode is selected at run-time.
>--
>Send bugs reports to this list.
>To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 

Thanks.

At 11:20 23/05/2006, you wrote:
>On Tuesday 23 May 2006 13:16, Victor Lazzarini wrote:
>
> > So, in that case, did you set the default for OSX for fltk
> > to run in the main thread?
>
>Yes, the default is not using any thread related stuff on OS X
>or if displays are enabled.
>--
>Send bugs reports to this list.
>To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth