Posts by HiassofT

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

I noticed there's an open issue about the 7" display on RPi kernel github: Full KMS does not work with pi4 and official touchscreen on kernel 5.10.1 · Issue #4020 · raspberrypi/linux · GitHub

That issue and 6by9's post on the RPi forum also mention that "ignore_lcd=1" should be added to config.txt How does the official Raspberry Pi 7" Touch Screen work? - Raspberry Pi Forums

There's also a WIP PR to update the 7" driver WIP: KMS DSI panel config by 6by9 · Pull Request #3985 · raspberrypi/linux · GitHub - when this makes it into the RPi kernel we'll also include it in LE.

so long,

Hias

Adding dtparam=audio=on to config.txt should enable analog audio output.

so long,

Hias

Now this is really odd. vc4-kms-v3d will load vc4-kms-v3d-pi4 on RPi4 (due to some magic trickery of the firmware using overlay-map.dtb) so the result should be exactly the same.

Can you post your config.txt file?

so long,

Hias

I think adding dtoverlay=vc4-kms-dsi-7inch to /flash/config.txt should do the trick.

/flash/overlays/README says:

Name:   vc4-kms-dsi-7inch
Info:   Enable the Raspberry Pi DSI 7" screen.
        Use edt-ft5406 for the touchscreen element.
        Requires vc4-kms-v3d to be loaded.
Load:   dtoverlay=vc4-kms-dsi-7inch
Params: <None>

vc4-kms-v3d is what LE10 on RPi is using (loaded via distroconfig.txt)

so long,

Hias

spooker most likely these log lines are unrelated to your audio issues. I spotted them, too, and was discussing that with popcornmix - our understanding is that the ErrorAdjust should lead to dropped or duplicated video frames - not audio issues - as reported here: RPi 4B - Periodic repeated frames, CDVDClock::ErrorAdjust in log · Issue #19263 · xbmc/xbmc · GitHub

I suspect you are running into the hardware fifo under/overrun issues that I've not been able to reproduce locally yet. Having a sample video or some other method to reliably reproduce the issue would help a lot.

so long,

Hias

I just tested and this affects only RPi0-3 on LE9.2, as they use an older firmware version. RPi3 on LE master is fine (the bootloader check returns "unknown" here).

Just ignore the "Command not registered" message on LE9.2, it's harmless.

so long,

Hias

mglae thanks, I'll take care about it.

so long,

Hias

Quote from lolek

Tbh didn't check logs for this but usually when there was a sound problem I could hear it right away. I'll try to check the log next time.

That's what I meant - I should better have written "keep an ear on the hickups" If sound is fine there's no need to look into logs.

so long,

Hias

lolek thanks, mainly keep an eye on the audio hickups and "broken pipe" log messages you initially reported - I think current nightly builds should be fine now though.

There seem to be occasional audio glitches with HD audio passthrough (which won't show up in logs), we are looking into it but so far I could not reproduce those here.

HDR output issues, like banding in the clouds, are also known - fixing those will take a while, kodi and video driver are currently missing several important bits and pieces.

Occasionally dropped or duplicates video frames is a different issue. We are aware of it, see also RPi 4B - Periodic repeated frames, CDVDClock::ErrorAdjust in log · Issue #19263 · xbmc/xbmc · GitHub

so long,

Hias

mrlindstrom HDR output on RPi4 isn't fully feature complete yet and most likely your Optoma doesn't like that.

It will take a while until all the missing bits and pieces are implemented in kodi and the video driver.

BTW: testing with nightly images is fine, all neccessary changes in my testbuilds are included.

so long,

Hias

You have to use "myoutput" as ALSA device in chrome - if you direct it to hdmi:... it'll bypass softvol, that's only in your "myoutput" PCM

so long,

Hias

It's best to use card names instead of numbers as the latter may change (eg if you plug in a USB audio card).

Simply run "aplay -L", that will show you the available PCMs with card names - then use the same PCM as you used in kodi. eg here on RPi4 it looks like this:

...
hdmi:CARD=vc4hdmi0,DEV=0
    vc4-hdmi-0, MAI PCM vc4-hdmi-hifi-0
    HDMI Audio Output
...

"hdmi:CARD=vc4hdmi0,DEV=0" is what you use as pcm and the name after CARD= (vc4hdmi0 in my case) is your card - on intel you'll have multiple devices (DEV=...), one for each HDMI output.

You can then create .config/asound.conf like this (adapt to your PCM/card):

pcm.myoutput {
  type softvol
  slave {
    pcm "hdmi:CARD=vc4hdmi0,DEV=0"
  }
  control {
    name "PCM My Volume"
    card "vc4hdmi0"
  }
  hint.description "My Output with softvol"
}

This creates a new pcm "myoutput" with a control named "PCM My Volume". The hint is only there so you can check with "aplay -L" if your new PCM is available. It should look like this:

LibreELEC:~ # aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
default
    Default Audio Device
sysdefault
    Default Audio Device
myoutput
    My Output with softvol
...

A small gotcha is that the new mixer control will only show up after the device has been used once, so to see the new volume control you'll have to first access it. eg:

speaker-test -c 2 -t sine -D myoutput

Then you should see the new mixer in amixer output:

LibreELEC:~ # amixer controls
numid=6,iface=MIXER,name='PCM My Volume'
numid=5,iface=MIXER,name='PCM Playback Volume'
numid=2,iface=MIXER,name='IEC958 Playback Default'
numid=3,iface=MIXER,name='IEC958 Playback Mask'
numid=1,iface=PCM,name='ELD'
numid=4,iface=PCM,name='Playback Channel Map'

In alsamixer and "amixer scontrols" it will show as "PCM My", as it automatically strips "Volume" from the end.

so long,

Hias