Project KOW : Console design

The jOrgan software uses "dispositions" as configurations for how a virtual organ will look and sound. When these dispositions are very complex, the control scheme is also complex. Generally, the player will choose combinations of stops and apply them to "pistons" which are basically presets. These pistons are physical controls and are generally located below the manuals, though pistons can be displayed on the computer screen and selected with the mouse, or via a touch screen.

During the performance, the pistons allow rapid changes of stop combinations that could not be achieved by manually changing the stop tabs. My first "proof of concept" organ used a ELO touchscreen, which allowed me to tap the screen to make changes.

So, now to console design. A touchscreen allows access to many stop tabs and pistons, but lacks the tactile feel of real switches. One can glance at physical switches to check and change configurations, but this is much more difficult with touchscreens.

I did extensive research online to help me decide on a design for my console. I have narrowed this down to Schlicker and Holtkamp consoles, as they often used a very minimalist design (some call it ugly) The console that most approximates what I am planning is this Schlicker practice organ :

http://mysite.verizon.net/dalderdi/organ/

Reducing the number of controls allows all controls to be "real" and eliminates the need for a computer display. This will allow me to concentrate more on playing, and less time fiddling. There will be likely fewer than 30 physical control elements, which also makes the console project much more "doable". The thought of wiring even 100 different controls is daunting.

Project KOW : The portable organ project

For my current musical project I thought it would be fun to bring a virtual pipe organ to the recent North Carolina Maker Faire, but a traditional organ console was not very practical. I would need something more portable. Portability was necessary for my situation. But what if portability were a design goal rather than an inconvenience?

This requires a rethinking of the organ console, which has remained relatively unchanged for hundreds of years. Since I have only recently started piano lessons, I have no preconceptions of how an organ console should work.

The computer side is relatively easy if your goals are modest.

BUILDING AN ORGAN
The organ that I displayed at MakerFaire was rather minimal -- a touchscreen, a laptop and a 61 note MIDI keyboard. I ran the jOrgan software under Windows XP.

GOALS
My goals for the console design are :
AGO standard manual (keyboard) spacing - An organist can play it
Self-contained - No separate computer
Reduced size and weight - I can carry it
Appliance philosophy - The computer is there, but hidden
Don't reinvent the wheel - Use commercially available parts when practical
Flexibility - Be able to experiment with different interfaces without having to start the project over
Modularity - Be able to expand without having to start over

Next : Design