Studio One's MIDI Clock is a joke

[Andywanders]

Has anyone ever tried slaving an external hardware sequencer to Studio One?

I have, and it sucks.

Play from start is fine - it sends clock start to the external device.

Stop also sends a start message - HAHAHAHA.

Return To Zero ALSO SENDS A START MESSAGE..!


HAHAHAHAHAHAHAHAHAHAHAHAHAHAAAA



But it gets better...

Start Studio One from anywhere other than zero - bar 5 for example - and your hardware starts from the beginning.


Just open Studio One's MIDI Monitor to see for yourself if you don't believe me.


And what are Presonus doing about it?

Well, it's been reported on their forums a few times, but it seems like they just don't give a shit.


Glad I've still got an old Cubase on this system.

[Acid Mitch]

But it gets better...

Start Studio One from anywhere other than zero - bar 5 for example - and your hardware starts from the beginning.

It sounds like it always sends a "start" message and not "continue" , which is
actually quite useful sometimes,depending what your trying to sync.
And it's also not sending song position pointer, which is kind of normal. Half the stuff(sequencers,drum machines,etc) I've used can send and receive it, the rest ignores it.

As for the other stuff, aye, that's not quite right.

You'llk be hard pushed to find PC programs that don't have at least one issue or another with MIDI clock.

[murnau]

now that change everything!

[lfm]

I don't think Midi clock is not to be used like this.

Use MTC(Midi Time Code) sync to sync external devices with daw.
Either way with daw as master or slave.

Have not tried with S1 in particular, but running other software in parallell as well as with external devices. Had a portastudio as master and computer daw as slave etc.

[Andywanders]

I don't think Midi clock is not to be used like this.

Yes it is.

Use MTC(Midi Time Code) sync to sync external devices with daw.
Either way with daw as master or slave.

Either way - MTC or MIDI Clock - it doesn't work. And Studio One won't slave.

This gets funnier.

Have not tried with S1 in particular, but running other software in parallell as well as with external devices. Had a portastudio as master and computer daw as slave etc.

Other software is no problem - Cubase, Logic, Live, Reaper, Sonar, Samplitude - They all do the right thing. If you haven't tried it with Studio One, I suggest you do (if you want to that is).

[lfm]

Other software is no problem - Cubase, Logic, Live, Reaper, Sonar, Samplitude - They all do the right thing. If you haven't tried it with Studio One, I suggest you do (if you want to that is).

Right now I don't need it - and I think it might be the one thing left out in S1 Producer version.

Did you put a support ticket on this to Presonus?

Then it might be fixed till I need it.

[TmTmClb]

2019, problem still the same. I wrote twice, explaining in full details the flaw in their MIDI clock implementation. it seems they just don't want to hear about it.
And you still can't set Studio One as slave.

Scr*w them, I'm not buying.

[lfm]

2019, problem still the same. I wrote twice, explaining in full details the flaw in their MIDI clock implementation. it seems they just don't want to hear about it.
And you still can't set Studio One as slave.

Scr*w them, I'm not buying.

I just tested - and it send midi continue starting transport.

But there is a setting in external devices - for each device - if to use midi start or not - did you by accident check that?

I get continue and stop, that is what I get. But running 4.1.4 and not sure about earlier v4.x if it might be fixed or not.

You even have an MTC option if you want that kind of sync.

But does not send song position pointer which is is necessary if to sync two sequencers, I think. If you move transport in StudioOne you are lost.

But for step sequencers might not be so important not covering a full song.

[TmTmClb]

Hi,

MTC is no go for me.

This is what I sent them:

When we pause Studio One, the SongPosition message is sent to MIDI output with a time value of -1000 (according to the Studio One MIDI Monitor), instead of containing the actual song timeline position as is standard. This makes external hardware (tested with Arturia DrumBrute and Roland TR-8S drum machines) go to the beginning of the next bar, and wait (MIDI clock has stopped, correctly). Then, when we press "Play" again, THE PROGRAM WAITS FOR THE NEXT BAR AND ONLY THEN SENDS either a ClockStart message (if "Send MIDI Clock Start" is checked in the Options) or ClockContinue message, and only then resumes sending MIDI clock. This means that synced external machines do NOT start playing back until the next bar is reached. If we set a loop that doesn't start and end exactly on bars, pressing Play/Pause and NumPad1 a few times or repositioning the playhead repeatedly within the loop region with the mouse (like when trying to pinpoint track/notes sync problems), the external machines stop reacting and just wait until the cows come home.