Ohh. I'll stay at htpc then. OPi will be a torrent server with Armbian. Thank you for all your help to Jernej!
Early community images for H3, H6 and A64
-
jernej -
September 13, 2018 at 8:00 PM -
Closed -
Thread is Unresolved
-
-
BTW, streaming was not actually well tested. Just few seconds once. I guess error handling has to be improved, but that is known already.
Zattoo works pretty decently here, including dash streaming.
So far the best zattoo client for me.
-
I suggest you start from GitHub - jernejsk/LibreELEC.tv: Just enough OS for KODI
1. Add A20 specific subfolder here: https://github.com/jernejsk/libreelec.tv/tree/hw_dec_ffmpeg/projects/allwinner/devices Check H3 subfolder what it has to contain. You can just copy H3 folder as a starting point and check every file what needs to be changed. You have to definitely remove all Linux patches and add A20 specific ones. You have to add patches from Paul Kocialkowski where he added support for YUV (kernel/git/next/linux-next.git - The linux-next integration testing tree - everything from 2018-11-27 and newer) and support for DRM format modifiers (patches are somewhere on some mailing list, probably dri-devel). Remove all U-Boot patches.
2. Enable A20 specific drivers in kernel config: linux.arm.conf
3. Add boards to U-Boot helper script: LibreELEC.tv/uboot_helper at hw_dec_ffmpeg · jernejsk/LibreELEC.tv · GitHub
4. Extend FFmpeg support for using modifiers in V4L2 request codec. But if you come to this point, ping me and me and others could assist you.
After that, there are various small tasks, but most important one - hw video playback, will be already done.
In general, make bootable image first (points 1 - 3). However, to do that, you don't need any Linux patches, so that should be really easy.
Hello.
According to Your recipe I created Libreelec for Bananapi A20 arm. I applied patches from kernel/git/next/linux-next.git, but I am confused about support for DRM format modifiers. Please, can You suggest a path?
Thanks in advance
-
- Official Post
I applied patches from kernel/git/next/linux-next.git, but I am confused about support for DRM format modifiers. Please, can You suggest a path?
There are no ffmpeg patches for this yet. Maybe wait until they are ready? Or you want to be proactive and help us with programming?
-
There are no ffmpeg patches for this yet. Maybe wait until they are ready? Or you want to be proactive and help us with programming?
Hi,
I would like to help but I am not an expert in this field (ffmpeg, hw video acceleration and so on).
When it comes to drm format modifiers patches i found this: [RESEND,v5,04/23] drm/sun4i: frontend: Pass DRM format info to input format helpers - Patchwork I do not know if it's all and if it's enough.
-
- Official Post
I do not know if it's all and if it's enough.
You need whole series, not just that patch. Series is enough for kernel side, but ffmpeg side is still missing.
-
Hello. I want to connect orange pi pc to the old TV. How to make an analog TV output on this assembly.
Google Translate. I am Russian-speaking and it is very difficult for me to understand the text on this forum.
Здравствуйте. Хочу подключить orange pi pc к старому телевизору. Как сделать аналоговый тв выход на данной сборке.
Я рускоговорящий и мне очень сложно понимать текст на этом форуме.
-
Hello. I want to connect orange pi pc to the old TV. How to make an analog TV output on this assembly.
Google Translate. I am Russian-speaking and it is very difficult for me to understand the text on this forum.
Здравствуйте. Хочу подключить orange pi pc к старому телевизору. Как сделать аналоговый тв выход на данной сборке.
Я рускоговорящий и мне очень сложно понимать текст на этом форуме.
I think the best solution will be hdmi to analog adapter like this:
-
- Official Post
How to make an analog TV output on this assembly.
Analog TV out driver is not yet completed, although anyone with some Linux driver skills could use existing but old patches for that functionality.
-
I think the best solution will be hdmi to analog adapter like this:
I've thought about it, but there's a more budget option
Analog TV out driver is not yet completed, although anyone with some Linux driver skills could use existing but old patches for that functionality.
To my great regret, I am very unfamiliar with Linux. I found instructions on how to turn on the TV output to Arabian. Here is the reference Настройка ТВ выхода/TV out на Orange Pi PC под Armbian - MicroPi . I don't know if this will work on libreelec. So realistically do or driver need to wait?. How long to wait for the driver?
Thank you for answering so quickly.
-
- Official Post
Here is the reference
This is an English-only forum. This also applies for linked webpages, as many of us don't understand Russian or other Balkan languages.
-
Installed the system on an orange pi pc and got a few problems.
The remote is not working. There are 2 remotes, one of them works with Kodi 18 on 905 CPU and the settings (conf) remote I have. Tried manually re-create the console database via shh.
"Now hold down button "key_power".
Something went wrong: Cannot decode data
Please try again. (23 retries left)"
My TV(Samsung) does not see HDMI-SEC. 905 although on the console it works. Orange can only turn my TV on and off, which is very strange.
In system settings I did not find the item hdmi-sec.
The most important thing is why the remote control does not work, it is inconvenient to control the mouse.
What am I doing wrong?
-
Bought today Orange Pi PC board to mess around with. Built an image from jerjejsk git. First impressions:
1. It can actually play video!
2. Tested with my DVBSky S960 satellite DVB tuner. It works well. I used VDR + VNSI + OSCam.
GUI is slow compared to RPi3 - looks like it is limited to 10 fps of something like that. On RPi there is an option in "Player"-->"Videos"-->"Processing"-->"Limit GUI updates during playback" and when it is set to "Unlimited" - GUI is very smooth. Is it possible to implement it here?
-
Installed the system on an orange pi pc and got a few problems.
The remote is not working. There are 2 remotes, one of them works with Kodi 18 on 905 CPU and the settings (conf) remote I have. Tried manually re-create the console database via shh.
"Now hold down button "key_power".
Something went wrong: Cannot decode data
Please try again. (23 retries left)"
My TV(Samsung) does not see HDMI-SEC. 905 although on the console it works. Orange can only turn my TV on and off, which is very strange.
In system settings I did not find the item hdmi-sec.
The most important thing is why the remote control does not work, it is inconvenient to control the mouse.
What am I doing wrong?It's very easyInfrared Remotes [LibreELEC.wiki]
There is very easy way to have success!
According to Infrared Remotes [LibreELEC.wiki] and my experience
Delete the file: \storage\.config\lircd.conf if exists.
Find your remote in \usr\lib\udev\rc_keymaps\
If You want to change something in found file; copy it to folder \storage\.config\rc_keymaps\ and there you can do it.
Run command: ir-keytable
You should see something like:
Found /sys/class/rc/rc0/ (/dev/input/event1) with:
Name: sunxi-ir
Driver: sunxi-ir, table: rc-empty
lirc device: /dev/lirc0
Supported protocols: other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd
Create file \storage\.config\rc_maps.cfg with this content:
sunxi-ir * tevii_nec
-
There is very easy way to have success!
According to Infrared Remotes [LibreELEC.wiki] and my experience
Delete the file: \storage\.config\lircd.conf if exists.
Find your remote in \usr\lib\udev\rc_keymaps\
If You want to change something in found file; copy it to folder \storage\.config\rc_keymaps\ and there you can do it.
Run command: ir-keytable
You should see something like:
Found /sys/class/rc/rc0/ (/dev/input/event1) with:
Name: sunxi-ir
Driver: sunxi-ir, table: rc-empty
lirc device: /dev/lirc0
Supported protocols: other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd
Create file \storage\.config\rc_maps.cfg with this content:
sunxi-ir * tevii_nec
I do it, but my OrangePi PC don't get RC commands =(
My rc_maps.cfg:
My keymap
Code
Display More$> cat /storage/.config/rc_keymaps/my_remote # table samsung, type: NEC 0x70760 KEY_UP 0x70761 KEY_DOWN 0x70765 KEY_LEFT 0x70762 KEY_RIGHT 0x70768 KEY_SELECT 0x70747 KEY_PLAY 0x70746 KEY_STOP 0x70758 KEY_BACK 0x70704 KEY_1 0x70705 KEY_2 0x70706 KEY_3 0x70708 KEY_4 0x70709 KEY_5 0x7070a KEY_6 0x7070c KEY_7 0x7070d KEY_8 0x7070e KEY_9 0x70711 KEY_0 0x70748 KEY_NEXT 0x70745 KEY_PREVIOUS 0x7072d KEY_CLEAR
After boot my ir-keytable dont read setting:
Code$> ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event0) with: Name: sunxi-ir Driver: sunxi-ir, table: rc-empty Supported protocols: other rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp Enabled protocols: bus: 25, vendor/product: 0001:0001, version: 0x0100 Repeat delay = 500 ms, repeat period = 125 ms
And If I load my keyfile manualy, Kodi dont see comands (but ir-keytable read and decode key to command) =(
Code
Display More$> ir-keytable -c -w /storage/.config/rc_keymaps/my_remote Read samsung table Old keytable cleared Wrote 21 keycode(s) to driver Protocols changed to nec $> ir-keytable -t Testing events. Please, press CTRL-C to abort. 467.546112: event type EV_MSC(0x04): scancode = 0x70761 467.546112: event type EV_KEY(0x01) key_down: KEY_DOWN(0x006c) 467.546112: event type EV_SYN(0x00). 467.654209: event type EV_MSC(0x04): scancode = 0x70761 467.654209: event type EV_SYN(0x00). 467.890052: event type EV_KEY(0x01) key_up: KEY_DOWN(0x006c) 467.890052: event type EV_SYN(0x00).
-
I do it, but my OrangePi PC don't get RC commands =(
My rc_maps.cfg:
My keymap
Code
Display More$> cat /storage/.config/rc_keymaps/my_remote # table samsung, type: NEC 0x70760 KEY_UP 0x70761 KEY_DOWN 0x70765 KEY_LEFT 0x70762 KEY_RIGHT 0x70768 KEY_SELECT 0x70747 KEY_PLAY 0x70746 KEY_STOP 0x70758 KEY_BACK 0x70704 KEY_1 0x70705 KEY_2 0x70706 KEY_3 0x70708 KEY_4 0x70709 KEY_5 0x7070a KEY_6 0x7070c KEY_7 0x7070d KEY_8 0x7070e KEY_9 0x70711 KEY_0 0x70748 KEY_NEXT 0x70745 KEY_PREVIOUS 0x7072d KEY_CLEAR
After boot my ir-keytable dont read setting:
Code$> ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event0) with: Name: sunxi-ir Driver: sunxi-ir, table: rc-empty Supported protocols: other rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp Enabled protocols: bus: 25, vendor/product: 0001:0001, version: 0x0100 Repeat delay = 500 ms, repeat period = 125 ms
And If I load my keyfile manualy, Kodi dont see comands (but ir-keytable read and decode key to command) =(
Code
Display More$> ir-keytable -c -w /storage/.config/rc_keymaps/my_remote Read samsung table Old keytable cleared Wrote 21 keycode(s) to driver Protocols changed to nec $> ir-keytable -t Testing events. Please, press CTRL-C to abort. 467.546112: event type EV_MSC(0x04): scancode = 0x70761 467.546112: event type EV_KEY(0x01) key_down: KEY_DOWN(0x006c) 467.546112: event type EV_SYN(0x00). 467.654209: event type EV_MSC(0x04): scancode = 0x70761 467.654209: event type EV_SYN(0x00). 467.890052: event type EV_KEY(0x01) key_up: KEY_DOWN(0x006c) 467.890052: event type EV_SYN(0x00).
Sorry, I forget one important line in my previous answer:
Code# ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event1) with: Name: sunxi-ir Driver: sunxi-ir, table: rc-empty lirc device: /dev/lirc0 Supported protocols: other lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp Enabled protocols: lirc nec bus: 25, vendor/product: 0001:0001, version: 0x0100 Repeat delay = 500 ms, repeat period = 125 ms
You have to see some enabled protocol (nec)
If there is nothing to see, You can enable it manually:
Why not allowed when loading is a great secret!
-
any eta when this will move from beta to kodi 18.1 ?
-
- Official Post
any eta when this will move from beta to kodi 18.1 ?
I can upload new updates today, but except Kodi update, 4K H264 decoding and maybe HDMI CEC fix, nothing else would be new. I'm still struggling with some problematic H264 and HEVC videos.
If you think that's ok, then I can do it.
-