A project using only a Scaler 3 track with no external instrument routing.
kltest2.zip
In the editor the notes don’t appear to be cut short, as they are when routing to an external instrument, but when you play the track they are. I also included some pairs of notes where the E was preceded by a C instead of a D, and you can hear they are not cut off, it is only when they are preceded by a D. This varies from chord to chord, but I think it is always when a 5th is preceded by a 3rd in a triad. The notes I have referred to are Scaler’s keys lock placeholder notes, because that is what is recorded, not the ones that you hear which are those of a G chord.
It happens with chords muted or not.
The video you referred to was about a similar but different problem. That happens with a keyboard with polyphonic aftertouch (see the conversation above). The issue we are now discussing is not related to that and happens on any keyboard.
Hi Nick. Apologies for being slow to get to this. Would you mind checking if your download link is still valid? I get an error message when I click on it.
That’s strange. I created a new link:
kltest2
You have to click the download button at the bottom, the icon itself isn’t a link.
OK apologies, for some reason I was getting a OneDrive error whenever I clicked on the link from a Mac, but the PC managed to download it just fine. Thanks for submitting that project file, I can definitely hear those notes being cut off so we’ll need to take a close look and figure out what is going wrong. Thanks again!
@NickC4555 apologies for the lack of communication here. Just wanted to let you know that the Scaler 3 1.0.6 update is now available. Of the many improvements here is a fix for an odd MIDI timing issue that was related to audio buffer size settings.
Whilst it doesn’t directly address keys lock, we suspect it will assist with a variety of reported issues. So would you mind installing this update when you can and seeing if it improves things for you? If not we’ll certainly look into your specific case a bit closer now that we have a few pressing concerns addressed.
1 Like
It’s still doing it. Sorry!
I have just tested this in 3.1. The bug is still present. Whatever chord is selected in section C, the cut off note of the 5th when preceded by the 3rd. I realise there is a lot going on at Scaler, but this is fundamental to being able to improvise with keys lock.
Scaler 3 is unusable for me. I have little keyboard ability so I rely on keylock white keys only when I want to play in any key other than C. Scaler 2 works fine. Whenever you play a note that is shifted on Scaler 2 on your MIDI keyboard you see the converted note light up on the Scaler plugin, but in Scaler 3 the original note and the converted note lights up and this seems to be causing the problem. If you play one of these highlighted notes, let go and play the other soon after then the second note is cut off. If you play the second note though while still holding down the first one then it plays properly. It is even worse if you use the chord notes (or it might be chord extensions…. I have memory problems ) as you get silent notes even when playing notes an octave away from the chord notes.
I like the new features of Scaler 3 but I’ve had to go back to Scaler 2 because of this problem.
1 Like
This sounds to be the same or very similar to the problem I have described here too. I have also had to revert to Scaler 2 because of this, a problem I first reported 4 months ago.
I think the developers have overstretched themselves with new features at the expense of the fundamentals. I’ve been a Scaler customer since v1 (six years) and as you can see from this topic, I put considerable effort into documenting how to replicate the bug and yet several v3 releases later, it still is overlooked. It’s disappointing to say the least.
I’ll add a bit more info here.
Both keyboards I used with Scaler 3 do have after touch. I initially noticed this issue using my Montage M6 as a Midi keyboard. This has mono after touch. I switched to my Native Instruments Mk3 and this has the same problem, whether in poly, mono or even with the after touch turned off.
I can easily repeat the problem. Select F Minor scale, and turn on keys lock white keys only. Tap the midi keyboard’s F key in a staccato style, which plays a converted A# and follow it reasonably quickly with a C on the midi keyboard, which tries to play a converted F in the scale. If the duration between the notes is just right then the second converted note will cut off. If I just tap the 2 keys again and again at the right speed then plenty of dud notes will occur, and it will always be the converted F, never the converted A#.
Does this need to be posted in the bug report section or do devs still read these posts?… I notice that it’s been months since the last official reply on this thread.
Hi folks. Our apologies, this is indeed on our list of issues to address, unfortunately that list is quite long and this is not something we have been able to get to just yet. We have however looked into this and do now understand the cause, so this should be resolved in the next Scaler 3 update.
As I understand it, when using Keys Lock, if you trigger a second note before releasing the first note, and the second note being triggered is the same note as the first trigger note used e.g. play keys D then E, and the key E triggers a D, releasing the first key will send a note off message to the second note, resulting in the note being cut off. In another case, notes from triggered chords can be cut off when releasing keys lock keys if there are shared notes.
Given this issue only occurs in specific circumstances it was tricky to initially reproduce. But you’re correct that this did not occur in Scaler 2 so we have escalated this in priority and as mentioned should be able to address it in the next Scaler 3 update. Apologies again for the inconvenience here.
1 Like