Hi Steven,

I just compiled this from CVS and I'm getting some crashes and odd 
behavior... here's the crash report that the OS reports after throwing 
a Csound tidy up: Bus error

Also it seems like playing the notes doesn't quite work from the ASCII 
keyboard; I will press a note and occasionally it will show the 
keyboard key turning blue (it accurately senses the duration of the 
held note) but the most I get from the audio output are random and 
sporadic sputters of sound reminiscent of setting the buffer size 
incorrectly for the hardware. I've also attached the .csd file that is 
causing these errors.

Also of interest may be the fact that I compiled csound (as I always 
do) with FLTK threads enabled. Is this not recommended in the case of 
the virtual keyboard plugin?


Date/Time:      2006-11-01 23:42:07 -0600
OS Version:     10.3.9 (Build 7W98)
Report Version: 2

Command: csound
Path:    ./csound
Version: ??? (???)
PID:     2340
Thread:  1

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0:
0   libSystem.B.dylib         	0x90000b84 malloc_zone_malloc + 0
1   libSystem.B.dylib         	0x90017cdc _pthread_create_suspended + 
0xb0
2   libfltk.1.1.dylib         	0x007aadcc do_queued_events(double) + 
0x168
3   libfltk.1.1.dylib         	0x007aae54 fl_wait(double) + 0x1c
4   libfltk.1.1.dylib         	0x0076eac4 Fl::wait(double) + 0x19c
5   libvirtual.dylib          	0x006bbd24 ReadMidiData_ + 0xb0
6   csound                    	0x000474d4 sensMidi + 0x8c
7   csound                    	0x000133ac sensevents + 0x640
8   csound                    	0x000038b8 csoundPerform + 0x60
9   csound                    	0x00002028 main + 0x20c
10  csound                    	0x00001b4c _start + 0x188 (crt.c:267)
11  csound                    	0x000019c0 start + 0x30

Thread 1 Crashed:
0   libSystem.B.dylib         	0x900396bc pthread_join + 0x18
1   libfltk.1.1.dylib         	0x007aa6d0 DataReady::CancelThread(char 
const*) + 0x68
2   libfltk.1.1.dylib         	0x007aae0c do_queued_events(double) + 
0x1a8
3   libfltk.1.1.dylib         	0x007aae54 fl_wait(double) + 0x1c
4   libfltk.1.1.dylib         	0x0076eae4 Fl::wait(double) + 0x1bc
5   libwidgets.dylib          	0x012e1470 fltkRun + 0xd8
6   libSystem.B.dylib         	0x90024990 _pthread_body + 0x28





On Nov 1, 2006, at 5:35 AM, Steven Yi wrote:

> Hi All,
>
> Just wanted to mention that the FLTK keyboard now has ascii input to
> trigger of MIDI notes and that some bug fixes went in today so there
> should be no more stuck notes.  Interestingly enough, it seems that
> the keyboard autorepeat has become a non-issue and that you can hold
> down keys as long as you want to do chords without things
> retriggering.  Also a bug was fixed if you were running the keyboard
> within an API program like Csound5GUI that the window wasn't being
> properly hidden and destroyed on moduleDestroy.
>
> Thanks!
> steven

OK,

First of all, sorry Steven. I just recompiled csound using 
noFLTKthreads=1 and everything works as it should. I answered my own 
problem.

On Nov 1, 2006, at 11:51 PM, David Akbari wrote:

> Also of interest may be the fact that I compiled csound (as I always 
> do) with FLTK threads enabled. Is this not recommended in the case of 
> the virtual keyboard plugin?

How could the FLTK code be made reliably multi-threaded ? Or is it not 
worth it to do so ? If the latter, will there ever be a point when the 
FLTK threads option in SConstruct is removed in favor of default 
behavior that puts everything in a single thread ?


-David


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net