Another issue I found is that people seem to be building it for 64-bit, but our userland is 32-bit. This is probably causing a struct problem with the ioctl.
I tried playing around with udev and and added the following line in “999-fix-amlogic.rules”: ACTION=="add", KERNEL=="ge2d", SUBSYSTEM=="ge2d", GROUP="video", MODE="0660"
this fix from the hardkernel forums “echo 3 | tee /sys/module/amvdec_h265/parameters/double_write_mode”
Hyperion drives an Arduino Teensy 3.0 via FastLED library and my own ADALight implementation.
So far I haven’t encountered any lags or glitches while playing HD and UHD content…
Maybe this info will help you making this possible on the Vero 4k+.
I just installed a pair of lightstrips on my tv, and was looking to try hyperion. It sounds like there are a few things still being ironed out - should I wait for now?
I got some time on my hands in the late afternoon and want to give it another go on the Vero 4K+.
I’d like to try two things:
replicate what I did on the Odroid (using the prebuilt CoreELEC addon and double_write_mode
parameter) @sam_nazarko: Is there an easy way to install the CoreELEC addon on the Vero? Or would copy and paste work as well?
going the GE2D route again with udev rule @sam_nazarko: any news on the udev rule? I tried this but failed: ACTION=="add", KERNEL=="ge2d", SUBSYSTEM=="ge2d", GROUP="video", MODE="0660"
I think it’s just a binary in the same way it’s built above. I doubt it is using the GE2D interface but you can verify that with verbose output.
I’d start with double write mode first
Sliiightly offtopic question but which value for blackborder detection are you guys using? It might be imagination but since a couple of weeks the LEDs at the top and bottom hardly light up at all when playing non-16:9 material, so everything with black bars at the top and bottom that has an aspect ratio of something between 16:9 and 21:9. FullHD or UHD material works completely fine.
So after initially going with 15 %, I turned it up to 16 % but couldn’t detect any difference. The blackborder detection section of /etc/hyperion/hyperion.config.json looks like this
I never changed the black border detection default parameters and never had an issue with it. On less powerful hardware (RPI) it sometimes took a second to detect and switch the upper/lower leds but with Vero 4K+ I never had this happening to me.
Do you have overscan enabled by any chance? When using hyperion.ng you could check the live video/leds in the web config (might work with HyperCon as well)
Anyways I’ve been testing the Vero with hyperion.ng and the experience was pretty good. What keeps happening though is the occasional hiccup (known slowdown, a/v getting out of sync) every 30-45minutes of UHD…
But I’m a very happy customer now
For me the Vero 4K+ is now the benchmark over all the other boxes (I tried quite a few) struggling with 4K60FPS Ambilight! (my condolences go out to the people selling 400€ 4K HDMI splitters, linkers and what not)
:
