![]() It's not handy for me to test this at the moment, but it should work ok unless I hooked something up wrong out of the fact that it's the end of the night here. Sorry if I'm telling you something you know already. Keep in mind that you put your equations into QC by choosing the mathematical expression patch and going to "settings"(or maybe just the math patch for this), and that you can add inputs to your multiplexer the same way. I don't like the limitation of choosing one way or another on that. I leave my multiplexers as virtual, b/c "that's how I roll". Remember that in QC, you won't see any values unless you are feeding info to a pink/consumer patch of some sort. ![]() Then, you feed that to another multiplexer the one whose index you actually need to change (in your scenario). Trying to get my head around this: the reason I can play a middle C on my controller and the sound that comes out will always be. Now, if I have a MIDI note that Cakewalk calls 'C1,' Stutter Edit will respond to it as C1, but MRhythmizer thinks the note is C2. ![]() You take and make an additional output splitter on the midi output and feed that to a multiplexer that chooses your "math chain" everytime it passes a "1". This got me through my Producertech Stutter Edit course without clawing at my head. So you need to do a chained multiplexer setup, like in the sample qtz I'm attaching. The problem is that if you hook up a math patch, and add, say "5", that value is going to pass on to whatever (your renderer, or filter, etc). You can take a math patch and hook it up to your midi note output, and "add" whatever you want to the output, to have it deliver the given value. In QC, this is equivalent to ON(1), or OFF(0). When the midi QC patch detects a value from a key, it puts out a 1.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |