Controlling stops with external controls - GrandOrgue/grandorgue GitHub Wiki

A physical console is nicest to play when it has motorised drawstops or tablets. This short note shows how I configured a organ to have its virtual stops controlled by MIDI messages from the external hardware and how to send messages to the hardware if the virtual stops are altered by combination pistons of on-screen clicks.

The screen-shots involve a little cheating as my testing hardware stops are actually interfaced on the same computer as GO so the MIDI wires are software ones implemented by the LoopBe utility (https://nerds.de/en/loopbe1.html).

In the Audio/Midi menu choos Midi & Audio Settings and the MIDI Devices tab

MIDIPorts.png

Click the* MIDI-Output-Device...* button. This dialog will appear

OutputDevImage.png

Select the MIDI device which relates to your physical stops and click OK. Click OK to close the Midi & Audio Settings dialog.

Next, one by one, you configure your stops associating a virtual stop with MIDI messages to and from the real one. Right click a virtual stop. The following dialog will appear with the Receive tab selected

RightClickedStopBlnk.png

Click Listen for Event and operate the physical stop. The fields of the dialog will be filled in corresponding to the channel/note etc. used by the hardware so you will get something like

RightClickedStop.png

Now move to the Send tab. This will initially be blank or greyed out (or perhaps have an old configuration!)

RightClickedSendBlnk.png

Click the Copy current receive event button. The dialog will populate with numbers that are the same as the automatic detection put into the Receive tab.

RightClickedSendSet.png

Click OK. Now test that clicking the virtual stop changes the real one and using the real one changes the virtual stop.

Repeat right-clicking all the virtual stops that you wish to control with real ones.

Don't forget to Save the organ or all your work will be lost (without warning) on shutdown.

This page will become redundant when the Help file is updated to describe the MIDI Output Device and Copy current receive event buttons.

Hope this helps someone else.

Published by John Prentice under the GPLv2 or later (12 April 2019)

Example: How to get the LED lights working on Novation Launchpad with GO

There is, I think, also a very simple and easy way. I’ m under the impression that the above, with added color schemes and all is way more complicated than how I got it working. I will describe it here for you and hopefully everyone can easily understand and reproduce that, just from reading it.

First of all, I have two Novation Launchpads NOVLPD01. They were first released in 2009 and appeared not to be 'class compliant' (which means they don’ t work under Linux; someone built a driver for it however, https://sourceforge.net/projects/drivernovationl , but that did not work for me, having the latest Ubuntu Studio version and I would probably have to go back to a very old Ubuntu release (I tried several releases, but I could not get it working); also only releases based on Debian are supported by that driver). I was confused by that, because the latest Novation (2019), the MKII, is class compliant, as stated on the website (https://novationmusic.com/launch/launchpad). Also the older S version, which was released next after the NOVLPD01, is class compliant; https://d2xhy469pqj8rc.cloudfront.net/sites/default/files/novation/downloads/4700/launchpad-s-prm.pdf

Anyway, not getting it to work under Ubuntu studio, was enough reason for me to switch to Windows 10 pro. Here you can download the Windows 10 driver for the NOVLPD01: https://customer.novationmusic.com/support/downloads?brand=Novation&product_by_type=481&download_type=all

Now, there are a couple of things important to get the Launchpad working with GO, including the Led’s.

  1. In GO a sound driver has to be selected an working fine.
  2. The Novation has to be selected, not only as Input MIDI device (standardly checked), but as Output MIDI device as well (standardly switched off). Of course they have to be connected and recognized by GO).

How to make the 2nd setting? Make sure the Novation(s) ar checked! (otherwise the Led' s won' t burn for sure; they have to receive a MIDI signal for that and so, seen from GO, they have to be set as Output device as well...)

Now go to the console overview of GO, which shows the organ and the stops. Then right click on one of the stops. Then hit a key on the Launchpad (the button you want to correspond with the stop on the screen).

Originally it says, at 'Event' 9x Note, but that should be changed to ' 9x Note On Toggle'

Now go to the Send tab. Then at 'Devices:', select the MIDI Out device name (with number) that matches the Launchpad you' re setting right now. Then make the settings like this: