Posts by Klojum

Please remove all banned/illegal repositories and addons from your setup, and try to play your local NAS videos again.

Is the problem only with videos with atmos?

I have a C1037UN machine here, it does all videos okay in general.

Weird. I had no problems with a couple of Krypton builds I tested on my C1037u Ivy bridge box. And that was up to 4K rendering.

Quote from DFergFLA

I have to do this from within LibraELEC

Again LibraELEC ?!? What is wrong with LibreELEC?

You need to be in an existing folder first for the context menu to display the "Create folder" option.

First, it's LibreELEC, not LibraELEC.

On a PC, it's preferred to have the "Wait for network" option enabled. That option can be found in the LibreELEC Settings add-on.

After that, go to the addons section and update the Kodi repository. After that, all add-ons including skins in the Kodi repository should be available.

LibreELEC has its own built-in Backup/Restore tools. I suggest you simply use those.

I honestly have never used the 'Backup Add-on', so I have no idea what it specifically does different from LE's own tools.

Enable "Wait for network" in the LE Settings addon and restart LibreELEC. Kodi can be a little too quick for the network hardware to initialize.

When you have a network connection, refresh the kodi repository in the addons section.

Try looking from the /media folder and onwards.

Also, insert such a DVD and enter the following command(s) in SSH:

mount | pastebinit

blkid | pastebinit

dmesg | pastebinit

and share the URLs here.

You have found out that you cannot use 2 different screen resolutions from 1 video output. Kodi itself only supports cloned displays anyway, so two different video outputs on your NUC would not have worked anyway.

Doing xrandr commands in your own bash files is an option. The bigger challenge is to link them to a keyboard shortcut or remote control button. And that's where my skills end, I'm afraid.

You probably need to refresh the Kodi repository via the slide menu on the left in the addons section.

Also make sure you have 'Wait for network' enabled for at least 30 seconds (Pi hardware is slow).

Why not simply add the 2 tags I mentioned to your AV.xml file and see if it works?

You mean "those" not so very legal video streams?

Perhaps some typo somewhere in the file, or you saved the file with the wrong editor.

Use a text editor that can deal with Unix/Linux EOL(s), like NotePad++.

If you have SSH access, then there is no need for photos. LibreELEC has pastebinit support built-in.

Just 'pipe' the data and you will receive a URL:

For example: xrandr | pastebinit

and share that URL on the forum.

Usually laptops have a key combination for switching internal and external monitors.

Kodi does not support dual monitor with individual resolutions, it only supports clones.

Therefore, you probably get a 1366x768 screen portion on your 1080p television.

Disabling your laptop screen is key here. After that, xrandr commands in the autostart.sh file could do the rest.

Do you actually need the BerryBoot loader, or can you just install LibreELEC as is? It would avoid possible problems with updates.

So.. a 5TB hdd attached to a router.

A Raspberry Pi using WiFi.

You can see how 'big' the internal wifi antenna is, so it automatically will not win any championships for you.

Wifi situations vary on a case by case basis, so it's impossible to predict how good/bad/awful the data throughput will be in your case.

In any way: if you ever have the option to use Ethernet cable, go for it. It will simply work. Power adapters tend to give various results.

Routers are usually not the fastest servers because of their own low-powered setup. If you have a redundant pc gathering dust, put the HDD in there. It will get cooled better (external drives usually have no airflow at all), and with a proper network connection to the router, data throughput will be better.

The biggest bottleneck? Wifi, by far. Gigabit connections on the router are useless if you don't use them. The USB (2.0, 3.0) port on the router is not likely to reach full USB speeds, again because of the router's limited internal capabilities.

You talk about "large 1080p video files". What sizes are we talking about? 5GB, 25GB, 40GB? What is the current top speed of your RPi3 wifi? 2,5MB/s? That would mean a maximum support of 10Mb/s bitrate. Do your videos have a higher bitrate than that? Then prepare for video buffering. Network caching may help partially, but I think it's only a band aid. It could also wear out the microSD card on the Rpi much quicker.

It would be ever so nice if you could tell us which hardware device/box/pc you are having issues with.

And by the way, we are up to Kodi 17.5(.1) now.

Quote from overdrive

Back to my first question.

Don't you just love it when people ask more questions after everything is done?

If Docker has its own root folder for settings and/or applications, you can simply add those to the folders mention in the tar command in post #4.

If they are somewhere below in the .kodi folders, they will already be backed up.

Do you have any settings in the advancedsettings.xml file minimizing the fanart size?

2.4.1 imageres

This tag is new for v12 (Frodo), replacing <thumbsize>.

Specify the maximal resolution that art should be resized to in pixels. The width is automatically calculated as being 16/9*height. The image will be resized to fit within this size. e.g. an image that is 2000x500 will be cached at size 1280x320. An image that is 500x800 will be cached at size 450x720 using the default value of 720.

<imageres>720</imageres>

2.4.2 fanartres

This tag is new for v12 (Frodo), replacing <fanartheight>.

Specify the resolution that cached fanart should be resized to in pixels. The width is automatically calculated as being 16/9*height. Only images that are exactly 16x9 and equal to or greater than this resolution will be cached at this size - all other images will be cached using <imageres>. The default value is 1080.

<fanartres>1080</fanartres>

Default settings for the Raspberry Pi may be such to keep things like fanart easy because of the slower hardware.