It is currently Thu Mar 28, 2024 4:01 am


CustPg1_InputKbd_DivCodeX

Using the CODM to create your own organ definitions, exchange CODM organ definitions, ...
  • Author
  • Message
Offline
User avatar

chr.schmitz

Member

  • Posts: 374
  • Joined: Sun Aug 25, 2013 11:49 pm

CustPg1_InputKbd_DivCodeX

PostThu Feb 18, 2016 10: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
Offline
User avatar

mdyde

Moderator

  • Posts: 15441
  • Joined: Fri Mar 14, 2003 1:19 pm
  • Location: UK

Re: CustPg1_InputKbd_DivCodeX

PostSat Feb 20, 2016 4: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.
Hauptwerk software designer/developer, Milan Digital Audio.

Return to Custom Organ Design Module (CODM)

Who is online

Users browsing this forum: No registered users and 5 guests