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

Raspbian with HiFiBerry - ALSA equalizer not working #23

Closed
3579km opened this issue Sep 24, 2017 · 16 comments
Closed

Raspbian with HiFiBerry - ALSA equalizer not working #23

3579km opened this issue Sep 24, 2017 · 16 comments

Comments

@3579km
Copy link

3579km commented Sep 24, 2017

I have Raspberry Pi 2 with installed Raspbian Lite from HiFiBerry download page. It has been modified to automatically detect and configure of the HiFiBerry DAC+ Pro board. I installed Raspotify and it works great: spotify connect and sound, and then i installed ALSA equalizer from this manual https://www.hifiberry.com/build/documentation/guide-adding-equalization-using-alsaeq/

But editing equalizer to manual setting not working, sound not changes.
I tested it, play file by command: aplay /path/to/file.wav
and i hear changes, edited in equalizer.

Maybe it's the problem with setting in Raspotify?

@markheloking
Copy link

Directly from that link you sent:

The equalization works only when the application uses the default output device from asound.conf. Applications that are configured to use the hardware device directly (you might see “hw:0” or similar in the command line options or in the configuration file) won’t use the equalization plugin.

Aka this plugin does not work for Raspotify since Raspotify uses the audio hardware directly instead of the default audio output device. I think that's actually part of librespot (which raspotify uses) and not raspotify itself.

@schlachtkreuzer6
Copy link

Is it possible to change that in anyway?
I found this, but I didn't try it.
http://www.gerrelt.nl/RaspberryPi/wordpress/equalizer/

@RealZac
Copy link

RealZac commented Jan 27, 2018

Is it possible to change that in anyway?
I found this, but I didn't try it.
http://www.gerrelt.nl/RaspberryPi/wordpress/equalizer/

I tried it, but it doesn't work. Raspotify still uses the audio hardware directly.

@RealZac
Copy link

RealZac commented Jul 22, 2018

Hi,
is there anything new about this? Or maybe an other way to control bass and treble?
Thanks.

@jlssmt
Copy link

jlssmt commented Sep 1, 2018

Hi,
I'm looking forward to a solution.
I'm not a hardware/ linux developer but I found in /etc/defaults/raspotify this information:

To choose a different output device (ie a USB audio dongle or HDMI audio out),
use --device with something like --device hw:0,1. Your mileage may vary.

Can this help us to get an equalizer for raspotify?

Thanks in advance!

@FredRanG
Copy link

Tried to use ALSA equalizer with a HifiBerry Amp2 and hitting the same issue. In /etc/default/raspotify setting OPTIONS="--device hw:0" bypasses the equalizer as expected. Only alternative I have been able to get sound with in raspotify is OPTIONS="--device plug:plugequal" based on the asound.conf values suggested in https://www.hifiberry.com/build/documentation/guide-adding-equalization-using-alsaeq/ but even with that alternative device, alsamixer -D equal doesn't change the sound in raspotify.

@FredRanG
Copy link

ALSA Equalizer working now with sudo -u raspotify alsamixer -D equal and OPTIONS="--device equal" in /etc/default/raspotify.

@RealZac
Copy link

RealZac commented Nov 5, 2018

ALSA Equalizer working now with sudo -u raspotify alsamixer -D equal and OPTIONS="--device equal" in /etc/default/raspotify.

Perfect! Thank you.

@schlachtkreuzer6
Copy link

Great thx

@ghost
Copy link

ghost commented Nov 25, 2018

ALSA Equalizer working now with sudo -u raspotify alsamixer -D equal and OPTIONS="--device equal" in /etc/default/raspotify.

After adding parameter OPTIONS="--device equal" no sound. Any ideas why?

@agonzalezv
Copy link

agonzalezv commented Mar 27, 2019

After adding parameter OPTIONS="--device equal" no sound. Any ideas why?

  • rm ~/.asoundrc (good idea to make a copy before)

  • sudo touch /etc/asound.conf (or check if the file exists and make a copy if it does)

  • Then follow these instructions: https://www.hifiberry.com/build/documentation/guide-adding-equalization-using-alsaeq/ , make sure you add the contents of asound.conf as described.

  • sudo vi /etc/default/raspotify, add OPTIONS="--device equal"

  • alsactl kill rescan

  • sudo systemctl daemon-reload

  • sudo systemctl restart raspotify
    (or sudo reboot now to restart the system)

  • To change EQ settings: sudo -u raspotify alsamixer -D equal

@NickMous
Copy link

Can't do it, it says that file or map doesn't exist

@MarshMelone
Copy link

to whom it may concern:

I use 2 raspberry 2. For the first the "sudo -u raspotify alsamixer -D equal" works out of the box to set the equalizer with raspotify.

For the second it didn't work. I don't know why.
I had to edit "sudo nano /lib/systemd/system/raspotify.service".

I changed the line:
"ExecStart=/usr/bin/librespot --name ${DEVICE_NAME} $BACKEND_ARGS --bitrate ${BITRATE} $CACHE_ARGS $VOLUME_ARGS $OPTIONS --device hw:0,0"

to:
"ExecStart=/usr/bin/librespot --name ${DEVICE_NAME} $BACKEND_ARGS --bitrate ${BITRATE} $CACHE_ARGS $VOLUME_ARGS $OPTIONS --device equal"

I changed only the name of the device to the previously set device "equal" (see the link which was told in the comments above).
Now the mixer works with the second raspi too via: "sudo -u raspotify alsamixer -D equal"

I hope i can lower the stress level of someone with this info :-)

@NickMous
Copy link

NickMous commented Aug 5, 2020

It doesn't work for me, raspotify can't access the equalizer, because the ¨operation is not permitted¨.

@github-actions
Copy link

This issue is over a year old and has been marked as stale. It will closed in 7 days if there is no activity.

@github-actions
Copy link

This issue has been closed due to lack of activity.

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

9 participants