Hi all,
Picture this:
In Zebra I have a 16 step arp sequence.
But i also want to have a filter close slowly over that pattern, using an MSEG.
But it doesn't seem possible, as the MSEG re-triggers with each note-on received from the arp.
Is there a way to tell the MSEG to only re-trigger with a note-on from the midi input?
Hmmmm, clear as mud, i'm sure!
Thanks! .......Mr.D
Zebra: Stop MSEG re-triggering with internal note-on when using the arp?
-
- KVRAF
- 8237 posts since 22 Sep, 2008 from Windsor. UK
Easiest way I can think of is to use a 16 step mod mapper set to alternate, then each step in the mod mapper will be triggered by the arpeggiator. That will give you a one bar slope. Of course you could add more steps to the mod mapper for a longer filter sweep.
Mod mapper modulates cutoff, obviously.
Mod mapper modulates cutoff, obviously.
Soundcloud | Facebook |
-
- KVRian
- 1172 posts since 21 Jul, 2012
Doing it with a Mod Mapper set to alternate is one way, but to do it with an MSEG:
Set the MSEG to 'single' but make sure you have the loop on. That way it will loop around as long as the single note that plays the arp is held. It will retrigger at the beginning of the loop as soon as a new note is played.
Set the MSEG to 'single' but make sure you have the loop on. That way it will loop around as long as the single note that plays the arp is held. It will retrigger at the beginning of the loop as soon as a new note is played.
-
- KVRAF
- 4197 posts since 23 May, 2004 from Bad Vilbel, Germany
What LFO8 wrote 
In general: Set the MSEG mode to 'Single'.
If you want a one-shot instead of a looping MSEG, set the loop start and end to the last 2 points in the MSEG, then delete one of them. if you don't know how to do some of these things, look in the manual.
In general: Set the MSEG mode to 'Single'.
If you want a one-shot instead of a looping MSEG, set the loop start and end to the last 2 points in the MSEG, then delete one of them. if you don't know how to do some of these things, look in the manual.
-
- KVRist
- 129 posts since 16 Feb, 2013 from Sydney
Just a quick FYI, as this has caught me out a few times....
There is a (long-standing) bug with the 'single' MSEG when used with the Arp - if it has a loop, then the 'release' segments after the loop end will never be executed, even after all keys have been released
There is a (long-standing) bug with the 'single' MSEG when used with the Arp - if it has a loop, then the 'release' segments after the loop end will never be executed, even after all keys have been released
-
- KVRAF
- 4197 posts since 23 May, 2004 from Bad Vilbel, Germany
I could be wrong, but I think that's on purpose, Ed (i.e. not a bug). It ensures that 'Single' is practically like a 'one-shot' envelope in which the length of the gate is irrelevant.
-
- KVRist
- 129 posts since 16 Feb, 2013 from Sydney
Latest builds - Revision 2709 [Tue Sep 23, 2014 6:16 am]
A working release segment would,
Howard wrote:Aha, I think we've seen that one before! If Michael hasn't already added this to our To-Dos, I will...EdHarvey wrote:MSEG bug with Arpeggiator...
If a MSEG is set to 'single' trigger and voice mode is set to arpeggiator, then the MSEG never leaves the loop stage even when all keys are released.
A working release segment would,
- behave the same in both arp & non-arp modes. i.e. be consistent...
- be really useful
-
- KVRAF
- 4197 posts since 23 May, 2004 from Bad Vilbel, Germany
