No that is the expected behavior. What that feature does is take any physical key on your keyboard which is not in the current Scale and when you play that key it will play the closest Note which is in the Scale. That’s why you are seeing pitch doubling. Basically this lets you hit any physical key on your controller & it will always play a Note that actually is in the Scale.
To have the white keys play an A Major scale use the Transpose function instead - either up by 9 half-steps or down by 3.
FWIW, I don’t think this is properly implemented. An incoming G could be mapped either to F# or to G# - same distance. The right answer, IMO, would be to map it to G# - a) because there is already a note mapped to F#, b) because having the 7 white keys map to any target scale that is also 7 notes is highly desirable, and c) because the suggested work-around of using direct transposition is destructive of the locality of pitches on the keyboard.
Yes, the mapping should allow you to hit any physical key on your controller & have it play in the scale - but should do so while putting a 7 note scale entirely on the white keys (with no duplications). There are other DAWs that seem to have understood this point.
Thanks though for making the point about transposition. Even though it hurts locality, it will put the target scale on the white keys!
That’s not a work around, it is the intended design.
Speak for yourself, that sounds very undesirable from my perspective. I’ll stay with the status quo.
FYI although Drum Maps were designed for mapping drums (duh) you can use them to remap your keyboard however you like. I once mapped the white keys to play like a kilimba.