Workarounds for no Program Changes?
Workarounds for no Program Changes?
Hey all.
Just looking to see what people are doing to workaround the inability of Live to handle program changes.
I currently have a live set that has over 60 channels... All with different instruments. I only use about 2-4 at a time, but since I can't put in program changes for VST instruments, I've been reduced to scrolling back and forth like a madman trying to be able to change my instruments.
Luckily, if a VST instrument isn't in use, it doesn't generate CPU load, so it's a relatively effective, though ineffecient workaround. I just arm record any track I like and bang away.
The problem with Live Clips and Live Sets is that I cannot save midi or key mappings to them.
I started using clip envelopes to change ALL of my parameters when I'm synth programming, but it's getting fucking tedious.
So, any suggestions to reduce the number of channels I'm using?
Just looking to see what people are doing to workaround the inability of Live to handle program changes.
I currently have a live set that has over 60 channels... All with different instruments. I only use about 2-4 at a time, but since I can't put in program changes for VST instruments, I've been reduced to scrolling back and forth like a madman trying to be able to change my instruments.
Luckily, if a VST instrument isn't in use, it doesn't generate CPU load, so it's a relatively effective, though ineffecient workaround. I just arm record any track I like and bang away.
The problem with Live Clips and Live Sets is that I cannot save midi or key mappings to them.
I started using clip envelopes to change ALL of my parameters when I'm synth programming, but it's getting fucking tedious.
So, any suggestions to reduce the number of channels I'm using?
I know that when I'm using a vsti in Live, pushing the "program up (or down)" buttons on my K-station change the presets on the vsti, fwiw. Also, when I type in a new program number, it often changes the vsti's patch, though I've yet to scientifically figure out what the logic is--ie what number entered on the k-station=what vsti patch. lets hope for this in 6 at the very least!
Dell Studio XPS 8100 Windows 7 64-bit, 10 GB RAM. RME Multiface, Avalon U5 & M5, Distressor, Filter Factory, UC33e, BCR-2000, FCB1010, K-Station, Hr 824 & H120 sub, EZ Bus, V-Drums, DrumKat EZ, basses, guitars, pedals... http://www.ryan-hughes.net
Why don't you use dummy clips? Just create another clip on the same channel where your VST is(double click on a slot) then select another program from the list. When you want a particular program loaded just fire the corresponding clip from the keyboard. You can name the clip with the name of the program for convinience.
???geo wrote:Why don't you use dummy clips? Just create another clip on the same channel where your VST is(double click on a slot) then select another program from the list. When you want a particular program loaded just fire the corresponding clip from the keyboard. You can name the clip with the name of the program for convinience.
Can you explain that a little better?
I mean, I select a preset for a VSTi, and it's not a property of the clip... I can play a dozen different clips all day and the sound of the VSTi doesn't change...
Little help?
What list? The list of presets that's in the instrument below? That's totally clip independant, and if it's not, then could you explain how I can put two clips in the same channel and have one trigger midi using preset A and another in the same channel trigger preset b?geo wrote: then select another program from the list.
i think he's talkign about the prog change ability of MIDI clips.
try this:
on your track playing the VSTi, create a blank MIDI clip.
then in the clip properties (bottom of screen, over on the left) change the prog -> sub bank -> bank to whatever patch in the vsti you want.
the clip has to be set to auto for the clip to play (of course...) so make sure to rec enable if you're playing live.
some vstis start at 0, some start at 1. so you need to double check the patch # you want based upon the vsti.
i've found though that changing Reaktor patches and other vstis cause a large CPU spike and basically aren't usable in a live situation. but it might work for you...
let me know how it works out - (or not?)
cache
try this:
on your track playing the VSTi, create a blank MIDI clip.
then in the clip properties (bottom of screen, over on the left) change the prog -> sub bank -> bank to whatever patch in the vsti you want.
the clip has to be set to auto for the clip to play (of course...) so make sure to rec enable if you're playing live.
some vstis start at 0, some start at 1. so you need to double check the patch # you want based upon the vsti.
i've found though that changing Reaktor patches and other vstis cause a large CPU spike and basically aren't usable in a live situation. but it might work for you...
let me know how it works out - (or not?)
cache
www.cachemusic.com
myspace.com/1800cachecall
myspace.com/autonomousunit
myspace.com/kinesicla
myspace.com/pocketonfridays
myspace.com/1800cachecall
myspace.com/autonomousunit
myspace.com/kinesicla
myspace.com/pocketonfridays
works fine for me - I did a live setup a month back with about 8 midi clips to switch between Reaktor sounds for solos and stuff . Worked great.Cache wrote: i've found though that changing Reaktor patches and other vstis cause a large CPU spike and basically aren't usable in a live situation. but it might work for you...
let me know how it works out - (or not?)
cache
mbp 2.66, osx 10.6.8, 8GB ram.
-
Michael-SW
- Posts: 2054
- Joined: Sat Apr 30, 2005 4:05 pm
- Location: Stockholm, Sweden
Just a small question on that topic. If you have record enable activated (which is the only way to work with program changes and playing the instrument live), then when you play it starts midi recording. I could deactivate the loop function of the midi clip so I won't hear the loop again over my newly played part but what if I switch to another clip with another program change and then back to my original one? I will hear it again, anyways...You see what I mean?Cache wrote: the clip has to be set to auto for the clip to play (of course...) so make sure to rec enable if you're playing live.
Why not just use 2 midi tracks? One for midi clips and one for live input. Turn monitor to "in" instead of arming the track.geo wrote:Just a small question on that topic. If you have record enable activated (which is the only way to work with program changes and playing the instrument live), then when you play it starts midi recording. I could deactivate the loop function of the midi clip so I won't hear the loop again over my newly played part but what if I switch to another clip with another program change and then back to my original one? I will hear it again, anyways...You see what I mean?Cache wrote: the clip has to be set to auto for the clip to play (of course...) so make sure to rec enable if you're playing live.
Hmm...it doesn't seem to work, I got 2 midi channels, the first with the VST on and record enabled, the second receiving midi from track 1(so MIDI From comes from Track 1) with 2 different empty midi clips on the session view having two different program changes and Monitor set to In. When I fire the clips it doesn't change the program.hoffman2k wrote:Why not just use 2 midi tracks? One for midi clips and one for live input. Turn monitor to "in" instead of arming the track.geo wrote:Just a small question on that topic. If you have record enable activated (which is the only way to work with program changes and playing the instrument live), then when you play it starts midi recording. I could deactivate the loop function of the midi clip so I won't hear the loop again over my newly played part but what if I switch to another clip with another program change and then back to my original one? I will hear it again, anyways...You see what I mean?Cache wrote: the clip has to be set to auto for the clip to play (of course...) so make sure to rec enable if you're playing live.
Yeah, I see, I see now, thanks a lot, man, that was a great advice!hoffman2k wrote:Track one doesn't need to be record armed. that track should be set to monitor in. Unless you want to record.
Track 2 needs to be set to auto. so that it actually sends out the program changes.
Program changes are like notes, they're ignored when you're working with dummy clips.