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

Issues with J416 support #41

Open
cisoun opened this issue May 11, 2024 · 4 comments
Open

Issues with J416 support #41

cisoun opened this issue May 11, 2024 · 4 comments

Comments

@cisoun
Copy link

cisoun commented May 11, 2024

Hello,

I'm running a Macbook M2 Pro from 2023 with J416 speakers, on GNOME.
I've noticed some issues with this hardware:

  • The frequency response is "flat". I believe the convolver does not work properly, hence the second point:
  • Toggling on "effect_output.j416-convolver" in Easy effect just mute the audio. Same when I switch to "Pro audio" in pavucontrol. (Might be related to the last point.)
  • Switching between profiles just create new "MacBook Pro J416 Speakers" in my output devices list for some reason.
  • Changing the volume with the mouse in the shell makes the sound quieter and makes it sometimes "jump" shortly to higher volume. Using the keyboard to change it restores the volume to the right value. (GNOME issue?)
  • speakersafetyd does not seem to support J416 speakers yet. Here's the output:
INFO [speakersafetyd] Config file: "/usr/local/share/speakersafetyd/apple/j416.conf"
INFO [speakersafetyd] Device: hw:AppleJ416
thread 'main' panicked at src/main.rs:143:27:
Failed to read config file: "couldn't read /usr/local/share/speakersafetyd/apple/j416.conf: No such file or directory (os error 2)"
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I guess the J416 support isn't ready yet. Or did I miss something?
Let me know how can I help otherwise.

Thanks a lot for your work!

EDIT: I've found /usr/share/speakersafetyd/appl/j416.conf but for an unknown reason, speakersafetyd looks for the profile from /usr/local, I'll investigate why...

@chadmed
Copy link
Collaborator

chadmed commented May 11, 2024

Some initial points:

  1. Do not use the Pro Audio profile on the hardware device.
  2. Do not switch profiles at all. in fact. You're not even supposed to be able to see the hardware device
  3. libgnome-volume-control is known to be broken and exposes the hardware device even though we don't want it to
  4. Starting speakersafetyd manually requires certain switches to be passed to it. See its systemd unit file for an example.

What distro are you using? Please post the output of asahi-diagnose.

@cisoun
Copy link
Author

cisoun commented May 12, 2024

Hi,

Thanks for the clarification.

I'm currently using Fedora Linux Asahi Remix 40 (Forty). Here's the output of ̀asahi-diagnose:

cyriaque@macbook-fedora:~$ asahi-diagnose
grep: /home/cyriaque/.local/state/wireplumber/restore-stream: No such file or directory
Collecting system diagnostic information...

Saved diagnostic information to /home/cyriaque/asahi-diagnose-20240512-161604.txt

Here's the diagnosis as well:
asahi-diagnose-20240512-161604.txt

Thanks!

@chadmed
Copy link
Collaborator

chadmed commented May 18, 2024

Speakersafetyd is launching at boot, so you shouldn't try to start it manually. Again, please do not try to change the device's profile. You need to keep it at default. Can you try to delete ~/.local/state/wireplumber/, reboot your machine, then just select MacBook Pro J416 Speakers in GNOME's volume mixer? This should at least get us into a known-good state.

@cisoun
Copy link
Author

cisoun commented May 18, 2024

Done. For now, I'll just use the headphones instead since the J416 is rather unstable on GNOME and the convolver doesn't work. Let me know if you need further tests/feedbacks.

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

No branches or pull requests

2 participants