One Screen Control for Two Functions

[chr.schmitz]

I have created a division with a tremulant. Some ranks have corresponding tremmed ranks, others require modeling. The tremmed ranks are enabled using a <stop> entry (together with a stoprank.StopCodeToSwitchToAlternateRank entry); the modeled tremmed ranks are enabled with some additional code in the <rank> table.

I solve the problem currently using a single screen control for both, tremulant <stop> and <tremulant>.

This technique works nicely on the screen, but if you MIDI-learn this control, HW finds only one of the two controls.

Is there a way to solve this issue in a CODM?

Best, Chris

[mdyde]

Hello Chris,

It's possible to use Stop.StopCodeFromWhichToCopyState and Tremulant.TremulantCodeFromWhichToCopyState to copy states from objects of the same type (and to set AccessibleForMIDIInputAndOutput=N for either), but it isn't possible within the CODM to copy states between Stop and Tremulant objects. I don't think there's any way you could achieve exactly what you're hoping for within the CODM, I'm afraid.

However, the user could potentially auto-detect both the virtual stop switch and the virtual tremulant switch to the same MIDI switch/piston.

[chr.schmitz]

Martin,

thank you very much for the quick response! I had already tried to use the two ...CodeFromWhichToCopyState parameters and had realized that they do not allow to copy states from different types.

I had also found out that the parameter stoprank.StopCodeToSwitchToAlternateRank requires a stop code and does not work with a tremulant code.

However, your workaround does the job nicely. Again, thanks a lot!

Best, Chris

[mdyde]

Thanks, Chris.

[mdyde]

P.S. I've also logged as an enhancement request that it could be useful if Hauptwerk allowed states to be copied between any of the three object types (instead of just objects of the same type).

[chr.schmitz]

Great! Thank you!

Chris