Testing results on PCM DAC IC with CLK/BCK (reg 13 and 14 , please refer to PCM datasheet)
Different scenarios for SCK for DAC clock
Scenario 1: Reg 13 set to BCK, PLL enabled, Reg 14 set to SCK
Result: SCK is not going to DAC clock
Scenario 2: Reg 13 set to SCK, PLL enabled, Reg 14 set to auto select
Result: SCK is feed to DAC clock through PLL
Scenario 3: Reg 13 set to SCK, PLL disabled, Reg 14 set to auto select
Result: SCK (outside) is feed to DAC clock
Scenario 4: Reg 13 set to BCK, PLL disabled, Reg 14 set to SCK
Result: SCK is feed to DAC clock
Default: Reg 13 set to BCK, PLL enabled, Reg 14 set to auto select
Result: SCK is not feed to DAC clock, PLL generates the required clk
Basically if SCK is present , PCM51xx does not automatically sw to the better clock. The DAC registry (s) needs to be programed to take care of the right clock.
We are modifying the driver to take advantage of and will add to our github soon..
I hope that some of you guys can give us some feedback on SQ. I will do my own testing this weekend/
Different scenarios for SCK for DAC clock
Scenario 1: Reg 13 set to BCK, PLL enabled, Reg 14 set to SCK
Result: SCK is not going to DAC clock
Scenario 2: Reg 13 set to SCK, PLL enabled, Reg 14 set to auto select
Result: SCK is feed to DAC clock through PLL
Scenario 3: Reg 13 set to SCK, PLL disabled, Reg 14 set to auto select
Result: SCK (outside) is feed to DAC clock
Scenario 4: Reg 13 set to BCK, PLL disabled, Reg 14 set to SCK
Result: SCK is feed to DAC clock
Default: Reg 13 set to BCK, PLL enabled, Reg 14 set to auto select
Result: SCK is not feed to DAC clock, PLL generates the required clk
Basically if SCK is present , PCM51xx does not automatically sw to the better clock. The DAC registry (s) needs to be programed to take care of the right clock.
We are modifying the driver to take advantage of and will add to our github soon..
I hope that some of you guys can give us some feedback on SQ. I will do my own testing this weekend/
Last edited:
Isolator board for RPI/ i2s/ i2c
We are working on a isolator board for RPI . The basic design is over and I just want some feedback .
i2s isolated---configurable as master or slave
i2c isolated --bi directional
GPIO (1)
Power:
On board isolated DC/DC convertor 5V (380ma) ... ripple less than 15mV
5V pass through ---3.3v using LDO 200ma
External :
Batteries linear psu etc... a minimum of 6V (to 19V)
LDO1---5v standard (but configurable 7V , 9V and 12V output ) 500ma
LDO2 ---3.3V standard (but configurable to 7v , 9v , 15v) 200ma
You can use only one PSU at the time (disabled if not used by SW)
We are working on a isolator board for RPI . The basic design is over and I just want some feedback .
i2s isolated---configurable as master or slave
i2c isolated --bi directional
GPIO (1)
Power:
On board isolated DC/DC convertor 5V (380ma) ... ripple less than 15mV
5V pass through ---3.3v using LDO 200ma
External :
Batteries linear psu etc... a minimum of 6V (to 19V)
LDO1---5v standard (but configurable 7V , 9V and 12V output ) 500ma
LDO2 ---3.3V standard (but configurable to 7v , 9v , 15v) 200ma
You can use only one PSU at the time (disabled if not used by SW)
Cool stuff @greinedo
I have a few side projects experimenting trying to utilize the kali also!
On Mike Moffat's baby multibit Dac:
https://www.youtube.com/watch?v=JbIYoG586fY
(Kinda specific... but kali related )
What AKM board is that?
Hi Sckramer !
This one : Module Board DAC AKM AK4495SEQ I2S 32bit 384khz - Audiophonics
Not HAT compatible for sure but sound first !
Attachments
I hope that some of you guys can give us some feedback on SQ. I will do my own testing this weekend/
If the updated driver patch is available, I will try this at the weekend, if I get chance.
What I do not understand is how to select the firmware. I will not be using Moode or Volumio, so how does the driver know which firmware to load?
Also, how does the sample rate work? Does the selected firmware need to match the sample rate of the program material? If not, what happens?
new isolator board announced...please comment
http://www.diyaudio.com/forums/pc-based/300075-isolator-board-rpi-i2s-i2c.html
http://www.diyaudio.com/forums/pc-based/300075-isolator-board-rpi-i2s-i2c.html
personnaly I am waiting for a way to adjust the cutoff (LP point and HP point) between 60-150H without any Single Board Computer (sparky, raspberry connector input...) nor distribution , thinking using i2s input : either ask for a specially requested factory preset frequency or use purepath studio are the only feasible solutions ?
Hello,
my first test with Raspberry Pi 2- Kali-Piano 2.1
I'm using Runeaudio.
My usual front end is composed by :
Cubietruck + Runeaudio => I2S => DAM 1021 => biamped dipole speakers
1st test:
Raspberry Pi 2 + Runeaudio => Piano 2.1
works well like my ES9023 I2s Dac. Normal life and air. Correct for the money.
2nd test:
Raspberry Pi 2 + Runeaudio => Kali => Piano 2.1 Better life and air. It's easy to ear the difference. Very good value for money.
Raspberry is powered by linear LM1085 PSU
Kali and Piano 2.1 are powered by Salas shunt PSU clone
At the moment, Cubietruck + Runeaudio => I2S => DAM 1021 are at another level of life, air and space but my next step will be:
Raspberry Pi 2 + Runeaudio => Kali => Dam 1021
and may be:
Raspberry Pi 2 + Runeaudio => Kali => Diyinhk PCM1704 DAC
See you soon.
Ciao
Guglielmo
Hello,
I'm slow but fanatic!
3rd test:
Cubietruck + Runeaudio => I2S => DAM 1021
VS
Raspberry Pi2 + Runeaudio => I2S => DAM 1021
Both systems work well, Raspberry is a bit more silent but the sound of Cubietruck is more dinamic and life like.
4th test:
Cubietruck + Runeaudio => I2S => DAM 1021
VS
Raspberry Pi2 + KALI + Runeaudio => I2S => DAM 1021
DAM1021 is insulated and reclocked but with Raspberry and Kali everything seems ok, no harsh and full of life.
For the moment in my system Raspberry and Kali are the winner.
I hope this help.
Regards
Guglielmo
Attachments
i´m waiting for my kali to arrive...let´s see how it holds against hfb dac/digi pro feeding my akm board
See here for one view:
http://www.diyaudio.com/forums/digital-line-level/294940-new-fifo-buffer-rpi-sbcs-3.html#post4827178
Greg in Mississippi
Listening comparison
Did a lenghy listening comparison yesterday between:
- RPi3/Kali/Subbu DAC (see pice in an earlier post)
- Beaglebone black with external oscillator (same NDK ones as on Kali) feeding a Subbu dac (clone version from Ebay) so both were ES9023 DACS.
Both via ethernet connection and both using LMS/Squeezelite and FLAC files. I was able to sync the tunes and levels were the same so pretty much seamless switching on the fly.
AND.... I couldn't tell the difference!
My system is reasonably well detailed and clean, Mark Audio 10P drivers which to me resolve detail really well. There may have been times when I would pick one having a bit more detail at the expense of slightly more aggression but, in all honesty, if someone else did the switching I wouldn't be able to pick it. Both sounded great.
Conclusion.... maybe I have cloth ears or....
Did a lenghy listening comparison yesterday between:
- RPi3/Kali/Subbu DAC (see pice in an earlier post)
- Beaglebone black with external oscillator (same NDK ones as on Kali) feeding a Subbu dac (clone version from Ebay) so both were ES9023 DACS.
Both via ethernet connection and both using LMS/Squeezelite and FLAC files. I was able to sync the tunes and levels were the same so pretty much seamless switching on the fly.
AND.... I couldn't tell the difference!
My system is reasonably well detailed and clean, Mark Audio 10P drivers which to me resolve detail really well. There may have been times when I would pick one having a bit more detail at the expense of slightly more aggression but, in all honesty, if someone else did the switching I wouldn't be able to pick it. Both sounded great.
Conclusion.... maybe I have cloth ears or....
- Home
- Vendor's Bazaar
- New FIFO buffer for RPI/SBCs