Disclaimer
I am aware that I am running a beta version of macOS, I just thought I'd report this so that it can be fixed ideally soon, but for the upcoming release at all. Especially since nowadays Apple is releasing public betas and those are available like 3 months before the public release and it would be too bad if eqMac would not work till Sept/Oct.
Describe the bug
When installing eqMac on macOS 11.0 Big Sur Beta 1 and 2, the program does work sometimes (weirdly enough) but then other times it does not start at all. The console prints the following when trying to launch via terminal:
$/Applications/eqMac.app/Contents/MacOS/eqMac
2020-07-08 10:17:41.901 eqMac[8116:132180] Sentry Started -- Version: 4.5.0
eqMac (Source/Application.swift:184) Setting up Audio Engine
Error: 2003332927 -> /Users/romanskisils/Programming/Bitgapp/eqmac/native/app/Source/Audio/Sources/System/Driver.swift:123
ERROR: SentryCrashMachineContext.c (232): void sentrycrashmc_resumeEnvironment(): thread_resume (0000d807): (os/kern) object terminated
[1] 8116 segmentation fault /Applications/eqMac.app/Contents/MacOS/eqMac
Manually installing the driver anew, prints:
$ sudo /Applications/eqMac.app/Contents/Resources/install_driver.sh
Device not ready yet, waiting...
Device not ready yet, waiting...
Device not ready yet, waiting...
Device not ready yet, waiting...
ERROR: Device did not become active
Another weird thing about this all: the driver is actually running and is visible in the Activity Monitor as a Core Audio Driver process.
Steps to Reproduce
Steps to reproduce the behaviour (feel free to change the placeholder as you need):
Expected behaviour
eqMac should just start every time and work?
Setup information:
If it works sometimes then has nothing to do with Big Sur and is probably related to other issues
Interesting point, I am going to keep my eyes open for any new release on here and will try everything to see once it goes back to work. And I will also try to provide more feedback if I find any more details.
I've also had this issue, albeit consistently, on both betas thus far.
Also have had this issue, consistently on Big Sur 11.0 Beta 4 (20A5343i).
Also have had this issue, consistently on Big Sur 11.0 Beta 4 (20A5343i).
Same here, the terminal output reads:
020-08-12` 11:34:38.555 eqMac[9390:466999] Sentry Started -- Version: 4.5.0
eqMac (Source/Application.swift:184) Setting up Audio Engine
Error: 2003332927 -> /Users/romanskisils/Programming/Bitgapp/eqmac/native/app/Source/Audio/Sources/System/Driver.swift:123
ERROR: SentryCrashCPU.c (58): _Bool sentrycrashcpu_i_fillState(const thread_t, const thread_state_t, const thread_state_flavor_t, const mach_msg_type_number_t): thread_get_state: (ipc/send) invalid destination port
ERROR: SentryCrashCPU.c (58): _Bool sentrycrashcpu_i_fillState(const thread_t, const thread_state_t, const thread_state_flavor_t, const mach_msg_type_number_t): thread_get_state: (ipc/send) invalid destination port
ERROR: SentryCrashMachineContext.c (232): void sentrycrashmc_resumeEnvironment(): thread_resume (0001860b): (ipc/send) invalid destination port
Segmentation fault: 11
logout
same here...
I have the same issue. Would be great to know if there is anything we can do about it. I really enjoyed the app in the past and would like to use it with Big Sur as well.
Just update Big Sur, audio sounded garbled when using eqMac. stopping (quitting) eqmac, restores the audio back to normal but without the eqmac equalizer setting.
Please help to rectify.
I recently installed Big Sur 11.0.1 and I experienced the same issue where eqMac wouldn't open.
I redownloaded and reinstalled from the official website and that fixed it.
Killing the coreaudiod process seems to always work for me when I have eqMac issues (Big Sur). The process respawns automatically.
Most helpful comment
same here...