Posts by Da Flex

Thanks for testing. I just copied that from another thread, and it doesn't work on my RPi, too. Sorry.

After some more research, I suggest this:

1) Make PulseAudio's daemon.conf editable by creating a copy:

cp /etc/pulse/daemon.conf /storage/.config/pulse-daemon.conf.d

2) Open it by nano editor:

nano /storage/.config/pulse-daemon.conf.d/daemon.conf

3) Activate flat-volumes setting by removing the leading ";" character and set it to no:

flat-volumes = no

4) Save the file (Strg + S), leave the editor (Strg + X) and reboot.

pactl set-sink-volume 50% doesn't work?

Android is highly optimized for all media. All you need is the Android Kodi app for the Shield. Developing LE for the Shield would be stupid.

On LE's audio settings you should see your DAC as new output device after driver activation. Maybe the menu will show multiple DAC output entries (profiles), and you can select a mixing or non-mixing profile.

I don't have this hardware. The HiFiBerry forum can tell you more about those DAC profiles.

That's good news! So I guess you just have to activate the driver, and the default routing of the driver (not LE) will do the trick.

Add this line to config.txt:

dtoverlay=hifiberry-dacplus

Looks like Dolby is selling this as per-board-license: click. So we are currently not involved.

The routing directly from DAC's input to DAC's output would be the perfect routing (lowest latency). As I said, I don't think this routing is possible due to the DAC's hardware design. Maybe there is a hidden option to do this anyway, but only HiFiBerry can tell you that.

Quote from Anke

I have another issue as well:

Norwegian censorship stops DNS resolving of opensubtitles.org

kodi's SOCKS5 with DNS is not supported by PriveteInternetAccess (aka PIA) that I use. (not the DNS part)

nor does PIA support RPi .. their (rather nice) Linux client is great on Ubuntu - so that could indicate that I really should just use a weak (not-noisy) SFF computer or something like that for the job.

Please open a new thread for this question.

I close this one to make it not too messy.

If you go DAC -> RPi -> DAC, then the RPi will become a bottle neck, because incoming DAC data have to go to RPi's bus controller, and then back to GPIO. I belief that the GPIO itself is another bottle neck, because probably the same pins will be used for input / output.

Even if such a pass-through-over-RPi function exists, it has to be managed by the HiFiBerry driver, not by LE. Again: Ask the HiFiBerry support to get the definite answer. They are friendly and firm. On a regular PC you would be right, and you would get the desired routing options, but an RPi is different.

Original post is here. That's why I close this copy bot thread.

I think I understand your setup now. You want a pass-through function inside the HiFiBerry DAC. This is not part of LE's audio.

Those DAC's are made for RPi -> DAC and DAC -> RPi, but not DAC -> DAC. Ask the HiFiBerry support to be sure (they are pretty good).

I suggest to use something like this instead (and hope for low latency).

Yes, reducing video quality to increase audio quality points to a weak data bus. That's why your above RPi sound card will not do the trick.

If you search for best audio compatibility (Dolby Atmos etc.), and price doesn't matters, then have a look at the Nvidia Shield TV. It's probably the best streaming box (also available as "pro" version).

If you want to stay with LE, an Intel NUC will provide better performance. I don't have this, so other users should verify AAC / H265 compatibility before you buy.

OK, looks like AAC codec is the problem. Another user made an interesting point: He changed the HDMI mode to make it work - click.

PS: I just mean that HDMI 5.1 / 2.1 / 2.0 audio is no official standard.

Next things you can try:

1) disable buffering (<buffermode>3</buffermode>)

2) test latest nightly builds (maybe it's already fixed)

3) if 1) and 2) fails, provide a link to a complete log file

Quote from TomB19

I have my RPi plugged into a switched AVR outlet. It's rude but has been working great for some months.

Too rude, because instant power-off without shutdown procedure can destroy your file system.

Maybe you don't know it, because this is your first RPi. The RPi doesn't shutdown completely. If you want a complete shutdown (zero power consume on the board), you have to use additional hardware.

A benefit of the incomplete shutdown is the option to power-on by GPIO button press. You can buy RPi 4B cases with power buttons, or make your own.

I assume you want to connect an RS232 interface to the serial GPIO pins of an RPi. To get the Python GPIO library, all you have to do is to install the "Raspberry Pi Tools" add-on. Start your Python script with this lines to import that add-on lib:

#!/usr/bin/python

import sys
sys.path.append('/storage/.kodi/addons/virtual.rpi-tools/lib')
import RPi.GPIO as GPIO

This is hard to answer, because so much data is missing on your description.

What exactly do you want to do?

What's your hardware (RPi version, HifiBerry version)?

Which input / output ports do you want to use?

Do you want to use a MIDI device connected to the RPi?

If the answer to last question is yes, then LE is not the right OS for you. Instead you'll need a real-time (RT) kernel OS (like Patchbox OS). That will provide low latency MIDI processing.