Search the Community

Hi All, Hoping someone can tell me how or if this is possible with the mbseqv4. I'm wanting to know if I can set a start position and value of a CC# for instance and have the sequencer generate accurate values at each step up to and including an end position and value that I also set. Say I have a 128 beat long pattern over which I'd like to do a filter sweep,. Can I set a cutoff filter at say a start value of 10 on beat 1, and an end value of 100 on beat 128, and have the sequencer fill in beats 2 thru 127 with generated values gradually stepped between my start and end thresholds?. Or I may want a pattern to fade out over 20 beats stating at beat 44. Can I have the sequencer do the hard work for me? This could be used for filter sweeps, easy bass/snare drum rolls using velocity, useful for panning stereo sweeps etc. steps 0-16 gradually increasing from left to center, steps 17-31 gradually from center to right etc etc, copy/paste and repeat for steps 32- 64. Secondly, can this be done across multiple patterns. i.e. If I wanted to arrange filter automation across multiple patterns in song mode can it be done and if so how? Not that I've really progressed to song mode yet anyway but curious minds want to know :smile: Still getting my head around the power and usability of this wicked machine. I'd love to see many many more tutorials and/or videos on it's usage. More so people using it to create (start to finish), rather than the end creations only. A dedicated "how to use" forum would be great for anyone wanting to post tutorials on funky things they've learned to do on the MBSeq too (but I guess that is another thread altogether). What has me thinking like this is the many graphical DAWs that allow a user to simply draw a filter curve or velocity curve (or line), via mouse on screen across a pattern or even multiple patterns. Setting A/B points with interpolation in between would be a fast way of adding such? Then again perhaps I'm thinking about this in all the wrong ways too. Happy to be set straight ;) It'd also be smart if the value changes are less frequent than the number of steps required then the CC#'s are only put in where required rather than at every step. No point sending values of 99,99,99,99,100,100,100,100 etc over 8 steps when you could send 99,nothing,nothing,nothing,100,nothing,nothing,nothing etc... Reducing the amount of midi traffic. Any and all suggestions very much appreciated. Cheers, Arkay.