The title says it all really. I have tried the usual suggestions ...
Checked the MS Visual C++ 2010 x86 libs (2019 already installed as 2015-2022 set), re-registered the appropriate .dll files, deleted AWE_Server.ini and tried launching from File Explorer and the command line (no errors returned).
AWE_Designer displays the splash screen and spawns AWE_Server (monitored in Task Manager)
AWE_Server dies after 5 seconds or so (when spawned or launched independently).
AWE_Designer pops up the 'Error connecting etc.'
On a few occasions a black splash screen larger than the first appeared with no content and no window decoration - could this be an NVIDIA graphics refresh problem? Unable to reproduce after reinstalling software.
System Info:
AWE Designer 8.D.1.1 STMicro edition
Dell 3070 i5-9500 8GB
Windows 11 Pro 22H2 and User has full admin rights
On board Intel UHD 630 & NVIDIA GT 1030
TI IEEE1394 Firewire controller with M-Audio 610 audio I/F
Focusrite VRM Box (Headphone I/F)
Generic USB Class 2 compliant audio I/F with SPDIF In/Out & 4 analogue in, 8 analogue out channels
Cubase LE Elements with eLicenser dongle
Pro Tools 8.02 & iLok License Manager and dongle
ASIO4ALL
Analog Devices Sigma Studio
Although this seems to look like a lot of audio stuff, they normally co-exist fine and removing the system down to the minimum 2 channels had no effect.
Many Thanks
9:36pm
Hello SMJ,
Let me email you on the side about this.
Thanks,
Kevin
3:56am
I also met the same error, could you please help on that? Thank you.
Standard 8.D.2.2
Windows 10 _ X64
ASIO4ALL
9:00am
Hi Yang,
I'll emailed you to resolve this.
Thanks,
Kevin
7:35pm
I am encountering this same issue - Error connecting to the AWE Server - Error in => awe_designer.m at line 128
1:17pm
Hi AutoBuckSF,
By any chance do you have a HEAD acoustics driver installed on your machine? We have found that when AWE Server scans for ASIO drivers, labCORE throws an error which in turn results in error 128. It can be resolved by updating the HEAD acoustics driver.
3:40pm
Hi Kyle,
Thanks for the reply. We don't have a HEAD acoustics driver installed, but this insight led us to investigate the ASIO devices detected by the AWE server. We have two RME devices connected to the computer, and evidently AWE had an issue with that while scanning for ASIO drivers. We were able to work around this issue by unplugging one of the interfaces to start up Audio Weaver, and plugging it back in once the application opened up.