What happened?
Environment:
OS: macOS Apple Silicon M1
Plugin: Waves Tune Real-Time VST3
Hardware Context: Yamaha DM7 (Steinberg USB Driver), MIDI Touchbar 2.7
Description:
I am experiencing a bug with how Element passes MIDI velocity data to plugins to control parameters.
In Waves Tune Real-Time, MIDI control for the "Root" key parameter works by using a specific MIDI Note to target the dropdown menu, and the incoming Velocity of that note to dictate the specific value (the 12 musical keys are divided mathematically across the 0–127 velocity range).
When sending a fixed MIDI Note with a fixed, hardcoded Velocity through Element, the plugin fails to select the corresponding static value. Instead, with every identical MIDI input received, the parameter continuously cycles through different keys.
Steps to Reproduce:
1 Load Waves Tune Real-Time into an Element graph.
2 Route a MIDI input device to the plugin.
3 Configure the external MIDI controller to send a static Note On message with a fixed, unchanging velocity (e.g., Note C1 at exactly Velocity 59, which corresponds to the key of F).
4 Trigger the exact same MIDI note multiple times.
Expected Behavior:
The plugin should instantly snap to the exact key mapped to that velocity (e.g., 'F') and remain there consistently upon every trigger, as the exact same velocity integer is being passed to it.
Actual Behavior:
The plugin ignores the static velocity value and instead cycles through different keys/parameters on each subsequent MIDI trigger. It appears Element is somehow altering, scaling, or misinterpreting the Velocity data or the Note On/Off messages before passing them to the plugin.
Additional Context:
This issue does not occur when running the exact same MIDI hardware setup in other hosts (e.g., Reaper). In Reaper, the fixed-velocity MIDI triggers correctly lock the plugin to the expected target key 100% of the time.
This confirms the MIDI hardware is outputting the correct static values, and isolates the bug directly to Kushview Element's MIDI handling.
Version
1.0.0 (Latest)
Relevant log output
What happened?
Environment:
OS: macOS Apple Silicon M1
Plugin: Waves Tune Real-Time VST3
Hardware Context: Yamaha DM7 (Steinberg USB Driver), MIDI Touchbar 2.7
Description:
I am experiencing a bug with how Element passes MIDI velocity data to plugins to control parameters.
In Waves Tune Real-Time, MIDI control for the "Root" key parameter works by using a specific MIDI Note to target the dropdown menu, and the incoming Velocity of that note to dictate the specific value (the 12 musical keys are divided mathematically across the 0–127 velocity range).
When sending a fixed MIDI Note with a fixed, hardcoded Velocity through Element, the plugin fails to select the corresponding static value. Instead, with every identical MIDI input received, the parameter continuously cycles through different keys.
Steps to Reproduce:
1 Load Waves Tune Real-Time into an Element graph.
2 Route a MIDI input device to the plugin.
3 Configure the external MIDI controller to send a static Note On message with a fixed, unchanging velocity (e.g., Note C1 at exactly Velocity 59, which corresponds to the key of F).
4 Trigger the exact same MIDI note multiple times.
Expected Behavior:
The plugin should instantly snap to the exact key mapped to that velocity (e.g., 'F') and remain there consistently upon every trigger, as the exact same velocity integer is being passed to it.
Actual Behavior:
The plugin ignores the static velocity value and instead cycles through different keys/parameters on each subsequent MIDI trigger. It appears Element is somehow altering, scaling, or misinterpreting the Velocity data or the Note On/Off messages before passing them to the plugin.
Additional Context:
This issue does not occur when running the exact same MIDI hardware setup in other hosts (e.g., Reaper). In Reaper, the fixed-velocity MIDI triggers correctly lock the plugin to the expected target key 100% of the time.
This confirms the MIDI hardware is outputting the correct static values, and isolates the bug directly to Kushview Element's MIDI handling.
Version
1.0.0 (Latest)
Relevant log output