unk wrote:1.- the note gate seems to be a bit unstable in its behaviour
unk wrote:2.- in theory pitch bend should be treated separatelly from note on/note off messages.
unk wrote:3.- You are asuming that note of is always message 128, while the widely common knowledge ( althou isn't clear to me if it's supported by MIDI spec) says that a message 144 ( note on) with velocity should also be considered as note off
unk wrote:4.-you conversion to frequency is nice if you need it in float form. but if poly form is acceptable. symply connect you midi note id to a pitch 2freq module and that's all
unk wrote:5.- MIDI CC could be simpler if you use the MIDI CC module
unk wrote:not tried but i feel that now we have arrays, should be posible to implement all of this in a much simplier code module
NothanUmber wrote:Hi unkargherthunk wrote:1.- the note gate seems to be a bit unstable in its behaviour
Hm, not reproducable here, could you please give me a description how to provoke that behaviour?
NothanUmber wrote:I copied the behaviour of the note extractor from bidule (well, it's a combination of "Note Extractor 1" and "Note Extractor 2" and found that it greatly simplified my tasks there - in bidule you simply connect a pre-pitchfilter to the note extractor if you really don't want to have the frequency affected by the pitch bend events. (Such a filter should be easy: Just change the status to 224 (E0) and remove the CC number comparsion part from the CC Filter and a Pitch Bend Filter you have )
NothanUmber wrote:Nice idea! Is it somehow possible to convert the poly data back to floats? (I need to use the frequency for further calculations so floats are more practical there)
NothanUmber wrote:Is it possible to also get the data that doesn't match the criterium? (That's important for me as I manipulate the CC data and mix it back into the main midi stream afterwards so the CCs have to be filtered out, otherwise i'd have both the original and the modified ones what would lead to unexpected behaviour)
NothanUmber wrote:Do you have an idea how to get midi data and float values inside the code component? (One could try to write a new code component with the parser components but that's some effort and I'm a little bit short on time atm. and glad if I manage to get my midi stuff ready...)
unk wrote:It's A basis of something Bigger ?
unk wrote:Question. You're trying to buil a synth foran stange hardware controller, or you're trying to simulate a hardware controler in a software way ?
unk wrote:I supose it sends, quite obviousy, note on/note off, pitchbend, modulation and maybe 2 or 3 midi CC.
unk wrote:Assuming this, IMHO, is better and simpler to build a "dedicated solution". Solve the questions directly Related to THIS project, instead of building a generic midi framework, that could be easily be obsoleted by the upcoming note management system and/or the arrival of more specialized MIDI components.
Users browsing this forum: No registered users and 0 guests