- January 7, 2006
- 1,335
- 1,006
- Home Country
- Netherlands
- Thread starter
- #131
Ok - not a big difference - so what would be needed is impossible to acomplish - a calculation of teh content before it is send ... I'm sure Lightning loves task like crwaling a videstream parallel and beforehand it being send. No - honestly - I have no idea how teh player is implemented in MP but - as with Atmolight - it seesm to have a small delay - can this be managed? In the delay can be increased postprocessing could become a visible preprocessing.
Think Lighting is always up for a challenge
What I'm wondering - what is the difference between Transition Time and Send Delay? Am I correct that if I set the send delay to 0 (I tried it ) and play around with the transition time only around 150ms it starts tobrig small flash - but - more interesting - if i select a scene with fast changing colors i can see that when the sequence ends the data is processed from teh fast szene - meaning - if teh send delay is smaller than teh transition time it will at one point floof the bridge or where is the dtata hold? And - if it is like I think - what sense does irt make to separate the transition time and the send delay?
The Send Delay is to throttle the maximum number of commands we send to the bridge per x ms, because if were to send them with the actual frame rate of like 50fps for instance the bridge might not be able to handle it.
It also depends on the content and how well the bridge responds as that seems fluctuate for unknown reasons, could be Z-wave protocol delay / wireless interference / or just maxing out Bridge resources.
The Transition Time is something we send along a color command and is handled internally by the Bridge, basically it queues up color commands and phases them in but if we were to push it too many commands it will not always know what to do (starts flickering or get flooded).
Adopted the Win Hue 2 color calculation code which is based on HueApi examples and testing it out now, it does more corrections but does reset any custom calibrations that may have been set as it handles it differently.
Also looking into reducing the command size, so would only include the color and nothing else to see if that helps speed things up.
For fun started looking into Arduino + Z-Wave as an Hue alternative, it does seem possible and potentially a bit cheaper as well:
http://code.mios.com/trac/mios_arduino-sensor/wiki
Basically you have an Arduino connected to Ethernet and you forward it commands just like now but since it's completely open-source and the hardware can upgraded it should have some very nice response times in theory at least
Definitely not as easy as plugging in an Hue but still looks pretty good and you can also control other appliances with it.
But gonna look into some simpler alternatives to Hue and support those in AtmoHue as well, if anyone knows any good ones that can also be controlled over Wi-Fi just let me know
/edit: found these:
http://www.limitlessled.com/
Fairly new but seems to not have the epilepsy restrictions and is open-source, too bad they only make bulbs
Last edited: