How to save a mapping for VST synth ?
How to save a mapping for VST synth ?
Hello,
Actually, each time I need to control a VST synth, I re-create the mapping for my midi controller.
Is it possible to save this mapping inside Live as a mapping preset for a specific VST synth?
I would like to be able to open these mapping on a track where I have a VST synth.
Regards,
Pierre.
Actually, each time I need to control a VST synth, I re-create the mapping for my midi controller.
Is it possible to save this mapping inside Live as a mapping preset for a specific VST synth?
I would like to be able to open these mapping on a track where I have a VST synth.
Regards,
Pierre.
Re: How to save a mapping for VST synth ?
I have the same problem!!!pmestrez wrote:Hello,
Actually, each time I need to control a VST synth, I re-create the mapping for my midi controller.
Is it possible to save this mapping inside Live as a mapping preset for a specific VST synth?
I would like to be able to open these mapping on a track where I have a VST synth.
Regards,
Pierre.
drop it in a rack, assign macros, save the rack.
there are no presets for plug in assignments. you can only save midi assignments on a project level, not on a VST level. IOW no you can't load up a plug in and also load up a preset of assignments.
there are no presets for plug in assignments. you can only save midi assignments on a project level, not on a VST level. IOW no you can't load up a plug in and also load up a preset of assignments.
In my life
Why do I smile
At people who I'd much rather kick in the eye?
-Moz
Why do I smile
At people who I'd much rather kick in the eye?
-Moz
-
guerillabass
- Posts: 61
- Joined: Wed Jun 11, 2008 10:22 am
-
guerillabass
- Posts: 61
- Joined: Wed Jun 11, 2008 10:22 am
cool. but you'll go back to being pissed off when you realize that there are only 8 macro assignments. even then you're limited to an arbitrary 128 plug in parameters to control.guerillabass wrote:Thanks for the rack adviceTone Deft wrote:drop it in a rack, assign macros, save the rack.
there are no presets for plug in assignments. you can only save midi assignments on a project level, not on a VST level. IOW no you can't load up a plug in and also load up a preset of assignments.
Live needs work in this area.
In my life
Why do I smile
At people who I'd much rather kick in the eye?
-Moz
Why do I smile
At people who I'd much rather kick in the eye?
-Moz
so the bit about the macro (something I rarely use, if ever) is meant as an alternative for midi assignments rather than as a workaround to get there. It kind of saddens me that I'm going to have to live with this. Hopefully it'll be around in the next release? But who am I kidding. It's already been two years if not longer since this feature was requested.Tone Deft wrote:drop it in a rack, assign macros, save the rack.
there are no presets for plug in assignments. you can only save midi assignments on a project level, not on a VST level. IOW no you can't load up a plug in and also load up a preset of assignments.
Thanks for the alternative though. I might have to look into that once I get over the fact that my X-Station will only be used as a control surface for Live's main board.
racks are ways of bundling and controlling groups of effects.
they're also a great way to make your brain hurt and have you throwing the Live manual around your studio, you can make quite complex things with them. you can also keep it simple, cool devices.
really what you want is an automapped device, I'm not sure if yours is supported, google around a bit to see what's up with that.
they're also a great way to make your brain hurt and have you throwing the Live manual around your studio, you can make quite complex things with them. you can also keep it simple, cool devices.
really what you want is an automapped device, I'm not sure if yours is supported, google around a bit to see what's up with that.
In my life
Why do I smile
At people who I'd much rather kick in the eye?
-Moz
Why do I smile
At people who I'd much rather kick in the eye?
-Moz
-
David Brent
- Posts: 42
- Joined: Fri Jul 27, 2007 7:09 am
-
bosonHavoc
- Posts: 1936
- Joined: Wed Sep 19, 2007 8:34 am
- Location: Austin, Texas
- Contact:
-
habibelhabab
- Posts: 15
- Joined: Sat Jul 28, 2007 4:26 pm
to be honest, I haven't really been keeping track of the frequency of VST usage. I think what really gets my goat is not being able to simply copy another instance of a the midi map of a VST that has already set up and mapped in a song. This lack makes my workflow really enmired in stupid workarounds.
the only solution I've found...
is dropping in the vsti's you often use to an empty set..
map everything...
save the set...
(you can save it as a template... so the fully mapped set will load automatically when you start live)
then drop tracks from outside...
after ...you can delete what you don't use...
my template set for the studio has :
1. Operator fully mapped
2. pro53 fully mapped
3. midi cc envelopes and program changing clips for the evolver.
4. all functions in live are mapped ... so I can do anything I want from the BCR...
(except 'loop select')
I use the mapped instruments to build sounds as though it was hardware...
when I build a sound with the Operator for instance...
and I want to build another sound...
I just duplicate the Operator channel...
and build antoher sound with the fully mapped Operator...
...I have also a template for jam sessions... and a template for DJing...
all differently mapped...
it's still a workaround.... but it works for me...
is dropping in the vsti's you often use to an empty set..
map everything...
save the set...
(you can save it as a template... so the fully mapped set will load automatically when you start live)
then drop tracks from outside...
after ...you can delete what you don't use...
my template set for the studio has :
1. Operator fully mapped
2. pro53 fully mapped
3. midi cc envelopes and program changing clips for the evolver.
4. all functions in live are mapped ... so I can do anything I want from the BCR...
(except 'loop select')
I use the mapped instruments to build sounds as though it was hardware...
when I build a sound with the Operator for instance...
and I want to build another sound...
I just duplicate the Operator channel...
and build antoher sound with the fully mapped Operator...
...I have also a template for jam sessions... and a template for DJing...
all differently mapped...
it's still a workaround.... but it works for me...
