@CleverConQueso - That is an ingenious plan! If bsork's idea works I will probabily use that but I will definately be using your idea elsewhere in my patch. I had never thought of using an inrement fader to work my way through the different voice, that is a very good idea. So far I have been using busses and appending the voice number to the buss name. I think it would be good to add some examples such as this to the polyphony section of the wiki to show different ways of communicating with specific voices in a polyphonic patch.
Statistics: Posted by caco — 14 Dec 2011, 21:02
]]>
When you play a note, the MIDI note should route to one of the voices along with the time delay for that note. When the note has been triggered, the dispatch will wait a moment and then advance to the next voice.
If that all works, another way to route to the polyphonic patch without using dispatch and multiple input leads for each voice is to put '= voice number' on a 'pass' inside the voice and instead of advancing the dispatch, send the fader value into the subpatch and have it open the 'pass' for each individual voice.
I'll be interested to try this out when I get home from work.
-CCQ-
Statistics: Posted by CleverConQueso — 14 Dec 2011, 19:11
]]>
]]>
]]>
]]>
I want to have a second step module where the steps control the individual note durations and am wondering the best way of creating and handling polyphonic midi. The voice despatcher looks interesting but it doesn't quite do what I want so I am looking for good ideas. At the moment I am looking at having a separate data delay for each individual step but this seems a bit limiting for incase I want to change the number of steps. I feel like their must be something more elegant I am missing
Statistics: Posted by caco — 14 Dec 2011, 15:47
]]>