Ok, so never mind my suggestion, I guess it is not really necessary.
Statistics: Posted by gurulogic — 01 May 2010, 11:26
]]>
and as in new swich can choose on and off val can even get rid of the not module if inversing..
.. do we really need something that will just avoid one "has chgd"?
Statistics: Posted by 23fx23 — 01 May 2010, 11:19
]]>
]]>
I just think it can be better to a have function such as basic midi note on and off creation not depend on needing extra patching to make it work. Also this can get even more complex when you want to work with many midi notes generated within Usine, or different ways of triggering notes.
I perceive midi somewhat as I perceive audio...it is a vital function and it should work with no fuss! I myself have been confused by this, as well as I have seen confusion from other users, this is why I suggest it, but maybe there is a better solution?
(sorry clearscreen, I deleted my post and changed the picture while you made your post)
Statistics: Posted by gurulogic — 01 May 2010, 10:45
]]>
]]>
]]>
The optional new function would create a single note on message for the duration that a value of 1 was received at the the create inlet and then when a value of 0 was received at the create inlet, a not off message would be sent.
This would greatly simplify a lot of patching tasks as well as make the create midi module much easier for new users to understand. I know it took me a good deal of time to realize that whenever a note on message was created with the module, a note off also had to be created with a new module (or some clever patching of one module)
Also sometimes problematic with the current method is that any time you would like to trigger a midi note on with something other than a button or has changed module, the create midi module will continuously generate note on messages until the input value is 0, which can be confusing at first.
Perhaps this could be added as an option in the message type as Note ON/OFF ?
Statistics: Posted by gurulogic — 30 Apr 2010, 04:49
]]>