Search:
Submit Search


CustPg1_InputKbd_DivCodeX

Using the CODM to create your own organ definitions, exchange CODM organ definitions, ...

CustPg1_InputKbd_DivCodeX

Postby chr.schmitz » Thu Feb 18, 2016 11:50 am

Hello,

when compiling a CODM into an ODF, HW creates two entries in the <keyboard> node: <CustPg1_InputKbd_DivCodeX> and <CustPg1_OutputKbd_DivCodeX>. Why does that happen? The visual controls for the keyboards (keys) are obviously connected with these entries? Why is the corresponding "main" keyboard not connected directly?

Best,
Chris
User avatar
chr.schmitz
Member
 
Posts: 171
Joined: Mon Aug 26, 2013 12:49 am

Re: CustPg1_InputKbd_DivCodeX

Postby mdyde » Sat Feb 20, 2016 5:56 am

Hello Chris,

Are you actually having some kind of problem? (The displayed keyboards are actually generated that way to avoid infinite loops, but as long as it works, which it should, then the exact way the CODM works internally, i.e. compiles things, shouldn't matter.)
Best regards,
Martin.

[Please use email or the Contact page if you need to contact us privately, rather than private forum messages.]

Image
User avatar
mdyde
Moderator
 
Posts: 10175
Joined: Fri Mar 14, 2003 2:19 pm
Location: UK


Return to Custom Organ Design Module (CODM)

Who is online

Users browsing this forum: No registered users and 1 guest