Re: [CM] midi-received functions

2016-02-20 Thread Forrest Curo
I'm quite happy! -- and given how much blundering & hassle an inexperienced user can enjoy in the installation process -- Would my compiled binary be useful on sourceforge -- What's the proper way to check that possibility out? On Sat, Feb 20, 2016 at 5:37 AM, Taube, Heinrich K wrote: > if you

Re: [CM] midi-received functions

2016-02-20 Thread Taube, Heinrich K
if you are in 3.9.0 and its working as you expect im happy! > On Feb 19, 2016, at 10:46 PM, Forrest Curo wrote: > > Given that the error isn't from the current distribution, I suppose there's > no issue... > > Ah, I seem to have finally bumbled through installing 3.9.0, thanks! > > On Fri, Fe

Re: [CM] midi-received functions

2016-02-19 Thread Forrest Curo
Given that the error isn't from the current distribution, I suppose there's no issue... Ah, I seem to have finally bumbled through installing 3.9.0, thanks! On Fri, Feb 19, 2016 at 2:19 PM, Forrest Curo wrote: > function mychord (data) > with channel = second(data), >keynum = third(da

Re: [CM] midi-received functions

2016-02-19 Thread Forrest Curo
function mychord (data) with channel = second(data), keynum = third(data), velocity = fourth(data) send("mp:midi", key: key, vel: vel, chan: chan) send("mp:midi", key: key + pick(3,4), vel: vel, chan: chan) send("mp:midi", key: key + 7, vel: vel, chan: chan) end -

Re: [CM] midi-received functions

2016-02-19 Thread Taube, Heinrich K
its not clear to me what the issue is. does it not work. BTW no need to use send() and just call the function directly so > send("mp:midi", key: key, vel: vel, chan: chan) can be written mp:midi(key: key, vel: vel, chan: chan) i thought I got rid of all that in the documentation and help files.

Re: [CM] midi-received functions

2016-02-19 Thread Forrest Curo
The section is "Input Hooks" (speaking of errors... but still not the first title I'd look for this under.) On Fri, Feb 19, 2016 at 7:59 AM, Forrest Curo wrote: > Okay, among 'examples' there is a section titled 'Output Hooks' (not, to > my mind, the most obvious titles to look for) > and the ex

Re: [CM] midi-received functions

2016-02-19 Thread Forrest Curo
Okay, among 'examples' there is a section titled 'Output Hooks' (not, to my mind, the most obvious titles to look for) and the examples have errors: ie ; An opcode receiver that plays a major or minor chord whenever a ; Note On arrives function mychord (data) with channel = second(data),

[CM] midi-received functions

2016-02-18 Thread Forrest Curo
I see a tutorial on sending midi out and ways to declare a function to be receiving midi in with specific opcodes but I'm not at all clear on how such a function should be written to extract the data when a midi message comes in. Examples anywhere? ___