Hey friends:
Having an issue sending MIDI clock from Cubase 14 to the Future Retro Vectra synth.
When I play a sequence on the Vectra when NOT connected to MIDI, it plays normally.
However, when I connect the Vectra’s clock to Cubase, the sequence plays much faster, (despite the tempo being set the same) as though Cubase is sending too many pulses. ALSO, the notes in the Vectra sequence sustain until the next note begins, as though they have no note-off information.
I suspect this is a setting in Cubase that needs changing (there are no options within the Vectra outside of midi channel), but haven’t been able to figure it yet.
I’d really appreciate any help. The Vectra is a very cool synth, but it sure hasn’t agreed well w Cubase so far. The synth has performed fine w Ableton and Logic.
Here’s a tiiny video showing it:
Mac Mini M4 Pro, Sequoia, Cubase 14, MIDI running thru MioXL.
Thanks for that. I know it’s hard to see in the video, but it’s set to 4-4. You can see it on the second screen (the one that says PLAY at the top). On the right side, it’s showing LENGTH: 16 steps, at 4-4.
Hey there! So yep, besides selecting the MIDI channel on the Vectra’s basic global page, the only options for the vectra’s MIDI / clock are those shown in the video…
In the video, you’ll notice on the page marked SEQUENCER, beside TEMPO, it will either show A. the internal tempo the Vectra is set to, or B. (if switched, by pressing the knob to its right) MIDI, which of course means midi clock.
Attached are the requested screenshots! Thank again!
If you’re sure, that’s not the issue, next question I have:
Since you’re also sending clock data to other hardware, is there any hardware MIDI connection from another one of your hardware devices to the Vectra Synth?
If yes, is there a chance, that it passes through the Cubase clocking, so that you end up getting duplicate clock pulses into the Vectra?
What happens when you de-select your Vectra as a MIDI Timecode destination? I’m kind of stumped, but as @Nico5 is suggesting–it seems like there could be another MTC master. Have you turned off the other devices attached to you mioXL while troubleshooting this?
I BELIEVE it is solved!?! After recording the Vectra into Cubase at 120bpm internal, and then 120bpm Cubase clock, I could see the latter was playing exactly twice as fast. So despite all other midi gear being off, and inside an empty project (no other MIDI track or VST triggering etc), the Vectra was still receiving twice as notes as it oughta be.
You all were very helpful in encouraging me to click where I hadn’t in a while… so within Project Sync Setup –> Destinations, I unclicked the clock destination labeled “To the Vectra.” And BANG! It immediately started playing properly. So then I slowly unclicked the other Destinations until I found the one that made the Vectra stop altogether.
So short of the long, inside Auracle, the set-up app associated w my MioXL MIDI router, another channel had somehow started additionally routing to the Vectra. Not sure how or when that happened, but it seems to be the culprit.
MioXL works great. So great I rarely need to look at it. But that also means I’m a bit in the dark each time I actually have to! Thanks again everyone. You definitely helped me sleuth it out.
