Fri Apr 22, 2022 4:00 am
Thanks, Rod.
Yes -- if you're still getting no sound after:
- Reverting all Hauptwerk settings to defaults, then:
- Relaunching the same configuration (desktop shortcut) within which you had reverted the settings to defaults, then:
- Selecting the Audiofire ASIO driver as Hauptwerk's audio device, then:
- Loading St. Anne's, then:
- Turning on some virtual stops by clicking on them, then:
- Clicking on some virtual keys
... then the problem must either be within the Audiofire ASIO driver, or the audio interface hardware, or the audio cabling, or the amplifiers/speakers [which are connected to output channels 1 and 2 on the Audiofire].
My first suspicion would be the Audiofire's ASIO driver, given that you're trying to use Windows 10, and Echo never released a Windows 10 driver for it.
To try to determine whether the problem is within the hardware or the ASIO driver you could try:
- Exit Hauptwerk.
- Right-click on the speaker icon near the right-hand side of the Windows Task Bar, and select "Open Sound settings".
- Select the Audiofire as the output device.
- Open and play a .wav file (e.g. in Windows Media Player) by double-clicking on it, or use your Web browser to try playing a video on Youtube, or something else that would cause Windows to play sound.
If you can hear the sound through your Audiofire then you know that the hardware must be (at least partly) working, so the problem will almost certainly be the Audiofire's ASIO driver. (Windows doesn't uses a different type of driver for its own sound output, whereas ASIO drivers are used for professional audio applications.)
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.