-Scaler 3.3.2 (build 79ae621) VST3
-Ableton Live 12.4.6 (Suite)
-Windows 11 Pro 10.0.26300
-No instrument loaded, Scaler receiving MIDI
Summary:
Pressing Detect while Scaler is receiving MIDI generated by Live’s Arpeggiator into Bouncy Notes chain makes Live hang (“Not responding” in Task Manager, ~4% CPU) and then crash when the window is closed. 100% Reproducible in a fresh set. First found it at Bouncy Notes 16 voices / 4-bar lifetime; it still reproduces at 2 voices / 1-bar lifetime.
I realize this may be an ‘edge case’ and sending generated MIDI into detect probably is not a typical workflow (I’m still exploring in “Trial Mode”) - reporting because it crashes the DAW to desktop instead of ‘failing gracefully’
How to reproduce:
1: New Live Set, 4/4, 120BPM
2: On a MIDI track add Arpeggiator (Up & Down, Rate 1/8, Hold ON, Repeats infinite, Gate 50%, Scale Chromatic) → Bouncy Notes (Voices 2, Lifetime 1 bar, Drop: Press, Speed 100, Gravity 1.19, Mass 2.68, Friction 0.01) → Scaler 3 (VST3).
3: Play chords so Arpeggiator/Bouncy Notes start generating
4: In Scaler, press Detect
Result:
Live stops responding; closing the window produces a crash report on the next launch
Full process dumps and crash reports are available, which I’d rather not post publicly; happy to share privately.
Hi @jeremeyhustman, welcome to the forum and thank you for the detailed report.
I have attempted to replicate your crash scenario and although Scaler 3 does appear to become briefly unresponsive I did not experience any crashes.
Keep in mind that when running things like MIDI arpeggiators into Scaler 3’s MIDI detector, each new note is registered as a new chord. So the result is a very large number of detected chords so it appears the detector is being overloaded by all of the incoming MIDI notes.
If you do have a crash report and/or a Live set you would like to share you’re welcome to DM me so we can investigate further.
Thanks Tristan -
It’s a ‘hang’ instead of a crash. Live goes into “Not responding” within seconds of hitting detect and never comes back. The UI freezes and I can’t stop the transport.
I did the test again and left it untouched for 12 minutes. In task manager, here is the working set every 2 minutes so it does look like it’s accumulating; it’s just that once it starts- I can’t stop it.
t+0 Running CPU 3% 1,048 MB
t+2 Not responding CPU 4% 1,087 MB
t+4 Not responding CPU 3% 1,114 MB
t+6 Not responding CPU 4% 1,135 MB
t+8 Not responding CPU 3% 1,151 MB
t+10 Not responding CPU 3% 1,172 MB (task manager dump taken)
t+12 not responding CPU 4% 1,406 MB (dump taken, the increase is probably dump-related)
It’s at this point that I hit the ‘X’ on scaler itself, which crashed Ableton
DM’ing you a link to the crash reports