Hi there,
When I Detect chords in Scaler 3 and hit the bind button nothing happens. In order to get them bind I have to drag all chords down to the main track which is not what I want to do!
My workflow is the following:
I play around and whenever I like a chord I detect it. After a while I have, let´s say, around 20 chords. I usually use the “bind” function and play around with the chords until I have a chord progression that I want to continue working with, which I then drag into the main track.
But since the bind function does not work with detected chords, I either have to drag all chords into the main track, or instead of playing, I have to press on the chords with the mouse and then bring them down in order to be able to continue working with scaler at all.
Furthermore, the chords are always displayed incorrectly at the top of the display when I use “Detect Midi”. It always says “unison” or “second” but never the correct name of the chord. In addition, this display changes when I press more often on the same chord.
This only happens when I play in, chords from outside, not when I work within Scaler!
But since this is my workflow and the possibility is offered and also works flawlessly in Scaler 2, Scaler 3 should have no problems doing this too!
Here are 2 Screenshots:
Binding:
Displayed chord names:
Sorry, but unfortunately I can’t work properly with Scaler like this and it kills creativity. Since this is not the only Scaler problem I hope you can understand the frustration and fix this with an update!?
Thanks
Hi @intersolar, yes unfortunately not being able to bind detected chords in Section A is a known issue, listed on the known issues forum page, however this will be resolved in the upcoming Scaler 3.1 update.
The display you are referring to at the top of the screen should accurately list chord names for any incoming MIDI data and is not affected by notes being produced by Scaler i.e. chords being triggered. So you should only see chords/notes appear here during the detection process when Scaler is receiving MIDI notes, or when playing notes on a MIDI controller into Scaler. Otherwise this section should display transport and tempo info.
Do the chord names displayed here appear correct during MIDI detection?
Hi @Tristan,
This statement:
So you should only see chords/notes appear here during the detection process when Scaler is receiving MIDI notes, or when playing notes on a MIDI controller into Scaler. Otherwise this section should display transport and tempo info
The statement is only partially correct as shown in my previous screenshot.
In Scaler 3, the correct chord name is shown on the display when I detect the chord, that´s right.
However, if I then work with the chords in Scaler 3 and play chords with my keyboard or mouse, only e.g. D unison or D second is displayed, as already described. When I try to read the name in the chord field (screenshot)
I have to hoover over it and the name is shown like in a news ticker style way.
If I go to Scaler 2, the name of the chord currently being played is displayed, not only in detection mode, which makes perfect sense if you have chords whose names cannot be read in the small fields.
If you look at the screenshot from Scaler 2,
I play the Emaj7(sus2)/F# (arrow with marker 1)
and at the same time
it is shown in the display (arrow with marker 2)
This behaviour of Scaler 2 should be implemented in Scaler 3!
Often I like to play to the chords I recorded with Scaler in my DAW and like to see which chord is played when I play along and so I open Scaler and see the Chord names and also the individual notes!
Hope I could clarify the situation
Hey @intersolar The reason we don’t display the chord names in the chord panel display when chords are triggered is that it would be constantly flashing. But I do agree that it’s a good opportunity to show the entire chord name now we are restricted (due to space). Maybe we can show it on mouse click only? We will discuss internally thanks for feedback.
1 Like
