Workarounds for no Program Changes?
Program Changes for Efx
Will this workaround work for vst effects also? What happens if the plugin doesn't respond to program changes? Is there a way to send program changes to switch the presets saved directly in Ableton? Do I need a seperate midi track for each plugin loaded up?
Chris
Chris
Works like a charm, thanks!!! I actually put all 128 of them in 128 scenes and mapped a midi button to the "play clip in selected scene" button.Machinate wrote:^^^^^ what he said: all the program change messages for bank one are on our website, stick them in a folder and drag in the clips when needed - a lot easier than going through drop-down menus.
Friggin brilliant. Kudos to Machinate!!!
Unfortunately Live's instruments don't respond to program changes, but hey, that's life. Maybe version 6.cml3160 wrote: Will this workaround work for vst effects also? What happens if the plugin doesn't respond to program changes? Is there a way to send program changes to switch the presets saved directly in Ableton? Do I need a seperate midi track for each plugin loaded up?
Chris
This workaround functions perfectly for many VSTs, but that depends on each one. Pro-53 (my current fav virt analog) works great with no pops or dropouts at all when you change progs.
With Live 6, I made a MONSTER device rack for my drums, and I'm working on one for synth basses.
I basically created 16 impulses in paralell within a device rack, and then set the range for each so that as I move a macro knob it selects a different drum kit. It takes about 30 seconds to load with no audio streaming off the 7200 RPM hard disk, so if you create a large rack like this with a lot of samples in it (multilayered Sampler, impulses, etc) don't drop it in a set while it's playing - start with it in a dedicated channel all by itself.
You could easily do this with 127 impulses (or other device), it would just be a wickedly large device group.
Since Live only plays one device at a time, you won't end up with an increased CPU cost.
Very nice solution in my books.
Here's what it looks like:
Note that I've selected the "chain" to view, rather than keyrange or velocity. In this case, you can see that the kits all fade into one another using the small bars above the ranges - except for between kits 33-48 and 48-56 which are a sharp transition between them.
To map it to a knob, select the little bar at the top, as shown here:
It's helped me 100%! This is better than a workaround, it's 95% the real deal, except that you use a CC instead of a program change.
I basically created 16 impulses in paralell within a device rack, and then set the range for each so that as I move a macro knob it selects a different drum kit. It takes about 30 seconds to load with no audio streaming off the 7200 RPM hard disk, so if you create a large rack like this with a lot of samples in it (multilayered Sampler, impulses, etc) don't drop it in a set while it's playing - start with it in a dedicated channel all by itself.
You could easily do this with 127 impulses (or other device), it would just be a wickedly large device group.
Since Live only plays one device at a time, you won't end up with an increased CPU cost.
Very nice solution in my books.
Here's what it looks like:
Note that I've selected the "chain" to view, rather than keyrange or velocity. In this case, you can see that the kits all fade into one another using the small bars above the ranges - except for between kits 33-48 and 48-56 which are a sharp transition between them.
To map it to a knob, select the little bar at the top, as shown here:
It's helped me 100%! This is better than a workaround, it's 95% the real deal, except that you use a CC instead of a program change.
The first suggestion would be to use the latest update of Live 5. Which is 5.2.jendask wrote:I am using Live 5.01 and Vsti's like Pro53, Arturia moog, Mellotron and B4.
Could you suggest something about my case?
The synths you mentioned respond to program changes. You can send 1 program change from each MIDI clip.
Have a good long and hard look at a midi clip or check the manual.
Cheers
- B
jendask wrote:I am using Live 5.01 and Vsti's like Pro53, Arturia moog, Mellotron and B4.
Could you suggest something about my case?
Is this something that also works in Live 5.01, or is it essential to upgrade to 5.02?hoffman2k wrote:The first suggestion would be to use the latest update of Live 5. Which is 5.2.
The synths you mentioned respond to program changes. You can send 1 program change from each MIDI clip.
Maybe I haven't made myself clear, though...
Let's say that during a jam I play in one midi track using Pro 53 and I change programs in the instrument itself. Then I can listen back to what has been recorded but I cannot recall which programs I have used, because these changes I have made haven't been written anywher in Live like "automation". Sorry for using probably wrong terms but I am a beginner in Live, recently moved from Cubase where this kind of automation was recorded automatically.
Last edited by jendask on Tue Dec 19, 2006 12:34 pm, edited 1 time in total.
The iRack in Live 6 rules!!!
Ableton just needs to fix some bugs (602b) and i'll use it on stage.
Ableton just needs to fix some bugs (602b) and i'll use it on stage.
Live 6.0.3 Win XP sp2, P4 2.8 GHz, 1 GB, UXGA video, RME Multiface (1), Nord Lead 3, Korg X5D, TR-Rack, ER-1, Roland Juno 106, JV-2080, Elektron Machinedrum-UW, SidStation, SPL Charisma, Soundtracs CP6800 (40/12/24), Genelec 1030A, Furutech TP80, etc.
Could someone please answer to my simple and maybe... stupid question?