Hello Federico,

Although not themselves designated as MIDI-accessible, where indicated they would have Stop.StopCodeFromWhichToCopyState set, and the stop they would copy from is MIDI-accessible, so they would be controlled *indirectly* from MIDI (via the copied stop states).

Thanks, Federico.

I'm afraid I don't really have time to help in detail at the moment, so I'll have to leave you to experiment, but hopefully that topic will give you some ideas for approaches that you could use.

Thanks, Mark and Iain. Although any of those things could be implemented within the 'full' ODF format, the CODM wasn't really designed to handle them (although it would just-about be technically possible, albeit fiddly, to implement a basic Pedal divide as covered in the topic linked previously). We ...

Thanks, Federico. I don't have the Blackburn sample set, but is my understanding correct that (within a CODM ODF) you're hoping to implement a coupler/switch that behaves as follows: - When the switch is *not* turned on, all of the keys on the pedalboard play the Pedal division's ranks and couplers ...

Hello Federico, [I'll move this topic to the " Custom Organ Design Module (CODM) " section of the forum once you've had a chance to read this reply.] Do you mean that (using the Great and Swell as examples), if you play a chord on the Great you would like to have a single coupler (named something ...

Hello abaymajr, Pleaser try following these steps I mentioned earlier to gjschipper: Please try: - Make sure that Windows drive indexing and Superfetch/Sysmain are disabled. - Reboot the PC and log in. - Temporarily disconnect it completely from the Internet/network. - If it has a virus scanner ...

When a supplier says our new product will help to solve your problem, I am very scepetical. In this case it has turned out to be true. HW9 offers to turn off facilities that you don't use, so I turned off the mixer and all was OK. Thanks Martin. Excellent. Thanks, David. However, it does look like ...

Thanks, David. Excellent. Hope you enjoy v9.

Hello again, David. Just a quick follow-up to say that Francois has emailed a direct download link to you, and that the our web developer is aware of the problems with the download form, so hopefully it will be resolved soon. In the meantime, if anybody else finds that the download form gives an ...

Thanks, David, and sorry to hear about the error with the download form. Please don't give up playing the organ!

I've just tried the form, and I too get that error message at the moment. I'll enquire, and we'll get back to you as soon as possible.

One change in HW9 is to make not binding threads to cores the default, where binding was the default in previous versions. You might want to tick the option to bind threads, if it's currently off, and see if that helps your load times without causing audio glitches. Hello Mark, Although the default ...

Hello Bruce, To add to to Mark's reply, this is what the Hauptwerk prerequisites document/chapter says about Launchpads: Hauptwerk also has native support for Novation Launchpads (specifically, the “Launchpad X”, ”Launchpad Mark 2” model, and the original “Launchpad” mark 1 model), which are good, po ...

Hello David, Thanks very much for buying the v9 upgrade. You can download the software itself via the 'Download' link at the very top of the forum. (It mentions a trial, but it's the full software.) Enter your name and email address and it will email a download link to you. The Hauptwerk v9.0.0.258 ...

Thanks, gjschipper. There's no difference in the loading mechanism, or threading, between v8 and v9. Hauptwerk (either version) simply leaves the OS to decide on which CPU cores the loading threads are placed. Presumably currently on those PCs Windows is sometimes putting some or all of the loading ...

Hello Charles,

Yes -- we're aware that a VST3 port of the Hauptwerk VST Link would be highly desirable. (As you found, there is still an option in Cubase to enable VST2 support.)