Back again! Thank to all for the help on the codes for notes and keyboards. I now have two 61 key manuals working w/midio128 on one core.
I guess I’m still missing something, as I have no idea how to program pistons in the .ini file. It looks like I just program the pedal notes with a 92 code for channal 3, but I could sure use some help with the pistons. Using another core with two DINs with midio128, I plan on adding 25 pedals, and 10 buttons under each manual. It looks like I can use a modified midio 128 to add an expression pedal, or a hex file from Per S to add 3 pots. I’m still a little confused there.
I soon hope to start wiring in the Conn 642. Thanks for all the help
Four DINs on one core for the two manuals, and two more DINs on another core for pedals and pistons. All the hardware is built and tested, but I now need to configure the second core. Then it’s into the organ!
I guess I’m still missing something, as I have no idea how to program pistons in the .ini file.
##########################################
# Pin # On Evnt # Off Evnt # Behaviour #
##########################################
86 = CF 7C 56 80 25 56 @OnOnly # General Cancel
87 = CF 00 57 80 26 57 @OnOnly # P Solo
88 = CF 01 58 80 27 58 @OnOnly # MF Solo
89 = CF 02 08 80 28 59 @OnOnly # F Solo
90 = CF 03 06 80 29 5A @OnOnly # FF Solo
91 = CF 04 07 80 2A 5B @OnOnly # FFF Solo
92 = CF 05 05 80 2B 5C @OnOnly # 1 Solo
93 = CF 06 5D 80 2C 5D @OnOnly # 2 Solo
This should give you a general idea. The “Off Evnt” is don’t care since it’s “@OnOnly”. Also the third byte is don’t care since this is a “Program Change” command which is only two bytes long. See Miditzer settings under Pistons.
When I woke up this morning, It occurred to me that, unlike notes, the piston settings would be specific to Miditzer. The pistons and stops settings in setup now made sense to me. Your specific code examples clear up things even better.