Problems viewing/using Generals Panel with Pitea School of Music organ

[ekortright]

Hello,

I put together a MIDI console for my church about four years ago, and I'm currently running GrandOrgue v3.12.3-1 on Rocky Linux 9.3.

The church organist was originally playing the Burea Church extended organ, which displays 30 general pistons in the main window, so he was used to setting his combinations by touching the buttons on the screen, and he could always tell which general preset was active by the corresponding button being highlighted whenever he pressed a hardware piston mapped to that button.

However, some months ago he switched to the Pitea School of Music organ, and that organ only displays 10 general pistons in the main window (virtual pistons G0 - G9). At first he thought he could only program 10 generals, but I showed him that he can always set combinations 11-30 by pressing the corresponding hardware pistons instead of touching buttons on the screen.

All the same, I thought I could give him the visual feedback he's used to by having the Panels > Generals window open so that he can see all the generals instead of just the first 10. The problem is that the panel behaves rather strangely.

1. For some reason, the first 10 general buttons do not highlight when the corresponding hardware pistons are pressed or when the panel buttons are touched/clicked on. I suspect that this is somehow related to the virtual piston definitions, because general buttons 11-30 (which do not have a graphical counterpart) are all highlighted when their hardware piston is pressed. Also, unsetting any of the first 10 generals restores the highlighting when the panel buttons are touched/clicked on (of course, nothing happens apart from the highlighting). Finally, when pressing a hardware piston, some buttons in the main window (G0-G9) are highlighted, but not all; the ones that are not highlighted, do get highlighted in the generals panel).

2. Another odd thing is that touching/clicking on the generals panel buttons 1-10 activates the corresponding combination for most of the buttons, but for some of them nothing happens (the combination does not change). Touching the corresponding virtual piston in the main window does activate the preset.

Can anyone tell me if this is something that can be configured to make the generals panel behave consistently, or is there a possible bug either in GrandOrgue or perhaps the organ definition? Let me know if I can provide any other information or test anything.

Finally, I would like to express my gratitude for all the effort that has gone into GrandOrgue and the amazing organs painstakingly build by Lars Palo and others, all made available for free, but there are simply no words that can do the job! :^)

[larspalo]

Thank you so much for your kind words!

So, the current download of PiteaMHS20160115.orgue use 10 (old style) ODF defined generals on the main panel. They are not the same as the GrandOrgue built-in generals available on the (built-in) panels. That's why they won't lit up on the Panels->Generals panel. Actually, I also see that the divisionals are of the old style ODF defined versions... Thus, the divisionals on the main panel won't be the same as on the Panels->Divisionals.

I should most likely create a new release of this sample set that only utilize the built-in GO generals and divisionals so that no confusion will arise. Basically, the only reason to use the old style of ODF defined generals and divisionals nowadays would be if it's necessary to implement fixed combinations or other "tricks" needed to model some odd organ behaviour, otherwise it's better to just use the GO built-in versions altogether.

For your specific use case a possible fix, that should work already right now, would be to connect all the physical buttons on the playing console to the built-in generals/divisionals available from the Panels->Generals and disregard all the versions displayed on the "main" panel. This will mean that the generals/divisionals on the main panel won't be lit up when the console buttons are pressed - but (all) the ones on the Panels->Generals and Panels->Divisionals will!

I'm sorry for the confusion but I hope that this explains the reason why... Remember that 2016-01-15 (when the latest PiteaMHS was released/updated) is more than nine years ago by now! Much have changed since that time.

Again, thanks for using GrandOrgue and the sample sets I've created (by myself or in collaboration with others)!

[ekortright]

Thank you very much! I will try that and report back to let you know what happened.

[ekortright]

Well, it worked exactly as you said--after removing the event listeners on the virtual pistons in the main panel, the built-in GO buttons now respond as expected: they are highlighted when clicked on or when the physical piston generating the event they are listening for is pressed, and the combination is changed.

Now I only need to make sure that the built-in GO generals/divisionals are set to the same combinations as the virtual ones were.

Thank you once again! This was very confusing, and now makes a lot more sense.

[larspalo]

Great that you got it to work!

You can just "copy" over the combinations by manually first activating a combination on the main panel - say General 1, and then push "Set" and after that push the Panels->Generals general number 1 and finally deactivate Set by pushing it again. Repeat for all the divisionals and generals you have available.

[ekortright]

Thank you! That's what I'll do.