Posts by Da Flex

rhino I've been noticed that the Milhouse update channel is out of date. Instead use the latest RPi2 test build from here. It's based on the brand new Kodi 18.9. You can update by putting the image into the /storage/.update folder and reboot. Be careful: make a backup before the update or use another microSD.

Watch our nightly builds, probably Kodi 18.9 will fix it (known bug).

Quote from rhino

I'm new to Libreelec, Is there a way to update Kodi to 18.9? Is an update coming for Libreelec?

No ETA for major releases, but you can switch to the nightly builds update channel.

I'm not sure whether I understand the question. When LE is the selected input source of the TV, all CEC commands will stay in LE. You can't control TV functions at that mode.

If you switch back to TV tuner as your input source, then you should be able to change the TV channel with your RC. Does this work?

Which LE hardware do you use? Do you use the original RC of your Samsung TV?

Friedhofsblond Try this or eject command on terminal.

Play with CEC options at Settings -> System -> Input -> Peripherals -> CEC Adapter.

An illegal repo stops our support immediately. Closed.

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).