Custom Couplers for non-common harmonics

Using the CODM to create your own organ definitions, exchange CODM organ definitions, ...
Post Reply
jrball
Member
Posts: 197
Joined: Fri Feb 06, 2004 2:07 pm

Custom Couplers for non-common harmonics

Post by jrball »

CODM coupler codes exist for classic harmonics and uses.
What if a theatre organ needs "third" and "fifth", and "seventh" and other non-common harmonics?
I suspect "CustomCoupler" codes may be used but I cannot see how to set them up and how many I can get.
Can anyone shed light on how to do this?
User avatar
mdyde
Moderator
Posts: 15695
Joined: Fri Mar 14, 2003 1:19 pm

Re: Custom Couplers for non-common harmonics

Post by mdyde »

Hello jrball,

Yes -- you can use 'custom couplers' for those. Have a look at the 'Custom organ definition table: Coupler' section in the 'Design tools | View Custom Organ Design Module ... format documentation' document.

Set the CouplerCode to be one of the 'custom coupler' values for the appropriate divisions, then use CustomCoupler_MIDINoteNumIncrementFromSourceToDest to set the coupling pitch. If I recall correctly, the 'ExampleCustomOrgan2' example CODM organ definition has some custom couplers, by way of examples.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
jrball
Member
Posts: 197
Joined: Fri Feb 06, 2004 2:07 pm

Re: Custom Couplers for non-common harmonics

Post by jrball »

Thanks, Martin.
The Organ2 and CODM manual references don't mention multiple harmonic couplers for the same Div to Div combination.
Overrides for 10050-10057 might support: Solo-Solo 16', Unison, 4', 3rd, 5th, 7th, etc?
However, overrides are only allowed for non-standard divisions.
I'm still unclear on how to do it.
User avatar
mdyde
Moderator
Posts: 15695
Joined: Fri Mar 14, 2003 1:19 pm

Re: Custom Couplers for non-common harmonics

Post by mdyde »

Thanks, jrball.

By way of example, make a copy of ExampleCustomOrgan2 CODM ODF, find its Coupler object that currently has CouplerCode=1006 ("Coupler: Gt to Ped") section, and edit it to change it as follows:

CouplerCode=10003 [which means "Couplers: custom coupler 4 to Pedal" -- this ODF already has three other custom couplers for the Pedal division, so this one will be the fourth]
Name=Coupler: Gt to Ped 5th
CustomDisplay1_Text=GT TO PED 5th
DisplayName=GT TO PED 5th
OverrideSourceDivisionToSpecifiedDivisionCode [leave this at 0/null, since CouplerCode above defines the source division]
OverrideDestDivisionToSpecifiedDivisionCode=2 [Great]
CustomCoupler_MIDINoteNumIncrementFromSourceToDest=7 [since a scale interval of a 5th is +7 semitones]
CustomCoupler_KeyActionTypeCode=1 [normal]
CustomCoupler_KeyActionEffectCode=1 [normal]
CustomCoupler_PipeMIDINoteNum036_PizzOrReitPeriodMs=0/null
CustomCoupler_PipeMIDINoteNum096_PizzOrReitPeriodMs=0/null

Since this ODF has a ShortcutPiston object as a reversible (which is named "Reversible: Gt to Pd") pointing to that original Gt to Ped coupler, we will also need to edit that ShortcutPiston to change it to point to the new coupler code as follows:

Name=Revers: Gt-Pd 5th
CustomDisplay1_Text=GT-PD 5th
CouplerCode=10003
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
jrball
Member
Posts: 197
Joined: Fri Feb 06, 2004 2:07 pm

Re: Custom Couplers for non-common harmonics

Post by jrball »

Thanks again Martin.
I looked at this method but didn't try it because the override description is restricted to non-standard divisions:
"Since the main coupler code only covers the 7 standard divisions, you can only couple to/from the non-standard divisions using these two settings."
Did I mis-interpret that wording?
User avatar
mdyde
Moderator
Posts: 15695
Joined: Fri Mar 14, 2003 1:19 pm

Re: Custom Couplers for non-common harmonics

Post by mdyde »

Thanks.
jrball wrote:"Since the main coupler code only covers the 7 standard divisions, you can only couple to/from the non-standard divisions using these two settings."
By that I meant that the only way that it's possible to couple to non-standard divisions is by using those two settings. I didn't mean to imply the converse, although I see that it could be interpreted that way. My apologies for not being clearer.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
jrball
Member
Posts: 197
Joined: Fri Feb 06, 2004 2:07 pm

Re: Custom Couplers for non-common harmonics

Post by jrball »

Yes, I now see it both ways also.
So, onward to coding those pesky couplers.
Post Reply