version Scaler 2.9.1
I manage to cause Scaler 2 crash every time with the following setup:
Hi @neldivad
Welcome to the forum.
I have just tried detecting midi from my old Oxygen keyboard playing an Ab maj 7 copying the chord to Section C ad then playing it back with no issues.
My environment is
DAW: Reaper 7.25
OS : WIN 10 Home 22H2
RAM: 16GB.
Can you give you give details of your DAW and operating environment, please? If you can record a video of this happening it would also help.
May I also suggest that you upgrade to the latest version (2.9.1)
DAW: FL Studio 24
OS: Windows 10
Chord: Ab maj seventh [Ab4, G5, Ab5] (not Ab maj 7) (you can only get this chord by detect midi function)
Version: 2.9.1 (latest scaler 2) (from scaler settings GUI)
Version: 2.7.0.4394 (from FL plugin wrapper)
Playback has no issue. Playback with performance applied to chord will crash.
Thanks for posting the video. I have tried to replicate your pattern on my Scaler running in Ableton Live. Having replicated your pattern to the best of my ability and created a performance playback group which I have applied to the last two blocks in the pattern as per your video, Scaler plays with no issues.
However, I am confused by a couple of points in your last posting
It looks as if you have two versions of Scaler installed I am not familiar with FL Studio 24 but I do wonder why you are using Scaler version 2.7 in FL Studio 24 rather than version 2.9.1. I wonder if this is causing you the issue.
The second point that is confusing me is
You can create this chord in Scaler using the keyboard on the CHORD page so you don’t have to use the detect midi function. Having said that, searching for Ab maj seventh in the CHORD SEARCH box results in Ab maj (this may be a bug).
I am trying to recreate your issue but have not had any success yet. If you could export the Scaler state and upload, I could then import it into my Scaler which may help identify the issue.
No I dont have 2 versions of scaler installed. I made a mistake thinking the number is scaler’s version. Turns out its just the version for FL wrapper for plugins. Opening any other plugins in FL have the same version displayed.
The true version of Scaler is right at the settings which correctly displays 2.9.1.
Yeah I can’t search the chord Ab maj seventh. My understanding is that detect midi feature is possible to name non-standard combination notes as a “weird chord” that would be incompatible with some performances that algorithmically “look for say 3rds, 5ths” to produce a standardized performance.
I hypothesize that when non standard chords are missing those notes expected by performances, it crashes.
It could also be an FL issue, considering they have a reputation of doing a lot of things differently relative to other DAWs.
The easy fix is to just stick with standard chords, and detect midi should be used conservatively to learn about the chord name and quality but not using it with other features to avoid playback bugs.
Glad you don’t have 2 versions of Scaler installed.
I have tried creating a pattern with Ab maj seventh as the last chord and then adding a second pattern. On the last two chords of the first pattern I have added a playback performance using the ACCENTO performance. The first chord on the second pattern is a Db maj. This plays in Reaper 7.25 and Ableton Live 11 with no issues.
I have uploaded the state below and you may want to import it into your project to see if the issue recurs. This may help identify the cause.
Ab maj seventh test.xml (25.2 KB)
No two DAWs are the same 
IMHO everybody interprets the standard slightly differently.