[ New ] Midi remote control redesigned

[Tim E. Real]

Hi all.
After some discussions in another thread, I have re-worked the midi remote control dialog. A lot.
In github master now.

It may seem overkill, but it was necessary for maximum flexibility of users' midi devices and controllers.
I hope this helps the few who use this feature.

[ Edit ] Depending on users' actual devices, some buttons send two values - on and off, others don't.
By playing around with the 'Value Type' settings, it is hoped that all scenarios can be accommodated.
There is 'Trigger', 'Toggle', and 'Momentary'.
For example even if your buttons only send an on value, you can still select 'Toggle'.
If your buttons send on and off, you can take advantage of the 'Momentary' setting for FF and REW if you wish, for example.

Caveat: the 'CC' section only works with regular midi controllers.
It will not recognize (N)RPN or pitch wheel or program controllers.
It was mainly designed for midi push-buttons anyway, not continuous linear controllers.

Here are some screen shots (some text is in French, I'm experimenting with locale):

Screenshot_20230829_173607.png (43.89 KiB) Viewed 1599 times

Screenshot_20230829_173712.png (60.88 KiB) Viewed 1599 times

Screenshot_20230829_173803.png (54.37 KiB) Viewed 1599 times

[Tim E. Real]

Half an hour later:
Pushed a slight bug fix with the new midi remote control dialog.
Try it again.

[Impostor]

Half an hour later:
Pushed a slight bug fix with the new midi remote control dialog.
Try it again.

Muse-seq.cfg is updated only, and every time, upon closing MusE, so after the following actions

1. Configure global remote settings.
2. Open an old project.
3. Close MusE.

the global settings are lost again, because opening an old project resets the global remote settings to default.
When I insert action

2.a Open new project

between 2. and 3. then the global settings resulting from 1. are saved to Muse-seq.cfg since somehow the override from the old project is undone upon creating a new project (if I haven't closed MusE yet, that is). Nevertheless, if I ever close MusE from an old project again, the global control settings will be lost with it.

[Tim E. Real]

Thanks for the test.
Should be fixed now in git master.

Old songs and old config files both contained midi remote values.
I neglected to accommodate that global vs song difference when loading these old values.
All the values, regardless of whether they were in the config file or a song file, were incorrectly being sent to the global settings.

Try 'er out.
Thanks.

[Impostor]

Try 'er out.

Yes, it works well now...except when you assign the controls with "midi learn": In the global case the midi port should default to "any", because the port number of the midi controller may differ from project to project, and then remote control may stop working if you switch projects. Of course, it isn't much work to manually set them to "any", but you may prevent unnecessary bug reports by defaulting to "any" for the global case.

And step record "insert rest" via cc doesn't seem to work.

[Tim E. Real]

Thanks. CC step rest should be fixed in git master now.

Yeah the whole global vs song thing, it's the reason I added song-specific settings.
Ports can disappear between sessions.
Not much I can do as far the global settings, but they are there if needed.

[ Edit ] And ports can reappear again, such as someone forgetting to plug in a USB midi.
For that reason we generally do not want to touch the settings if a port was not found, we want to preserve them
for the next time the ports might reappear.