I’m a bit of a novice in Pi land…I actually design sound systems for big theatres for a living, but this is another world.
Everything is bypassed in DSP land. Other than bypassing, how would I pull the DSP out of the mix?
Okay, so you’re not using DSP. Please provide a screenshot of the Device Settings for FamilyPi. Also, if you go to the Ropieee web interface, can you confirm that you have the correct device set … aha! There is a HiFiBerry DAC+ DSP … is this your device? And is Ropieee setup correctly?
Roon Settings - I am suspicious of the disconnect between the audio device here and the selection in HiFiBerry. But that doesn’t seem like it would impact the optical output. Seems like it should either be active or not.
I just tested to install Roopie to Rasp4 and use DAC+ DSP hat. (I was running that fine with dietpi, just wanted to test this issue)
I have little different version of Rasp :Raspberry Pi 4 Model B Rev 1.1
Flashed image from Roopie site, install went fine, version was 3.066. Tested with Roon, worked fine (tested only analog out!). Roopie asked to update version, Updated to version 3.084.
Tested with Roon, again worked fine.
I checked settings at Roon, I had “Device Volume” instead “DSP Volume”, tested
with that “DSP Volume” setting , still worked.
You have Display attached, maybe powersupply problem, doesnt give enough power?
Can you test your hats without display?
Board Serial ID:
Raspberry Pi 4 Model B Rev 1.1
USB FW Version:
Also version of “DSP DAC v.1.3” printed on the HAT
It was my experience that I had to check the box USB Audio for the HiFiBerry Dac I have to work with Ropieee even though I was using the HiFiBerry DAC output. Ultimately I switched to the HiFiBerry OS just because. You might give that a try.
I installed the HiFiBerry OS and I have the same problem through Roon, and through Bluetooth: UI looks correct, but no audio. I am thinking I managed to get (2) bad HiFiBerry cards…It just seems that the probability of that happening is very low…
It turns out a bunch of HiFiBerry DAC+ DSPs were shipped without the jumper installed near the TOS input. That jumper’s function is undocumented, but when removed it stops the soundcard from identifying itself during boot.
Once that jumper is installed everything works as it is supposed to work.