0

HiFiBerry DAC+ Pro hardware volume problem

Jason

January 30, 2016 15:06

None

Follow

Volumio 1.5.5 cannot use the hardware volume control with Raspberry Pi2 + HiFiBerry DAC+ Pro

I googled so many website, tried so many way to enable the hardware volume control, but fail.

Anyone using the DAC + PRO?

 

 

• Facebook
• Twitter
• LinkedIn

10 comments

• 0
  
  Jason January 30, 2016 15:07

  
  The mpd.conf output

  type "alsa"
  name "Output"
  device "hw:0,0"
  mixer_control "Playback Digital"
  mixer_device "hw:0"
  mixer_index "0"
  dop "no"

  Kernel version:

  Linux Jason-DAC 4.1.15-v7+ #830 SMP Tue Dec 15 17:02:45 GMT 2015 armv7l GNU/Linux

  card output:

  **** List of PLAYBACK Hardware Devices ****
  card 0: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

  Thanks,
  Jason

• 0
  
  Peter January 30, 2016 16:10

  Hi Jason,

  I have the DAC+, which has the same issue/problem.  I posted a workaround in this thread, scroll down to my post from January 16:

  https://support.hifiberry.com/hc/en-us/community/posts/206671215-RPi-B-DAC-Volume-hardware-control 

  I believe that Daniel called it a bug, not sure if that is the case or not.

  It stems from the name of the control parameter which corresponds to hardware volume control.  Basically Volumio talks to Alsa to set the volume, not to the hardware directly.  Volumio uses the wrong name for volume control, so Alsa does not listen.  It's like having the wrong address, and wondering why nobody answers.

  You have to do a lot of reading about Alsa, the amixer command, and Alsamixer to finally understand how this works, having the correct name of the control parameter is just the start. 

  The current versions of Volumio and Rune Audio both use the wrong control parameter.  Neither is willing to fix it because they are busy with development of the new graphical user interface, and trying to beat each other. 

  There is a better fix than mine posted on the Rune Audio forum.  It is an actual patch for the Rune Audio software, not a back door workaround like the one I posted.

  However:  Even after enabling the hardware volume control, Volumio has problems, one of which is the usable range.  Only about 30~40% of the 0-100 range is usable.  Below that you get no sound, and above that you can overdrive your amplifier.

  So,sadly, your best options are either software volume control w. Volumio, Rune Audio, or waiting for the next release of either, and hoping they fix this.... :(

   

  Edited by Peter January 30, 2016 23:33
• 0
  
  D Rush January 31, 2016 10:15

  I was using the DAC + pro with volumio 1.5.5 and hardware controls. It is possible with an unupdated vanilla install.

  You cannot update the Pi software or change the settings in volumio if you want to keep hardware control. I posted in this thread with my findings. It might not be completely accurate for everyone.

  From what I have read work has stopped on 1.5.5 with all efforts focusing on 2.0. Either keep your pi updated and use software volume control or install a vanilla version of volumio 1.5.5 and don't touch anything - even in volumios settings.

  Edited by D Rush January 31, 2016 11:06
• 0
  
  Peter January 31, 2016 16:54

  @ D Rush: I think you are right, but if you are not going to touch the Volumio settings anyway, then you might as well use the updated version, and edit mpd.conf manually with the correct volume control name.

  There must be a better solution for Volumio, just like there is a patch posted on the Rune Audio forum for this problem. 

• 0
  
  D Rush January 31, 2016 22:36

  @Peter That's cool that you found a fix. Personally I got fed up with volumio's long load times. I switched to OSMC and bought the yatse app on my phone to connect to it. OSMC completely loads in a few seconds and I can control everything without a monitor. I added a monitor anyway to get music visualisations and now I also have a home cinema to boot. No regrets.

• 0
  
  Jason February 01, 2016 02:34

  @D Rush,

   

  I'm going to upgrade the kernel, because If I don't upgrade it, the OS cannot recognize my [DAC + Pro], the system will just recognize it as a [DAC +].

  If the system recognized the board is DAC +, the dual clock in the DAC+ pro will not in use.

  I want to use Volumio is because I have using the Spotify, it support Spotify(Runeaudio support too)

   

  Anyway, I will give moode a try, to see it work or not, because the hardware control is very important to me.(OK, I'm lazy)

   

  @Peter,

   

  May I have more information about the Runeaudio's patch?

  BTW, Thanks for your reply, I will try to fix the parameter first.

   

  Jason

   

   

• 0
  
  Peter February 01, 2016 06:59

  @DRush: I have Xbian/Kodi on one RPi2B with a Digi+, and Rune Audio on a second one w. a DAC+.  I am a bit torn between a full-blown multimedia player and the Volumio/Rune Audio solution for audio.  In theory, and if done right, an audio-only, 2-channel (stereo) player would be best for just  music (I did say "in theory", right?... :D)
  
  @Jason: See my post here: https://support.hifiberry.com/hc/en-us/community/posts/206381499-RPi-2B-HiFiBerry-DAC-RuneAudio-0-3  It has a link to the original thread at the Rune Audio forum.
  
  I only understand part of what the patch does, but obviously, the control parameter name has to match Alsa.  Less obviously, that name seems different depending on the version of the software (??).
  
  I could probably figure this out, but honestly, it is hard to justify reading the code when you know someone on the Rune Audio or Volumio team could fix it in five minutes.
  
  Please note I am not recommending Rune over Volumio or vice versa (I wish they were still on the same team!)
  
  For comparing one device to another, I am avoiding using any kind of volume control in the app.  I use the other control parameter, for -6db attenuation, that Daniel kindly pointed out in a different thread, to avoid clipping and any chance of overdriving my inputs. Then I control the volume the old fashioned way... the big knob on the front panel... :D
  
  For casual listening, I can live with software volume control for now, and will look forward to the next release of Rune Audio, Volumio, or whatever they call it next.

  Honestly, hardware volume control, software volume control, or disabled, the sound is much better than the other alternatives which use HDMI or USB, so - I can live with a bug or two in the software.

• 0
  
  JoergZ August 01, 2016 17:16

  @Jason

  Try to uncomment or insert into your output section of /etc/mpd.conf the line

  mixer_type   "software".

  I never got mpd running with volume control even with build-in audio nor with a external usb audiocard without setting this parameter. And it works fine with the android app MPDControl.

• 0
  
  Jason August 02, 2016 06:50

  @JoergZ

   

  Thanks for the reply.

   

  The HifiBerry DAC+ Pro is support the hardware volume control.

  Your setting is going to use the software volume control?

   

  Anyway, the Volumio 2 seems fixed this issue.

  I can go to the setting menu, to set analog volume control, and it work.

   

  Jason

   

• 0
  
  JoergZ August 02, 2016 13:21

  Hardware volume control works immidiatly after setting up the hifiberry system as it is described. But, finally there is nothing to check. Only off (0 %) or on (96 % of master volume) can be choosed. In my case I use a raspberry pi as a "headless" systems what means everything is controlled by client applications: ncmpc (or other software) from Linux and MPDControl from android smartphone. If I used mixer_type "hardware" the volume control works only by using the volume control knob at the amplifier.  But my amplifier is in another room than the speakers,..