Thanks for the update (Prophet 5 & 10 Main OS 2.0.4 and Panel OS 1.1.3).
Here are some observations:
- New Feature: Adjustable Velocity and Aftertouch Amounts per patch
Judging by ear, the new Velocity Amount parameter works by scaling the amplitude of the envelope based on the received velocity value. In other words the envelope is getting shallower the lower the Velocity Amount is set. As a result with Velocity Amount set fairly low the filter envelope barely opens. In addition the output volume of presets with low Velocity Amount settings are fairly low. Often the main volume pot isn’t able to compensate for the volume drop (and of course the main volume can’t be saved with the preset).
I’m wondering… what if the new ‘Velocity Amount’ parameter is interpreted / implemented as a ‘Velocity Sensitivity’ parameter instead? In this approach the velocities values are processed - not the envelope. Lowering the Velocity Amount could for example process the incoming velocity data with an increasing logarithmic function thus the response to velocity is getting less and less noticeable. One could argue that this is very similar to what the global Keyboard Vel Response parameter is doing. However with 128 values the ‘Velocity Amount’ parameter allows for much finer adjustments. It also reacts to external MIDI Note messages and more importantly it can be stored per preset.
In my view replacing the current ‘Velocity Amount’ with a ‘Velocity Sensitivity’ parameter has a couple of advantages:
- The filter Envelope Amount as set on the P5/10 is preserved. As a result the programmed cutoff frequency can still be reached
- The Amp output isn’t dropping in volume as much
- Consequently switching Velocity On / Off doesn’t change the sound as much overall
- Likewise preset without velocity can be changed to respond to velocity with only small filter and amp adjustments to compensate for the change of sound at lower Velocity Amount settings
- Arguably… playing the keyboard dynamically with lower Velocity Amount (Sensitivity) settings sound more “musical” in comparison (personal perception)
Possibly my thinking above is flawed… nevertheless it would be interesting to hear your opinion.
- Changed Feature: Adjust balance between programs in a split/stack by holding PRESET and turning the volume pot. Volume pot centered is equal volume on both patches.
The new implementation allows to easily balance the volume levels of split and stack sounds. However there is also a small drawback:
In the previous OS you could hold the velocity button and program a discrete volume level per stacked/split preset. While undocumented this parameter also worked with “regular” presets without being in stack or split mode. So I used this feature to adjust the output volume for each of my “normal” (non-stack/split) presets so that they have roughly the same output volume when switching through presets. This turned out to be especially useful with 'unison' presets as they are usually much louder. Fortunately this can still be done, however the workaround is somewhat convoluted.
Workaround:
1. enable stack or split mode
2. as the "A" preset load the preset for which you like to set and store the output volume
3. as the "B" preset load a "bogus" preset (I use a silent preset with all oscillator waveforms turned off)
4. adjust the volume by holding the 'Preset' button while turning the 'Volume' knob
5. switch back to the “A” layer
6. save the stack/split preset
7. turn stack/split off
8. save the preset again --> Result: The volume level set in step #4 is saved with the preset and stays persistent even when not in stack or split mode.
23 Replies
4014 Views