[BRX]

 I think most users with a tablet aren't going back and forth between a screen/keyboard though, so the same inefficiencies aren't present. The app was originaly designed around tablets, not a monitor with just a keyboard, so I'll have to do some work figuring out how to make it all easier to use in that scenario. It sounds like you may need the screen with additional key/action mappings to be implemented for this to all work as you desire, as me just fixing the searching and song selection won't be enough by itself.

I agree with Shawn though. Can't speak for other users, but I often use MSP on my (no touch) desktop W10 machine to prepare setlists or to maintain my archive (especially for filling out written annotations or fields like composer, genre etc. it's really a benefit to have your normal keyboard). Also on W10 a user is inclined to use MSP and not the companion. All the more because the syncing has become much more efficient and easier with the sync feature or simple because of the relative paths.

Also I believe that it would be again very beneficial to have better keyboard support for those who like to have a "stationary installation" on top of a piano or something (like that in that other post recently). There are a lot of screens, mini pcs or all-in-ones which don't have touch support but would be great for this use.

So, while of course MSP comes from tablet use and will stay that way you shouldn't underestimate the usefulness of MSP for W10 devices without touch support.

Thanks for the tip with the pedal functions. I wasn't aware of this workaround and I must have missed it when I complained some time ago about the lack of keyboard support in W10 myself.