Arturia Forums
Hardware Sequencers => KeyStep Pro => KeyStep Pro - Technical Issues => Topic started by: Wildhomenetwork on April 28, 2020, 03:56:52 pm
-
What's wrong with this keyboard ?
There is so much bugs it's a stupid joke.
I can't even list all of it here !!! Maybe you should release your product when it's finished !!!
There is so much bugs than i just can't use it to work on it.
the sequencer is so buggy is so many ways, i can't record anything serious on it. I can't even imagine use it on stage... !! >:( >:( >:(
I made a list as as soon as I realise there is too many for remember :
The worst :
When you play for exemple some long bass note with just after some short note in staccato, in record mode, the staccato notes are not recorded, even theses are well play in real time (=> well deserved to the midi chanel)...
In the manual P82 : "Step-editing a pattern : Hold the Step button of an existing event and press the key. The velocity value will be remembered." => it could be cool, but it doesn't work.
Sometimes when you past some steps, and copy to another step, the new step is totally buggy : the main encoders leds arn't ON anymore on the new one (and you have no control on it), the new step led is not lighting, but there is some information on it (there is some trigger and gate information coming out of this step you absolutely can't erased, or control, or toggle off...). Truely a joke...
In every way, the past function is a joke : Anything you want to past is somewhat lost, sometimes, it's past, but not really, sometimes, it just say : there is nothing in the copy buffer, and you can redoing the thing a lot of time without any working it... and suddenly, it works. why is that ? you don't event know !
P98 : "SOLO takes priority over Mute" : would be cool if it do it, but it doesn't... When Muted track is soloed, is still muted...
Another bug (with an example) : on the first track sequencer, we play and rec on the fourth patern. Anytime we press Stop, it come back on the first pattern without our consent. it's a bug only shown in the first sequencer
another one : some of your recorded -- and editing because every live recorded with or without quantized is a joke, with a lot of note that doesn't record well -- pattern disappear or going messed up when you going to another pattern and come back. it's often just one chord who is just messed up without reason when it's well played just the last time you launch the pattern...
You can add up the lack of this features :
We can't erase just one page in a pattern (in drum mode in mono, if you copy by mistake, you have to toggle off until 16 steps in 32 tracks, and this is just a "toggle off", not an erase function...)
We can't erase just a note in a chord while in overdub.
We can't erase a step you can just "toggle it off"
There is a lot of things we can't erase or correct in a subtle way.
With the drum sequencer, we can't have (for exemple) a binary beat with some triplet hit-hat added. Goodbye all of the hip hop based drum pattern, good bye, possibilitie of add some triplet break at the end of your binari beat !
The swing is just foward, it can't be backward (why ? goodbye half of the swing of the world cultural music...!)
You can't charge some midi files, read live some external midi and rec it, there is not software sequencer where you can edit your pattern... This would be ok if the sequencers weren't a JOKE full of bugs and wierd things...
I just don't know how to temper my wrath >:( >:( >:(
The worse on that is that i still didn't even try to use it intensively or enter my musics on it ! All this bugs have just showed up on very simple test with the manual ! Ha, the manual is also a joke, full of nonsense and false informations or mispell words (ok, it's not the priority).
Oh, and i get the last update, so i can imagine that the first release was even worse... !
I hope arturia will work very hard to at least transforme this joke on the usable and multi track keyboard/sequencer they promised they sell... ! >:(
-
Unfortunately I have to agree with this post a bit. I have the similar experience that this product is a bit prematurely released. If we as users have found this many bugs in this short time it can not have gone through very rigid testing prior to release. I almost feel like a tester when I’m in front of the KSP now, don’t let the customers be beta testers. I wish the Keystep Pro team at Arturia to get into task force mode and start releasing fixes very soon.
That said, I am not a unsatisfied customer yet, I can feel the potential for the KSP under my finger tips! And I am having fun :)
Make me a happy customer, make it stable first and keep implement the features suggested by the community (at least the ones that fit :) )
-
the worst for me is that keystep "pro" is missing many features and functions from the original keystep.not happy so far with it
-
This unit is really frustrating.
I have started a thread explaining my issues between the KSP and Ableton but haven't had any replies yet (hopefully early doors lol).
Just read the post on this thread by johndoe and see some similarity to my problem. johndoe, you state that when playing back a recorded session from your DAW that it plays both the session and the original KSP session recording simultaneously. My problem is a little worst as I can't get the Daw to playback the midi instruments connected to the KSP at all but like your's it always starts playing back the sequences stored in the KSP. If I press stop on the KSP I hear nothing from the gear connected to the KSP but I can see the note led's of each track lighting up in the correct sequence, just nothing sent to the synths and drums over midi.
I assume that the data received on the KSP is coming thru the USB Midi route as I can disconnect the midi in/out cables from the KSP and still see the same sequencer led responses. I thought that the USB might be the problem (and it still may be), but I am able to load analogue Lab 4 and I can play the instruments on that via the KSP without issue. However, if I try to do the same with any of the Arturia VST's it doesn't work and can cause the Scarlett audio interface to freeze and corrupt the driver so that I have to reboot in order for it to function properly again.
Was wondering if you could tell me if you had to customize the KSP Utility settings in order to get the daw to playback midi tracks? I have tried various customizations but nothing seems to make any difference.
I wish I had confidence in the problem(s) being fixed by the next firmware update but with all the different issues being reported here and nobody reporting the same issue I'm having I'm not at all sure that it will help me.
I guess I'll have to shelve it and go back to the Keylab 49 and Beatstep Pro for the time being but that is so annoying as I have been waiting for this since it was first announced and I pre ordered it in January. I have limited space and was hoping that this would replace them both as one unit and the poly sequencers would be so nice to use.
-
Ok actually to fix my problem I have to mute the KSP track and it's fine then, no more notes conflict - it will play the Midi recorded clip from Ableton.
I still can' get my heard around default note length in Step Seq mode though (is there a way to make the gate length longer by default?), and in Live Seq rec the first note(s) sometimes are not recorded. Also, the Quantize isn't clean or I'm doing something wrong. Is there a latency to compensate btw?
-
This unit is really frustrating.
I have started a thread explaining my issues between the KSP and Ableton but haven't had any replies yet (hopefully early doors lol).
Just read the post on this thread by johndoe and see some similarity to my problem. johndoe, you state that when playing back a recorded session from your DAW that it plays both the session and the original KSP session recording simultaneously. My problem is a little worst as I can't get the Daw to playback the midi instruments connected to the KSP at all but like your's it always starts playing back the sequences stored in the KSP. If I press stop on the KSP I hear nothing from the gear connected to the KSP but I can see the note led's of each track lighting up in the correct sequence, just nothing sent to the synths and drums over midi.
I assume that the data received on the KSP is coming thru the USB Midi route as I can disconnect the midi in/out cables from the KSP and still see the same sequencer led responses. I thought that the USB might be the problem (and it still may be), but I am able to load analogue Lab 4 and I can play the instruments on that via the KSP without issue. However, if I try to do the same with any of the Arturia VST's it doesn't work and can cause the Scarlett audio interface to freeze and corrupt the driver so that I have to reboot in order for it to function properly again.
Was wondering if you could tell me if you had to customize the KSP Utility settings in order to get the daw to playback midi tracks? I have tried various customizations but nothing seems to make any difference.
I wish I had confidence in the problem(s) being fixed by the next firmware update but with all the different issues being reported here and nobody reporting the same issue I'm having I'm not at all sure that it will help me.
I guess I'll have to shelve it and go back to the Keylab 49 and Beatstep Pro for the time being but that is so annoying as I have been waiting for this since it was first announced and I pre ordered it in January. I have limited space and was hoping that this would replace them both as one unit and the poly sequencers would be so nice to use.
I didn't customize the KSP utility settings, and I'm only using USB. Make sure in Ableton Sync etc. it's all ON in preferences.
-
Okay, thanks Johndoe, I thought that might be the case. I've reloaded the firmware for probably the 3rd or 4th time now and performed a factory reset this time after loading as I read today that it would be necessary. No change though.
Yes I have looked at sync settings, they are all on. I've just about exhausted all options. Guess I'll just have to wait for a firmware update and hope. Until then I'm getting myself better aquainted with the sequencer.
I can see how muting would fix the issue with double playback but it's a workaround that shouldn't need doing like so many other things. I could work around my problem by playing back through the focusrite scarlett midi interface but that's not really an acceptable solution and I still have a few recording issues from the KSP like Ableton not seeing any data on channel 10 for the drums and it splitting the recording on one of the channels into 4 beat sections unless I switch monitoring in Ableton from auto to in. Also during any attempt to playback I get a Back to Arrangement error occur and Ableton starts locking tracks until I click the Back to Arrangement icon only for it to happen again a bar or two later.
Certainly need a lot of patience with Arturia gear. I had multiple issues when I first got the BSP but it ended up working fine.
-
Me too NickG same here I was excited as it's my first sort of advanced Midi controller, I waited since January not to buy any other since it was exactly what I needed, no more, no less.
The first week has been really frustrating considering the many bugs and also the fact I had to learn myself from scratch, since not coming from the Keystep (although I watched quite a few things before about it).
I'm getting more at ease with it now (even though I think it's not syncing well at times) and I believe Arturia tech team is going to do what's necessary to fix these issues rapidly and implement some of the missing features.
Let's keep us posted on that :)
-
Aaaaand another one which is really wtf... !
between pattern in the same project, the drums track doesn't change the time division even if the good time division is well saved.
For example : the 1st pattern is in 1/16 and the second in 1/32. When i change from p1 to p2, the time division in P2 is showing 1/32 but it runs in 1/16. i have to reactive the 1/32. when i get back to P1, time division is showing 1/16 but runs in 1/32...
a bug only in the drums track, whatever poly or mono mode.
I can't believe the arturia developpers tried to play the KSP even once... it's a shame....!
-
Hi again,
It seems all the issues are different but mostly related to the USB Midi interfacing.
Aaaaand another one which is really wtf... !
between pattern in the same project, the drums track doesn't change the time division even if the good time division is well saved.
For example : the 1st pattern is in 1/16 and the second in 1/32. When i change from p1 to p2, the time division in P2 is showing 1/32 but it runs in 1/16. i have to reactive the 1/32. when i get back to P1, time division is showing 1/16 but runs in 1/32...
a bug only in the drums track, whatever poly or mono mode.
I can't believe the arturia developpers tried to play the KSP even once... it's a shame....!
I understand your comment about the developers but I think in reality it does get tested by multiple dvelopers and some of the great moderators on this forum but maybe not on multiple platforms.
I wonder then if half the faults are due to how the KSP programming responds with different PC USB controllers / processor architectures and MB BIOS Programming platforms of which haven't been tested with the KSP. I would have thought that some correspondence goes on between hardware manufacturers and DAW software producers so I'm a little surprised that (in my case) Ableton hasn't got such a master piece of new hardware listed in the controller options. It has been known about in it's finished format for longer than the general release. I'm not sure who is responsible for that. Ableton or Arturia but I wouldn't have thought it would be that hard to do.
Anyway, let's hope they are taking note on all these issues and respond with some fixes sooner rather than later.
Having said all that, many of the problems I'm reading about here on the forum are internal programming issues so that partially blows my theory away.
NickG
-
Hi NickG, thanks you for your implication,
Sorry, but no. ::)
All my other controllers are doing fine with my interface, and I use a PC with Reaper, which is the less buggy DAW in the market.
Anyway, this is not some USB issues because, i don't use often the usb sync.
Any of those bugs are shown with ARTURIA Micro Freak, ROLAND TR-8S, and MOOG Sub Sequent 37, in MIDI, with no multiple sync and still when there is no sync at all.
I know my stuff, so please, don't make excuse for this keyboard to arguing that me or my gears are the problem.
Another bug I just find ?
After FOUR F****ng hours of implementing drums, the step edit mode have some issues, and all my drum tracks are buggy : the steps are lit, but doesn't send any data. I can't change the data in it => when in step edit mode or when i hold the step, all the knobs leds are off, and when i turn knob, nothing change. I can shut off the step, but when i reactivate it, it's still buggy. I've lost four hours of job. :'(
Thanks you Arturia, really !
I start to suspect a hardware flaw in my device, or else this keyboard is a fraud >:(
-
Hi Wildhomenetwork,
Hi again,
It seems all the issues are different but mostly related to the USB Midi interfacing.
Aaaaand another one which is really wtf... !
between pattern in the same project, the drums track doesn't change the time division even if the good time division is well saved.
For example : the 1st pattern is in 1/16 and the second in 1/32. When i change from p1 to p2, the time division in P2 is showing 1/32 but it runs in 1/16. i have to reactive the 1/32. when i get back to P1, time division is showing 1/16 but runs in 1/32...
a bug only in the drums track, whatever poly or mono mode.
I can't believe the arturia developpers tried to play the KSP even once... it's a shame....!
I understand your comment about the developers but I think in reality it does get tested by multiple dvelopers and some of the great moderators on this forum but maybe not on multiple platforms.
I wonder then if half the faults are due to how the KSP programming responds with different PC USB controllers / processor architectures and MB BIOS Programming platforms of which haven't been tested with the KSP. I would have thought that some correspondence goes on between hardware manufacturers and DAW software producers so I'm a little surprised that (in my case) Ableton hasn't got such a master piece of new hardware listed in the controller options. It has been known about in it's finished format for longer than the general release. I'm not sure who is responsible for that. Ableton or Arturia but I wouldn't have thought it would be that hard to do.
Anyway, let's hope they are taking note on all these issues and respond with some fixes sooner rather than later.
Having said all that, many of the problems I'm reading about here on the forum are internal programming issues so that partially blows my theory away.
NickG
Sorry if you thought I was judging your gear mate, you must have misunderstood what I was saying.
My point was that as many of the problems being experienced differ from one user to another the discrepancies may be due to a lack of pre-launch testing across the multiple platforms and interfaces that we use.
I've been using my pc, running Ableton, with BSP, KL 25 and KL49 as controllers and Focusrite Saffire 6, Scarlett 2i4 and 18i20 interfaces successfully. All my gear is Midi connected but the PC interface to the KSP is USB so no matter how much I connect with Midi there will always be an element of USB programming to get the KSP talking with the DAW.
My KSP will only allow me to record to Ableton (with bugs) and no audible playback from DAW to KSP at all and I know it's not my gear that's at fault so I wasn't blaming you at all.
NickG
-
Sorry for the rude answer,
i just discover bugs after bugs in this KSP, so i'm pissed off. so sorry, it's obviously not your fault...
For me, a lot of bugs are not even related to the sync (usb or midi) The sync works pretty good by the way : I meet some midi sync bugs like "ghost in the machine", but I was prepared for this kind of bug, because midi has always issues with SYNC, DAWs, USB, Clocks, specially when the sync is bilateral. The only problem about sync is my DAW can't send midi on the KSP, and i think this is not a bug, just another "DLC" in comming... this piece of gear is just not finished yet...
By the way, the most bugs i discover are linked to the sequencer itself.
I just found another one on the drums track : My seventh step on the kick track (C0) is stuck with a big velocity. I can set the velocity on this step at 0 but it always send between 90 and 120... And that do it on all patterns shows of my kick track ! Only on the seventh steps. (and step 23, 39 and 55) it force the groove i don't wanna on my track. And i can assure you that my KSP have bad taste, regarding groove ! ::)
-
Hi Wildhomenetwork,
No apology required mate, I fully understand and sympathise.
I think we nearly all have 339 reasons to feel a bit pissed off. It's a drain on the productive juices spending hours trying to figure out what does and doesn't work and why.
We all just want it to assist our workflow not add to it.
NickG
-
Hi guys since you have a bit more practice with it, could you perhaps help me out here:
1. is there a latency to compensate for the KSP in Ableton using USB only? While I'm using the KSP *Real Time Recording Mode*, I feel like the notes I'm live recording are not perfectly on grid (the first note anyway, as I check the clips in Ableton later on). what is the default Quantization setting of KSP Real Time mode, where can I monitor it at any given time and which setting do I need to manage to play synced on grid? I ordered a Midi soundcard Scarlett 18i20, I hope going full Midi will prevent possible DAW sync issues.
2. now in *Step Recording Mode*, how to set the default length of notes while recording? It seems to only enter very short notes, making it unplayable and bad/stuttering sounds with my source synth or vst (whereas in Real Time Recording it's fine, it will record the right sequence/notes length). Do I need to change the gate of each note afterwards, there's no global gate adjustment setting for the whole track before/after playing notes?
Thanks.
-
Hello guys.
Sorry to read that you encountered some issues that slipped through the test / beta test.
We are actively working on the KeyStep Pro, so any bug report is welcome.
Would it be possible to report them to the support team team? https://www.arturia.com/support/askforhelp/issues (https://www.arturia.com/support/askforhelp/issues)
This way these will be duly referenced which will help us troubleshoot and prioritise the bug fixes.
By the way, a new update is scheduled for mid may !
Best regards
Edouard
-
Hi guys.
Another bugs :
The first step when you run the sequencer doesn't send the gate datas... !
The copy function are buggy as ever : whenever i copy a pattern, it give my some "ghost steps"... (lit, but any data in it, can't change any data on it, i have to rec something on the track for remake the step usable : any "ghost steps" are still litt but like "null steps" with any record in it, but now i can change it.)
I found some flaws in some of my accusations :
The time division issue are well connected to some sync issues. it seems that i have to power off the KSP to have the pattern time division stop being buggy... (even when i desync, the bug is still here until i power off)
For the "triplet" steps on a binnary track, you can do it with use more than one track per inst. It's a pain to rec and edit, but it works. This is just REALLY not userfriendly...
Hello Edward, i making my answer for the support, but they told me to make some video, and when i want to demonstrate a bug, another one occur ::) so it was hard to find the time to show propely one bug at the time. ::)
Hello Johndoe,
here is my thought :
I saw that there is a lot of jitter with the usb cable : my clock in sync are running back and forth like hell (for example i set 64PM on my daw, and the KSP show jitter of 32.5 to 65.5, it's huuuge... i will try to sync my soundboard clock with the KSP when i'll have the good adaptater... can you send your experience when you recieve your midi soundcard ?
For your 2nd point, you have to set the gate encoder before playing your notes, when there is no selected step. There is no global change after, or change of multiple selected step (and this is uncool)
-
Hello Johndoe,
here is my thought :
I saw that there is a lot of jitter with the usb cable : my clock in sync are running back and forth like hell (for example i set 64PM on my daw, and the KSP show jitter of 32.5 to 65.5, it's huuuge... i will try to sync my soundboard clock with the KSP when i'll have the good adaptater... can you send your experience when you recieve your midi soundcard ?
For your 2nd point, you have to set the gate encoder before playing your notes, when there is no selected step. There is no global change after, or change of multiple selected step (and this is uncool)
Thanks, very interesting. Which adapter you need for your setup, you mean USB to Midi adapter? Yes I'll debrief you after receiving my Midi audio interface.
Re second point, this is very uncool indeed if Step Recording Mode doesn't allow global step gate change setting, or change of multiple selected steps - I'm going to bring this specific point to the support team.
-
* My sound card not
soundboard.
I have a Clock out in BNC in my soundcard, so i have to find a way to link the BNC output of my Audient ID44 to the 1/4TRS jack input of my KSP to sync it all the stuff with my Audient. (because my daw is sync by USB with my AUDIENT, and the KSP sync with the DAW by Another USB, so i thinks it is the cause. Maybe your solution with a MIDI Sync will do the same job ! (and maybe better, i don't even know if i can send BNC ouptu Clock to 1/4TRS Jack Input without a process between the two...!)
So, I talked with the support, aaaaaand finally, I found that even if in utility => misc => firmware version it showed i had the latest version, it was not. Damn ! >:(
When i hard reset the KSP, it still show the last version (1.1.7. 473), but not the real one (aka the first one firmware send with the KSP 1.1.3 when you hard reset)
SO :D
A lot of bug are already fixed, and it's really conforting me, because I was wondering why all this is happening to me.
The main bugs with the record mode are left. There is still a lot, but it was really the worst angering me the most which have disappered with the last firmware upgrade.
I'M SO RELIEVED ! :o
Hope the others bugs will be fixed and other features will be release soon !
-
Hello.
Just stepping on the last message you sent:
I have a Clock out in BNC in my soundcard, so i have to find a way to link the BNC output of my Audient ID44 to the 1/4TRS jack input of my KSP to sync it all the stuff with my Audient. (because my daw is sync by USB with my AUDIENT, and the KSP sync with the DAW by Another USB, so i thinks it is the cause. Maybe your solution with a MIDI Sync will do the same job ! (and maybe better, i don't even know if i can send BNC ouptu Clock to 1/4TRS Jack Input without a process between the two...!)
Sorry WildHomeNetwork, but an audio interface BNC port is made to carry world clock to sync your audio interfaces together, but it is not made to carry MIDI clocks :)
I saw that there is a lot of jitter with the usb cable : my clock in sync are running back and forth like hell (for example i set 64PM on my daw, and the KSP show jitter of 32.5 to 65.5, it's huuuge... i will try to sync my soundboard clock with the KSP when i'll have the good adaptater... can you send your experience when you recieve your midi soundcard ?
Here the jitter induced in USB can be related to your computer (Windows computers are more subject to jitter) and to the programs running in background.
If you are using Live, this great article can help you understand the in and the outs of MIDI sync: https://www.ableton.com/en/manual/midi-fact-sheet/ (https://www.ableton.com/en/manual/midi-fact-sheet/)
With the drum sequencer, we can't have (for exemple) a binary beat with some triplet hit-hat added. Goodbye all of the hip hop based drum pattern, good bye, possibilitie of add some triplet break at the end of your binari beat !
You can shift any note to your convenience, plus you can record unquantized so this should be achievable :)
-
Hello guys.
Sorry to read that you encountered some issues that slipped through the test / beta test.
We are actively working on the KeyStep Pro, so any bug report is welcome.
Would it be possible to report them to the support team team? https://www.arturia.com/support/askforhelp/issues (https://www.arturia.com/support/askforhelp/issues)
This way these will be duly referenced which will help us troubleshoot and prioritise the bug fixes.
By the way, a new update is scheduled for mid may !
Best regards
Edouard
Mid-May huh? Saw this coming, won't be an update before weeks...
-
Hello.
We had a release candidate but some regressions have been spotted and requires some additional work.
We want to bring the update asap, but we want to make it right and without any regressions !
-
Hello.
We had a release candidate but some regressions have been spotted and requires some additional work.
We want to bring the update asap, but we want to make it right and without any regressions !
Thanks Edouard, I appreciate your answers here to keep us to date.
That said (and it's not your fault) I'm amazed that a product of this value, with such a brand, engineer team and past product development history behind, still cannot get properly stable and glitch-free at this stage. The KSP was presented almost 6 months ago and it seems like it won't get a first fix update before June, and probably not the other improvements before 2021. I have never seen something like this in my life as a customer, and everyone at Arturia seems to consider this timeframe and release procedure as standard, instead of pre-sale beta testing and feedback. I will certainly re consider purchasing Arturia hardware products in the future.
Nice day.
-
Yep, full of bugs, am beginning to consider going back into the box so I can actually make some music instead os sitting in studio scratching head!
-
With the latest firmware, I still have many bugs, on top of occasional hangs:
- MIDI OUT velocity output was totally messed up one time. Confirmed by USB MIDI message monitor and Monitoring MIDI OUT signal. It was sending illegal MIDI messages. The issue fixed by setting velocity curve setting.
- Messing up of MIDI CC# assignment. Sometimes suddenly MIDI CC# controller assignment is reset by project loading. Controller assignment is global setting so it should not be affected. When it happens, MIDI CC number and adjustable range becomes weird (Min is around 50 and Max is around 60). I need to reconfigure it (or reload setting from PC).
-
Is another firmware in the cards for this product? Like the other posters in this thread, I also find mine to be full of bugs —an amazing product based on the promised feature set, but in practice, really frustrating. It sends occasional phantom clock and reset pulses when it’s stopped; the clock doesn’t start cleanly every time; sometimes it drops a step while looping sequences i’ve recorded and they get out of sync… all sorts of things that are inconsistent and unpredictable and make it very hard to rely on the KSP for live performance. It’s very disappointing because there’s nothing else out there that does what the KSP claims to, but it really feels like this still in beta.
-
Is another firmware in the cards for this product? Like the other posters in this thread, I also find mine to be full of bugs —an amazing product based on the promised feature set, but in practice, really frustrating. It sends occasional phantom clock and reset pulses when it’s stopped; the clock doesn’t start cleanly every time; sometimes it drops a step while looping sequences i’ve recorded and they get out of sync… all sorts of things that are inconsistent and unpredictable and make it very hard to rely on the KSP for live performance. It’s very disappointing because there’s nothing else out there that does what the KSP claims to, but it really feels like this still in beta.
I would like to know this as well. Last update was 1 year ago in June 2021. Is a final firmware update in the cards Arturia?
+1 to the max, unbelievable there hasn't been a peep.
-
In my latest session alone, my KSP:
1) ignored my efforts to turn on the Ch 2 arpeggiator entirely, until I powered cycled the KSP
2) [once I power cycled it] played the arpeggiator 2x as fast (and with triplets on) as it did the last time I had it on (same project, same settings, just played back differently)
3) inserted notes I never played into the arpeggio—some of which weren't displayed in the arpeggio indicator LEDs and some of which were.
This is in addition to all the bugs I mentioned in my previous post with regard to the clock and the sync.
I can't even imagine how frustrating this kind of unpredictability is to KSP users who 1) are professional musicians rather than hobbyists like me, and 2) have spent more time learning the deeper features on the KSP than I have, expecting it to be a central part of their live rig. Even for me, I started today's session planning to perform and record a live set, and I ended it right here, posting this message. Not exactly the creative path I was hoping to travel!
I hope some folks from Arturia are reading this thread and can provide some follow-up. IMO, it's totally understandable for a tool as complex and multifunctional as the KSP to have bugs... but this long after release—and especially almost a year after the most recent firmware update—I'd expect to be seeing edge-case bugs, not deal-breaking, show-stopping (sometimes literally) bugs. It's hard not to feel taken advantage of, as a customer, to have purchased in good faith a piece of equipment that was billed as something I could use as the brains for my entire rig and have it fail in so many fundamental ways.
I'd really appreciate if someone from Arturia could provide some feedback about the current and anticipated state of support for the KSP so I can make an educated decision about whether I can justify continuing to pour my limited time and energy into this instrument. Thanks.
-
I reported similar issues with arpeggiator on August 2021...opened 2 tickets with support, both with the same reply "we are working on it". Sure doesn't feel they are working on it, it's been 10 months! There hasn't been an oficial response on the forum for a long time. However, they keep launching new products, so you can see where the development efforts are going.
-
To update: I emailed Arturia and received a response that they are in fact working on a firmware update, but they couldn't share with me the expected timeline or the expected contents.
I find it encouraging that the product supposedly isn't yet abandonware, but disappointing that they won't share any more details, especially with customers who already made a purchase and are frustrated that the product doesn't live up to what was promised. I asked them to share that frustration uphill with management (who knows if they will or if management cares) but if you feel like emailing and expressing similar sentiments, maybe it'll have an effect.
Anyway, fingers crossed there's another update someday that actually does smooth things out.
-
Which products are you looking for?
-
To update: I emailed Arturia and received a response that they are in fact working on a firmware update, but they couldn't share with me the expected timeline or the expected contents.
I find it encouraging that the product supposedly isn't yet abandonware, but disappointing that they won't share any more details, especially with customers who already made a purchase and are frustrated that the product doesn't live up to what was promised. I asked them to share that frustration uphill with management (who knows if they will or if management cares) but if you feel like emailing and expressing similar sentiments, maybe it'll have an effect.
Anyway, fingers crossed there's another update someday that actually does smooth things out.
I was like you but I've come to the conclusion, especially after the design/hardware limitations described by the Arturia staff on the forum, that any future firmware update, as good as it could be (and that's still a if), won't make this product as complete as I expected in the first place. I'm better off paying more bucks in the range of 600+ and other brands offer better deals for the ones of us simply wanting to use a sequencer 'on the fly' with a DAW, vsts and a couple synths, nothing too fancy, BUT it should work, fast, no time to be wasted on interface setup, and no bugs of any sort.
Good luck to all.
Willing to share what you're moving to instead? I could be convinced to pay more money than the cost of a KSP for something that actually works, but for a lot of what KSP does, I'm not sure what else in the market does it. I primarily use the KSP to record and loop multiple rhythmic/melodic MIDI/CV sequences at a time, to trigger my modular synthesizer. I can't really seem to find anything else that has multiple channels of live sequencing and looping in the same way—especially in as small a package—but maybe I'm missing something...
-
The most similar device would be the Endorphins ground control...it's more expensive though and for eurorack. I think it has midi but not sure.
To update: I emailed Arturia and received a response that they are in fact working on a firmware update, but they couldn't share with me the expected timeline or the expected contents.
I find it encouraging that the product supposedly isn't yet abandonware, but disappointing that they won't share any more details, especially with customers who already made a purchase and are frustrated that the product doesn't live up to what was promised. I asked them to share that frustration uphill with management (who knows if they will or if management cares) but if you feel like emailing and expressing similar sentiments, maybe it'll have an effect.
Anyway, fingers crossed there's another update someday that actually does smooth things out.
I was like you but I've come to the conclusion, especially after the design/hardware limitations described by the Arturia staff on the forum, that any future firmware update, as good as it could be (and that's still a if), won't make this product as complete as I expected in the first place. I'm better off paying more bucks in the range of 600+ and other brands offer better deals for the ones of us simply wanting to use a sequencer 'on the fly' with a DAW, vsts and a couple synths, nothing too fancy, BUT it should work, fast, no time to be wasted on interface setup, and no bugs of any sort.
Good luck to all.
Willing to share what you're moving to instead? I could be convinced to pay more money than the cost of a KSP for something that actually works, but for a lot of what KSP does, I'm not sure what else in the market does it. I primarily use the KSP to record and loop multiple rhythmic/melodic MIDI/CV sequences at a time, to trigger my modular synthesizer. I can't really seem to find anything else that has multiple channels of live sequencing and looping in the same way—especially in as small a package—but maybe I'm missing something...
-
That guy obviously doesn't know what song mode is.