Omnivocal does not respect other track’s key editor SOLO button. If I edit a keyboard midi in key editor and press the red SOLO button, all other tracks mute - except the omnivocal. Perhaps I’m overlooking something? Is there something going on in Cubase? I also had a instrument track that was not visually muted but had to press the mute button twice in the project window to make it sound again.
I can confirm that. The MIDI activity LED in the OmniVocal window goes out, but the sound is still output.
That is an unfortunate side effect of Omnivocal not just being another plugin but being a bit special.
Everybody has the same behaviour. I think muting the Omnivocal tracks helps.
Even though OmniVocal is a “special” and, moreover, excellent plugin, it should adhere to Cubase conventions. At the latest when it is no longer in beta.
I wonder whether there are more interactions with Cubase that result in some quirks. I’ve tested on a public domain song, (old Italian traditional, that I made into a Jazz ballad). Working with this 3 instrument track project I found: (1) At some point the Omnivocal did not respond to pitchbend info anymore, had to setup a new Cubase track. (2) Using Omnivocal with an effect like pingpong delay produces artifacts that can not be expected from the delay settings. (in project ‘offline’ mixdown, as well as real time). But otherwise it is already an incrediable useful tool. Anways you can download the project from: https://hamicast.nl/hans/yamahaomnivocal_f3648248-f202-4551-a1bf-cf306df0afc7/ there is a noticable echo quirk going on midway the song