That was fast!https://www.hifiberry.com/shop/boards/hifiberry-dac8x/ - "Note that the DAC8x is only compatible with the Raspberry Pi5."
That was fast!https://www.hifiberry.com/shop/boards/hifiberry-dac8x/ - "Note that the DAC8x is only compatible with the Raspberry Pi5."
https://www.hifiberry.com/shop/boards/hifiberry-dac8x/ - "Note that the DAC8x is only compatible with the Raspberry Pi5."
Why does that matter? Performance isn't near 24 bit let alone 32. Expect performance similar to the DAC+ at a fair bit less than 4x the price.
No 32-bits
I want to avoid an analogue volume control between DAC and power-amplifier.Why does that matter? Performance isn't near 24 bit let alone 32. Expect performance similar to the DAC+ at a fair bit less than 4x the price.
I guess Rene want only 32 Bit DAC'SWhy does that matter? Performance isn't near 24 bit let alone 32. Expect performance similar to the DAC+ at a fair bit less than 4x the price.
24-bit dynamic + 8-bit volume control = 32-bit ;-)I guess Rene want only 32 Bit DAC'S
On ADC it's matter more i guess then on an DAC.
24Bit >16milion of stepps between lowest and highest Level
32Bit > 4000Milion
64Bit > 1.8 10(19) Big Number! Camiila works with 64Bit
Not sure you are able to heare the difference on an DAC Output 24 vs 32Bit Dynamic vise 24 Bit are very Good already
Robert
i dont like Volumecontrol in Digital Domain at all That why Relaisvolumecontrol after DAC is my Key to go24-bit dynamic + 8-bit volume control = 32-bit ;-)
Yes SABRE Dacs have his Voumecontrol in Dac and its handyLuckily everyone has a personal taste.
For now I'm planning to drive the power-amp in my Technics SA-TX50 directly with the DACs.
The pre-amp is way to noisy.
The pre-amp is hissing but the power-amp sounds fine and is quite fast and powerful.Technics SA 50 is an oldscool Surround Amp without HDMI, nice.
But on Technical Information it says:
Fremdspannungsabstand: 70 dB (you are sure thats only the preamp and not the Poweramp also???
Gesamtklirrfaktor (halbe Leistung, 1 kHz, 6 Ohm): 0,03 %
No 32-bits
Hi, Does it mean i could use the Slave MCLK from MC_FIfo+MC Dualclock to use on the RPI5 as MCLK in to get better Jitter ?? As you know i am not an ExpertBTW this is a good example where the RP1 MCLK output would get handy, avoiding the MCLK PLL in PCM5102A.
And if Hifiberry had waited a bit, they could have done it - two weeks ago the GPIO CLK support was merged to RPi 6.6 kernel.
Add GPCLK support on RP1 by P33M · Pull Request #6013 · raspberrypi/linux
Prompted by https://forums.raspberrypi.com/viewtopic.php?t=365761&hilit=gpclk this lets users drive gpclks via overlays (and if suitably motivated, drive off-chip sources into peripherals). I've no...github.comdrivers: clk: rp1: add GPCLK source muxes and additional PLL dividers · raspberrypi/linux@d731b47
General-purpose clocks are routed (via a pad) to a large variety of peripheral aux muxes, and themselves gather a large variety of source clocks. Entries without a corresponding name string should ...github.com
I do not know exactly your intention. The MCLK pin can be configured as output - feeding your codecs, or as input - clocking RPi5 I2S IN/OUT interface being in master mode. If you need the RPi5 I2S as slave, it does not need any MCLK.Does it mean i could use the Slave MCLK from MC_FIfo+MC Dualclock to use on the RPI5 as MCLK in to get better Jitter ??
The PCM5102A autodetects the MCLK input and does not need any I2C configurationIt's currently a public beta so they could still adopt that before production. I don't remember seeing any members from HifiBerry here, so maybe worth mentioning via their cmmunity site?
IMO all they need to do is to connect one of the GPCLKs to the SCK pins and configure the clock output in their overlay https://github.com/raspberrypi/linu...boot/dts/overlays/hifiberry-dac8x-overlay.dts , as discussed e.g. in https://forums.raspberrypi.com/viewtopic.php?t=365761 . But of course trying so may reveal some other steps necessary to take.The internal PLL is disabled as soon as an external SCK is supplied.
The device starts up expecting an external SCK input, but if BCK and LRCK start correctly while SCK remains at ground level for 16 successive LRCK periods, then the internal PLL starts, automatically generating an internal SCK from the BCK reference.
Ah ok RPI 5 is Slave Mode and my RPI 4 is in Master but is before MC Fifo so i gues no need to feed in MCLK there.I do not know exactly your intention. The MCLK pin can be configured as output - feeding your codecs, or as input - clocking RPi5 I2S IN/OUT interface being in master mode. If you need the RPi5 I2S as slave, it does not need any MCLK.
I am afraid I do not undestand your setup. Why do you need the FIFO? Do you combine RPi4 and RPi5?Ah ok RPI 5 is Slave Mode and my RPI 4 is in Master but is before MC Fifo so i gues no need to feed in MCLK there.