![]() You shoud always bear in mind that the state of every plugin you use in a rackspace will be stored within this rackspace! So changing rackspaces will also recall the settings of all the plugins in it. And these can be “mirrored” onto your rackspace panel by using widgets. So if a plugin offers you some dozens of parameters on switches and knobs, you maybe will use only five or ten of them. five… and mostly it would be something like “switch effects on or off” or “change gain”. I guess in most cases it might be a number of max. Maybe you are used to map your controller directly to the plugin, but how many of the parameters that a plugin offers do you really change during a performance? Of course, it needs a bit of work to build a panel, but i’d say it’s always worth the effort in terms of live-usability! ![]() ![]() That way you are not only more flexible regarding to how you setup your whole rig (or if something should change, like Pianopaul already mentioned), but you have also only those parameters under control which you really need for your performance… not more and not less. The main purpose of GigPerformer is the best possible support of “Live performance”, like the name already states… and one the best features of GigPerformer to achieve this, is the use of widgets and user-defined panels. As you might have noticed already, GigPerformer follows a diffrent concept than most of the other VST-hosts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |