Openelec Build for OPI PC and 2 now with HW decoding

PaulR · Published in 2016-4-19 17:06:16

...ature. It was partially explained on Kodi forum. Implementation of sync playback to display is impossible in Android, but might be possible Linux (Openelec) as Linux might have implementation of video reference clock. Sadly, I have no knowledge how to achieve that

see posts #4 and #22. http://forum.kodi.tv/showthread.php?tid=219796&page=2

Dima · Published in 2016-4-19 17:13:41

I think it's the problem of being limited by the kernel. Maybe when we would finally have a functioning mainline kernel, it would be possible to fix

PaulR · Published in 2016-4-19 20:36:34

At this point playback of 23.976 with this Openelec build is still better than current (5.05) Armbian's playback with hw accelerated mpv (resolution set manually to 1080p24). It's all about barely noticeable hiccups in openelec ;)

jernej · Published in 2016-4-19 23:18:42

Dima replied at 2016-4-19 10:13
I think it's the problem of being limited by the kernel. Maybe when we would finally have a function ...

Now I know why that clock reference is used

It seems that it is not so hard to implement. I will try, but before I continue to work on Kodi, I would like to sort out mess called backported media drivers.

jernej · Published in 2016-4-20 03:43:12

I'm trying to clean up the mess with backported DVB drivers, many of them are duplicated and race conditions can occur while loading. I removed old drivers and updated DVB drivers to very latest one.

Can somebody test this OPiPC image and reports how well DVB drivers work?
https://mega.nz/#F!JQpnnYLZ!0svQ37k5XHkOYR3KXMUB4A

This image also contains dvbhdhomerun driver. Can anyone test that?

Thanks.

Dima · Published in 2016-4-20 22:04:37

jernej replied at 2016-4-20 03:43
I'm trying to clean up the mess with backported DVB drivers, many of them are duplicated and race co ...

For me nothing changed compared to (very) old builds. The devices are recognized by the kernel (dmesg), but not by tvheadend.
But as I understand, I have some exotic DVB-sticks so it's not really relevant.

jernej · Published in 2016-4-20 23:29:10

Dima replied at 2016-4-20 15:04
For me nothing changed compared to (very) old builds. The devices are recognized by the kernel (dm ...

Do you know what is the problem? Maybe firmware?

Dima · Published in 2016-4-21 04:08:27

jernej replied at 2016-4-20 23:29
Do you know what is the problem? Maybe firmware?

No idea. Someone explained that the Hauppauge is too old and generic (I remember that there were a lot of driver issues back when I actually used it), and the cheap China one has too many variants due to which the exact driver is unkown.
I don't use DVB-T anyways because I don't have sufficient signal. I just tested it to play around with OpenELEC.

I actually still sometimes use the China to play around on Windows PC's (known that Linux often doesn't work, which makes sense that it doesn't work with OpenELEC). For example I listen to ATC and track ADB-S data of passing planes. I'm a bit of an aviation geek :+

keiser1080 · Published in 2016-4-23 22:43:35

Hi,

i would install hyperion for doing ambilight clone.
In order to use hyperion from any source i have a Fushicai USBTV007 Video Grabber [EasyCAP].
I don't found the driver on the laste version off openelec.
I have found a compiled version (for raspbery pi) off usbtv.ko.

But i don't know where to put the file maybe /lib/modules/3.4.110/kernel/drivers/video/ ?

could you help ?

jernej · Published in 2016-4-23 23:12:39

keiser1080 replied at 2016-4-23 15:43
Hi,

i would install hyperion for doing ambilight clone.

What exactly is hyperion? Kodi's configurator?

I see that you are not using latest test build for DVB and the like drivers. usbtv driver is already included there. Check post #911 for the link. If the driver still doesn't work, please tell me, because I suspect there might be some problem with the image.