Can anyone think of a clever way involving gates or filters or anything that will allow me to use apTrigga to trigger random samples at different velocity levels? Currently apTrigga forces me to choose one or the other, either random multisamples at one velocity or one sample per velocity level triggered dynamically...
Can anyone think of a way where I could duplicate the snare track to like 4 tracks each with it's own instance of apTrigga that only look at the signal in a certain velocity range? So the track that's supposed to catch the quiet hits ignores the loud hits for example? I just need a clever way of setting an upper threshold that cuts out anything louder than that threshold....
One solution I did think of was to duplicate the track for each layer I wanted, run one instance of apTrigga set to dynamic mode but load blank samples into the dynamic ranges that I don't want to use and then load any percussive sound into the one layer that I DO want to trigger, then run another instance of apTrigga after that one set to random mode and load in the multisamples for that layer... It'll definitely work but it seems excessive, especially with the wasteful CPU hogging that would occur from having so many instances running where 90% of them are triggering blank samples all the time...
Can anyone think of a way where I could duplicate the snare track to like 4 tracks each with it's own instance of apTrigga that only look at the signal in a certain velocity range? So the track that's supposed to catch the quiet hits ignores the loud hits for example? I just need a clever way of setting an upper threshold that cuts out anything louder than that threshold....
One solution I did think of was to duplicate the track for each layer I wanted, run one instance of apTrigga set to dynamic mode but load blank samples into the dynamic ranges that I don't want to use and then load any percussive sound into the one layer that I DO want to trigger, then run another instance of apTrigga after that one set to random mode and load in the multisamples for that layer... It'll definitely work but it seems excessive, especially with the wasteful CPU hogging that would occur from having so many instances running where 90% of them are triggering blank samples all the time...