Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ASIO4ALL driver not working [WIN10] #54

Open
GuillemGongora opened this issue Sep 22, 2020 · 5 comments
Open

ASIO4ALL driver not working [WIN10] #54

GuillemGongora opened this issue Sep 22, 2020 · 5 comments
Labels
bug Something isn't working question Further information is requested

Comments

@GuillemGongora
Copy link

When selecting ASIO4ALL driver on the Audio Setup, Mercury crashes when evaluating any code. Directsound audio driver seems to work well.

@tmhglnd
Copy link
Owner

tmhglnd commented Sep 22, 2020

Hmm, this is something that is really hard for me to debug. Also not even sure if this is something in my code or that it is part of a Max bug? I think I will have to work on better crash-logs so I can see what happens under the hood.

@tmhglnd tmhglnd added bug Something isn't working question Further information is requested labels Sep 22, 2020
@tmhglnd
Copy link
Owner

tmhglnd commented Oct 27, 2020

Is this still an issue?

@GuillemGongora
Copy link
Author

Seems more stable, as in I can now play audio through it like before, but occasionally the crash happens when running code for the first time. Absolutely no idea what causes the crash...
Also, this error message when changing between certain audio drivers: adstatus: doesn't understand "append"

@tmhglnd
Copy link
Owner

tmhglnd commented Oct 27, 2020

Alright, I'll just leave it open for now in case someone else runs into the same issue. I honestly have no idea what to do with it though. The adstatus error is not really a problem except for that I need to find a way that it doesnt print it, haha. It is just a setting issue that sends an append message to adstatus, but that's minor.

@GuillemGongora
Copy link
Author

The crash might not be related to the driver, but to other cpu stressing processes (even though running i7-9750H here...). We'll see if it goes away on its own with another update hahah

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants