Hello,
Is there a way to try your new DAC+ Pro utilizing the new clocks? Does it act like the normal DAC+ without new drivers?
Thanks!
Scott
Date
Votes
61 comments
-
HiFiBerry team Hi Scott,
it acts like a normal DAC+ without the new drivers. While we have the driver for Linux 3.18.x here, it is not easy to update an existing system with these. This is not something a normal user can do.
There are still some issues with the new driver, therefore we can't release it yet. However, I expect that we will have it ready soon. It will then be pushed to Github and will be integrated into one of the next kernel releases.
Best regards
Daniel -
Scott Kramer New Dac+ pro is awesome, wish I could try the clocks! :D
No i2s out until thats done? (P4)
https://app.box.com/s/qn6172d78i18csz7hyk063aajb8htio5 -
HiFiBerry team Hi Scott,
I will see if we can provide a Raspbian image with the old 3.18 kernel and the updated drivers.
Best regards
Daniel -
HiFiBerry team Hi Scott,
the new driver is now on Github and Stuart will work on updating the Raspbian image in our installer. However, I also expect that the driver will be integrated soon in the official Raspberry Pi kernel.
Best regards
Daniel -
Scott Kramer Great News! Thank you very much. -
Scott Kramer will get it all set up as it is now (as the DAC+) with my linear power supply etc. (using piCorePlayer), and get used to the sound in my main audio system
your Digi+ w/linear power supply into my PSaudio DLIII (Cullen level 4 upgrades) -- sounds amazing -- was not expecting that, and why I was motivated to take it further, the BNC & remove the optical
...compared to that the DAC+ really falls down, flat, receded sound -- which is fine, it still sounds good -- really good on a smaller system
will be interesting if the clocks change anything
Fun stuff, Thanks! -
-
HiFiBerry team The DAC+ Pro driver is now available by rpi-update. Kernel version should be at least 4.1.10 after running rpi-update and rebooting.
Best regards
Daniel -
Scott Kramer Ok, Updated it on a max2play 2.22 install, will the squeezelite plugin use it correctly?
pi@max2play ~ $ uname -a
Linux max2play 4.1.10+ #820 PREEMPT Sun Oct 4 15:33:59 BST 2015 armv6l GNU/Linux
pi@max2play ~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0 [] -
HiFiBerry team Hi Scott,
yes, for the application, there is no difference. It just uses the sound driver. The whole clock circuit control is included in the driver and fully transparent for the application. The driver automatically selects the right clock depending on the sample rate of the playback.
Best regards
Daniel -
Scott Kramer Great Daniel, Thanks!
The PR was accepted quick from the official rpi linux, nice!
I let the piCorePlayer guys know also (at least tried to)... it's based on tiny core linux, think it's more involved than just an rpi-update -
HiFiBerry team Hi Scott,
we're working closely with the RPI guys. As we contributed already a lot to the sound subsystem our patches are usually accepted very quick.
Best regards
Daniel -
Tim Curtis Hi Daniel,
Really nice to see DAC+Pro with improved clock method :-)
Couple of general questions and a few specific ones so I can get the coding done correctly in Moode Audio Player 2.4 so users can just elect the DAC+Pro from dropdown and have it automatically configured.
General
(1) Is 5122 being operated as Master to Pi in your solution?
(2) When switching clocks is audio muted to avoid any sort of "pop" noise
Coding and Config
(1) In 4.1.10+ kernel does DAC+Pro use dacplus overlay?
(2) Should the two analog volumes in 5122 (Analogue and Analogue Playback Boost) be set to 100?
(3) Is ALSA volume 100 = 0dB?
Regards,
Tim Curtis
MoodeAudio -
HiFiBerry team Hi Tim,
yes the chip runs in master mode. Muting and all configurations are done in the driver. You don't even have to select between DAC+ standard and DAC+ Pro. The overlay is the same for both - the dacplus overlay. The driver automatically detects if the board is a normal DAC+ or a DAC+ Pro.
About ALSA volume: you can use db settings - amixer sset Master 0dB. Leave the playback boost at the default setting.
Best regards
Daniel -
-Felix- Hi Daniel,
I am very curious about the DAC+ Pro's clock-jitter performance compared to the Digi+, which I already use. Does the dual oscillator configuration deliver better jitter results than the WM8804-PLL with single oscillator configuration? Or will the jitter performance be on the same level? In how far will the DAC+ Pro's performance increase when supplying power from a dedicated linear psu? Any test results available? Is it possible/useful to supply dedicated power to the Digi+?
I am not interested in either the DA-conversion or the S/PDIF output. I need the HiFiBerry board exclusively to clock the I²S bus to transfer audio data from my RPi to an external DAC. So, there will be three devices on my I²S bus:
1. Digi+ or DAC+ Pro as controller (in master mode)
2. RPi as transmitter (in slave mode)
3. My external DAC as receiver (in slave mode).
Should I use Digi+ or DAC+ Pro?
As far as I understood (without looking at the driver source code), both drivers set the respective HiFiBerry board in master mode and the RPi in slave mode. Therefore, both should work out of the box without driver modifications, correct?
Best regards,
Felix -
HiFiBerry team Hi Felix,
does your external DAC needs a master clock that is a multiple of the bit clock? Only the DAC+ Pro provides this. It is also hard to connect external circuits to the Digi+ as there is no pin header for it. Therefore the DAC+ Pro is the right choice here.
Best regards
Daniel -
-Felix- Hi Daniel,
thanks for pointing out that the DAC+ Pro provides a master clock output for I²S. I didn't know that. However, my external DAC is based on dual ES9018 and doesn't need an external master clock input. It "reclocks" the I²S signal using its own high precision oscillator/PLL. However, from brief subjective hearing tests I have got the impression that input from the Digi+ sounds better than I²S signal clocked by the RPi itself. I guess that there are more bit-errors when reclocking a high-jitter I²S signal than with a low-jitter I²S signal (or maybe other effects of imperfect reclocking).
Fortunately, the Digi+ already provides the holes for a secondary GPIO header, which I can use for accessing the I²S bus. Thanks for including this in the Digi+ design :-)
Is there any documentation how to connect a third device to the I²S bus using the DAC+ Pro?
Any comments on jitter performance Digi+ vs DAC+ Pro?
Best regards,
Felix -
Nico Oosterwijk Daniel,
I have rpi-updated my RPi and am running 4.1.10
FLAC files on 44.1/88.2/176.4 kHz are running fine but any FLAC on 48/96/192kHz does not produce any sound.
I have not put the DAC+ PRO an a seperate power source, it's just sitting on the RPi P1 connector.
please advise how to get sound out of hi-res files.
kind regards,
.Nico
P.S. Should your description in the DAC+ product be:
'48/96/192kHz' where is says '48/97/192kHz'
ie. 96 instead of 97 -
Archey Hi Daniel,
Today I received the DAC+ Pro board and it is working with fine with RuneAudio. Since I would like to connect an external I2S DAC, I started figuring out how to use the external master clock signal and became very confused about it. Maybe I have it all wrong, but this is what I have found:
Both XpressO oscillators (X44: 22.5792 MHz and X48: 24.576 MHz) are simultaneous connected to +3.3V, ground and pin 20 of the DAC chip (System clock input of BB PCM5122). Since the output of the oscillators are direct connected to each other, how does the board switch between X44 and X48?
Because I don’t understand the configuration I started measuring with an oscilloscope on the outputs of the oscillators, and instead of getting a signal of 22.5792 or 24.576 MHz I’m getting 2.82 MHz while playing a 44.1 KHz flac file. It looks like the oscillators are producing no signal and the 2.82 MHz is produced by the Dac chip.
Daniel, can you correct me if I have this all wrong and explain how to use the onboard XpressO oscillators for an external I2S DAC?
Best regards,
Archey -
Nico Oosterwijk Daniel,
After removing the snd_bcm2835 in /etc/modules I do have sound playing the hi-res files.
So it could be a problem that when switching to anothe clock, the sound get switched to the second ALSA device?
Anyways, it is solved now since I only have one device left now.
rgds,
.Nico -
Archey Hi Daniel,
My post was too soon, I do now understand the configuration of the oscillators. I was not familiar with the Enable / Disable option of the XpressO oscillators, with this option the oscillators can be switched on and off independently by the DAC chip..
Later on I found this:
www.hifiberry.com/2015/09/new-product-releases-hifiberry-dac-light-and-dac-pro
---------------
The new onboard clock generator needs an updated driver. We’re working on this and expect the updated driver to be released soon. While the board also works with the existing DAC+ drivers, the onboard clock generation is used only with new driver.
---------------
Is this driver already available for RuneAudio?
Best regards,
Archey -
Scott Kramer Hi Archey,
Maybe not running the new driver?, so the clocks are not enabled, 2.82MHz is prob the raw PCM, also 22.7592MHz/8 = the 2.82Mhz so not sure--
need to be on 4.1.10 kernel
and aplay -l has "Pro" in the name:
Just a guess, Daniel will probably know.
May I ask what oscilloscope are you using? -
jimmy.kl Hi Daniel,
I'm planning on using an RPi to send I2S over HDMI via an Audio-gd output module to a Wyred4Sound DAC-2 DSDse.
Do you know if the limitations of the Rpi's built-in clock would affect the I2S signal? And if so I assume it would be beneficial to use the DAC+ Pro and connect the Audio-gd unit to that?
Cheers,
James. -
HiFiBerry team @Nico: This looks like one of the oscillators might has been damaged. I think we have to test the board here. Please return it to us, we will check it here.
Best regards
Daniel -
HiFiBerry team @Archey: I don't know how often ArchLinux updates the kernel. You might ask the ArchLinux developers when the official 4.1.10 kernel will be released for ArchLinux.
Best regards
Daniel -
HiFiBerry team @jimmy.kl: I don't know the product you linked. Therefore I can't say, if it will work with the DAC+ or DAC+ Pro.
Best regards
Daniel -
Archey @Scott/Daniel: Thanks for your reaction. I have installed Volumio with the 4.1.10 kernel and the clocks are working fine now. With the standard power adapter attached to the Raspberry I can actually see jitter on the clock signal with the oscilloscope (Rigol DS1074), but with a battery based power supply, its’s not visible and the soundstage is very good!
Regards,
Archey -
Scott Kramer Very interesting Archey, would love to see pics of the scope comparing the two! Do you know how to get a ps # amount of jitter? re 50ps , 700ps (which is bad) etc...
Are you using the 5volt header for the alternate power (to power the dac & pi together)?
With my own setup, added a linear power supply to a Digi+/raspi B+ and could not believe how much the sound improved. I bought it as a backup to my squeezebox touch (that is optimized to get the best spdif signal) not expecting it to sound very different or slightly worse. -
HiFiBerry team @Archey: Even with a bad power supply you should not see any jitter with your oscilloscope. Jitter is below the bandwith and sample rate of your Rigol scope. Most likely you did not use the ground directly on the oscillator but somewhere else. This can result in additional noise which might look like jitter. It could also be trigger jitter depending on your trigger point.
Best regards
Daniel -
mail I got my HifiBerry DAC+ Pro in the mail last week. So just to be clear...I have updated the Linux kernel to 4.1.11 which apparently includes the latest drivers for the HifiBerry DAC+ Pro. The system recognizes that I have HIfiBerry DAC+ Pro installed (as opposed to just HifiBerry DAC+) when I type the command "aplay -l" under SSH.
I currently have Volumio v 1.55 running. But under the drop down menu it only shows HifiBerry + as the only appropriate option for i2S DACs. I was expecting to now show a DAC+ Pro option. Can I assume that the system is using the internal clock despite whatever shows up under Volumio?
Thanks
Please sign in to leave a comment.