Arturia Forums
Hardware Sequencers => KeyStep Pro => KeyStep Pro - Technical Issues => Topic started by: RGRAINGER on August 06, 2020, 11:51:26 pm
-
I got a Keystep Pro today, and I was delighted at first. It seems to be what I've been waiting for.
I was running sequences that were playing on my Pro-1, Minibrue 2 and Minitaur. It worked great.
But as soon as I introduced drums, I ran into problems. I am not using the Keystep's drum track here, I am trying to sync an external drum machine to it. I couldn't get it to send clock at a sensible rate to my Volca Sample (I tried all the clock division settings), so I updated the Keystep Pro's firmware to the latest version. I still couldn't get it working.
So I tried MIDI DIN. It didn't start the Volca's sequencer reliably.
So I decided to try with my Drumbrute Impact. Same issue as with the Volca over MIDI DIN. It starts when I hit start on the Keystep Pro. But it starts a beat behind, or sometimes very slightly behind. There seems to be no logic to it - it doesn't start in sync, but the amount it's out of sync varies each time I start the Keystep sequence.
So I tried the second MIDI output of the Keystep Pro, so there's a direct MIDI DIN cable between the KP and the Drumbrute. Same issue.
If I start the Drumbrute or Volca manually, they stay in sync with the Keystep. But I don't want to do that. The whole point of this set up is to have everything start in sync when I hit play. 100% of the time they fail to start on the beat when I press play.
So I tried with the Minibrute 2 sequencer. Same issue. It doesn't trigger the start of the sequence on the beat.
So the Keystep Pro with the latest firmware seems incapable of starting external sequencers on the beat. This is more than a bit rubbish.
I've also experienced other glitchiness when I'm sequencing. Steps suddenly looping for no apparent reason, the metronome going wild are just two examples. I couldn't rely on this to improvise a piece of music or play live.
And I can't sync any external drum machines or sequencers, which is the whole reason I bought the damned thing.
This is more than a bit rubbish, to put it very politely. None of the gushing reviews from Youtubers mention that it doesn't actually work.
-
OK, I've found a combination of features that works. Clock out works to synchronise the DrumBrute Impact. I haven't yet tried it with other external devices, e.g. the sequencer on the Minibrute 2, but this looks like a promising workaround for my uses.
So in summary, clock out doesn't work with the Volca but it does work with at least some (and possibly all) other devices.
MIDI DIN sync out just doesn't work. A pretty basic function of a MIDI sequencer. This should have been tested before Arturia rolled out the firmware. It's hardly an obscure use case.
-
Can confirm this. I got the beatstep pro and the keystep pro synced via midi. No DAW in between.
I got drum sequences on both machines. They won't start together. I have to hit several times the play and stop button to get proper sync.
This is really bad. Workflow killer. And as a note, this shouldn't be the case. Stable Midi Clock is "Key" for music production. Focus should lies there as performance is always key.
-
Weirdly, the Volca suddenly started syncing for me via MIDI this morning. ??? I haven't changed the firmware or done anything else that should affect it.
-
It looks like my main issue - DIN Sync - might be to do with the clock out setting. I'll experiment over the weekend and report back with what I find.
-
It looks like my main issue - DIN Sync - this might be to do with getting the clock out setting right. If that's the cast, I take back what I said. I'll experiment over the weekend and report back with what I find.
Hmm... if you are slaving the KSP to midi clock from the USB, I believe it is currently not working correctly, where midi clock is now not being sent properly to the DIN out. Is this what you are experiencing?
If I am not mistaken, this should be fixed in the next update.
Apologies if I am wrong on this, or am misinterpreting your problem.
-
Thanks. No, I am using the internal clock on the Keystep Pro. It's not connected to a computer or other device by USB.
Keystep Pro > MIDI DIN lead > MIDI THRU box > Synths and drum machines.
That's my setup. I have also tried going out from the KSP directly to the drum machine, in case the THRU box was the iusse (although the box works with the Beatstep Pro and regular Keystep).
I have found what is causing the issue, and as a result, have a workaround for anyone else experiencing the issue, like Jan Juno.
The clock out setting on the KSP affects MIDI sync. I can reproduce this behaviour. By changing the clock output value in the KSP's menu, I can break and fix the MIDI sync. For me, a setting of 24PPQ allows MIDI sync to work.
Should this setting even affect MIDI sync? The manual suggests it only affects analog sync. Indeed, if the setting affects both, it means you can only use a mixture of analog sync and MIDI sync for some devices (it will depend on the clock rate of the device you want to control with analog sync).
Having found this, I am relieved that this isn't a hardware issue. It seems to be firmware-related and can presumably be patched.
-
I apologize for not re-reading your original post, before making my comments above. I did read your initial post a couple days prior and thought I understood it, so made the post I did above, even though it was wrong.
As for your findings, that doesn't sound right at all. Analog clock and midi clock should 100% be separated. The fact that one is affecting the other, sounds like a bug to me. I would definitely get in touch with support and share your findings, along with reproduction steps, so it can be looked at in house. If it is a bug, it should be fixed, as this would definitely affect a lot of users, in its current standing. The KSP's strength is in its diverse connection points and being able to only use certain instruments, depending on what your clock setting is, sounds very restrictive.
-
I will do. I assumed that issues flagged up here would percolate through to Arturia support, but I'll raise a ticket.
-
I will do. I assumed that issues flagged up here would percolate through to Arturia support, but I'll raise a ticket.
No, always better to raise it direct. Thank you from all of us users, for doing this.
-
Arturia support have confirmed that they can reproduce the problem, and they're going to patch the bug.
-
8)
-
If I am slaving keystep pro to DAW (Ableton live 10) - keystep pro will start with daw but does not start my analog rytm mkii (KSP midi out 1 into RYTMII in). If i hit play on the KSP it works fine.
-
Hello.
This is fixed in the current beta :)
Best
Edouard
-
That's good news. Thanks Edouard.
-
I'm having horrible timing issues with beat step pro sending out midi beat clock. All my other gear syncs when anything else sends midi beat clock. But when using KeyStep pro to send beat clock everything else is off.
-
Yea this bug definitely needs to be fixed. I have my KSP connected to my BSP via midi and the timing is atrocious. Literally takes 2 secs to start my BSP. Like seriously, how did this get past QC? or was it just something they intended on fixing later? Either way, it is extremely poor development and its a shame because this has sequencer has a lot of potential. I hope this is fixed immediately.
-
Works now way better. But BSP first note won‘t be played. Please update beatstep pro.
-
I updated my KSP to firmware 1.3.2 and I still have the problem where an eternal drum machine slaved to the KSP via midi din cable doesn't start in sync when pressing play on the KSP.
Depending on the Sync Output setting, the delay between the start of the KSP and the start of the slaved drum machine can be more or less long.
At 24 and 48 PPQ the slaved drum machine start almost in sync, but sometimes the first beat is skipped.
At any slower rate, the slaved drum machine starts more or less late in a very noticeable manner.
Lower the rate to the lowest setting of 1 PP4Q and you can wait for several seconds for the slaved drum machine to start after pressing start on the KSP.
My main problem is that I use the clock output to connect to a modular synth and clock LFOs etc... and so 24 or 48PPQ is just too fast to be usable on the modular.
So either my drum machine is out of sync, either my modular is going too fast...
Pretty unusable for a master sequencer that is supposed to make the bridge between modular, hardware and software...
Can Arturia confirm that this is a known bug and is gonna be fixed?
Because based on what @Edouard_Arturia said, I was expecting this fix to be released with version 1.3.1/2 since it was in beta a couple weeks before the new firmware was available.
Or I'm just mistaken on what the fix was supposed to be and it indeed got released.
Anyway this is very frustrating as I finally acquired a drum machine to go along with my setup and it's just not working...
-
I've got the same behavior.
The KSP is the master, going from midi out to a thru box, which is sending the clock to 4 other devices (Octatrack, Microfreak, Hydrasynth, Ipad).
I'm trying to use Arps and lfos, but it is never accurate. Strangely, a setting of 24 PPQ seems to afford a barely stable sync, but I have to hit play several times to get lucky for a good sync.
-
I have a ticket opened with Arturia technical support, they asked me to do a factory reset but the problem persists.
I'll update here once I have more.
-
OK so Arturia confirmed that this problem I described was not resolved.
They were able to reproduce it with an Elektron Analog Rytm mkII, I have an Elektron Model:Samples.
They said that the developers are working on a firmware update that contains fixes for this problem as well as other ones.
It gonna be at least a couple weeks and maybe more for them to be able to go through the whole fix/qa/validation for the list of bugs they have lined up.
I'll report here when I am able to confirm that this is solved.
At least they were very reactive when contacted via the technical support form on Arturia's website.
-
I am having sync issues as well. My clock runs from a Moog DFAM to my clock in on the KSP which then sends MIDI clock to my rig. My Mother 32, FH-2, Korg Electribe ESX-1 all run reliably in sync however my 1010 Music Bixbox Mk1 does not. It chokes, warbles, starts on offbeats, its a mess. I spent the weekend thinking it my Bitbox but when I run clock from my DAW directly to Bitbox it works as it should, as well when I run clock from my Electribe to Bitbox it also runs just fine. The analog clock from KSP to Bitbox also does not sync.
-
...still waiting for an update (even a verbal one from Arturia would suffice at this point). I can't for the life of me believe that no body was able to pickup on this issue during development, it should have been one of the first things tested! This issue has made me have to use one of my drum gates as a clock for my Eurorack while using midi clock for my BSP. It essentially eliminates one of the sequencers leaving me with only 3...
-
Hello.
The update is supposed to be released today, it greatly improves the sync.
Kind regards, and stay safe.
Edouard
-
Hello.
The update is supposed to be released today, it greatly improves the sync.
Kind regards, and stay safe.
Edouard
Hi Edouard,
Could you please post patch notes? There exists no documentation about fixes, changes and added features since 1.3.1 anywhere at all.
-
Hello.
The release notes are available from the resources page, in the firmware row, by hovering the info button.
But it's true that it pretty hard to spot that if you don't know that :)
I also created a thread here: https://forum.arturia.com/index.php?topic=104690.0 (https://forum.arturia.com/index.php?topic=104690.0)
Best
Edouard