Bug/quirk when DAW-synced causing stuck notes

Scaler 3 Support Bug Reports
1

When using Scaler 3 as a MIDI FX plugin in Logic Pro with DAW sync turned on to play some one bar chords I found that Scaler 3 is sending two MIDI Note On messages for every note at the start of each chord and then two Note Off messages for every note at the end of each chord. However if the DAW transport is stopped in the middle of a bar interrupting the Scaler progression, only one set of Note Off messages is sent:

[NoteOn channel:1 pitch:56 [G#2] velocity:110]
[NoteOn channel:1 pitch:59 [B2] velocity:110]
[NoteOn channel:1 pitch:63 [D#3] velocity:110]
[NoteOn channel:1 pitch:56 [G#2] velocity:110]
[NoteOn channel:1 pitch:59 [B2] velocity:110]
[NoteOn channel:1 pitch:63 [D#3] velocity:110]
[NoteOff channel:1 pitch:63 [D#3] velocity:127]
[NoteOff channel:1 pitch:59 [B2] velocity:127]
[NoteOff channel:1 pitch:56 [G#2] velocity:127]
>

This causes the notes of the interrupted chord to continue playing with some VSTs. The stuck notes can be cleared by disabling the Scaler 3 plug-in which sends a second set of Note Off messages.

If Scaler 3 is allowed to play through the chord progression without interruption, there are two Note Off Messages sent for each note. Here is an example of two triads played by Scaler 3 through past the end of the second chord:

[NoteOn channel:1 pitch:56 [G#2] velocity:110]
[NoteOn channel:1 pitch:59 [B2] velocity:110]
[NoteOn channel:1 pitch:63 [D#3] velocity:110]
[NoteOn channel:1 pitch:56 [G#2] velocity:110]
[NoteOn channel:1 pitch:59 [B2] velocity:110]
[NoteOn channel:1 pitch:63 [D#3] velocity:110]
[NoteOff channel:1 pitch:56 [G#2] velocity:110]
[NoteOff channel:1 pitch:59 [B2] velocity:110]
[NoteOff channel:1 pitch:63 [D#3] velocity:110]
[NoteOn channel:1 pitch:63 [D#3] velocity:110]
[NoteOn channel:1 pitch:67 [G3] velocity:110]
[NoteOn channel:1 pitch:70 [A#3] velocity:110]
[NoteOff channel:1 pitch:56 [G#2] velocity:110]
[NoteOff channel:1 pitch:59 [B2] velocity:110]
[NoteOff channel:1 pitch:63 [D#3] velocity:110]
[NoteOn channel:1 pitch:63 [D#3] velocity:110]
[NoteOn channel:1 pitch:67 [G3] velocity:110]
[NoteOn channel:1 pitch:70 [A#3] velocity:110]
[NoteOff channel:1 pitch:63 [D#3] velocity:110]
[NoteOff channel:1 pitch:67 [G3] velocity:110]
[NoteOff channel:1 pitch:70 [A#3] velocity:110]
[NoteOff channel:1 pitch:63 [D#3] velocity:110]
[NoteOff channel:1 pitch:67 [G3] velocity:110]
[NoteOff channel:1 pitch:70 [A#3] velocity:110]
>

Based on the velocities it looks like the Note Off messages in the transport stop scenario (first example) are being generated by a different mechanism than those in the play-through-to-the-end scenario.

Is there a reason for sending the duplicate messages? I only have one other third-party MIDI FX plug-in installed currently and that one does not send duplicate messages.

If the duplicates are by design, is there some setting that I need to change to ensure the corresponding extra set of Note Off messages will be generated on DAW transport stop?

2

Thanks for taking the effort to do that. We’re putting together a range of possible related things so this helps.

3

I’m using Scaler 3 v1.0.7. Currently as a VST3 in FL Studio 25 (beta 6) / Win 11.

Since I bought the plugin I’ve had lots of stuck notes when previewing chords with the mouse on internally hosted synths, e.g. Serum 2 VST3 and internal Instruments like the Grand Piano.

It’s not only the click preview; the same thing happens with chords triggered from my MIDI keyboard. Unfortunately, it’s so annoying that I’ve had to stop using Scaler 3 for now.

Setup

  1. Windows 11 Pro / Scaler 3 / FL Studio 25 (beta 6)
  2. Load Serum 2 and choose any polyphonic preset (or chose internal instrument) inside Scaler
  3. Project tempo 150 BPM / PPQ 192, DAW is in “Song Mode”, DAW playback is stopped and stays stopped for this.
  4. Scaler 3 “DAW Sync” disabled
  5. Play some chords with the mouse or linked keys in Scaler, for example C Phryfian mode with Passages 9 x2 active :-). Let got from pressing the mouse or key randomly while playing different chords/performances.
  6. Notes should get stuck quickly. (Now hit the MIDI Panic button several times or replay the note that didn’t receive a Note-Off … :upside_down_face:)

I hoped this would have been fixed, since I’ve seen other reports about stuck notes here. Well, here’s my report… :sweat_smile:. I’ll check back from time to time and keep an eye on plugin updates, too… but for now I’ll remove Scaler 3 from my workflow. It’s pretty frustrating when this happens a hundred times a day. :frowning:

Thanks for reading and keep it up - this still are epic plugins, they helped me a lot in the past.

4

Hi @mzett. Thanks for taking the time to report this. While there are some differences between your report and GrapefruitDream’s, I’ve merged your post into this existing topic, as both reports seem to point to the same underlying issue.

1 Like