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:
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.
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.
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.
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.
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.
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.
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
