Posts by HiassofT

Start with 2, and also send the email to Sean Young (he's the IR remote maintainer). When he acceptet your patch create a PR for LibreELEC, ideally with a link to the linux media patchwork URL.

so long,

Hias

Maschingun thanks for the info! I'd still be interested in seeing your edid, if you have time please run the command I mentioned in post 155 RE: RPi4 testbuild with HDR support

so long,

Hias

With pastekodi -c > mylog.txt you can save the log into a file - then copy it via scp/sftp to your PC and attach it here. You can also grab a ZIP with logs from the "Logfiles" smb share - and again attach it here.

so long,

Hias

smp you are forgetting that kodi/ffmpeg aren't able to decode the object-based Dolby Atmos or DTS:X (sub-)streams - AFAIK there are no open source decoders available for that.

Without passthrough you only get the core TrueHD or DTS streams that ffmpeg can decode - only AVRs and TVs can support all features of these sound formats, so HBR audio passthrough isn't just a niche feature.

so long,

Hias

Maschingun thanks for the logs!

Can you please run the following command via ssh/putty and post the output URL?

od -t x1 /sys/class/drm/card0-HDMI-A-1/edid | pastebinit

Also: did you connect the RPi directly to the TV or via the soundbar? Which soundbar are you using?

so long,

Hias

This error usually means your putty is too old.

You can also use the logfile upload function in LibreELEC settings and then post the URL you got on your TV - see also Log Files - LibreELEC.wiki

so long,

Hias

Quote from Maschingun

No one has a Solution to my Problem?

Most likely you are running into the same problem as linuxuser but we don't know for sure as you didn't post a pastekodi log.

so long,

Hias

Quote from linuxuser

any news on fixing hbr audio problem that doesnt appear to all tvs?

Not yet. It's a bit tricky and we have to be careful not to break other configurations.

so long,

Hias

Very few users seem to have been using the analog audio output and those that did complained that the quality was bad, volume level quite low and/or that they got crackling audio during video playback (which are all known issues and to fix the latter audio_pwm_mode=1 is needed in config.txt which leads to even lower quality audio output). The simple solution in most cases was to use a cheap audio HAT or USB audio adapter instead.

Therefore I didn't consider to enable on-board analog audio output by default in LE10 - the feature is still there though for those who want to live with the limitations.

so long,

Hias

You have to add dtparam=audio=on to config.txt, then the Headphone output will show up.

so long,

Hias

You have to rebuild kodi (run scripts/clean kodi) whenever you change DRIVER_ADDONS_SUPPORT to "no" - otherwise you get the error / kodi crash loop you mentioned.

so long,

Hias

If you put "Remote" in rc_maps.cfg make sure the file in /storage/.config/rc_keymaps is also named "Remote" (with upper-case "R").

If you can't get it to work run the two commands I mentioned above and post all the output you got from them.

so long,

Hias

Update from LE9.2 to LE10 and downgrade from LE10 to LE9.2 are not supported on RPi - way too man things have changed.

If you want to go back to LE9.2 you have to restore your backup.

so long,

Hias

Go for 10 - we just switched the version number in preparation for the upcoming official LE10 alpha/beta release.

so long,

Hias

You should have a file /storage/.config/rc_maps.cfg with the following content

* * Remote

and a file /storage/.config/rc_keymaps/Remote with the keymap (scancode to key mapping as you posted above).

Make sure the files are named correctly and are in unix file format (not DOS/Windows line endings) and you don't have any typos. Follow the steps described in the wiki and check if

ir-keytable -c -w /storage/.config/rc_keymaps/Remote

amd

ir-keytable -a /storage/.config/rc_maps.cfg

work without error messages.

so long,

Hias

VC1 is a weird (and also quite niche) codec and software decoding (which is using ffmpeg) is poor - even on higher performance desktop CPUs. Best recommendation is to avoid vc1 or transcode the files to H264 or H265.

I just talked to RPi devs and did a few quick tests and it looks like it could be possible to get VC1 hardware decoding back on RPi2/3 - we can't promise anything at that point though.

so long,

Hias

Mario77 I just tested on RPi3B+ and I have to correct myself a bit: only MPEG2 HW decoding is implemented (and working), VC1 is not.

so long,

Hias

Hardware decoding (with licenses) will still work on RPi2/3.

Major issues on RPi2/3 are that the video driver currently has a severe problem (video cuts out and needs reboot), GPU accelerated HEVC decoding and deinterlacing doesn't work (deinterlacing also doesn't work on RPi4).

Therefore we decided to do the initial LE10 releases only for RPi4 - RPi2 will follow later, when the major bugs are ironed out.

so long,

Hias