[Cs-dev] sensekey
Date | 2006-03-25 01:28 |
From | matt ingalls |
Subject | [Cs-dev] sensekey |
finally trying out csound5 with MacCsound... first problem: error: no legal opcode, line 23: k1 sensekey i use sensekey (with csoundKeyPress() in API ) all the time.. what's going on? thanks, matt |
Date | 2006-03-25 02:14 |
From | "Steven Yi" |
Subject | Re: [Cs-dev] sensekey |
Attachments | None |
Date | 2006-03-25 04:53 |
From | David Akbari |
Subject | Re: [Cs-dev] sensekey |
I still see it in the -z list as well but for some reason, the Mac Terminal.app doesn't redirect the stdin to Csound as it should... Usually I just use MacCsound for sensekey related things, lol Here's the example I was trying with Csound5, and although it compiles and initiates performance correctly, I can't seem to get it to respond to ASCII input on Mac OS X. sensekey DOES show up in the -z list Csound version 5.01.0 beta (float samples) Mar 11 2006 [...] sensekey k (null) |
Date | 2006-03-25 06:09 |
From | matt ingalls |
Subject | Re: [Cs-dev] sensekey |
On Mar 24, 2006, at 6:14 PM, Steven Yi wrote: > I have sensekey listed with csound -z here on my computer, compiling > from CVS. I imagine it must be there. Do you have OPCODEDIR or > OPCODEDIR64 set, or if using from the API have you added those > directories from the host? ok thanks steven - i was setting OPCODEDIR wrong! so now it compiles, but it STILL doesn't work!!! i don't see anywhere in pitch.c where it uses csound->inChar_ which is what csoundKeyPress assigns the value to.. could you please add something like this in pitch.c int ksense(CSOUND *csound, KSENSE *p) { if (csound-> inChar_ > 0) { *p->ans = csound->inChar_; csound->inChar_ = 0 } else *p->ans = getchar(); return OK; } that way sensekey would support a keystroke sent via the API and stdin keys. and while we are at it, i have always wanted to either add a "keyup" opcode/API function. that way i can write an instrument that uses the keyboard keys like a piano keyboard... THANKS! -matt > > steven > > On 3/24/06, matt ingalls |
Date | 2006-03-25 12:01 |
From | Istvan Varga |
Subject | Re: [Cs-dev] sensekey |
Attachments | None |
Date | 2006-03-25 18:00 |
From | matt ingalls |
Subject | Re: [Cs-dev] sensekey |
well for one, FLTK does not work with the API on mac -- it hangs if you call csoundLib from a separate thread (which both of my host apps do) and even from the application thread, it takes over the host application's menus, which is not very nice.. if you are suggesting a separate application, i already often use a nice software MIDI keyboard [ "MidiKeys"http://www.manyetas.com/] i can send to csound fine, but i like using the computer keyboard directly with sensekey - the computer keyboard is pretty great - you can have around 100 commands, easily accessible. Mapping those to some kind of piano keyboard layout is NOT what i meant when i said "like a piano keyboard" -- i didn't mean pitch-wise -- just the ability to watch for key-release so you can "sustain" an action.. anyway, i can try to write my own opcode for this.... speaking of which, is there a OPCODEPLUGINDIR directory or something? or do you need to put 3rd party opcode plugins in OPCODEDIR? -- which means you need admin access on the mac. and when i update will the installer be smart enough to leave my 3rd party opcodes there? thanks, matt |
Date | 2006-03-25 19:50 |
From | Istvan Varga |
Subject | Re: [Cs-dev] sensekey |
Attachments | None |