OSMC and Hyperion

osmc@osmckodi:~$ apt-cache search libpython
libpython-stdlib - interactive high-level object-oriented language (Python2)
libpython2-stdlib - interactive high-level object-oriented language (Python2)
libpython2.7 - Shared Python runtime library (version 2.7)
libpython2.7-minimal - Minimal subset of the Python language (version 2.7)
libpython2.7-stdlib - Interactive high-level object-oriented language (standard library, version 2.7)
libpython3-stdlib - interactive high-level object-oriented language (default python3 version)
libpython3.5-minimal - Minimal subset of the Python language (version 3.5)
libpython3.5-stdlib - Interactive high-level object-oriented language (standard library, version 3.5)
libpython3.7 - Shared Python runtime library (version 3.7)
libpython3.7-minimal - Minimal subset of the Python language (version 3.7)
libpython3.7-stdlib - Interactive high-level object-oriented language (standard library, version 3.7)
osmc@osmckodi:~$ apt-cache policy libpython3.9
N: Unable to locate package libpython3.9
N: Couldn't find any package by glob 'libpython3.9'
N: Couldn't find any package by regex 'libpython3.9'

I’m sure I saw the installer script try to install python 3.9.

What Debian version is this?
lsb_release -a

osmc@osmckodi:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

So I’m guessing it is time for this?

sudo apt-get update
sudo apt-get dist-upgrade

I’m away from home for another 4 months and cant do this via the GUI.

It can actually wait until I return if that is preferable as my house sitter is not that fussed about it.

The myOSMC app is regarded as safer.
But yeah, one way or another you need to move on - otherwise you’ll need to build yourself, pointing at older dependencies etc. Beyond the scope here.

1 Like

Upgrade solved the issue. Thanks for the prompt assistance. :+1:

Hey @hissingshark any plans to upgrade to V? Just ordered mine and would love to see this working… or did anyone already tried this on the V?

Mine is a relatively primitive setup, but preliminary tests were good. Still successfully uses the internal grabber which is the main thing for now.

If I ever move to that Hyper-HDR fork the main issue is that they don’t support an internal grabber, so we’re into buying HDMI/USB peripherals…

1 Like

just got my V and was able to use your script to compile it from source. just replaced the relevant vero3 packages. so far it seems working fine :slight_smile:

1 Like

Great!

I’d forgotten that was in there! I’d added it out of habit because of my emulator work, but we don’t actually need it here as far as I can tell. As it is, the binaries are common to Vero 4k and Vero V.

Delighted to see somebody using the build function mind you - that was a lot of effort Why were you building your own?

good question, thought building it would might strengthen the chance to get it working?! didn’t even think of it to just to try the prebuild binaries…

I’m not going to cheapen the moment with an “eye roll emoji”.

3 Likes

Hey everybody,

my Vero V should arrive today - so I’ll definetly try to use the prebuilt route :stuck_out_tongue:

Good to know it should work on the ‘V’ as well…
Otherwise I’ll let you know :smiling_imp:

cheers
Anthrax

1 Like

Hi @hissingshark,

bad news: Release Hyperion 2.0.16 · hyperion-project/hyperion.ng · GitHub

:wink:

cheers
Anthrax

i get this error while try to forward. is there a solution?
image

Vero 4k

New versions of the hyperion needs mDNS for discovery forwarding targets.

You need to build hyperiond with enabled ENABLE_MDNS option with hissingshark’s toolkit:

sudo ./install.sh a93d79b #if you want 2.0.16 version

choose “Build from source”, enable recommended flags and additionally ENABLE_MDNS, then follow the steps of the wizard.

Or if you brave enough you can use binaries that I compiled for myself for the same scenario on vero4k: link.

i get everything to work but when i play something the screen just gets black. i see subtitles and all

Thanks for the tip on that one. I’ll add that on my next set of binaries.

2 Likes

But useful functions have also been added. You might also find CEC event handling useful. It’s allows to simply turn the backlight on and off along with TV.

CEC event handling depends on additional packages on Vero: vero3-libcec-osmc and vero3-libcec-dev-osmc for building. But the dependency packages are maked from acorns and logs, and therefore provided libcec.so not included in global LD_LIBRARY_PATH, without which hyperion runs with an error.

I simply made symlincs to /usr/lib/ to mitigate this problem

sudo ln -s /usr/osmc/lib/libcec.so.6.0.2 /usr/lib/libcec.so
sudo ln -s /usr/osmc/lib/libcec.so.6.0.2 /usr/lib/libcec.so.6
sudo ln -s /usr/osmc/lib/libcec.so.6.0.2 /usr/lib/libcec.so.6.0.2

but may be you will find better solution to maintain this without broking ld.so.cache

UPD: libcec have some limitations with multiple handlers in one system and there is problem with cec remote control working simultaneously with the hyperion’s handler. Looks not ready for use yet and requires some investigation.

1 Like

That is a great find and would mitigate a lot of workarounds I tried over the years including the necessity for wake and standby scripts

Inching ever closer to the perfect setup…

All eyes on @hissingshark now… :wink:

cheers
Anthrax