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

PeteB

smallfat

PeteB wroteLogin: root, PW: rune

Thanks PeteB

To enable RP 3 GPIO 40 Pin I2S,
I uncomment dtparam=i2s=on of config.txt.
Is it enough? I cannot enable option on MPD

Best Regards
Michael

PeteB

smallfat wroteI uncomment dtparam=i2s=on of config.txt.

Only the line in config.txt which corresponds to your DAC. Remove only one comment, from one line.

config.txt tells the Rune OS which hardware you have. Then after you reboot, the correct driver for your dac will be loaded.

Then you can select your dac in the MPD dropdown list.

smallfat

PeteB wrote
smallfat wroteI uncomment dtparam=i2s=on of config.txt.
Only the line in config.txt which corresponds to your DAC. Remove only one comment, from one line.

config.txt tells the Rune OS which hardware you have. Then after you reboot, the correct driver for your dac will be loaded.

Then you can select your dac in the MPD dropdown list.

Hi,

Thanks your prompt reply.
I want a generic I2S out to my desktop DAC,
From my experience at ODROID, I need not specific which DAC I am using.
Like picture attached.

: 檔案 3-4-2016 06 51 59s.jpg (67.09 KiB) Viewed 41444 times

hondagx35

Hi smallfat,

From my experience at ODROID, I need not specific which DAC I am using.

For the ODROID this is correct, but not for the RaspberryPi.
As Pete told you, you have to enable one of the DACs from the config.txt.

I want a generic I2S out to my desktop DAC,

Your desktop DAC? Is it red or green?
A bit more information would help.

Frank

smallfat

Hi Frank,

As our understanding, I2S signal cannot be transmit too long.
There are some proprietary transmission standard, no matter from famous brand or DIY market,
enable I2S signal transmit longer.
I use a conversion board which convert I2S signal to their proprietary standard.
Signal convert back to I2S at my DAC.

: I2S.jpg (71.04 KiB) Viewed 41382 times

So I need generic I2S signal like ODROID's I2S out.

Best Regards
Michael

hondagx35

Hi Michael,

So I need generic I2S signal like ODROID's I2S out.

A generic driver does not exist neither for the Raspberry nor for the ODROID.

Enabling "dtparam=i2s" only enables the hardware, but does not transmit any data.
Al drivers enable this by default, so no need to do it explicitly.

As Pete told you, you have to enable one driver from the list in config.txt.
If the ODROID driver (made for ODROIDs hifi shield) works for your DAC, i would recommend the Hifiberry DAC driver on Raspberry.

This all has nothing to do with the transport media (proprietary transmission standard).

Frank

smallfat

Hi,

Actually, on my ODROID C1 plus case,
when I select ODROID DAC, I get I2S signal.

Via the conversion board, signal pass to my DAC. Sound very well. Nearly 60-70% performance compare with my CDM3 CD player.

If I provide better quality of power, performance
even better.

Best Regards
Michael

dmcRune

Slightly off-topic - different DAC and RPi 3, but this might save some frustration:

For my RPi 3 and HiFiBerry DAC+PRO. Hardware mixer is working by changing the
name for the device in the redis-cli command to "Digital" instead of "Digital Playback"
or "PCM".

Again, please note that this information is for the DAC+PRO not DAC+.

Thanks to all for providing the information on this topic.

hondagx35

Hi dmcRune,

For my RPi 3 and HiFiBerry DAC+PRO. Hardware mixer is working by changing the
name for the device in the redis-cli command to "Digital" instead of "Digital Playback"
or "PCM".

With the latest version for RP2/RP3 this is the default, so no need to change anything!

Frank

dmcRune

I must have done something wrong. Thanks for setting me straight!

hondagx35

Hi dmcRune,

I must have done something wrong. Thanks for setting me straight!

No problem, i only commented to this to not confuse other users.

Frank

pelliott321

I apologize for being such a noob
but
I have Raspberry Pi3 with HiFiberry Pro DAC (Latest)
its on the network (wifi) with NAS Mounted and radio stations visible
need to get DAC configured
I loaded OpenSSh on windows 10 machine but do not know how to log on to Pi from SSH so I can do the commands of this thread
IP of wireless PI is 192.168.1.32

hondagx35

Hi pelliott321,

need to get DAC configured

With latest image the DAC should work with hardware volume (HW) without changes.

Or do you need to edit the config.txt file to activate your DAC in general?
If so, install Notepad++ on your Windows10 PC and put the SD card back in your PC to edit this file.

Frank

pelliott321

I have RPi3 with HIFIberry DAC +Pro working on wifi with NAS volume connected using software volume control
I would like to do this fix but really know nothing about SSH and connecting to the PI
I installed Putty on Windows 10 machine, and know the IP address of the PI
I do not know how to log on. I believe the user name is "raspberry" but what is the password?

hondagx35

Hi pelliott321,

best would be to read the docs!
http://www.runeaudio.com/documentation/quick-start/quick-start-guide/#advanced-users

user: root
pwd: rune

But again, hardware volume (HW) should work without modifications!
So what is your problem?

Frank

pelliott321

I apologize for being such a neophyte and appreciate your time patience and efforts
I did not read the whole thread before posting
I never tried the HW setting because I did not really understand it
Then I started to read this thread so I wanted to give it a try.
So now I will without editing your script

dunghnguyen

smallfat wroteHi Frank,

As our understanding, I2S signal cannot be transmit too long.
There are some proprietary transmission standard, no matter from famous brand or DIY market,
enable I2S signal transmit longer.
I use a conversion board which convert I2S signal to their proprietary standard.
Signal convert back to I2S at my DAC.

So I need generic I2S signal like ODROID's I2S out.

Best Regards
Michael

Can you give me the link where I can buy that simple board for usb to i2s conversion? Thanks buddy.

Miel

Aloha,

After endless tries, i finally managed to get HW volume control to work (setup: RPI 2, PIFI DAC+ 2), the only problem i have now is the range of the volume. Set to approximately 60 (or any lower value) the audio becomes, well, inaudible

From 60-100 i can adjust the volume, but obviously, i would like a bit more fine grained control.
I've added my debug info to pastebin: http://pastebin.com/dLR6b4VM

If anyone can provide some pointers, that'd be greatly appreciated.

Cheers!
Miel

hondagx35

Hi Miel,

welcome to Rune Audio.

This is a known issue, but nothing we can solve at the moment.
#254

Frank

« Previous Page Next Page »