[BugFix] HiFiBerry DAC+ HW Volume (RuneAudio 0.3-beta)

123456

Sorry for the late answer.
I was way from the pi.
Here are my results:

[root@runeaudio ~]# redis-cli hset acards_details snd_rpi_hifiberry_dacplus "{\"sysname\":\"snd_rpi_hifiberry_dacplus\",\"extlabel\":\"HiFiBerry DAC+ (I&#178;S)\",\"mixer_numid\":\"1\",\"mixer_control\":\"Playback Digital\",\"hwplatformid\":\"01\",\"type\":\"i2s\"}"
(integer) 0

[root@runeaudio ~]# php /var/www/command/refresh_ao
amixer: Unable to find simple control 'Playback Digital',0

Notice: Undefined offset: 0 in /srv/http/app/libs/runeaudio.php on line 1793

Warning: socket_write(): unable to write to socket [32]: Broken pipe in /srv/http/app/libs/runeaudio.php on line 99

Harware volume control is still impossible.
But I really like that, compared to Volumio, no restart is requird for applying changes.

Is there another way, to make those changes?

hondagx35

Hi 123456,

the steps are:

- set the new details for your card:

redis-cli hset acards_details snd_rpi_hifiberry_dacplus "{\"sysname\":\"snd_rpi_hifiberry_dacplus\",\"extlabel\":\"HiFiBerry DAC+ (I&#178;S)\",\"mixer_numid\":\"1\",\"mixer_control\":\"Playback Digital\",\"hwplatformid\":\"01\",\"type\":\"i2s\"}"

- update database

php /var/www/db/redis_acards_details

- refresh alsa settings

php /var/www/command/refresh_ao

The right setting for "mixer_control" can be found in the debug data (MENU->Debug).

Frank

123456

Hello Frank,

I tried a bit on my own.
First step was:

alsamixer

: Bildschirmfoto 2015-11-10 um 19.13.18.png (40.55 KiB) Viewed 4466 times

As you can see, PCM is the first control and works quite good.
So I did this:

redis-cli hset acards_details snd_rpi_hifiberry_dacplus "{\"sysname\":\"snd_rpi_hifiberry_dacplus\",\"extlabel\":\"HiFiBerry DAC+ (I&#178;S)\",\"mixer_numid\":\"1\",\"mixer_control\":\"PCM\",\"hwplatformid\":\"01\",\"type\":\"i2s\"}"

/srv/http/command/refresh_ao

Got an error:

Warning: socket_write(): unable to write to socket [32]: Broken pipe in /srv/http/app/libs/runeaudio.php on line 99

Next step was:

nemus wroteEdit /etc/modprobe.d/blacklist.conf

blacklist snd_bcm2835
blacklist snd_soc_hifiberry_dac

Than reboot.

Now airplay:

ChiiFii wroteedit the hardwaredevice in /usr/lib/systemd/system/shairport.service on line 11
in my case: hw:1,0 to hw:0,0

ExecStart=/usr/bin/shairport -w --name=RuneAudio --on-start=$ON --on-stop=$OFF --meta-dir=/var/run/shairport -o alsa -- -d hw:0,0

systemctl daemon-reload

systemctl restart shairport

The command made an error. I used nano instead.
At last: reboot

Hardwaremixer is working now.
I left this away:

hondagx35 wrote- update database

php /var/www/db/redis_acards_details

Could this cause any trouble?

Jan1959

I posted ealier

by Jan1959 » 14 Oct 2015, 18:49
I also post it (already) in the rune audio 0.3 beta post.
Probably wrong so i put it here once more (or again).

Is there a version of runeaudio with the right hifiberry+ analog and HW volume for the raspberry 2B that works directly without the correction that is mentioned in this post. I am a complet noob in linux. Probably a version 0.31-beta. I wil save a lot of studying how linux, putty, shh etc works.

Thank you for your answer in advantage.

Because i got no reply a tried for several hours to learn wat putty is etc.
I copied the code etc and nothing happens.
For the case i damaged the initial code i downloaded it again and tried three times to get mine hifiberry as an option,
Nothing for so far.

I see more people struggling to get it working.
I thought it was een little thing to update the initial 0.3 version so all the things goes a bit smoother.
Probably it is a big thing to update it into a 0.3b version with the hifiberry and HW volume bug solved.

Can anybody tell me what to do so i can enjoy mine raspberry in combination with mine hifiberry.

matock

Hi all,

Same for me, my HifiBerry DAC+ is not recognized on Raspberry Pi2 and RuneAUdio 0.3beta.

I tested all possible solutions exposed in that long thread and none of them is working:
- 3 different "redis-cli" commands
- with or without "blacklist.conf"
- 2 different way to call "refresh_ao"
- with or without calling "redis_acards_details" command

Every time the refresh_ao fails with errors:

Notice: Undefined offset: 0 in /srv/http/app/libs/runeaudio.php on line...
...
Warning: socket_write(): unable to write to socket [32]: Broken pipe in /srv/http/app/libs/runeaudio.php on line 99

Is anybody have a clear and definitive solution for this?
Is the HifiBerry DAC+ is really compatible or not?

Many thanks

sylvain

Hi all,

Could someone help me with the hardware volume issue please ? (i've tried many workarounds in this thread)

I'm running a Rasp2, and a 9023 SABRE audiophonic DAC (Hiberry driver),

Here's my debug details : http://pastebin.com/2Fg2e4F3

Thanks...

Jan1959

The last 3 post, please mr. Orion is there anyway to post a working download with the hifiberry working.
Or should we wait for 0.4 for the bug fix in the initial download.

Thank you for your answer in advance.

hondagx35

@ Jan1959 and matock,

Orion is there anyway to post a working download with the hifiberry working.

First, Hifiberry DAC+ works fine on all versions.
The only thing that doesn't work on all versions out of the box is hardware volume.
You have two options:
- Update your system via git

cd /srv/http/
git stash
git pull

- get the image from here. The local browser is optional, so don't worry about this.

@[deleted]

Your DAC doesn't have a hardware volume control.
From the hifiberry site:

Q: Does it have a volume control?
A: Our new HiFiBerry DAC+ board comes with an integrated volume control. However the older HiFIBerry DAC uses the digital data without any post-processing. It will output the sound stream with the volume the application feeds it. Many applications can use an internal volume control (so called software volume control). If the application you want to use does not have a software volume control, you can’t control the volume by software. However the best way to control the software is a analog volume control after the DAC. While software volume control is an option, it will reduce signal-to-noise ratio. If you connect the DAC to your amplifier, you should use the volume control of your amplifier.

Frank

matock

Hi again,

I found how to activate the audio card in PDM settings.

Just edit the /boot/config.txt file

nano /boot/config.txt

uncomment the line corresponding to your card (start from line 42)

device_tree_overlay=hifiberry-dacplus

and reboot.
This will work for any HifiBerry or IQaudIO card.
(source http://support.hifiberry.com/hc/en-us/articles/205377651-Configuring-Linux-3-18-x-or-higher and #86241

I found it after reading hundreds of posts. I'm a little bit angry, really. Why this obvious thing is not mentioned in the documentation section? It will avoid to loose hours for many and to spam the forum for nothing.

But the main issue from this thread remains: the HW volume control doesn't work. As I understood, this a bug. Ok, it is something that I can accept. this is a beta release after all, I can wait. sorry guys for the anger, but it relieves!

Nevertheless, a very good job have been done here. Many many thanks... and stay concentrated.

hondagx35

Hi matock,

I found it after reading hundreds of posts.

I thought it would be enough to put this hint on the settings page:

RuneOS kernel settings
Linux Kernel
There are no other kernels available at the moment!
I²S kernel modules
Enable I²S output by selecting one of the available sets of modules (in this version you have to edit /boot/config.txt), specific for each hardware. Once set, the output interface will appear in the MPD configuration select menu, and modules will also auto-load from the next reboot.
Sound Signature (optimization profiles)
These profiles include a set of performance tweaks that act on some system kernel parameters. It does not have anything to do with DSPs or other sound effects: the output is kept untouched (bit perfect). It happens that these parameters introduce an audible impact on the overall sound quality, acting on kernel latency parameters (and probably on the amount of overall jitter). Sound results may vary depending on where music is listened, so choose according to your personal taste. (If you can't hear any tangible differences... nevermind, just stick to the default settings.)

In the docs (see here you are pointed to the settings page.

Frank

matock

Hi Frank,

Those explanations are clear but I cannot find from where they are coming. The doc you mentioned in Rune > Settings (http://www.runeaudio.com/documentation/runeui/settings/) is different and less detailed.

Just for my info: why all the lines are commented in config.txt. Does it consume memory or cpu if we load them all? The idea is to allow the users to select their DAC card directly in the Rune config UI without tinkering manually system files. Another solution could be to select the card via the UI, then to update automatically the boot.txt file and to warn the user that the system will reboot.

In fact the user shouldn't have to do twice the same thing: the configuration should be done manually OR via the UI, but not both. This is not intuitive nor logical. This is just - I hope - a constructive remark.

Matock

Jan1959

Frank and or Matock

Is it possible to post the correct image somewhere on this site so everybody could download it without edit it.

@Matock, i support your vision how it should work. I think it will increase the number of satisfied users of Runeaudio.
Plug and play

Jan1959

See no lines to edit or to unmark

Attachments

: Knipsel.PNG (11.51 KiB) Viewed 5381 times

hondagx35

Hi Matock,

Those explanations are clear but I cannot find from where they are coming.

They are from the UI.
Go to MENU->Settings and scroll down.

Just for my info: why all the lines are commented in boot.txt.

Because you can't enable multiple drivers at the same time (they all use I2S interface).

The idea is to allow the users to select their DAC card directly in the Rune config UI without tinkering manually system files.

You are absolutely right, but at the moment this is not possible.
As you may know, we support not only RaspberryPi.
We have images for ODROID, Cubietruck and the older PIs.
All these devices need different linux kernels, so the procedure to enable a special driver is not the same.
Only the "new" RP2 uses the so called device tree there you have to enable the drivers in /boot/config.txt.

The next image will consider all this.

Frank

hondagx35

Hi Jan1959,

this is only valid for the PI2.

The file you have to edit is "/boot/config.txt"

Frank

Jan1959

I have an XBMC-2B-HIFIBERRYY
Hifiberry + Bord1 x Rca

How should i enable the drivers

hondagx35

Hi Jan1959,

this should be a HifiBerry DAC+.

So open the file /boot/config.txt and remove the # in front of "device_tree_overlay=hifiberry-dacplus".

# Uncomment one of these lines to enable an audio interface
#device_tree_overlay=hifiberry-dac
device_tree_overlay=hifiberry-dacplus
#device_tree_overlay=hifiberry-digi
#device_tree_overlay=hifiberry-amp
#device_tree_overlay=iqaudio-dac
#device_tree_overlay=iqaudio-dacplus

Frank

Jan1959

Frank, MPD says HifiBerry Dac+

Thank you for your help. Tomorrow listing to the music with the hifiberry+
.

Jan1959

First hour of listning is over.
The PI and hifiberry come to life with Runeaudio.
Really good sound. The GUI of runeaudio does a good job

Thanks to your service.

Hit the donate button

tbahrman

I'm getting a "command not found" error when I try to run the refresh_ao command. The HiFiBerry DAV+ does not appear as an option under the Audio output interface drop-down menu on the MPD page after executing these commands. See the dialog session below...

Last login: Fri Jan 22 06:32:02 2016 from 192.168.1.75
[root@runeaudio ~]# redis-cli hset acards_details snd_rpi_hifiberry_dacplus "{\"sysname\":\"snd_rpi_hifiberry_dacplus\",\"extlabel\":\"HiFiBerry DAC+ (I²S)\",\"mixer_numid\":\"1\",\"mixer_control\":\"Playback Digital\",\"hwplatformid\":\"01\",\"type\":\"i2s\"}"
(integer) 0
[root@runeaudio ~]# refresh_ao
-bash: refresh_ao: command not found
[root@runeaudio ~]#

Thanks!
Tom

« Previous Page Next Page »