Support
Looper's Delight
|
Support |
|
|
Just remembered a related hint that is useful. When you have set up a rack in Live to handle your patches/plugin instances you need to scroll through all of them before you begin to play. If you forget to do this you may nevertheless run into nasty crackling audio drop-outs when switching between patches. My guess is that Live doesn't automatically go through all patches to fixate a memory structure for safe playback, so you need to initially kick Live's ass to assure a decently behavior. (this is true for many other music apps, not only Live) Greetings from Sweden Per Boysen www.perboysen.com http://www.youtube.com/perboysen On Thu, Jan 19, 2012 at 8:40 PM, Per Boysen <perboysen@gmail.com> wrote: > Hi Kris, > > "Rule number one" when dealing with hosted plugin instruments is to > not call up patches like we do it on a hardware device. This because > that would force the plugin host application to reset its memory > structure on-the-fly and as you know the extra time buffer for this > doesn't exist in music software - since there is always a next note to > play in time, no time for rest. > > So how is this issue solved in real-time music applications? By pre > loading many instances of the plugins, each one set to the preferred > preset patch. Mainstage does that right away and recalls by MIDI > Program Change but with Live you need to first create an > instrument/effect rack. Inside this rack you load up many instances > set to all the preset patches you want to use. When looking at the > rack GUI click the little box named "Chain"; a grid with 128 points > will open. Each of those 128 points may host one of your patches > (unique plugin instance loaded for this patch). On the upper > horizontal row you will see an orange colored marker; click MIDI Learn > (upper right in global window), click the orange marker and send in a > MIDI CC value. Each MIDI CC offers 128 values so if for example you > want to use the modulation wheel to scroll between patches your first > patch will be recalled by CC#01-01, second patch by CC#01-02 und so > weiter. The mod wheel was a bad example though, because you may want > to use some physical controller that is incremental, letting you > advance by one patch at a time. > > If you want to use two pedal switches or push buttons, one for Next > Patch and the other for Previous Patch, you need Max For Live. The M4L > device that does this is named "rack inc-dec". > > Oh, I almost forgot: For this rack method of switching patches you > have to first save each patch into Ableton Live's own format. > > Greetings from Sweden > > Per Boysen > www.perboysen.com > http://www.youtube.com/perboysen > > > > On Thu, Jan 19, 2012 at 7:27 PM, Kris Hartung > <krispen.hartung@gmail.com> wrote: >> Here's one for you Live gurus. So I'm using Live to host my VST >> synths and >> the Reaktor VST, which has my ensembles (soft synths) and snaps (like >> patches or presets) inside of that. This is what I'm struggling with >> and >> I'm not sure if there is a solution. >> >> Let's say I have a favorite VST synth loaded in a MIDI track. And >> inside >> that VST synth, I have a favorite patch. Right now, if I want to access >> that patch in a live performance context, I have to first activate the >> MIDI >> track (because I don't want it playing until that point), then click on >> the >> VST synth's menu of presets, and then manually select the preset. With >> Reaktor it requires an additional step, since Reaktor itself is a >> collection >> of synths. I have to activiate the MIDI track that has Reaktor in it, >> select >> the Ensemble (synth), and then select the snap (patch). That's three >> steps. >> It is a royal pain in the ass and total improv buzz killer. >> >> What I'd really like to do is hit a single MIDI button or pad on Axion >> 25 >> that goes directly to the patch I want and combines all these steps >> together. Is there a way to do this? >> >> Kris >> >>