OSMC and Hyperion


#1

So I just installed my new Vera 4K and have most things arranged how I like it.
Didn’t test any 4K, hevc, 10bit, x265 yet though.

Anyway I had osmc on a pi3 and connected ambilight to the GPIO’s and hyperion installed.
Now that the vera 4K doesn’t have the pins I thought of just keeping both devices but does anyone know how I can actually get it working together?
I thought it was just a matter of entering the ip address of the vera 4k in the hyperion config file:

	// KODI CHECK CONFIG
	"xbmcVideoChecker" : 
	{
		"xbmcAddress" : "192.168.1.22",
		"xbmcTcpPort" : 9090,

However it doesn’t seem to work.

If anyone can help me with this that would be great. I really want the ambilight to work :slight_smile:


Vero4K+ and lightberry
Vero 4K new user a few quick questions
Vero 4K - need information before buying
Vero 4K new user a few quick questions
#2

You will need to have a hyperion server running on the vero, too to analyse the video. The data then needs to be sent to the raspberry that would display the colors on the leds.
Not sure if there is a grabber for the s905x platform in hyperion though.


#3

There’s support for AMLogic based grabbers as there are some USB based Hyperion devices. I also believe everything necessary is enabled in the kernel for this to work.

I don’t know a lot about Hyperion though. If you run in to anything not quite complete for Vero 4K, let me know and I’ll get it added.

Sam


#4

Ok I see it’s not as easy as I thought then.
I’ll try to mess around with the Proto/Json Forwarder (https://hyperion-project.org/wiki/HyperCon-External-Tab) by installing Hyperion on the Vera 4k as well. It will be difficult to test but let’s see.

Usually when installing other things or even updating OSMC itself, I always took out the sdcard and created a backup image with win32diskmanager. Now that Vera 4k has built in storage, what the best (and easiest) way to make a backup/snapshot to which I can easily revert to when I mess up.


#5

I would recommend just backing up important directories, like .kodi, or using the OSMC backup tool. We may offer a better way of backing up internal storage in the future.

Sam


#6

So I’m trying to install Hyperion on the Vera 4K (using this guide: https://hyperion-project.org/wiki/Installation-with-command-line) but get this error:
—> Critical Error: CPU information does not match any known releases -> abort

Any idea how to work around that?
Other install methods are mentioned here: https://hyperion-project.org/wiki/2-Installation but I don’t see another more suitable one.


#7

Remove this check:

if [ $CPU_RPI -ne 1 ] && [ $CPU_IMX6 -ne 1 ] && [ $CPU_WETEK -ne 1 ] && [ $CPU_X32X64 -ne 1 ]; then
	echo '---> Critical Error: CPU information does not match any known releases -> abort'
	exit 1
fi

Their script doesn’t properly handle an AArch64 kernel.


#8

Ok I removed that. But now it ends with:
—> Critical Error: Target platform unknown -> abort

So it doesn’t find any match with these:

# Select the appropriate release
if [ $CPU_RPI -eq 1 ] && [ $OS_RASPLEX -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_rpi_rasplex.tar.gz
	OE_DEPENDECIES=$HYPERION_ADDRESS/hyperion.deps.openelec-rpi.tar.gz
elif [ $CPU_RPI -eq 1 ] && [ $OS_LIBREELEC -eq 1 ] && [ $RPI_1 -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_rpi_le.tar.gz
	OE_DEPENDECIES=$HYPERION_ADDRESS/hyperion.deps.openelec-rpi.tar.gz
elif [ $CPU_RPI -eq 1 ] && [ $OS_LIBREELEC -eq 1 ] && [ $RPI_2 -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_rpi2_le.tar.gz
	OE_DEPENDECIES=$HYPERION_ADDRESS/hyperion.deps.openelec-rpi.tar.gz
elif [ $CPU_RPI -eq 1 ] && [ $OS_LIBREELEC -eq 1 ] && [ $RPI_3 -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_rpi3_le.tar.gz
	OE_DEPENDECIES=$HYPERION_ADDRESS/hyperion.deps.openelec-rpi.tar.gz
elif [ $CPU_RPI -eq 1 ] && [ $OS_OPENELEC -eq 1 ] && [ $RPI_1 -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_rpi_oe.tar.gz
	OE_DEPENDECIES=$HYPERION_ADDRESS/hyperion.deps.openelec-rpi.tar.gz
elif [ $CPU_RPI -eq 1 ] && [ $OS_OPENELEC -eq 1 ] && [ $RPI_2 -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_rpi2_oe.tar.gz
	OE_DEPENDECIES=$HYPERION_ADDRESS/hyperion.deps.openelec-rpi.tar.gz
elif [ $CPU_RPI -eq 1 ] && [ $OS_OPENELEC -eq 1 ] && [ $RPI_3 -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_rpi3_oe.tar.gz
	OE_DEPENDECIES=$HYPERION_ADDRESS/hyperion.deps.openelec-rpi.tar.gz
elif [ $CPU_RPI -eq 1 ] && [ $OS_OSMC -eq 1 ] && [ $RPI_1 -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_rpi_osmc.tar.gz
elif [ $CPU_RPI -eq 1 ] && [ $OS_OSMC -eq 1 ] && [ $RPI_2 -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_rpi2_osmc.tar.gz
elif [ $CPU_RPI -eq 1 ] && [ $OS_OSMC -eq 1 ] && [ $RPI_3 -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_rpi3_osmc.tar.gz
elif [ $CPU_RPI -eq 1 ] && [ $RPI_1 -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_rpi.tar.gz
elif [ $CPU_RPI -eq 1 ] && [ $RPI_2 -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_rpi2.tar.gz
elif [ $CPU_RPI -eq 1 ] && [ $RPI_3 -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_rpi3.tar.gz
elif [ $CPU_IMX6 -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_imx6.tar.gz
	OE_DEPENDECIES=$HYPERION_ADDRESS/hyperion.deps.openelec-imx6.tar.gz
elif [ $CPU_WETEK -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_wetek.tar.gz
	OE_DEPENDECIES=$HYPERION_ADDRESS/hyperion.deps.openelec-rpi.tar.gz
elif [ $CPU_X32X64 -eq 1 ]; then
	HYPERION_RELEASE=$HYPERION_ADDRESS/hyperion_x86x64.tar.gz
	OE_DEPENDECIES=$HYPERION_ADDRESS/hyperion.deps.openelec-x86x64.tar.gz
else
	echo "---> Critical Error: Target platform unknown -> abort"
	exit 1
fi

#9

Because there’s no checks for an AmLogic CPU and OSMC. You can remove the checks. It’s probably quicker / easier to build all of this manually.

You may also want to install the following development packages:

sudo apt-get install build-essential vero3-userland-dev-osmc

Sam


#10

I don’t really know how to build such a thing properly.

I can’t just remove that check because then the script doesn’t know which file to use for the installation.
Which one do I need to install it?


#11

Hello

The CPU check can be fixed by adding:

root@osmc:/home/osmc# diff -u install_hyperion.sh install_hyperion_new.sh 
--- install_hyperion.sh	2017-03-08 16:17:27.091604264 +0000
+++ install_hyperion_new.sh	2017-03-08 16:31:37.392600654 +0000
@@ -44,8 +44,9 @@
 CPU_IMX6=`grep -m1 -c i.MX6 /proc/cpuinfo`
 CPU_WETEK=`grep -m1 -c Amlogic /proc/cpuinfo`
 CPU_X32X64=`uname -m | grep 'x86_32\|i686\|x86_64' | wc -l`
+CPU_VERO4K=`grep -m1 -c Vero4K /proc/cpuinfo`
 # Check that we have a known configuration
-if [ $CPU_RPI -ne 1 ] && [ $CPU_IMX6 -ne 1 ] && [ $CPU_WETEK -ne 1 ] && [ $CPU_X32X64 -ne 1 ]; then
+if [ $CPU_RPI -ne 1 ] && [ $CPU_IMX6 -ne 1 ] && [ $CPU_WETEK -ne 1 ] && [ $CPU_X32X64 -ne 1 ] && [ $CPU_VERO4K -ne 1 ]; then
 	echo '---> Critical Error: CPU information does not match any known releases -> abort'
 	exit 1
 fi

There seems to be a tarball it pulls in however. I haven’t had a chance to look at this, but will open an issue on the Hyperion tracker asking what needs to be added.

Cheers

Sam


#12

Ok I’ll wait for that then. Thanks!


#13

Can I also see that issue you raised so I can follow a bit the progress?

I’d like to install hyperion soon as it’s the only issue left with my new Vera 4K and I miss my ambilight :slight_smile:


#14

I posted on the Hyperion forum but haven’t received a reply yet. It’s likely trivial to get running but we want them to add support to Hyperion upstream


#15

Do you have any update on this?
Many thanks


#16

I haven’t received a reply from anyone there yet


#17

Hyperion.ng will replace Hyperion “classic” when it’s released and this pull request should at least get it working.

The grabber will need testing


Usbtv driver missing on Vero4K
#18

If there’s an easy way for users to test this let me know.

If there’s anything I can do to help with this, happy to help

Thanks for bringing this to my attention

Sam


#19

So I read about this https://github.com/hyperion-project/hyperion.ng/blob/master/CompileHowto.md#the-general-quick-way-without-big-comments on the other forum.
Can you tell me which steps I need to take to get it on the Vero4k?
Thanks


#20

You just need to follow those instructions.

Also make sure you follow https://github.com/hyperion-project/hyperion.ng/blob/master/CompileHowto.md#debianubuntuwin10linuxsubsystem.

Vero 4K support is already included in Hyperion-ng :slight_smile:

Sam