Wed Apr 14, 2021 4:06 am
Hello Rod,
[I've split your posts off from the original topic to this new one.]
To add to Danny's reply, I'd suggest:
- Shut the computer down.
- Completely switch the computer, and all associated devices (USB devices, audio/MIDI devices, MIDI console, any other MIDI hardware, USB hubs, etc.), off at the mains (wall socket) for at least 15 seconds, especially so as to ensure that all USB devices get fully powered off (including the Launchpad).
- Make sure that in principle there is ample power supply for all of your USB devices, since insufficient USB bus power often causes USB devices to behave erratically. If connecting devices via a USB hub then make sure it's a good-quality (reputable brand) *powered* (not 'bus-powered') model. Better still, if your computer has sufficient USB ports, keep the Launchpad connected directly to a USB port on the computer.
- Switch everything back on, reboot the computer, and log in. The Launchpad's button lights should perform their 'start-up light-show' as it boots. If not, the driver and Launchpad aren't working properly together for some reason, so stop and resolve that.
- Wait at least 30 seconds so as to ensure that Windows has had time to finish loading all drivers, etc. before launching Hauptwerk.
- Make sure that all Windows power-saving preferences are disabled, and especially the option for putting USB devices to sleep. See the 7th bullet point in the 'Performance tuning: Other operating system and computer optimizations and diagnostics' section in the Hauptwerk user guide (page 274 in the current v6.0.2 version) for how to do that. If that Windows USB-sleep option isn't disabled then the PC may well lose communication with USB-MIDI devices, such as a Launchpad -- a very common problem.
- Launch Hauptwerk.
- Go to the MIDI ports screen.
- On the 'MIDI IN ports' screen tab, make sure that your Launchpad is (still) listed as a column *without* an 'off-line' suffix (an 'off-line' suffix would indicate that the computer isn't seeing it), and make sure that column is (still) ticked in the relevant 'Console MIDI IN' row.
- Do likewise on the 'MIDI OUT ports' screen tab, for a 'Console MIDI OUT' row. (The Launchpad must be visible to the operating system [not 'off-line'] and be ticked for *both* console input and output.)
- Load St. Anne's, and try auto-detecting a stop to a Launchpad button. You should see the button colour options during auto-detection.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.