See the video at https://youtu.be/tVF4gYKGJDE . Scaler seems not to be able to process simple MIDI messages coming from a controller to feed a VST in the latest Bitwig Studio for macOS. If you listen carefully you’ll see that some MIDI goes out but immediately stops, too, like with a ‘note off’. If I deactivate Scaler, everything is back to normal. I tried with two different MIDI controllers. Any suggestions for me to investigate further? Thanks!
Hi @giacecco, apologies I’m struggling to understand what is happening in your video. Is seems as through you are using a MIDI controller to play a VST instrument (CS-80) on one track successfully, but then trying to play Scaler 3 which results in no output aside from some glitchy noises. But I cannot see a Scaler 3 track anywhere, so perhaps I’m not understanding. Not being a Bitwig user this isn’t entirely clear to me.
First of all, if you are running Scaler 3.1.0, be sure to update to the latest v3.1.1 which includes many fixes and stability improvements. Could you please let me know if the issue persists with Scaler 3.1.1, and also when Keys Lock is disabled?
Thanks Tristan, I apologize, I thought Bitwig was similar enough to other DAWS not to require more explanation. In the meantime, I’ve upgraded to 3.1.1 and the issue is still there.
In the video, on a track, I have in a sequence the MIDI controller input, Scaler and Arturia’s CS-80. When Scaler is bypassed, everything works fine.
I’ve done more testing this morning and the issue seems to be caused by aftertouch messages. If I filter them out from the MIDI source, I do not have the issue. Scaler 2 seems to have the same problem.
I see on the forum others complaining of aftertouch issues at different points in the past versions of Scaler.