PlanetZ forums - scopeusers.com

Currently, I use a Midi-sequencer to drive synths, scope/xite and a cubase for audio-recording.
For various reasons, I'd like to get rid of cubase in smaler projects and use the VDAT instead.

After reading through some treads, I learned, that I cannot run the Vdat as a Midi-slave to my sequencer.
So I read the manual, where VCR-128 is said to be able to sync a sequencer, beeing Midi-Slave.
This didn't work for me. I cannot see any Midi-data coming out of VRC-128.

What is the way to keep a Midi-sequencer in sync with the VDATs ?

Look at Adern.com site, free devices, MIDI Clock to Click.
I have some devices for SMPTE and MTC too but my iPad won't let me post as file here.
Will share when I'm State side next week.

I tried the clock2click. It provides a Midi-clock-message.
But I would also need a start and a stop message.

Maybe my approach is stupid, but I'd like to have a start button somewhere, that starts the sequencer and the VDATs.
If it's located in scope or the startbutton of my sequencer doesn't matter.

Check out Alfonso's Modular Patch that deals with transports iirc.
I'll be back in a week and dig them up.

Haven't done this in a while, but Cubase used to have an option to send clock via ASIO. One of the ASIO source modules in Scope has a clk pad, which can be connected to VDAT providing sync.

Still fighting with this topic.
My problem is, that my midi-sequencer cannot act as slave.
The sequencer slightly drifts in clock..

With an vintage tripple-dat, it's no problem. It follows just perfect.

With cubase beeing asio-synced to scope, speedchanges are not followed.

Is there a way to get vdat or asio to follow the midi-clock ?
( clock 2 click is nice, but it's the inverse solution)

An Asio with clk-out cannot be found on my 5.1 system...