Does anyone have a sample project that syncs Audio and Midi between an Ultra A16, Syncplate, and Cubase and configures the remote control to start stop cubase.
I tried setting Ultra A16 to master and then take sync from BNC external in SFP and then use MTC->Clk to point to ASIO Dest to try and get Cubase to sync to cubase.
What options should I set in the MTC-Clk device and which sync type should I select in cubase? Asio or Asio/mtc.
Also I found that my luna Zlink destination -> Ultra A16 didnt seem to work when i used syncplate. Does ZLink HAVE to be the sync source? Is there a way to feed cubase sync from zlink?
And how to setup the remote control, i tried most permutations and nothing happens.
best configuration for syncing audio and midi with cubase, a
I suppose you work on one machine only.
-> Transport Sync
Midi clock provides a metronome and is most basic sync.
MTC is more 'clock one the wall', at midi accuracy. Both Midi Clock and MTC are send as midi data over midi cable.
EBU is clock on the wall, at samplerate accuracy. It is read/sent by Syncplate.
-> SampleRate Sync:
Set your DSP card master, slave A16. Cubase playing audio files ALWAYS follows the driver clock, here ASIO. This means that every sample that is read by Cubase, is sent out to your ASIO card when it asks for one. Due to current/ net voltage variations, a card never plays perfect 44.100Hz samplerate. This sync makes sure that all your wav files run smooth in sync as your driver asks for. This sync is transported via your ASIO driver.
Midi Clock, MTC or your EBU, can provide sync if you slave Cubase to an external sequencer, like a Video Editor, DAT or other computer. This type of sync is only for Transport sync, which means if you press play one one sequencer, the other one will follow and preferrably at the same speed. I don't think, from the explanation you gave above, that you have multiple sequencers. You can proceed to the next step. If you do have multiple audio sequencers/players, then you'll need your syncplate.
->Cubase Remote:
SFP: Connect SeqRemote to Seq Dest. Select the default preset, Cubase Control.
Cubase: go to Edit -> Preferences -> Key Commands -> Transport and Locations.
In 3.7, Cubase was preset to the preset in Seq Remote, now you have to do it yourself
Make sure Remote Key is set correspondingly, I advise keeping it on. Now start looking fo rCubase Transport functions that look like SeqRemote knobs. Open SeqRemote's command assignment, midi channel as you wish. Let's take notes as controllers, here in the example. But for practical reasons you might want to choose CC# or ProgChanges instead of notes as controller signals.
If you found corresponding Events, set
Event Type to 'Note' and dial in the note number you find in SeqRemote's Command Assign. You can Event value in Cubase, it will auto convert it to note. You can also type in B5 directly if you knew that was 95, I just type in 95 and Cubase converts for me
Repeat above step for every desired button on SeqRemote, and off you go!
I'm having somme trouble finding next track/prev track etc too, but browse thru the Key Command Preferences' other Tab pages and it must be there somewhere. For Spirit, normally
Whenever in doubt, come again.
at0mic.
<font size=-1>[ This Message was edited by: at0mic on 2002-05-09 18:38 ]</font>
-> Transport Sync
Midi clock provides a metronome and is most basic sync.
MTC is more 'clock one the wall', at midi accuracy. Both Midi Clock and MTC are send as midi data over midi cable.
EBU is clock on the wall, at samplerate accuracy. It is read/sent by Syncplate.
-> SampleRate Sync:
Set your DSP card master, slave A16. Cubase playing audio files ALWAYS follows the driver clock, here ASIO. This means that every sample that is read by Cubase, is sent out to your ASIO card when it asks for one. Due to current/ net voltage variations, a card never plays perfect 44.100Hz samplerate. This sync makes sure that all your wav files run smooth in sync as your driver asks for. This sync is transported via your ASIO driver.
Midi Clock, MTC or your EBU, can provide sync if you slave Cubase to an external sequencer, like a Video Editor, DAT or other computer. This type of sync is only for Transport sync, which means if you press play one one sequencer, the other one will follow and preferrably at the same speed. I don't think, from the explanation you gave above, that you have multiple sequencers. You can proceed to the next step. If you do have multiple audio sequencers/players, then you'll need your syncplate.
->Cubase Remote:
SFP: Connect SeqRemote to Seq Dest. Select the default preset, Cubase Control.
Cubase: go to Edit -> Preferences -> Key Commands -> Transport and Locations.
In 3.7, Cubase was preset to the preset in Seq Remote, now you have to do it yourself
Make sure Remote Key is set correspondingly, I advise keeping it on. Now start looking fo rCubase Transport functions that look like SeqRemote knobs. Open SeqRemote's command assignment, midi channel as you wish. Let's take notes as controllers, here in the example. But for practical reasons you might want to choose CC# or ProgChanges instead of notes as controller signals.If you found corresponding Events, set
Event Type to 'Note' and dial in the note number you find in SeqRemote's Command Assign. You can Event value in Cubase, it will auto convert it to note. You can also type in B5 directly if you knew that was 95, I just type in 95 and Cubase converts for me
Repeat above step for every desired button on SeqRemote, and off you go!
I'm having somme trouble finding next track/prev track etc too, but browse thru the Key Command Preferences' other Tab pages and it must be there somewhere. For Spirit, normally
Whenever in doubt, come again.
at0mic.
<font size=-1>[ This Message was edited by: at0mic on 2002-05-09 18:38 ]</font>
I will give examples why I'd want to use sync.
I have a GrooveBox, MC505, and want it to run sequences in sync to Cubase. I send Midi Clock from cubase (master) to 505.
I have S-5000, and want to sync it's LFO's to Cubase's . I send it Midi Cock too.
S-5000 is also samplerate sync'ed to SPDIF opt Out from Pulsar2, and sends ADAT back to Pulsar1, for mixing. I sync to SPDIF, cos I want smooth audio transfer, without glitches or clicks.
If I'd want to play 1hr music from S5000's sequencer in sync with Cubase song and Pulsar, I'd get myself a syncplate to connect to S-5000's EBU port, to provide perfect tight sync between both devices. EBU will tell Cubase what time it is in the song on the S-5000, at any sample that's been fired over the ADAT. LFO's, sequences or long triggered audio files will run in perfect sync now with the Cubase song.
I have no syncplate, but if I'd ever get it, you just have read why...
I have a GrooveBox, MC505, and want it to run sequences in sync to Cubase. I send Midi Clock from cubase (master) to 505.
I have S-5000, and want to sync it's LFO's to Cubase's . I send it Midi Cock too.
S-5000 is also samplerate sync'ed to SPDIF opt Out from Pulsar2, and sends ADAT back to Pulsar1, for mixing. I sync to SPDIF, cos I want smooth audio transfer, without glitches or clicks.
If I'd want to play 1hr music from S5000's sequencer in sync with Cubase song and Pulsar, I'd get myself a syncplate to connect to S-5000's EBU port, to provide perfect tight sync between both devices. EBU will tell Cubase what time it is in the song on the S-5000, at any sample that's been fired over the ADAT. LFO's, sequences or long triggered audio files will run in perfect sync now with the Cubase song.
I have no syncplate, but if I'd ever get it, you just have read why...
hi atomic , cool thanks
Its getting late now, 3am so Ill run through and try what you suggest tommorow.
Yes I just use 1 machine at the moment but may configure my other pc as a vst only box in the future - ill deal with that when the need arises.
And yes, for now I just use the one sequencer. When I talked about syncing midi from the sync plate I was really wondering whether the midi in cubase should (could?) be synced from the audio clock to keep them in time. Im guessing if I set the midi in cubase to sync to asio this will do that?
What does "clock on the wall" mean?
Ill have a go and if I dont get the expected results Ill take a screen shot and u can point out where ive screwed up
Its getting late now, 3am so Ill run through and try what you suggest tommorow.
Yes I just use 1 machine at the moment but may configure my other pc as a vst only box in the future - ill deal with that when the need arises.
And yes, for now I just use the one sequencer. When I talked about syncing midi from the sync plate I was really wondering whether the midi in cubase should (could?) be synced from the audio clock to keep them in time. Im guessing if I set the midi in cubase to sync to asio this will do that?
What does "clock on the wall" mean?
Ill have a go and if I dont get the expected results Ill take a screen shot and u can point out where ive screwed up
To be or not to be. What was the question?
Midi Timecode = Clock on the wall: song or movie position, ie. 2minutes 35secs 12234 samples. You FFW or REW, and song position is included and will follow.
Midi CLock = Metronome is not as accurate. The machine won't bother if it's a click behind.
You could leave Cubase, in Sync panel (double click sync on Transport Bar) to internal clock, it will follow Samplerate clock.
You make a point there, I've been discussing it this afternoon aswell, midi/audio sync. Recorded VSTi notes will play in perfect sync with recorded audio, Cubase will anticipate for latency of your card (no matter how high your ULLI is). If you enable 'Plugin Delay compensation, it will even undo the latency caused by VST compressors etc.
In my case, Cubase plays Rewire instruments (Reason) mostly, and they cannot be anticipated for: Reason doesn't know what your card's latency is. So I don't use much of VST fx, only on recorded audio.
Also, when you play keyboard->Pulsar->SeqDest-Cubase->VSTi, Cubase cannot anticipate, it doesn't preview when you are going to press the note.
ALL RECORDED EVENTS IN CUBASE LEAVE THE PROGRAM SIMULTANEOUSLY, with no latency offset. Only when you play live VSTi or Pulsar device THRU cubase, you get latency.
Also, all hardware I/O's and their processing (if not going to other software in your computer) are experiencing ZERO latency!
<font size=-1>[ This Message was edited by: at0mic on 2002-05-09 19:12 ]</font>
Midi CLock = Metronome is not as accurate. The machine won't bother if it's a click behind.
You could leave Cubase, in Sync panel (double click sync on Transport Bar) to internal clock, it will follow Samplerate clock.
You make a point there, I've been discussing it this afternoon aswell, midi/audio sync. Recorded VSTi notes will play in perfect sync with recorded audio, Cubase will anticipate for latency of your card (no matter how high your ULLI is). If you enable 'Plugin Delay compensation, it will even undo the latency caused by VST compressors etc.
In my case, Cubase plays Rewire instruments (Reason) mostly, and they cannot be anticipated for: Reason doesn't know what your card's latency is. So I don't use much of VST fx, only on recorded audio.
Also, when you play keyboard->Pulsar->SeqDest-Cubase->VSTi, Cubase cannot anticipate, it doesn't preview when you are going to press the note.
ALL RECORDED EVENTS IN CUBASE LEAVE THE PROGRAM SIMULTANEOUSLY, with no latency offset. Only when you play live VSTi or Pulsar device THRU cubase, you get latency.
Also, all hardware I/O's and their processing (if not going to other software in your computer) are experiencing ZERO latency!
<font size=-1>[ This Message was edited by: at0mic on 2002-05-09 19:12 ]</font>