Posts by Klojum

Please know that this is an English-only forum. If necessary, use tools like Google Translate for an english version of your postings.

For proper video processing, the GPU memory needs to be set to at least 320 MB on the RPi4. If that hasn't been set yet, please do so.

Also, a kodi.log file could be informative as to which processes are possibly running in the background.

The watched and resume statuses need to be activated in the advancedsettings.xml file, if you want to keep/export those settings.

During the export start, you can indicate if you want to export the fanart or not. And, there is a simple command to remove all the .jpg files from your drives, should that still be necessary. On the other hand, the default info provider TheMovieDB has cleaned out its fanart quite a bit, so rescraping your media collection could result in lots of empty posters or backgrounds. I'd suggest keeping the jpg files for now. One single big video file probably takes up more disk space than most of your fanart combined.

Quote from hachel

Does anybody have an idea why it goes up when it has to display video posters?

Kodi's listing pages are not static, they are being displayed at 30-60fps (whatever screen settings are active).

And is a rise by 8-9 percent really that much of a problem?

It's pretty simple: LibreELEC has no (S)FTP server onboard.

OSMC is more a full OS, while LibreELEC is a 'just enough' solution for Kodi.

The only file server in LibrELEC is Samba.

For external (backdoor) access you can use SSH, and also set up your own keys.

Quote from Wrestler7

I’ve turned the fans up to max so temperatures usually stay far below 40°C

So you prefer to have a very loud RPI case..? Really, the RPi's CPU can easily handle higher temperatures than that. There is no need to turn it into a refrigerator.

Quote from CloneSnow

I have no idea what it is

And so do we, for now. A couple of things:

- <buffermode> 1 </buffermode>

Don't place spaces in your xml values. It could be misinterpreted.

I'd remove the whole buffering section for now.

Also, you are providing only part of the full Kodi log file. We cannot solve puzzles with pieces missing.

Moreover, you first need to enable 'Debugging' in the Kodi settings, restart LibreELEC, and then provide a new Kodi log file via a pastebin website, as we prefer to keep our forum server as clean and trimmed as possible. We have no need to put useless lumps of text on our servers till the ends of time.

Quote from jfabernathy

/boot on raspbmc and /flash on openelec)

I think that part needs to be updated...

Edit: done

Changing a provider should not change your local network addresses, unless you also have a new/different router.

In a decent router you should be able to change the DHCP pool from which all your local network devices get their IP addresses.

In a decent router you should also be able to fixate certain IP addresses for selected network devices, which is recommended for (for example) NAS devices and other servers.

In your router's summary or other info, you should also see the (new) IP address of your NAS. Once you know the new IP address, you can change it in Kodi's advancedsettings.xml file, as you previously did for connecting to the shared library. With that new IP address, Kodi should work again.

Quote from JohnWayne111

Other question: can i expect more performance from SSD against usb 3.1?

Since when does a RPi4B have a USB3.1 port?

I think MiniDLNA has better chance at running in LibreELEC: See MiniDLNA tested and working on on LE 9.x

Quote from Master One

What exactly is the problem with HDR?

HDR comes in not one but many flavors, and afaict, different hardware manufacturers treat HDR differently.

As a rule: don't try to buy the hardware that should last at least 5 years. there is no such thing. Technology goes fast. Two, three years ago HEVC was all the rage, now it's gonna be AV1, for which there is only scarce hw acc support right now.

Quote from FeFiFoFum

I have had this problem with Kodi many many many times over the years, no idea why.

Maybe you're doing something wrong.

Quote from FeFiFoFum

What am I doing wrong?

Where is the kodi.log file?

HDR is currently still the problem factor.

Next time, please use a pastebin website for your dmesg listings.

It's kind of useless to store all that text on our own forum server till the end of times.

Quote from openbaffle

will it be possible for you to post the method of dual boot and grub

Just enter the correct details in Ubuntu's /etc/grub.d/40_custom file.

Not sure exactly how I got multiple setups, I think I created the initial one and then simply copied the two partitions a couple of times using GParted. Entering the correct drive & partition numbers in the 40_custom file does the rest.

Three LibreELEC setups here, mind to use your own root, boot and disk settings.

menuentry "LibreELEC Milhouse" {
set root=(hd1,5)
linux /KERNEL boot=/dev/sdb5 disk=/dev/sdb6 quiet
}

menuentry "LibreELEC 10.x" {
set root=(hd1,3)
linux /KERNEL boot=/dev/sdb3 disk=/dev/sdb4 quiet
}

menuentry "LibreELEC 9.x" {
set root=(hd1,1)
linux /KERNEL boot=/dev/sdb1 disk=/dev/sdb2 quiet
}

Then with the sudo update-grub2 , "things should work".(tm)

Quote from DaRuutz

I installed the Qobuz-app but for some reason it won't work.

As per information from the Kodi website, apparently Qobuz changed it API (= access to the back-office, so to speak) about a year ago, and no real updates have been made to the Qobuz Kodi add-on ever since.

I'm using separate drives for Ubuntu and LibreELEC. But that shouldn't make a difference when setting up GRUB2.