FR - Saving CC configurations as pre-sets

[Bunnyboy]

Timewastin had this idea, so all props to him

Midi CC maps in VST/i for automation. Currently, every time an instance of a plug-in is loaded, CC mappings have to be configured.

So have the ability to save configurations for CC mappings as a file like a .fxp/.fxb.

Save and open them in from the file menu in the plugin's interface

[Rellik]

Just wanted to add that this, ideally, could extend to the Mixer and any automatable comps as well!

I'd like to see some way to control the entire mixer using CC's that only affect it when no track is selected (because in the tracks the CC's are sent to the VSTi, in which they might be used for something else), as well.

Great idea about the MIDI CC maps. And I figure this is the place to rave about how great it is that eXT automatically begins searching for fxb/fxp inside the directory you loaded the VSTi from hopefully it will be the same with CC maps.

[Branis]

those are fantastic ideas

[ohm]

well, if the sequencer only relayed MIDI events from one channel instead of all of them, there would be a separate channel available for the mixer, for the mixer in another sequencer, etc, etc.
I think it's a bad solution that you have to deselect a track in order to control the mixer via MIDI

but I totally agree that the mixer should be MIDI controllable, in fact - all XT sliders and controls should be MIDI controllable.

[ohm]

a bump and a big +1 for the ability to save / load midi CC mappings. Let's have this in XT2 please.

I have one more idea to add to the FR:

Make it possible to define a default CC map that will automatically load each time you create a new instance of a VST / comp.

It could be done as simple as saving the mapping with the filename sampler.map or mixer.map or synth1.map. So if a CC-map file is found, with the same filename as the VST / comp, it's loaded by default.

The same idea could be extended to fxb files - I very often want to replace the default banks of a VST plugin - if this was as simple as saving and fxb with the same filename as the .dll this would be excellent.

[Maniah]

Yeah, these are good requests. +1

[djsubject]

+1, of course

[tjvigil66]

Saving/loading CC maps would be fantastic!!!

Until cc map files are implemented, you could always create/save a EXT file that contains only your synth or effect with CC#'s mapped to taste. Instead of loading the synth or effect, load a VST instance of eXT with the EXT file you created for your synth. All the CC's are mapped & ready to go!

[DarkStar]

+++1

[pHz]

+1

slainte rob

[DarkStar]

I see your +1 and raise you 1

[rsmus7]

and another raise +1

[robenestobenz]

The same idea could be extended to fxb files - I very often want to replace the default banks of a VST plugin - if this was as simple as saving and fxb with the same filename as the .dll this would be excellent.

I've wanted this for so long. I tend to make my own banks, so often an extra step is incurred each time I add a plugin.

[antiporter]

+1

[waveriderarts]

I would love it as well.....


But changes are coming in CC remoteland, maybe this Novation thing could be fun to use as well:
http://www.novationmusic.com/automap/

or something like what is used in Reason where you dont even have to map stuff.

...I think those 2 technologies are important also.

But we could use a config file or something to tell how each plugin is mapped, but once you load 2 or 3 they will fight for assignments