Openelec Build for OPI PC and 2 now with HW decoding

lymon · Published in 2015-12-11 22:38:11

runnerway replied at 2015-12-11 22:29
If i edit uEnv.txt (in the same folder as KERNEL and SYSTEM) with the one you posted my screen rem ...

yes, it the uEnv in the fat partition, which also contains the Kernel/system (or /flash in Openelec)

I am using the "OpenELEC-OPi2.arm-7.0-devel-20151211000653-r21671-g0770e97" image install on a Orange Pi PC (I know this image is supposed to be for a Orange Pi 2, but I don't mind to only have 1 working USB port)
1920x1080@60 works fine on my end.

jernej · Published in 2015-12-11 22:52:45

Edited by jernej at 2015-12-11 16:02

@swordfish,
thanks for helping with image building. Could you update link to my latest build, which is in comment 70#? I strongly advise that you also update your Orange PC build with same values as bronco suggest to prevent overheating. I can understand that CPU speed was an issue when it was SW decoded and it still can be sometimes when playing videos with high resolution, but once direct rendering (zero copy) is implemented, I think CPU speed will become completely irrelevant.

BTW, I changed default resolution to 1920x1080@60Hz which makes things a bit slower, I think.

@pieta,
you are probably using kodi git master code? Kodi 16 Jarvis still has this function but it seems that in the latest Kodi git code this function is not present anymore. I will remove CDVDVideoCodecSunxi :: GetPlayerPts () function in future patch because it is not really needed. For now, you can remove it too and change this line:

ret = DecodeVideoStream(m_videoCodec, 0, 0, m_DropBFrameIfDelay, GetPlayerPts());

Copy code

to

ret = DecodeVideoStream(m_videoCodec, 0, 0, 0, 0);

Copy code

Until direct rendering is implemented, 4K video is complete overkill for GPU rendering anyway.

@bodrick,
I can't help you with HDHomerunPrime, sorry. You can press "O" during playback to see which codec is used. If it's cedarx-something then HW acceleration is used and it shouldn't lagging. If thats the case, please try to find some sample video file with same problem and report it here or on github.

@lymon,
can you provide description of those kernel parameters you provided?

fritz · Published in 2015-12-11 23:35:12

I was just wondering from where this fb0_format = 10 comes in your opi2 fexfile.
the value 10 is not documented anywhere.
it was a mistake, right?

jernej · Published in 2015-12-11 23:53:01

fritz replied at 2015-12-11 16:35
I was just wondering from where this fb0_format = 10 comes in your opi2 fexfile.
the value 10 is not ...

I didn't research it. They were taken from loboris fex.

fritz · Published in 2015-12-11 23:53:39

@jernej
you may rename your OpenELEC-OPi2 into something more appropriate.
It should work with/for all H3 devices.

jernej · Published in 2015-12-12 00:03:28

fritz replied at 2015-12-11 16:53
@jernej
you may rename your OpenELEC-OPi2 into something more appropriate.
It should work with/for a ...

I know, but the question is how many links I will break with that change? Kodi has also an old name, e.g. xbmc, in his github url.

lymon · Published in 2015-12-12 03:28:12

I just discovered by accident that the onboard IR-receiver on the OPI seems to be linked to /dev/input/event1
(I had Kodi react to some buttons on a western digital ir-remote control that I have.)

this is confirmed by /proc/bus/input/devices:

I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="sunxi-ir"
P: Phys=RemoteIR/input1
S: Sysfs=/devices/virtual/input/input1
U: Uniq=
H: Handlers=sysrq kbd event1
B: PROP=0
B: EV=100003
B: KEY=ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff fffffffe

I am now trying to "link" /dev/input/event1 to lircd somehow, but event1 does not support the LIRC ioctl interface and also once kodi is running it locks event1, so other services/daemons can no longer access it.
It would be nice to have the onboard IR receiver work with Lircd so basically any IR-remote can be used to control Openelec

momo · Published in 2015-12-12 03:31:11

Edited by momo at 2015-12-12 03:32

Just checked the latest build on my OPi PC and it works great

.

2 things that are bothering me:
1. Is it OK that I can not wake it after entering suspend mode?
2. there is green stripe at the bottom of the screen when I am watching HEVC videos.

lymon · Published in 2015-12-12 03:51:15

Edited by lymon at 2015-12-12 04:03

jernej replied at 2015-12-11 22:52
@lymon,
can you provide description of those kernel parameters you provided?

@jernej,

video=mxcfb0,
This display specifier defines the ordering of display devices under Linux.

dev=X,
specifies the output interface used for the display.
(Options are lcd for the parallel RGB interface, ldb for the LVDS interface and hdmi for the HDMI transmitter.)

displayname or resolution,
can either define a named panel such as LDB-XGA or CLAA-WVGA or a resolution in VESA Coordinated Video Timings format.

if=depth,
Defines the output format at the transmitter.
Options include RGB666 for 18-bit panels and RGB24 for 24-bit displays.
(Note: this does not define the in memory bit depth of the frame buffer.)

bpp=X,
Defines colordepth (the number of bits used per pixel)

runnerway · Published in 2015-12-12 05:09:03

momo replied at 2015-12-12 03:31
Just checked the latest build on my OPi PC and it works great .

2 things that are bothering me:

Confirmed the green stripe at the bottom of the screen with H265 videos.

@jernej Any ideas?