Hello Francois/mnailor,
We do aim to add functionality in the future for migrating MIDI settings from a MIDI port/device of one name to to another.
'Any enabled port' is potentially risky; it's *only* safe to use if both:
1. You are absolutely certain that each of your MIDI hardware units (MIDI keyboards/encoders/etc.) uses a distinct MIDI channel, and you are absolutely certain that will always be the case. And:
2. If any of your hardware uses MIDI sys-ex then each of your MIDI hardware units (MIDI keyboards/encoders/etc.) uses a distinct MIDI sys-ex ID, and you are absolutely certain that will always be the case.
In any other situation (if you have 'any enabled port' selected) there is a significant risk that MIDI events could trigger unintended virtual controls (because of non-unique MIDI channels, or MIDI sys-ex). In practice, situations 1 and 2 above are actually fairly unusual these days (since people more commonly connect MIDI hardware units directly to to the computer using separate USB cables, with all hardware units using the same MIDI channel). People using 'any enable port' without fully understanding the implications and requirements (i.e. that 1 and 2 above *must* be adhered to) has resulted in a lot of problems for people in the past (and resulting support for us). Hence adding a preference (even if labelled as 'advanced') in Hauptwerk to make Hauptwerk default to auto-detecting as 'any enabled port' is something I think we'd be very wary of doing. I think it would much safer and more reliable instead to include functionality to migrate MIDI settings from one MIDI port to another, so that's what we're aiming for.
We do aim to add functionality in the future for migrating MIDI settings from a MIDI port/device of one name to to another.
'Any enabled port' is potentially risky; it's *only* safe to use if both:
1. You are absolutely certain that each of your MIDI hardware units (MIDI keyboards/encoders/etc.) uses a distinct MIDI channel, and you are absolutely certain that will always be the case. And:
2. If any of your hardware uses MIDI sys-ex then each of your MIDI hardware units (MIDI keyboards/encoders/etc.) uses a distinct MIDI sys-ex ID, and you are absolutely certain that will always be the case.
In any other situation (if you have 'any enabled port' selected) there is a significant risk that MIDI events could trigger unintended virtual controls (because of non-unique MIDI channels, or MIDI sys-ex). In practice, situations 1 and 2 above are actually fairly unusual these days (since people more commonly connect MIDI hardware units directly to to the computer using separate USB cables, with all hardware units using the same MIDI channel). People using 'any enable port' without fully understanding the implications and requirements (i.e. that 1 and 2 above *must* be adhered to) has resulted in a lot of problems for people in the past (and resulting support for us). Hence adding a preference (even if labelled as 'advanced') in Hauptwerk to make Hauptwerk default to auto-detecting as 'any enabled port' is something I think we'd be very wary of doing. I think it would much safer and more reliable instead to include functionality to migrate MIDI settings from one MIDI port to another, so that's what we're aiming for.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Hauptwerk software designer/developer, Milan Digital Audio.