Topic: BSOD When Changing WASAPI to ASIO:- Focusrite Scarlett Solo

Viewing 6 replies - 1 through 6 (of 6 total)

Replied May 20, 2020 at 13:33 #2581528

Scott
Moderator

Can you try another ASIO driver like ASIO4ALL and see if its a Focusrite driver or something else?

Scott Sibley - Toontrack
Technical Advisor

Replied May 20, 2020 at 13:49 #2581537

Neil Cummins
Participant

Hi Scott,

ASIO4ALL causes the same issue,as mentioned however,EZ Bass plugin works very nicely so far in Cakewalk using ASIO as the Focusrite Audio Driver.

Are there any crash logs I can provide?

Regards,

Neil

EZbass version: 1.0.2
Operating system: Windows 10

Replied May 20, 2020 at 14:33 #2581563

Scott
Moderator

Neil Cummins wrote:

Hi Scott,

ASIO4ALL causes the same issue,as mentioned however,EZ Bass plugin works very nicely so far in Cakewalk using ASIO as the Focusrite Audio Driver.

Are there any crash logs I can provide?

Regards,

Neil

EZbass version: 1.0.2
Operating system: Windows 10

If there were any generated they might point to the issue. When it crashes there should be an error log popup and a location to the crash file.

Scott Sibley - Toontrack
Technical Advisor

Replied May 20, 2020 at 14:56 #2581581

Neil Cummins
Participant

Hi Scott,

The crash is a Windows 10 crash,not the application itself,so there is no pre-warning of a stored crash log.If anything EZ Bass related is stored at the point of the crash,I’d need to know where in the Windows directory structure I could locate this.

Just out of interest,when freshly installed,what should be the default audio driver if I go into the Settings,Audio/MIDI setup? In my case,this was WASAPI with the output ports showing blank.At this point when I tried to select ASIO and the Focusrite L/R channels,the first crash happened.

As things stand,I have some stability with the Standalone set to WASAPI as the driver and the Focusrite L/R selected,but this isn’t how my three other EZ line products sit when used in Standalone,they all accept ASIO as selectable with no problems.

Maybe the audio engine design in EZ Bass has been refreshed,causing this problem.

Only a minor irritation in what otherwise seems to be a game-changing piece of sound engineering,and I’m sure all the initial bugs being reported will be ironed out one by one.

Cheers,

Neil

EZbass version: 1.0.2
Operating system: Windows 10

Replied May 20, 2020 at 15:38 #2581619

Scott
Moderator

For Windows 10 there may be an error log here:

– Type Event Viewer in the Windows 10 Cortana search box.
– Here is the main interface of Event Viewer.
– Then choose System under Windows Logs.
– Find and click Error on the event list. …
– Click on Create a Custom View on the right window.

I’m not sure what default drivers would be. I believe they are system specific depending on what are default in your system. I believe mine were Windows drivers that I changed to my RME ASIO drivers. I run a Windows 7 system however. Did you check that you are up to date with your Focusrite Drivers?

Scott Sibley - Toontrack
Technical Advisor

Replied May 20, 2020 at 22:14 #2581981

Neil Cummins
Participant

BEST ANSWER
Hi Scott,

Result! Re-installed the latest Focusrite driver and firmware state,I can now set the correct settings to support ASIO and the cracking and popping on playback(also reported by other users)appears for now to have disappeared.

No Blue Screen Of Death either when changing the settings.

So far,so good in my free DAW and low-spec laptop.

Regards,

Neil

EZbass version: 1.0.2
Operating system: Windows 10

1
Thanked by: Scott
Author

Replies

Viewing 6 replies - 1 through 6 (of 6 total)

BSOD When Changing WASAPI to ASIO:- Focusrite Scarlett Solo

EZbass Help

Viewing 6 replies - 1 through 6 (of 6 total)

BEST ANSWER