hi @hissingshark i tried your installer to compile latest commit of Hyperion.ng but without luck. i’ve tried latest commit to install.sh script 9d2e442 but without luck. After compile parameters didn´t show compilation menu parameters with enable support for amlogic FB QT and so on.
Thanks
I’ll have a look into it.
But was there a specific issue you were trying to resolve by building from a newer version? Or feature that you needed to add?
I have problem with version 2.0.0.5. I am using kodi script from hyperion team to automatic turning on/off LEDs according to state of KODI. With this version, when i stop playing movie they turn off but after a few seconds they will turn on again. Just this one i think it can be connected with commit
The latest commit built absolutely fine for me. Try running the installer in tmux so that you can scroll back and look for any error messages early on that might indicate the problem. I suspect you have some package contamination. I am on a clean 3.14 install.
My fault. I am running 4.9 kernel and Buster
I shall be testing there myself in due course so we’ll get it sorted.
Buster that is.
4.9 already checked out fine with me. This will be a package issue I’m sure.
u r fast 
I am just touching tmux. nice app
I found
CMake Error at /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find Python3 (missing: Python3_LIBRARY Python3_INCLUDE_DIR Development) (found version "3.7.3") Call Stack (most recent call first): /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.13/Modules/FindPython/Support.cmake:1130 (find_package_handle_standard_args) /usr/share/cmake-3.13/Modules/FindPython3.cmake:163 (include) CMakeLists.txt:29 (find_package)
If someone wants to test new version 2.0.0.8 for VERO4K . Here it is. Compiled on 4.9 kernel and Buster.
Sorry, I’d missed your post about the file upload.
Finally reproduced the fault on my 3.14 Buster setup. I’m improving the installer to cope in future with package changes (it’s always been python).
I’m the meantime binaries are being uploaded tonight. I’ve been testing for a few days and they seem fine.
Did the “fix” actually solve your problem?
That’s OK. I just tried latest commit and it didnt help. I think there is something what sends signal to hyperion and LEDs go ON in the menu. I am using Hyperion Control Addon in KODI for sending commands to server.
Now i should test older versions and find out if issue of hyperion or buster
btw. This release looks more stable for me. I f u wanna test ur installer and compiler I am in
Just after investigation i tried ur compiled version and my compiled version. Both same problem. I´ve found this problem already in this thread last year 
Below from log you can see that when i stopped video. LEDs went OFF. But after cca 20secs showed AMLOGICGRABBER Error Read of device failed: 11 … It restarted grabber and changed to FB mode and LEDs went ON.
I am using KODI control addon to auto stop LEDs in KODI menu and when movie plays LEDs goes ON. It seems after movie stopped there is no switch to FB mode resp. too late and gives /dev/amvideocap0 resource temporary unavailable.
2020-10-11T21:00:36.752 hyperiond HYPERION : <DEBUG> Hyperion.cpp:538:handlPriorityChangedLedDevice() | priority[255], previousPriority[250]
2020-10-11T21:00:36.752 hyperiond HYPERION : <DEBUG> Hyperion.cpp:541:handlPriorityChangedLedDevice() | No source left -> switch LED-Device off
2020-10-11T21:00:56.958 hyperiond AMLOGICGRABB : <ERROR> Read of device failed: 11 - Resource temporarily unavailable
2020-10-11T21:00:56.962 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:238:setInputImage() | Priority 250 is now active
2020-10-11T21:00:56.962 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:333:setCurrentTime() | Set visible priority to 250
2020-10-11T21:00:56.963 hyperiond HYPERION : <DEBUG> Hyperion.cpp:538:handlPriorityChangedLedDevice() | priority[250], previousPriority[255]
2020-10-11T21:00:56.963 hyperiond HYPERION : <DEBUG> Hyperion.cpp:548:handlPriorityChangedLedDevice() | new source available -> switch LED-Device on
2020-10-11T21:00:56.965 hyperiond AMLOGICGRABB : <INFO> FB mode
2020-10-11T21:01:05.182 hyperiond AMLOGICGRABB : <INFO> VPU mode
2020-10-11T21:01:18.852 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:238:setInputImage() | Priority 250 is now inactive
2020-10-11T21:01:18.852 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:333:setCurrentTime() | Set visible priority to 255
2020-10-11T21:01:18.852 hyperiond HYPERION : <DEBUG> Hyperion.cpp:538:handlPriorityChangedLedDevice() | priority[255], previousPriority[250]
2020-10-11T21:01:18.853 hyperiond HYPERION : <DEBUG> Hyperion.cpp:541:handlPriorityChangedLedDevice() | No source left -> switch LED-Device off
2020-10-11T21:01:39.178 hyperiond AMLOGICGRABB : <ERROR> Read of device failed: 11 - Resource temporarily unavailable
2020-10-11T21:01:39.181 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:238:setInputImage() | Priority 250 is now active
2020-10-11T21:01:39.182 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:333:setCurrentTime() | Set visible priority to 250
2020-10-11T21:01:39.183 hyperiond HYPERION : <DEBUG> Hyperion.cpp:538:handlPriorityChangedLedDevice() | priority[250], previousPriority[255]
2020-10-11T21:01:39.183 hyperiond AMLOGICGRABB : <INFO> FB mode
2020-10-11T21:01:39.183 hyperiond HYPERION : <DEBUG> Hyperion.cpp:548:handlPriorityChangedLedDevice() | new source available -> switch LED-Device onYeah, there’s no reason why my build would be any different to yours. It’s available through the installer now is all.
I don’t use the add-on myself. But could that be the problem, rather than Hyperion?
i think it is problem in hyperion self. Somewhere is error in capture daemon of hyperion. Or at least i guess. Needs more investigation.
Noone else has problem with auto switching LEDs off in KODI menu. resp. with KODI control Addon?
Hello @hissingshark,
had my first day off in ages today and naturally gravitated towards updating all my gear 
Your installer once again saved me a lot of hassle in trying to remember the specific way of how to build hyperion.ng on the Vero…
And for the first time I was able to just use the prebuilt binary (since all my devices are finally supported in the hyperion master branch) and it worked a treat.
Well to be honest, I got a heart attack at first when seeing python errors but then figured I should probably update my osmc to buster as well before blaming your installer to haved failed
so, as always, a big thank you is due!
best regards
Anthrax
PS: almost too easy now…
Ideally it should support both for the time being, but that’s on my to-do list.
Glad it’s worked out for you.
Hi @hissingshark,
having another day off I tried to fix a new bug that has been introduced with the latestest prebuilt binary (2.0.0-alpha.8 + fixes)…
BTW: the bug is that my hue lights won’t resume after the playback was paused and resumed (led strip and naoleafs work just fine)
So I tried to build from source with the latest commit # from the hyperion.ng repo to see if this might have been fixed already. At first it went smoothly until the vero somehow froze (I don’t think it was due to the build process though) somewhere around the 20% mark with the green text and stuff…
So after power cycling the vero I tried to build from source again but now the build options list looks rather strange 
I already tried deleting the hyperion-vero4k folder and redownloaded from git again but no luck - so is there anything I can do to clean up the mess or forcefully build everything new again?
best regards,
Anthrax
PS: I know, never change a running system and yet we always do 
I suspect the crash mid-build may have left some packages awry and caused the issue. Having said that, I’m seeing the same here so I think to some extent this is another Buster change.
I’ve filtered out the extraneous build options from the list now and we’re definitely looking for Python 3.7.
Builds fine here from master. Let me know how you get on.
man, @hissingshark your fix did it!
I were just able to successfully build from source again and can confirm that the build option list looks way more familiar again.
Thank you so much.
Anthrax
@lancelot, I used to until I thought it was causing the hue resume-issue…
Why do you ask? Are you having trouble as well or do you think it would fix my issue if I’d try it again/change some settings?
anthrax
Just if you have the same issue with autoswitching LEDs. I stopped movie LEDs went off but after 20s went ON again in KODI menu. I have set no LEDs in KODI menu.