Dealing with latency

[Andrew Henderson]

I am using my KSP in a hybrid setup, controlling external hardware synths, as well as soft synths, in Cubase 10.5.  I am unfortunately finding latency when dealing with the KSP sequencers, as they never stay 100% in time to the rest of my project.  Over time, they seem to drift and get a little worse and adding more to my project, only exaggerates this.  I would like it to stay a little more in time, to the grid.

I am using an RME Fireface 802 and like all RME devices, it runs on fantastic drivers, with VERY low latency.  I usually run at a buffer size of 128, but can go as low as 48, if need be.  The KSP is slaved to Cubase via midi clock. 

I have my hardware synths setup as external instruments in Cubase, so that they are delay compensated and these stay in time perfectly to my project, or close enough, that it can't even be noticed as a problem, if they aren't.  As of Cubase 10.5.20, midi clock is even delay compensated, greatly enhancing this functionality.  Unfortunately however, the KSP doesn't seem to be following along nicely to this.  I even created an external instrument for the KSP and routed midi clock through that from Cubase, but it doesn't really do much.  The KSP just seems to work differently, then all my other external gear, when it comes to staying tight in time.

I don't necessarily blame the KSP and am not overly surprised, but figured under even basic projects, that it would play a little tighter in time.  It makes it hard to get into things, when I can hear it is sloppy in timing.

Does anyone have any suggestions, or ideas, on how they may remedy this?  Anything would be better than nothing.  Is anyone else experiencing this, or is it just 'to be expected?'

[synthcreep]

Why not slave Cubase to the KSP's clock?

Also, any chance you are getting multiple clock streams messing things up?

[Terrym]

Hi Andrew,
I tested the sync with cubase 10.5 a lot and found that the KSP for me was really tight and always in sync..  I guess you are on windows from reading your thread, As i use Mac only so cannot say for sure what your issue is.
But it works fine for me plus i haven't sen many reports on sync issues only the usual tempo ones.

regards

[Andrew Henderson]

Thanks for the replies guys.  Yes, I am on PC.  I have thought of slaving Cubase, but I never found the DAW likes to slave well to other things.  Other weird things always seem to go on, when doing that.  No, I don't have multiple clock streams, as that is very obvious with things playing back at double time, etc.  My issues are not so severe, in fact, they are subtle, but noticeable enough that the final track will sound sloppy and unprofessional, if released that way.

So Terry, you tell me that you can have the KSP slaved to Cubase, have a fully loaded project, with lots of tracks, plugins etc and the KSP sequencers stay fully in time with the project?  No lag, or drifting?

Interesting that it is possible then!

[al80]

 maybe it is the usb connection.i have  synced  and slaved my ksp pro to cubase 9.5 for weeks now with no problems with midi din connection.maybe you have to take a look at the progect synchronization setup of cubase and the settings above the midi sync destination ports of this menu

[Andrew Henderson]

maybe it is the usb connection.i have  synced  and slaved my ksp pro to cubase 9.5 for weeks now with no problems with midi din connection.maybe you have to take a look at the progect synchronization setup of cubase and the settings above the midi sync destination ports of this menu

Thanks for your help on this, but yes, this is exactly where I have already set up midi clock to be sent to the Keystep Pro.  This is also where I enabled to do so, from creating an external instrument, to help it become delay compensated.

[bdrank]

KSP definitely goes out of sync over time when slaved to the Cirklon, have to stop/start to get things back in sync, not sure what's causing this. Sometimes goes out of sync quick, sometimes after 64 bars, dunno.

[Andrew Henderson]

KSP definitely goes out of sync over time when slaved to the Cirklon, have to stop/start to get things back in sync, not sure what's causing this. Sometimes goes out of sync quick, sometimes after 64 bars, dunno.

Thanks for confirming similar findings.  It really is disappointing and quite annoying when it happens.  For me, it certainly drifts over time on its own, but really gets worse much quicker, when I have plugins loaded onto the tracks that the sequencers are working with, in Cubase.  Having all hardware set up as external instruments in Cubase, is suppose to delay compensate such things and it always does... unless they are controlled by the KSP.  Midi clock is fully delay compensated as well now, as of the latest Cubase update, meaning it too doesn't drift or lose its place, even when plugins are loaded on tracks that are being fed midi clock.  It is only the KSP that is doing this, out of my entire setup.

[razzkazz]

I have a latency issue when using Ableton Live. It can be improved by adjusting the MIDI Clock Sync delay in the preferences. This messes up the first note when a sequence/arp is first played, but after that, the output from the KSP is in sync with the DAW.

[chompers]

 the keystep arpeggiator clock never resets once it get a tempo. you can hit a note, or a chord in time with a track and have the keystep play in time. you can get lucky, sure. But thats not the same as having an arpeggiator that recieves a sync tempo and then once you hit a note the machine plays the notes from that moment. Keystep doesnt work that way. Its a huge bug in the design. other sequencers and hardware arpeggiators allow you to set the clock to retrigger the sequence, with the correct tempo sync, once a not is played. Not the keystep.

[Neurophysix]

Any idea on how to set up the KSP with a volca beats? Im trying to use the drum channel with it and it  triggers most of the parts ( not all of them , idk why) but when i play a sequence it takes half a bar to start , while the synths on the other channels are starting on time. It is on sync but it starts at exactly half bar late. I have tried internal and auto on the arturia midi cc sync input at a rate of 2PPQ , output at 2PPQ also, wich i believe is what the korg volcas work with and thats what i get,  what could i be doing wrong? I havn't mapped the parts , it was automatically done and i cant play claves, agogo , or crash. I have tried different connections such as a midi thru box, straight from midi channel 1 or 2 from KSP).... Also have to mention that i own other volcas that are not having this problem with KSP , only volca beats.

Sorry if this is not the right thread to ask this.