Cycling 74 » Topic: poly note vs midinote

poly note vs midinote

Ploki — Sat, 17 Mar 2012 23:35:45 +0000

Because I wish to take use of midi/off velocity (and some other stuff) I’d like to send a custom message to an instance of poly (5part list i.e.) but i’d also like that poly knows when i’m sending an “off” message to that poly which receives the off.
Is this possible any other way than doing it with counter and specific instances? Because midi note handles that automatically but it doesn’t work with off/velocity (+ other parameters i’d like to send separated to each enabled voice).

The only way i can think of is using a massive routing system or a counter that counts the number of instances of poly and assignes specific notes automatically… which is tedious and complicated.

Is there anyway to tell poly “send this to the same voice that the other thing before was sent.” like midi note?

I have another idea (but am too sleepy to test it), if i set the poly patcher to have an internal memory so it remembers the input it first receives, and when it receives a “note off” its filtered by other active voices because they have different memory. That can’t trigger a new instance because it (note/off) would be sent directly to output not via “note” message, would trigger the mute 1 and cleared the memory of the patcher… So then, the next voice that comes via message “note” can occupy its spot? I think thats the most elegant solution so far with least data redundancy. It’s easy to set so note/off goes without “note” prepended and note/on goes in with prepended “note” message. I think i’ll do that if there isn’t a simpler solution. (like being references by the first number of the list i.e. like a note number.)

Re: poly note vs midinote

oldTurtle — Sun, 18 Mar 2012 09:34:59 +0000

your explanation sounds a bit confusing to me… i guess you’re trying to send note on, then note off WITH velocity (to the same instance), is it right?

if that’s so, and if it’s only these two mesages you want to send for each note (the 5-part lists), then you might just try to use midinote indeed, sort of: “midinote noteNumber 0 offVel whateverElse”, so that 0 cheats [poly~] to send it to same instance, then you use next number as note off velocity.

if you want to send more than note on/off messages, that’s another thing. but again, i can’t really figure out what you’re really doing, where you’re getting the note messages from, and what you wanna do with the lists to [poly~]… :)

Re: poly note vs midinote

Ploki — Sun, 18 Mar 2012 19:42:28 +0000

I actually need to send a 3-part message i figured, everything else is either constant or send to every instance. “freq, velocity, on/off” i.e. 548 25 1 or 548 25 0.
As far as I recall poly~ kills the voice with a note/off message? I need it to close the adsr rather then kill it.
I need to control adsr release and attack with velocity on and velocity off (and of course i need to send a mute command to adsr which is connected to this poly to mute it) and a frequency of the instance.

Also, i need like, at least 140 different “notes”, so midi note is out of range.

Re: poly note vs midinote

oldTurtle — Sun, 18 Mar 2012 21:25:12 +0000

i think what “midinote” does is just select an idle instance for note on (just as “note” does) AND send note off to same instance as corresponding note on, understanding first and second values in the list as note-velocity (0 meaning note off).

but it doesn’t kill the voice, you have to do it with “mute 1″ to [thispoly~]. so if you send “midinote noteNumber 1/0 velocity”, you’ll have messsages send to right instances(1 will be interpreted as on, 0 as off), then you can use the third value in the list as velocity, both with note on and note off. and only mute and set state to non-busy when the release part of the adsr is done.

but i don’t know now if i’m making sense any more… maybe a patch will help.

the 140 different notes issue seems tricky. in another situation you could use some msb-lsb thing: use yet another value in the list so that you have more than 7bits. but of course that would mess things up, dealing with [poly~].

Re: poly note vs midinote

Ploki — Sun, 18 Mar 2012 21:40:29 +0000

hm yes, i can see where you are going, but its time for some dummy patcher to try each method and see what works and what not.

Thanks, you gave me a few ideas to try out. Ain’t going the msb/lsb route though.. no way. :D

Re: poly note vs midinote

Ploki — Mon, 19 Mar 2012 11:19:32 +0000

Lol! It’s so simple i can’t believe i didn’t try it!
Midi note works well over its native range. i.e., “midinote 256 x y z e” works flawlessly.
let me sum up just in case a lost soul wander here after 3 years :P
“note” allows you to send a message to an open voice. In order to close it, you need to know which instance was called upon, or have it close automatically (via timer) or via send/recieve by another function.

HOWEVER, midinote sends a message to an open voice, and allows you to send another message to close it if the message begins with “midinote $i 0″
This is pretty much what you told me, the only difference is that i wasn’t aware that midinote works well over midrange. Theoretically, you can use any number as midinote. Brilliant. My problem is solved, this is exactly what I need, because I can simply ignore the midi off (0) message and close it via ADSR when midi/off is received.
You can also send it a list which can be as long as you wish, as long as the syntax is “midinote “note number” “velocity/0″ value value value value value…”

My god I have to rewrite this post, its awful.

Re: poly note vs midinote

oldTurtle — Mon, 19 Mar 2012 14:56:57 +0000

wahaha… one never considers the easy path on a first try. in fact that makes sense (there’s no real MIDI in there, so no 7bits limit), though i didn’t consider it neither. why should’t it? plain and simple…

wouldn’t it have been crazy to get a headache with lsb paraphernalia? XD

Re: poly note vs midinote

Ploki — Mon, 19 Mar 2012 18:42:28 +0000

Haha :D indeed. I was getting pretty desperate. I was waiting for someone and had my laptop with me and it just hit me “hey perhaps it actually works?!” and it does. Awesome moment