Posts by HiassofT

Same issue as above, delete profiles.xml.

BTW: you are running a really old build, I highly recommend updating to official LE 9.2.1 or a community build which includes kodi 18.6 - that issue should be fixed there.

so long,

Hias

Better someone else comments on the deinterlacer and scaler methods, I'd guess the motion adaptive one should be fine.

Concerning audio delay see here: Delayed audio problem

so long,

Hias

I've also read that on-board analog audio output level is quite low - haven't checked myself for ages though.

TBH it's best to stay away from the on-board analog audio out if possible. The quality isn't too great and the RPi has to throw in a lot of processing power (which then missed for video decoding etc) to get a somewhat acceptable quality out of the simple 1-bit dac.

so long,

Hias

Quote from Operations

And with regards to Deinterlace method, video scaling method?

I mean "VAAPI Bob" sounds pretty cool, but no idea if it is the right choice

I can't comment on that as I'm using RPi which has different (software only) deinterlacers.

"Bob" may sound cool but actually is a pretty simple / poor deinterlacer (have to use SW bob deinterlace here on RPi4 and deinterlaced SD material looks terrible).

The "yadif" and other deinterlacers (not sure what's actually available on PCs) should work a lot better.

so long,

Hias

Quote from Operations

So if i whitelist a resolution the TV handles upscaling and NOT whitelisted than Kodi will do it?

Kodi's whitelisting logic is a bit complex/confusing but, yes, basically it's this way. If you whitelist a display mode / refresh rate then Kodi can use that if "adjust display refresh rate" is enabled in the player settings (set it to "always" or "on start/stop").

So kodi can eg switch to 1080p23.9 if you play a HD movie.

so long,

Hias

Just stick to 3840x2160 - that's the native resolution of all UHD sets (and usually marked as preferred in EDID).

Run the GUI at 50 or 60Hz and whitelist the 23.98/24/50/59.9/60 Hz modes (better NOT the 25 and 29.9/30Hz modes as that may cause havoc with interlaced content).

As for 1280x720/1920x1080 you have to check yourself if you also whitelist them (and let the TV upscale) or let kodi do the upscaling to 4k.

The LG OLEDs have pretty good scalers so I'm not really sure if kodi is able to do a better job.

so long,

Hias

The coaxial and optical S/PDIF outputs on your hifiberry card are run in parallel and both carry the same signal.

You can use the audio profile addon to quickly switch between either analog output on your RPi or digital output on your hifiberry.

so long,

Hias

Keep in mind that you have to use a 48Gbps Ultra High Speed HDMI cable if you want to use the HDMI 2.1 modes (8k or 4k > 60p).

But there's not much point in using more than 60p on a mediacenter, these high refresh rate modes are mainly useful for gamers who want to have 100-120fps in their first person shooters.

so long,

Hias

Simultaneous audio output to HDMI and HifiBerry isn't supported in Kodi.

Have a look at the Audio Profiles addon Audio Profiles - Easy switch between different audio settings

You can invoke that from a keyboard or remote button (in the latter case use "remote" instead of "keyboard" in the example keymap file from that post and eg "red" and "green" instead of "a" and "c").

so long,

Hias

Thanks for dmesg, couldn't spot anything unusual except for the warnings you posted.

Can you check if the VIA USB firmware is up to date (in LibreELEC Settings->Update)?

It could be that your drive is acting up or dying, hard to tell though - haven't seen your specific issues yet and 2 WD drives (3.5" MyBook and 2.5" MyPassport) are working fine here on RPi4/USB3.

so long,

Hias

It's hard to tell anything without full dmesg. Could be undervoltage (that'd be logged in dmesg), could be the USB HDD adapter (model/vendor would be in dmesg) or something else.

so long,

Hias

The service.tvh.manager addon is the culprit:

2020-04-16 22:03:48.401 T:2700940144 NOTICE: [service.tvh.manager] Service was running w/o user activity
 2020-04-16 22:03:54.453 T:2700940144 NOTICE: [service.tvh.manager] Instruct the system to shut down using Application

Check the addon settings or just uninstall it, not exactly sure what this addon is useful for.

so long,

Hias

Check if ntfs-3g's big_writes option is set - you should see it via "ps ax | grep ntfs".

This option is known to speed up writes a lot and it's enabled by default in LibreELEC.

xbmc:~ # ps ax | grep ntfs
684 root 0:00 mount.ntfs /dev/sdc1 /media/Sat-Hias -o big_writes,fmask=0133,uid=0,gid=0,utf8

so long,

Hias

The fix should also be in current Milhouse builds, just not the ancient 0229 one you are using

so long,

Hias

Quote from mglae

Code

2020-04-12 06:47:51.414 T:2320466800  NOTICE: ADDON: service.bluetooth-audio v9.2.0.102 installed

Bluetooth Audio Device Changer is setting the defined default audio device when starting. Change the addon setting.

Well spotted, this is most certainly the culprit.

forget my comment regarding librespot, that addon is probably fine.

so long,

Hias

Your hifiberry card seems to be detected fine.

However you have a lot of pulseaudio errors in your log and seem to be using the librespot addon. Please try with the librespot addon removed, if that fixes audio device in kodi it's best to ask in the librespot thread.

so long,

Hias

Thanks for reporting back, glad it's working now! The bugfix will be in future LE releases, we already added it to our repository.

KEY_SLEEP and KEY_WAKEUP are remapped via eventlircd, changing that is a bit tricky.

Since you got lircd working it might be best to just disable all input from the device and let lircd handle everything - then you can also easily change button mapping.

Add the following lines to your 99-zotac udev rule file, that will prevent eventlircd from picking up the input from the remote:

ACTION=="add", SUBSYSTEM=="input", KERNEL=="event*", \
ATTRS{idVendor}=="0471", ATTRS{idProduct}=="20cc", \
ENV{eventlircd_enable}="false", ENV{LIBINPUT_IGNORE_DEVICE}="1"

You'll then also need to prevent xorg from picking up the input, you can do that by creating a /storage/.config/xorg.conf file, that will then be used instead of the default xorg.conf files in /etc/X11. Pick the one matching your graphics card and add the inputclass block from the linked kodi thread there.

so long,

Hias

Basically yes. If in doubt better also run "scripts/clean" with both packages after changing PKG_VERSION or if you want to rebuild both. Otherwise game.libretro.uae might not pick up a libretro-uae change.

so long,

Hias