Vangelis wrote:Hello,
I'm currently building a console with Nancy sampleset, This organ has four manuals and I have just three physical manuals, I use OLED display to visualise the name of each stops. Pedal, Positif and Great have their range of stops on the console, The Swell and Bombarde share the same range of stops as there is no space on the console to have both. With a switch I commute the use of the third manual between Swell and Bombarde divisions, and I would like to commute each Oled of this stops range according to the state of the Swell or Bombarde stops. To do that I need to memorise somewhere each stop state.
My question is relative to the state of each stops. Is there a HW function to know the stops state (On/Off) of each ? A such function could simplify for me the update of my Oled according to the manual used.
As usual, not sure to be clear, but I hope you understand me
Kind regards
Bernard
Hi Vangelis,
I don’t know if the implementation suggested by Mdyde is simpler or not, but I have a console with two manuals and pedalboard and 38 stop buttons in all. For samplesets that require more buttons, using BOME Midi Translator software, I developed a method of memorizing the states of each button shared with two stops. The idea is to assign a button the function of an alternating key of a group of other buttons that will toggle its functions according to whether that key button is on or off. The states of the buttons are memorized using environment variables of BOME Midi Translator: triggering of one of these buttons, its corresponding variable is also changed according to the status of the key button and an appropriate MIDI message is sent to Hauptwerk. So if there are, for example, 13 buttons that I want to switch between two divisions of the sampleset disposition, I reserve a 14th button as a key button, and assign 2 (or more, depending on the console implementation, whether Viscount or Roland, for example) variables for each button, the value of each variable being exactly the value(s) of MIDI message needed to trigger the corresponding console button state or, if the button state is changed in the console, the change of the stop state in Hauptwerk. The solution requires a certain programming expertise or, if this is lacking, a sufficient interest to study the language of BOME MIDI Translator, which is relatively simple. Once it's learned, this can be adapted for more groups of alternating buttons and/or more samplesets (custom MIDI messages after sampleset loading will inform BOME MIDI Translator which corresponding set of translating rules it should use).
About the inscriptions themselves on the buttons of the console, as I don't count on your marvelous LCD solution, I use a kind of thick paper template with the inscriptions previously prepared by me for each sampleset in a DTP program like MS Publisher that is put close (or on) to the buttons.