Studio One - Send MIDI clock via USB

Audio Plugin Hosts and other audio software applications discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

So, i happen to have the Novation Impulse 49 keyboard, which comes with an onboard arpeggiator, with the ability to receive MIDI clock from an internal source, or via USB or MIDI. Today, i tested a bit, and found out that, by default, the arp clock sync option is set to "Auto", which either should receive a MIDI clock signal from the internal source (when there's no MIDI clock received via USB, or MIDI), or, from USB, or MIDI, if there's a MIDI clock signal received.

I figured out, that, to receive MIDI clock signal from the DAW, in Cubase, i have to go into the Transport menu, choose "Project sync options", or however it is called in English, and there, have to set up the Impulse's MIDI port, as the MIDI clock target, and, after 10 minutes of banging my head why it doesn't work :D, i also found out that the "Send MIDI clock command in Stop-Modus" option has to be activated, for the sync to work, even when the DAW's transport is stopped...

Ok, so, i thought i'd also try in Studio One. Thing is, though, when you set up your MIDI device, in my case, i set it up as a generic "New keyboard", because it isn't supported by Studio One out of the box, and the New keyboard devices don't offer the ability to receive, or send MIDI clock signals. So, my question is, is it possible, and issue free, when i add a "New instrument", transmitting, and receiving on the same MIDI port, to get MIDI clock signals working on my Impulse? It's really bad that you can't just add a "universal" device in Studio One, which can be keyboard, MIDI control device, with sliders, knobs, and what not, and at the same time a device which can transmit, and receive data, like MIDI clock signals.

Post

Shouldn't be any issue with setting up a separate instrument to your Impulse in order to send it clock, I've done similar with my TR8 - separate "keyboard" (for using the pads) and "instrument" (for sending it all back again :D)

Post

Thanks. I actually just tried it yesterday, and, apart from that the new instrument device was set up with some pre-mapped controls (no idea why that is...), and some odd-ness with the control link mapping (it somehow first mapped my keyboard's controls to the new instrument controls?), I haven't faced an issue. Still a shame that Studio One doesn't allow a general MIDI device, and you have to set up multiple devices for the same device. They really should work that out. Anyway, works.

Post

Totally agree. That separation of keyboard and instrument threw me for a while when I first started using hardware synths with Studio One. Not a big deal in the great scheme of things though.

Post

Some oddities working with external gear in S1 made me ditch it.
This was S1 2.6.x so don't know if they changed anything.

Some oddities in Hammond midi implementation made me want to just record midi, not echo through with monitoring.
But unless monitoring was active - S1 only recorded notes, no controllers.
And you had to set it up toward a port and what to let through and all that.

Workaround was to insert a VST instrument and turn volume down to zero.

With VST instrument you never notice, since you always monitor.


If you arm for midi record - why not just record what comes in?
Presonus overcomplicated some things about midi, in my view.

Post

@lfm, that was fixed. You can now record controller data without monitoring enabled and/or without anything attached to the output of the Instrument track.

Post

daw.one wrote:@lfm, that was fixed. You can now record controller data without monitoring enabled and/or without anything attached to the output of the Instrument track.
How lovely, thank you, good to know. :)

Post

You may find this video useful:


Post

In S1 an external midi device with a keyboard requires 2 external devices set up.

1 for the keyboard.. set input to whatever midi interface connection that is using.

2 a instrument device for the actual external midi instrument sound engine. setting it to output to the same midi interface connection.
only the S1 external instrument devices have options for send midi clock etc.

then in the arrangement area drag over the external instrument you created in step 2..and tweak the midi input trigger and channels on the new arrangement item.. not that local off should be engaged on the actual external midi device so midi loop back triggers aren't experienced.. not cool.

then you can play midi notes to the external midi device.. synth or whatever it is..

Thing is.. audio.. πŸ˜‚

make sure you external midi device has an audio connection to the audio interface that S1 is using.. and in the mixer create a audio channel.. setting that to the input of the extend midi device.. and that's it.. midi and audio..

S1 v5 has aux channels now that can streamline this audio to external device system.. and saved as a default.. so assuming you don't go changing the midi cables and audio cable around like a lunatic you can effectively have a pre configured external device within S1.. ready to drag over from the browser when needed and the midi and audio channels will propagate.

trick here is to set up a S1 template for all you external gear and sick with it..

Currently I'm running 26 channels of audio from all external gear into S1 directly.. no mixer.. using S1 in real time.. and while it's complicated.. it works..

My tip is this.. use a midi merger.. and only send midi clock out once.. and let the merger redistribute the clock.. rather than sending clock to each external device in parallel from S1.. let the merger do the work there..

My setup is a presonus quantum 2632
And two 8 input Adat preamps..and a tube preamp over spdif.. giving a whopping 26 audio inputs..
for midi I have a motu MTP av usb midi merger.. and several devices are connected via usb for midi and the elektron A4 using overbridge with audio and midi vis usb..

It works.. πŸ˜‚

Post Reply

Return to β€œHosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”