Sat Dec 19, 2009 7:15 am
Hello Graham,
I think you could probably do that within the CODM ODF format by creating two full sets of Division objects - make the 61/30-compass Gt, Sw + Ped the primary divisions, attach the stops/pipework to those, and give them the standard division codes (1, 2 and 3, so that they get mapped by Hauptwerk as the default keyboards). Then create another set of 54/27-compass divisions with no stops/pipework attached and using the 'non-standard division code' range (8, 9, 10). Create one custom coupler object (use the 'custom coupler' code range, i.e. CouplerCode=10000 for the Pedal-Pedal coupler, 10010 for the Gt-Gt, 10020 for the Sw-Sw) for each of the non-standard divisions to link it to its corresponding standard division with:
DefaultToEngaged=Y
SwitchIsLatching=Y
StoreInDivisionalCombinations=N
StoreInGeneralCombinations=N
AccessibleForMIDIInputAndOutput=N
OverrideSourceDivisionToSpecifiedDivisionCode=<the division code of the 54/27-compass division>
OverrideDestDivisionToSpecifiedDivisionCode=<the division code of the corresponding 61/30-compass division>
CoupleDestinationKeyboardRatherThanKeyAction=Y
...
I haven't tried making a test example, so I might have overlooked something, but I think that approach should work.
The users could then choose to play (map to) whichever set of keyboards they preferred, according to whether they wanted 61/30 or 54/27 compasses. You could display the different compasses on different screen tabs.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.