Send initializing commands to virtual instruments to minimize misconfiguration risk

[rualark]

Develop framework:

• [x] Add CCName vector [cc number] with cc names
• [x] Add KswGroup vector [pitch] with group numbers
• [x] Add CCInit vector [cc number] with initial values
• [x] Add KswInit vector [pitch] with 1 when ksw should fire initially
• [x] Parse CC_Name
• [x] Parse KswGroup
• [x] Parse each InitInstrument, overwriting CC/Ksw values and resetting alternative ksw in each group
• [x] Send initial CC and ksw to midi

Implement for each instrument:

• [ ] Embertone
• [ ] Samplemodeling Brass
• [ ] Samplemodeling Woodwinds
• [ ] Piano
• • [ ] Check that panning works (easiest way is to check soundchecks)
• • [ ] Check that volume works (easiest way is to check soundchecks)
• • [ ] Check that all CC are named and set
• • [ ] Check that all keyswitches are named and set
• [ ] Vocal
• [ ] Organ
• [ ] Percussion
• [ ] Jazz drum set
• [ ] Harp
• [ ] ...

[rualark]

Initialization path:

• VST instrument parameter in VST
• VST instrument paramter binding to CC or keyswitch in VST
• CC_Name and KswGroup name binding in instrument config
• Initialization of parameter with value (obsolete InitCommand) in instrument config

[rualark]

How to implement:

• [ ] Check that panning works (easiest way is to check soundchecks)
• [ ] Check that volume works (easiest way is to check soundchecks)
• [ ] Check that all CC are named and set
• [ ] Check that all keyswitches are named and set