When I use the Detect Midi function, it will only store the notes at the top (to the right of Chord Set) if I am currently playing them on my midi keyboard; it will not store the notes properly if playing back midi written in the piano roll (I’m using FL Studio 2024) like in Scaler 2. Because of this it will not give the proper scales to choose from based on my melody/chord progression. I hope I explained that properly.
Hello, I think I understand you, Scaler 3 does read from MIDI input just like Scaler 2. See attached
Ah ok I just figured out what’s happening; any notes that overlap (like with portamento sliding synth for example) will cause it to cancel out the last read note instead of adding to the list. When I changed my notes to end right at the next note it works fine. Knowing that, it’s not the end of the world and a quick fix but I think it’s something to be aware of perhaps.
1 Like
After messing around a bit more I can see this potentially becoming a more of an issue. If I have a chord progression with any type of melody within the chords then that also introduces the issue. My whole workflow involves me writing my own chords and melodies and then using Scaler to help point me in less obvious directions but with the MIDI Detector behaving the way it is currently it’s kind of putting a damper on that unfortunately. Scaler 2’s detector did not behave this way.
Again, I know work arounds and have theory knowledge so I can deal with it for the most part, and it might not even be an issue at all for others, but I think it’s worth looking at. If you have any melody and/or bass run within your chord or use any type of portamento or legato phrasing in your MIDI notes the detector behaves differently, especially in the latter case. For the former, as long as the melody falls within a common/obvious scale I imagine it’s fine most of the time but I think if you deviate from the norm that’s when it would become more of an issue.