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

Constant crashing on MacOS when switching audio output device #644

Closed
1 task done
jdenglish opened this issue Feb 11, 2022 · 3 comments
Closed
1 task done

Constant crashing on MacOS when switching audio output device #644

jdenglish opened this issue Feb 11, 2022 · 3 comments

Comments

@jdenglish
Copy link

Disclaimer:
Please go through existing issues to avoid creating duplicates. If you found a similar issue please post a comment there. If you are uncertain your issue is related to others then create the issue. Obvious ignorance of this rule might get you blocked from posting new issues. Please tick the box below to show that you have followed the guideline.

  • I have checked for a similar issue and sure it hasn't been reported before.

Describe the bug
If I try to switch devices on the eqmac client or the Sound menu of the Mac eqmac hangs to the beachball and has to be 'force quit' from Activity Monitor. This happened occasionally until the recent updates when it changed to constant, eqmac is unusable on my Mac.

Steps to Reproduce
Steps to reproduce the behaviour (feel free to change the placeholder as you need):

  1. Go to eqmac
  2. Click on device selection list
  3. Scroll down to select another device
  4. no switch eqmac 'beachballs'

Expected behaviour
It should switch output devices

Setup information:

  • Audio device used for playback: DELL U3421WE monitor speakers/Jabra Speak 510
  • Audio transmission interface: monitor is USB-C, Speak 510 is USB
  • macOS Version: 21.2
  • eqMac Version 1.4.6
  • eqMac UI Version 3.2.4
@sway
Copy link

sway commented Feb 14, 2022

I reckon this is a duplicate of #636 that was reported some time ago

EDIT: Correct issue number, thanks @nitsujri

@nitsujri
Copy link

@sway probably mean: #636?

@jdenglish
Copy link
Author

Closing as covered in earlier report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants