New intel graphics work great with 10bit hevc
Posts by lrusak
-
-
This is a bug report. That is why it was reported in development > bug reports.
You should file it at the Kodi forums. We simply consume their application.
-
I think you are confused a little bit.
On amlogic hardware you get the option to enable/disable using amcodec completely. With it enabled you get the options for mpeg2, mpeg4, and h264. The options are off, HD only, and always. These options have nothing to do with video scaling. These options allow using the hardware video decoder that is present in amlogic chipsets.
Because amlogic uses it's own decoder and renderer there no possibility to use the HQ scalers when amcodec is in use. The same goes for mediacodec on android.
I can show you the code if you'd like.
PS. I'm not sure what you are talking about with the NUC. It has completely different HW accel options however the HQ scalers can be used all the time when VAAPI is enabled or not.
-
I was told to upgrade because of the many changes in pvr and to verify if bugs are fixed. 8.x is totally unstable. Only cvh 8.2 bild is stable. LE 8.2 is broken since every release after 7.90.010.
That's very helpful thanks. Why not file bug reports instead? Everyone else says 8.2 is rock solid
-
-
The installer will only use an entire hard disk. Only install to a disk that can be wiped.
LibreELEC has a backup and restore utility in the LibreELEC settings add-on that you can leverage.
-
You're using pre-alpha builds. If you want stability use 8.2.x
-
kodi isn't upgraded or downgraded with the backup.
You have to upgrade or downgrade LibreELEC to change the kodi version
-
might be able to use the LCDproc add-on if your lcd has a supported driver available.
-
Ps, tried using the hyperion tool to directly install to my Odroid C2, with no luck - "unknown architecture" or similar errors
Don't do that. Just install hyperion from our repo
-
Thanks for the reply Irusak.
Ah that's disappointing, I see it can be done in XMBC quite easily, shame that Libreelec doesn't allow it.. Ah well.
I'm not sure what you mean. What do you mean by "I see it can be done in XMBC quite easily" ???
Your best bet would be to use some UPNP player (or kodi) on android and just push content to it via UPNP.
-
You can try and use docker maybe to run teamviewer.
-
simple: the box cant hibernate or suspend. It is ON or OFF.
bingo
-
This is why it won't happen.
Code
Display MoreLibreELEC:/tmp # ldd opt/teamviewer/tv_bin/TeamViewer linux-vdso.so.1 (0x00007fff80d8d000) libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007fcd1c4a9000) librt.so.1 => /usr/lib/librt.so.1 (0x00007fcd1c2a1000) libdl.so.2 => /usr/lib/libdl.so.2 (0x00007fcd1c09d000) libQt5WebKitWidgets.so.5 => not found libQt5X11Extras.so.5 => not found libQt5DBus.so.5 => not found libQt5Quick.so.5 => not found libQt5Qml.so.5 => not found libQt5WebKit.so.5 => not found libQt5Network.so.5 => not found libQt5Widgets.so.5 => not found libQt5Gui.so.5 => not found libQt5Core.so.5 => not found libm.so.6 => /usr/lib/libm.so.6 (0x00007fcd1bd54000) libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007fcd1bb36000) libc.so.6 => /usr/lib/libc.so.6 (0x00007fcd1b78b000) /lib64/ld-linux-x86-64.so.2 (0x00007fcd1c6ea000) libsystemd.so.0 => /usr/lib/libsystemd.so.0 (0x00007fcd1c89a000)
We are not installing Qt into LibreELEC
-
Did you make sure they device was connected when you got those logs?
-
No bluetooth audio device is connected in your logs.
Perhaps bluez doesn't recognize that it is a bluetooth audio device or the device doesn't advertise that it is one.
-
I have no objections to that really. I don't really know why we don't offer it in the first place
-