@Anthrax Makes me wonder what your exact hardware setup is, because I am considering a 4k splitter.
Hi @Numiah,
this is my setup:
- Samsung UE75MU6179
- Vero 4K+ (october update, hyperion.ng)
- Teensy 3.0 with custom FastLED/adalight implementation connected via USB
- 5m, 160 LED WS2801 strip
- 12V, 10A power supply for the strip
- Denon AVR 1612
- Philips Hue lights
Are you thinking about buying the splitter exclusively for ambilight purposes? If so I would definitely try the osmc & hyperion route first!
If you need to split the HDMI for other purposes as well I would have a look at some of the newer AVRs like the Denon x2400h which come with dual HDMI out and should be up for some reasonable prices on black friday/cyber monday. This way you get 2 HDMIs plus all the new protocols and codecs for the same price as the splitter alone 
regards,
Anthrax
3 Likes
Just in case anyone is interested:
I have been running a very similar setup to Anthrax’s one (post above), but with the “old” hyperion, for two months now.
- UHD HDR TV
- Vero 4k+ (october/november update)
- Hyperion (old) using the amlgrabber
- Teensy 3.0 with some custom FastLED/adalight implementation connected via USB
- 150 LED (APA102)
Ambilight itself works just fine, but there is the same a/v out of sync issue.
Installation/Compilation was quite simple thx to hissingshark’s installer. Just had to add the echo 3 | … part (mentioned several times here) to my rc.local.
AMLgrabber config
“amlgrabber” :
{
“width” : 70,
“height” : 40,
“frequency_Hz” : 24.0,
“priority” : 799
},
Device/Output configuration
"device" :
{
"name" : "FernseherHyperCon",
"type" : "adalight",
"output" : "/dev/ttyACM0",
"rate" : 100000,
"delayAfterConnect" : 0,
"colorOrder" : "rgb"
},
But to be honest it is quite useless due to the a/v out of sync issue. I do not know if this can be fixed. But maybe sam will find some magic trick to get it to work.
1 Like
Hi @maxanier,
That’s exactly why I ditched the classic Hyperion as there were major issues with a/v getting out of sync.
With Hyperion.NG (the main git as well with the sjunkies fork) I have no issues at all below 4K and @4K it just happens every 30-45 minutes out of the blue. And then it’s easily fixed with a short skip back (though it’s getting rather annoying when all you wanna do is chill and not move the slightest bit after a full day of work ;-))
So if anyone has any idea why this is happening I’m certain Sam is the guy to crack this once and for all!
Anthrax
1 Like
Hey @Anthrax ,
the issue I am having with the old one is very similar to the one you are describing for your setup.
It only happens after 40-50 minutes and can be temporarily fixed with a short skip. However, it sometimes also occurs for non 4k material.
ah ok, happened more often with old one for me I think…
As described above my setup contains a Vero 4K that analyses the picture and acts as a Hyperion client to a Hyperion server installed on a Raspi3 responsible for controlling the LEDs. I used hissingshark’s installer to get Hyperion working on the Vero 4K.
Vero Hyperion Config (except for the change in blackborder threshold to 0.16)
Raspi3 Hyperion Config (except for the change in blackborder threshold to 0.16)
I can’t find anything regarding overscan in Hyperion’s config. Do you mean this part of /boot/config.txt in a typical Raspi install?
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1
That’s not available in the Vero 4K which does the analysing part. 
Occasionally I get slowdowns around the 35/40 minutes mark, but I just stop playback and immediately resume play at the timestamp, so nothing to worry about.
1 Like
Hey guys,
I’ve been reading the whole thread and tried to use Hyperion on my Vero.
I have the 4K+ and used the installer to build it from source, i selected qt5 and framegrabber during installation.
The LED is a single Philips HUE color light bulb placed behind the TV. It is linked with the Philips bridge. I created a MeetHue username etc.
My hyperion config looks like this:
{
// DEVICE CONFIGURATION
"device" :
{
"name" : "Vero4K",
"type" : "philipshue",
"output" : "192.168.0.40",
"transitiontime" : 1,
"brightnessFactor" : 1,
"setBrightness" : false,
"switchOffOnBlack" : false,
"username" : "xxx",
"colorOrder" : "rgb",
"lightIds" : [23]
},
// COLOR CALIBRATION CONFIG
"color" :
{
"channelAdjustment" :
[
{
"id" : "default",
"leds" : "*",
"pureRed" :
{
"redChannel" : 255,
"greenChannel" : 0,
"blueChannel" : 0
},
"pureGreen" :
{
"redChannel" : 0,
"greenChannel" : 255,
"blueChannel" : 0
},
"pureBlue" :
{
"redChannel" : 0,
"greenChannel" : 0,
"blueChannel" : 255
}
}
],
"temperature" :
[
{
"id" : "default",
"leds" : "*",
"correctionValues" :
{
"red" : 255,
"green" : 255,
"blue" : 255
}
}
],
"transform" :
[
{
"id" : "default",
"leds" : "*",
"hsl" :
{
"saturationGain" : 1.0000,
"luminanceGain" : 1.0000,
"luminanceMinimum" : 0.0000
},
"red" :
{
"threshold" : 0.0000,
"gamma" : 2.5000
},
"green" :
{
"threshold" : 0.0000,
"gamma" : 2.5000
},
"blue" :
{
"threshold" : 0.0000,
"gamma" : 2.5000
}
}
],
// SMOOTHING CONFIG
"smoothing" :
{
"type" : "linear",
"time_ms" : 100,
"updateFrequency" : 6.0000,
"updateDelay" : 0
}
},
// NO V4L2 GRABBER CONFIG
// AML GRABBER CONFIG
"amlgrabber" :
{
"width" : 64,
"height" : 64,
"frequency_Hz" : 10.0,
"priority" : 890
},
// FRAME GRABBER CONFIG
"framegrabber" :
{
"width" : 64,
"height" : 64,
"frequency_Hz" : 10.0,
"priority" : 891
},
// BLACKBORDER CONFIG
"blackborderdetector" :
{
"enable" : true,
"threshold" : 0.0,
"unknownFrameCnt" : 600,
"borderFrameCnt" : 50,
"maxInconsistentCnt" : 10,
"blurRemoveCnt" : 1,
"mode" : "default"
},
// JSON SERVER CONFIG
"jsonServer" :
{
"port" : 19444
},
// PROTO SERVER CONFIG
"protoServer" :
{
"port" : 19445
},
// EFFECT PATH
"effects" :
{
"paths" :
[
"/storage/hyperion/effects",
"/usr/share/hyperion/effects"
]
},
// NO KODI CHECK CONFIG
// NO BOOTEFFECT CONFIG
// NO BOBLIGHT SERVER CONFIG
// NO JSON/PROTO FORWARD CONFIG
// LED CONFIGURATION
"leds" :
[
{
"index" : 0,
"hscan" : { "minimum" : 0.0000, "maximum" : 1.0000 },
"vscan" : { "minimum" : 0.0000, "maximum" : 0.0800 }
}
],
"endOfJson" : "endOfJson"
}
The problem: in the homescreen the LED color changes according to the menu. So far so good but playing a video file, no matter SD or HD or UHD or SDR or HDR, the LED only shows a very dim blue color and Hyperion says:
AMLOGICGRABBER ERROR:[int AmlogicGrabber::grabFrame(Image<ColorBgr>&)] Failed to open the AMLOGIC device (12): Cannot allocate memory
What could be wrong here? Why can’t it access the amlgrabber?
Installing from binary has the same results. Thanks in advance for your help.
Thanks a gazillion for sharing the details.
Ordered all the parts a few minutes ago. Went for the APA102’s.
Now the long wait begins 
Allright, fingers crossed you’ll get the parts before christmas 
Would have gone for APAs as well these days…
Hey everybody,
after running hyperion.ng in 4K60FPS for some weeks now (well, with the occasional hiccups) I’m really, really happy I went for the Vero 4K+
One thing I’m still struggling with though (there always is something for the tinkerer as all of you might know) is the standby/resume behaviour. Could someone enlighten me on what happens when I tell Kodi to go to standby?
At first I thought I could just put
[Unit]
PartOf=mediacenter.service
into my hyperion systemd unit and it would be nicely started/restarted together with kodi. But standby seems to just be ‘faked’
Anybody with a clever idea on how to react to Kodi standby and control a services state?
cheers
Anthrax
PS: loving the santa hats!
I am going to add support for hooks to the standby mode.
This will let you run a Python script on stop/start; so you’ll be able to control Hyperion accordingly.
Please remind me about this after the next update and I’ll give you some instructions
Sam
1 Like
↑ This!
Glad to hear this. I wasn’t sure if we were putting them up too early.
Christmas is announced far too early until shops can move on to the next big thing (Halloween; Valentines; then Easter).
@RJ45: Never seen an Ethernet cable with a Christmas hat on it before. We can call this ‘Network November’ next year and make a ‘packet’.
1 Like
Awesome!
Hey everybody,
some recent activity and the hue entertainment api seemed to have rekindled development in the german hyperion-project forums…
I wrote a little how-to on the compilation/running process espacially for OSMC and the Vero 4K+ and thought it might help others around these shores as well
https://github.com/AnthraxLeprosyPi/hyperion.ng/blob/master/CompileHowtoOSMC.md
happy 1st advent (if you guys even know what that ist…)
regards
Anthrax
PS: if you hit a snag along the way when using this guide - please let me know! Or even better fix it yourself - that’s what git is for
4 Likes
Thanks a lot Anthrax for setting up the guide. Followed it to the letter.
Boy oh boy, lot’s of things happened and wizzed by on screen.
I seem to get stuck at one of the more simpeler things, copying the webconfig files to .hyperion directory.
For some reason I get this error. (cp: cannot stat ‘/root/hyperion.ng/assets/webconfig’: No such file or directory)
Which is odd, because these dirs do exist?
I’m not familiar with command line executing, so would love a gentle nudge in the correct direction
EDIT : Got some help from rantanplan1 (thanks a gazillion!)
Config thing up and running.
Just to be sure. With this I can safely run Hyperion on the Vero4k and it won’t cause issues unless I play 4K stuff?
1 Like
Hi @Vince35,
what do you mean by ‘safely’? I hope you don’t want to run this in your car 
…
Hyperion.ng works quite well for me now regardless of what I throw at it!!!
4K60 is working pretty good at the moment (some hiccups every now and then but a quick skip back fixes it all the time for me.)
cheers
Anthrax
Hi @Numiah,
you’re welcome and I’m glad you got it working.
Do you remember how you solved it - so I could put it in the guide?
Anthrax