On Wednesday 30 November 2005 16:47, Victor Lazzarini wrote:

> I see your point. I think the noFLTKThreads=1 should be the
> standard. I have tested it here and it works OK on all OSX
> platforms (including your changes from yesterday).
> I think in fact that we should remove the threading code as
> it is not guaranteed to work and it probably only works as a side-effect.
> See another reply from the FLTK guy:

While the non-threading mode should definitely be the default
on OS X, it may be worth keeping for Linux and Win32 where
threads seem to work (and the original version in CsoundAV also
uses threads) unless actual problems are found on those platforms.
Using threads (where doing so works, that is) does improve real
time audio performance, particularly when combined with the
--sched option. Although, the single-threaded model does have
its advantages: it allows for using widgets and graphs at the
same time, and eliminates the need for compiling FLTK with
--enable-threads as no lock/unlock/awake calls are used.

> If Csound is used in a a multithreading application, then FLTK widgets
> are out of the picture. It is not a problem, I think, as FLTK have been
> taken out of the core csound library and is supplied as plugins.
> Someone else might supply other plugins for graphics based on other
> library. And in the case of frontends, graphics might be supplied by the
> frontend itself (cf. cswish). 

Well, we do have the bus interface and chnexport etc. opcodes, but
need an actual host application that makes it really useful in
practice.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net