Oh goody! An actually useful update to the KSP. Thanks for diving into the new features. Think I'll stick with my OG KSP for the time being, but golly-gosh that Chroma edition looks sick.
Cool update! One thing I noticed when I updated, was the velocity, even though it was set to normal, was fixed…Simply turning it to fixed, then back to normal rectifies this. I hope in a future update Arturia gives us a way of having more than 5 controllers and implement something more akin to the encoders on the KS37, which has 16 over 4 banks of 4.
Thank you!!! Very clear and helpful overview of the upgrade. As soon as I have the KS Pro I will definitely go back and do it all again ;) PS Do you have an equally clear overview of the changes in update 2.0?
@@OscillatorSink , thank you for your feedback! Let's hope that Arturia will surprise us all soon and release update 3.0 (adding, for example, Strum and many other useful features).
Is it possible to connect two Keystep Pro units together, giving you an 8-Track sequencer that can control 8 different devices all playing in sync with each other?
And yet sadly, with these devices using RGB LEDs, those of us who are a bit colour deficient are spannered as the colours are really indistinct.. Cant tell the differenve *at all* in this video, so I'm hoping they're rather better IRL...
Under the bright lights I had shining at it, the colours aren't as clear, but in normal room lighting they're much better. I will add: I only showed three different colours in the video - and two of them were shades of blue. You do also still get the feedback of the particular track being lit while editing.
PC is pretty significant, does it glitch when doing a PC if you have the 1st step enabled of a sequence? What about bank changes, are you able to do this given synths with 512 patches normally have 4 banks with 128 patches. I am all for recycling hardware in live sets. You could have the PC set in a way where you don't even use the sequencer for notes, so left all blank, use another sequencer (I have a P PLAY), but use the KSP as a favs Patches for sets that don't have notes tied. That's 16 recalls of patches which is pretty cool imo, and you can do this for 4 synths, so I am going to try this later tonight. Thx for the update.
In the demonstration I have notes on the first step of both patterns and on the microfreak there's no glitch, so it appears to be sending the PC message a little ahead of time - but not every synth changes programs instantly so it might vary from instrument to instrument. It supports LSB/MSB program changing which is how most instruments give you access to larger number of patches, but again - it'll vary from one instrument to another, so get reading those MIDI implementation charts!
@@OscillatorSink yeah I am familiar with MIDI charts, have been using them for ages, even did a test on Pro Tools for PC with some gear, that's where the issue lied, it would glitch. Nice knowing there are no issues here.
PC doesn't seem to work unfortunately. Trying it with the KSP and the Microfreak, no luck, let alone with other devices. Updated the Firmware multiple times, watched all the Videos, read all the Posts etc. No can do ;D
I find that of you flick msb and lsb up and then back down to 1, then go to the assign it will then work. Seems to work fine first time on patterns that have never had any pc data on them . This trick works every time for me on microfreak and other synths.
Can this Keystep Pro also automate the midi channel it's transmitting on the way like it sends programme changes (from one pattern to another or from one scene to another). I mean if we have more than 4 hardware synths, let's say 6, can we automate which one of (gets midi and plays) from one pattern or scene to another? Or do we have to change the midi channel manually?
Midi channel is assigned to a track on a per project basis. So you have to switch projects, you can't do it per pattern (currently, in the firmware available at the time of writing).
A truly terrible update unfortunately. Program changes is great and all, but both units I've updated to 2.5 now do not save any mute data across any of my projects. Doesn't matter how many times I save or how I save it, all mute data is erased once the unit is powered down. Makes it all but useless to me now. Arturia wrote back saying they know about the problem but are essentially in no hurry to fix it. Great work Arturia. You almost make the best gear. Then you don't.
The old variable velocity setting drove me crazy - this is really great!
i used a work around this issue, via push shit / velocity knob to any edge low or high first and then fix to value that is wanted
Oh goody! An actually useful update to the KSP. Thanks for diving into the new features. Think I'll stick with my OG KSP for the time being, but golly-gosh that Chroma edition looks sick.
very helpful tips -- and wow this CHROMA version is nice! thank you 👍
Great video as always, thank you!!!
Thanks for watching!
Cool update! One thing I noticed when I updated, was the velocity, even though it was set to normal, was fixed…Simply turning it to fixed, then back to normal rectifies this. I hope in a future update Arturia gives us a way of having more than 5 controllers and implement something more akin to the encoders on the KS37, which has 16 over 4 banks of 4.
Thank you !
Hopefully they do a 7+1 version of it at some point. Using 2 is pretty clunky.
CAN YOU CHANGE ALL TRACKS AT THE SAME TIME ? ? ? ( like prst lnk in the bsp )
Anyone else facing some bugs with the drum mute feature?
Thank you!!! Very clear and helpful overview of the upgrade. As soon as I have the KS Pro I will definitely go back and do it all again ;)
PS
Do you have an equally clear overview of the changes in update 2.0?
Cheers! It doesn't look like I did one for v2.0. I seem to recall that there wasn't a lot in that update that I wanted to talk about.
@@OscillatorSink , thank you for your feedback! Let's hope that Arturia will surprise us all soon and release update 3.0 (adding, for example, Strum and many other useful features).
I wish there was a way to latch the scene button like that transpose latch!! Is there a way to do that already that im missing??
Does the Transpose , affect all the tracks? So that they are in the same key together? Is that a selectable option?
Re: the Program Changes… does it send Bank Select as well?
You have PC and also Bank MSB/LSB.
Is it possible to connect two Keystep Pro units together, giving you an 8-Track sequencer that can control 8 different devices all playing in sync with each other?
Yes.
And yet sadly, with these devices using RGB LEDs, those of us who are a bit colour deficient are spannered as the colours are really indistinct.. Cant tell the differenve *at all* in this video, so I'm hoping they're rather better IRL...
Under the bright lights I had shining at it, the colours aren't as clear, but in normal room lighting they're much better. I will add: I only showed three different colours in the video - and two of them were shades of blue. You do also still get the feedback of the particular track being lit while editing.
PC is pretty significant, does it glitch when doing a PC if you have the 1st step enabled of a sequence?
What about bank changes, are you able to do this given synths with 512 patches normally have 4 banks with 128 patches.
I am all for recycling hardware in live sets. You could have the PC set in a way where you don't even use the sequencer for notes, so left all blank, use another sequencer (I have a P PLAY), but use the KSP as a favs Patches for sets that don't have notes tied.
That's 16 recalls of patches which is pretty cool imo, and you can do this for 4 synths, so I am going to try this later tonight.
Thx for the update.
In the demonstration I have notes on the first step of both patterns and on the microfreak there's no glitch, so it appears to be sending the PC message a little ahead of time - but not every synth changes programs instantly so it might vary from instrument to instrument.
It supports LSB/MSB program changing which is how most instruments give you access to larger number of patches, but again - it'll vary from one instrument to another, so get reading those MIDI implementation charts!
@@OscillatorSink yeah I am familiar with MIDI charts, have been using them for ages, even did a test on Pro Tools for PC with some gear, that's where the issue lied, it would glitch.
Nice knowing there are no issues here.
@@OscillatorSink is the keystep pro a good piano to make music for film?
@@thegreat1548 it's a controller so it doesn't make any sound on its own. You need virtual or hardware instruments for it to control.
@@OscillatorSink yea I understand that part. Im just trying to find a controller that's good for film scoring
PC doesn't seem to work unfortunately. Trying it with the KSP and the Microfreak, no luck, let alone with other devices. Updated the Firmware multiple times, watched all the Videos, read all the Posts etc. No can do ;D
I find that of you flick msb and lsb up and then back down to 1, then go to the assign it will then work. Seems to work fine first time on patterns that have never had any pc data on them . This trick works every time for me on microfreak and other synths.
@@stuartsmith657 Thx! I actually got it to work with the MF now ;) but with the TR6S its CVing but randomly, haha. Well I'll get to that some day :D
When you change to full velocity for one channel does it affect all channels or can you have velocity on one channel but no velocity on another?
It's per track.
@@OscillatorSink Awesome! Thank you! :)
Can this Keystep Pro also automate the midi channel it's transmitting on the way like it sends programme changes (from one pattern to another or from one scene to another). I mean if we have more than 4 hardware synths, let's say 6, can we automate which one of (gets midi and plays) from one pattern or scene to another? Or do we have to change the midi channel manually?
Midi channel is assigned to a track on a per project basis. So you have to switch projects, you can't do it per pattern (currently, in the firmware available at the time of writing).
@@OscillatorSink Thank you!
is there a way to store track colors in memory and don't have to set them every time you turn on the device? Or is that a bug of the firmware?
It should save with the project (but you need to explicitly save the project once you've set them up, it won't auto save).
@@OscillatorSink That makes sense, thanks! just got it and I have a lot to learn
A truly terrible update unfortunately. Program changes is great and all, but both units I've updated to 2.5 now do not save any mute data across any of my projects. Doesn't matter how many times I save or how I save it, all mute data is erased once the unit is powered down. Makes it all but useless to me now. Arturia wrote back saying they know about the problem but are essentially in no hurry to fix it. Great work Arturia. You almost make the best gear. Then you don't.
I had the same issue. Can confirm they now fixed this with the latest update.
It’s actually kind of insulting this “update”
Nothing is new 😊