sleepytom
2011-04-12 22:46:31
Hi
I'm interested to know what is considered best practice when it comes to building presets; is it better to use variables and rules to construct midi messages for output or do we gain anything by splitting these commands across multiple translators?
at the moment i'm trying things like (qq is an incoming note var and PP selects the preset to load on outgoing action)
this obviously just filters for 2 specific notes, but i'm adding upto 64 eventually. it's a lot neater to have it all in code in one place, but sometimes things seem to work better if i use multiple translators filtering just their one specific note.
I'd appreciate others thoughts and experience with this as i'm new to MT.
I'm interested to know what is considered best practice when it comes to building presets; is it better to use variables and rules to construct midi messages for output or do we gain anything by splitting these commands across multiple translators?
at the moment i'm trying things like (qq is an incoming note var and PP selects the preset to load on outgoing action)
Code: Select all
if qq==68 then pp=1
if qq==68 then rr=h1
if qq==84 then pp=2
if qq==84 then rr=h2
if rr==1 then exit rules, execute Outgoing Action
if rr==0 then exit rules, skip Outgoing Action
I'd appreciate others thoughts and experience with this as i'm new to MT.