This device is a MIDI signal manipulator (eg. simulating couplers) - it can't generate any sound itself. For simulating classical organs its an overkill, because this kind of MIDI mapping are already done by GO/HW without any need for extra hardware.
For a VPO, you just start with some MIDI keyboards connect to the PC. You can start with the free GO or the limited HW free edition on the PC and speakers/header connected. Explore VPOs and learn about the topic, so that you know, what you really want.
Although, as the above poster says, this device looks like way overkill, and is probably quite expensive, and yes, many if not all the functions it performs can be done within the software of Hauptwerk or Grand Orgue, you may well need a "MIDI Merger" unit if you plan to use a stack of ordinary MIDI keyboards as your organ manuals.
Why is this? Because the typical MIDI keyboard on the market from Yamaha, Casio, Korg, Roland, and so many others, will have only a single "MIDI OUT" jack on the rear panel. How do you go about combining the signals from all these keyboards (assuming that you want to use about 3 of them, plus probably a MIDI pedalboard unit) into a single MIDI stream that can be sent directly into a laptop or desktop computer? You need a "MIDI Merger" -- usually a small "black box" device with several MIDI input jacks and a single "merged" output jack which will send along a signal that is a composite of all the incoming MIDI streams, with each one assigned to a unique channel number.
This is the type of signal input that the Hauptwerk or GO software is looking for and will make it possible for you to assign each keyboard to a unique division of the VPO.
There are other ways to do this, notably the USB method. Since many of the newer table-top keyboards today have a USB port instead of a traditional MIDI jack, you may actually need a USB merger to do this rather than a MIDI Merger. So see what kind of keyboards you get first, then get a suitable merging device to combine them all into a single stream for the computer to use.
Some computers have quite a few USB ports already, and if there are enough of them you might be able to simply attach each keyboard to a separate USB port and thus not need an external merging device. There are also inexpensive USB Extenders that take a single USB port on a computer and turn it into 3 or 4 or more ports. That may well be the least expensive option, if you can get some good USB keyboard units.
BTW, best of luck! Please post pics and report on your project!
John
---------- *** Please post your questions about technical service or repair matters ON THE FORUM. Do not send your questions to me or another member by private message. Information shared is for the benefit of the entire organ community, but other folks will not be helped by information we exchange in private messages!
From a very cursory overview of the linked product it looks like it IS a rather elaborate MIDI merger. IMO it isn't so much 'overkill' as it seems to be an answer to a question no one has asked since, as post #2 correctly notes, all the functions of this device and much more will be incorporated into any VPO software worth the name. Even the free ones. M-Audio (I think) makes a line of 'Keystation' MIDI controllers that have 61 semi-weighted keys and USB output that to this writer appear to hands down be the best option for inexpensive control of a VPO manual division. Even new they are under (well under) $200. I don't know how much the linked device costs but I'm guessing its not cheap. It should be though. And ... I may be crossing a line but ... IMO it ain't an organ unless it has pedals and at least two keyboards! Sorry, that would be my absolute bottom line for even a beginner practice instrument. Locating a pedalboard can be a challenge but it is necessary to do.
I have a couple of things to add here. It is interesting for me to avoid usage of any touchscreens during the playing. I would rather use switchable combinations. As the developer declared, the unit may also be used with external sequencers connected to each separate MIDI output. This is a second operation mode. I found it pretty useful. Combinations are unique for every used sample set and switching them up or down is quite a good way to control stops.
As the developer has said, the MIDI merger is not just a 4-to-1 channel merging device, which are easily available. The unit may update the speaking set of note, if a coupler is engaged. I think this function is implemented exactly for the second way of the usage (without single VPO software, but with sequencers).
A note for GO & USB: On LInux, GO will match the USB MIDI devices by the USB port they are connected to - so they have a stable ID and multiple USB MIDI devices are not an issue, if you connect them always in the same way. Using multiple USB MIDI interfaces instead of a MIDI merge with only one USB MIDI interface also work.
On Windows, the OS device number is used - using just one (USB) MIDI interface [+ MIDI merger] is the safest solution - multiple MIDI interfaces can lead to changing device IDs.
I have a couple of things to add here. It is interesting for me to avoid usage of any touchscreens during the playing. I would rather use switchable combinations. As the developer declared, the unit may also be used with external sequencers connected to each separate MIDI output. This is a second operation mode. I found it pretty useful. Combinations are unique for every used sample set and switching them up or down is quite a good way to control stops.
As the developer has said, the MIDI merger is not just a 4-to-1 channel merging device, which are easily available. The unit may update the speaking set of note, if a coupler is engaged. I think this function is implemented exactly for the second way of the usage (without single VPO software, but with sequencers).
Am I write?
Than you.
I am having trouble following your ideas. One reason is because they are unique. VPO's are no longer that new. There are already 'conventions' built up as to best practices for their use. I don't really like touchscreens either but you need to have a way to access stops individually. Some organs use pistons to control everything and that's fine. Commercial MIDI keyboards won't have enough pistons for that if they even have pistons at all. Why don't you give us the names of the keyboards you want to use. We want you to have success doing this and one way for a beginner to achieve success is to copy a known success. Good luck.
I am having trouble following your ideas. One reason is that they are unique. VPO's are no longer that new. There are already 'conventions' built up as to best practices for their use. I don't really like touchscreens either but you need to have a way to access stops individually. Some organs use pistons to control everything and that's fine. Commercial MIDI keyboards won't have enough pistons for that if they even have pistons at all. Why don't you give us the names of the keyboards you want to use. We want you to have success doing this and one way for a beginner to achieve success is to copy a known success. Good luck.
The "uniqueness" of my ideas is not so strong. They do not follow the mainstream application experience, but quite as common as possible.
My very simplified and unprofessional but preferred way of playing the VPO is:
1) Learn the organ's disposition to get the information about voices, controls, etc. Play each register to get the timbral and loudness info. Here I need only keyboards, pedal board, and PC mouse to enable each stop individually. No touchscreen is required.
2) Create a table of divisional and general stops combinations I will apply during my playing.
3) Analyze the piece of music, assign the sequence of combinations/pistons, play it, and adjust, if required. Program the sequence finally and store as "don't-touch".
4) Play the final revision using the "Sequencer".
In case if I would like to play the piece using the other sample set, I shall have to update (and keep it) the table of combinations for each and every VPO.
I have to put it again, I don't need a touchscreen during the performance at all. Instead, the console should have either good block of organ keyboards (in the best case special, with the "Drückpunkt" simulation). Normally, such a block conforms to AGO/BDO standards and has the proposed pistons and generals.
I have no AGO/BDO-specified MIDI keyboards, instead, I possess just very basic digital piano, MIDI keyboards and (next step) pedal board. I suggest it is a very common situation for all who enters the VPO-fun club.
It is required for me to connect external voicebanks (MIDI sequencers) in order to get non-organ-voice stops to the ensemble. This is rather unique, I agree. I need to be able to control them the same way as the coupling of organ divisions/octaves.
In most cases using the general approach (and hardware) will obviously lead me to failure. My goal is to get real virtuality of the organ functionality across my hardware.
Hmmm and hmmmm. I actually understood all of that. Seems to me you have a unique situation nonetheless :-) what you have described is not so much an organ as a synthesizer. Some amazing things have been done with a single keyboard and one or more sound modules and a sequencer. (they are not the same). Think of Wendy (nee Walter) Carlos' early work. You could do your 'analysis' and initial play throughs of the compositions you choose for projects without having any kind of organ functionality. You don't need couplers, stop switches, pedalboards and you certainly don't need touch screens.
If, however, you want to work with the AGO/BDO endorsed ergonomics that performing organists expect, then the devices that you are considering cannot fulfill any of those objectives. So why try? You could save yourself tons of money, time and headache by using the better of your present keyboards as a MIDI controller or buying a good MIDI controller and then organize your sound sources which may include a computer hosting various organ dispositions. Then you can work with any disposition you want, or more than one at at time, and add non-organ sounds and build up compositions layer by layer. What you can't do is play them into the sequencer in an authentic organ fashion because you will not, cannot, have the individual stop control, coupling, and multi-divisional (through several manuals) functionality.
In short, with just the equipment you already have you could create very advanced music.
Did you mean MIDI expander instead of MIDI sequencer?
GO has MIDI out functions - it can send MIDI signal for rank/division level. Adding a non-sounding stop (or using a unused stop), you can use it to drive a MIDI sound module instead of classical pipe rank. Some people even create (and share) sample sets containing organ + other instruments as stop.
Did you mean MIDI expander instead of MIDI sequencer?
GO has MIDI out functions - it can send MIDI signal for rank/division level. Adding a non-sounding stop (or using a unused stop), you can use it to drive a MIDI sound module instead of classical pipe rank. Some people even create (and share) sample sets containing organ + other instruments as stop.
Many thanks for the clarification. I have a question: does GO/HW software sends also MIDI information out when a graphical interface component (on the touchscreen) is toggled? As I know GO should have such functionality.
I have meant in the post above any MIDI sound generation device: either MIDI expander, or MIDI sequencer.
I would like to get more deep knowledge about the composite sample sets creation? Can you recommend the good source to read?
I have been playing organ since I was 10 and my teacher was a theatre and radio Organist during her career. After 40 years of playing piano and keyboards in wedding bands I am getting back to my roots. I have stacked my piano and two synths and added a pedalboard as well as a Behringer midi controller. What is the best way to add rail pistons via midi to the front of my keyboards. BTW, I am using Hauptwerk and the Paramount 310 for a theatre organ and St. Ann's for classical right now.
Anyone know how the Launchpads were mounted to the A-Frame stand on the wings off to the sides. This is very practical and exactly how I would like to mount my Launchpads, but I have been unsuccessful in finding mounting brackets.
I have an On Stage K7903 Stand. I am thinking of buying extra support mounts and either cutting a support bar or using PVC pipes. Then I'll attach the mounting arms to it.
I am also wondering if anyone has a training resource...youtube, webpage, pdf...on how to set colors on the Launchpad in Hauptwerk.
I know how to pick a color when using midi learn to assign stops, but how do you choose custom colors? I have not yet figured out how to have an “off” stop display red. I want to color code my stops the way they are on the actual organ.
AFAIK, Hauptwerk doesn't support custom colors, only the preset colors of red, orange, amber, yellow, and green of the gen I Launchpads. You can choose only one of those colors per function, toggling between bright/dim or bright/off. The latest Launchpads can display just about any color in the spectrum, but that's not supported in the latest version of Hauptwerk.
Looks like you’re enjoying the discussion, but you haven’t signed up for an account yet.
Tired of scrolling through the same posts? When you create an account you’ll always come back to where you left off. With an account you can also post messages, be notified of new replies, join groups, send private messages to other members, and use likes to thank others. We can all work together to make this community great. ♥️
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Tweet
Comment