Setup: I am running Vital 1.5.5 (free) on Windows 10
Occasionally, this bug will trigger when I am playing MIDI through a Loop Audio port via Musescore 3.6 (which has MIDI output as an option) or Audacity. I don’t know the precise set of conditions that initially triggers its tendency to do this, as it behaves normally for a bit, but once active, it is re-triggered when a MIDI track in Audacity is finished playing (or stopped) or a note is played in Musescore.
What happens is that all the tones from Oscillator 1 become a C3. The other 2 oscillators are unaffected. I can go to the “Advanced” page and click on the purple “Note Track” to gray it out, and then click on it again to turn it purple again, and it resets the issue until it is triggered again (by playing and stopping in Audacity or playing a note in Musescore). Likewise, I can also switch/reset the presets, and that resets it.
Oscillator 1 works, however, if it is being played on a sustained note, or if any of the channels currently have sustain active, even if they have no notes that were ever played.
My digital piano plays the same way, with oscillator 1 defaulting to C3 unless I use its sustaining pedal.
This bug occurs regardless of whether or not I have my digital piano connected to the computer.
When I restart my computer, the bug seems to subside for a while until I do something that somehow triggers it. I’m not sure what bugs are occurring where, but I would imagine that something is at least occurring on Vital’s end if resetting the note track button works, even if it doesn’t indicate that it is off and it sounds like it is off.
This issue is never triggered by playing on the digital piano.