Hello Luc,
All 60 of the scoped combinations work identically internally. If A1 is working as you want it, but a different one isn't, then either:
- There must be some difference in the scopes or registrations that you've stored to them, or:
- You have MIDI configured to/from something that's causing the difference in behaviour.
You could try temporarily switching off your MIDI console, then seeing whether you still see the problem with the on-screen stops, so as to try to determine whether the problem is related to MIDI messages to/from the console.
Also/alternatively, as a test, you could try using a 'spare' one of the 'Hauptwerk (alt config N)' configurations (desktop shortcuts), which has all-default MIDI settings (e.g. use "File | Revert all Hauptwerk settings to factory defaults" within it, then re-launch it, then don't configure any MIDI settings for it) to see whether you still see the problem with the on-screen stops.
Assuming that the scoped combinations *do* then work properly on the on-screen stops, within your normal configuration you could then temporarily enable the "General settings | General preferences | Advanced ... | Diagnostics: log all MIDI messages received and sent" option, then use "Help | View activity log" after testing a non-working scoping combination, so as to see exactly what MIDI messages were sent and received, and what virtual controls/functions any incoming MIDI messages triggered.