(2017-03-25, 14:23)djcorvus Wrote: So there's no hope at all??
I only built my adalight rig a few months ago and now it's useless??
Sorry, but I'm furious! This thing cost me $150
Is there really no other way at all?
Do the Kodi developers know about this? Can they fix this?
How does this Hyperion thing work? Can I hook it up to my existing LED lights (I don't know what make/model they are, but it's these: https://www.adafruit.com/products/322)? Or will I have to start from scratch again? Is there any solution at all that will enable me to use my existing LEDS?
I am only using this with Kodi, however I wouldn't mind a solution that enables capture from multiple HDMI sources - but I am worried that doing things that way will be expensive since every component in my AV system is HDMI 2.0a and a splitter will 'break' the chain and make it impossible to watch 4K60 content.
Sorry about all the questions, but I am extremely new at this and have barely any coding experience.
Can somebody please advise?
So the history of this is that going way back, Kodi (XBMC) included a python interface into this frame server. As best as I can tell this was to take screenshots.
The original developer of the Ambibox executable wrote routines to take those frames and send them directly to the Ambibox executable and found that XBMC served them up at reasonably good rates to make the whole thing work. I took over in 2013, improved a lot of things, added some things, optimized parts with c calls (ctypes.memove() etc) and things were good through Jarvis.
I know for a fact that using that part of API, the system *could* be pushed to the point that the video would stutter on *some* systems as a result of requesting large frames frequently.
The Kodi developers decided during the Krypton development cycle that these routines were poorly written and rewrote a good part of this subsystem.
It is only conjecture on my part, but I think in order to shield the rest of the system, the buffer was written to that it is lower in priority and that it will protect the video output at the cost of serving frames through the API.
If you go back through this thread and search the rest of the board and the bug tracking system, you will see that I made them aware of this and they fixed true bugs, but do not seem concerned that the performance is poor.
After all, this is meant for screen shots. Not as an interface to grab full speed video. So feel free to complain to them, but I will expect them to tell you learn how to code and try to improve it yourself. After all, they, like me, do this in their spare time as a hobby and for free. And I don't even use ambibox for my ambient lighting setup, as mentioned above.
Hyperion uses the same infrastructure and the last time I looked around, they were having similar issues.
Doing a simple google search I found several HDMI 2.0a compliant, HDCP compliant splitters capable of 4K60Hz, but they aren't cheap (i.e.
https://www.pulse-eight.com/p/177/1x2-hd...22-support).