Ok - so as expected 
- but that means what happens in these 4250ms so the Bridge does not send the colour to the lights?
- but that means what happens in these 4250ms so the Bridge does not send the colour to the lights?
Support for Philips Hue System (1 Viewer)
- Thread starter boldie
- Start date
- January 7, 2006
- 1,335
- 1,006
- Home Country
-
Netherlands
Correct , it will wait for 4250ms before sending the new color at least according to Hue API docs and other implementations I've seen.
Still need to read a bit more and might just write my own small json client for parsing the commands as that way we can rule out any bugs in the API currently used.
Btw uploaded the source to the new repo:
https://github.com/ambilight-4-mediaportal/AtmoHue/tree/master/AtmoHue
What I'm wondering is if you see the following message in your log window more than once:
"HUE has been intialized on COLOR CHANGE"
It should only show up once during first start but if not then something is wrong.
, it will wait for 4250ms before sending the new color at least according to Hue API docs and other implementations I've seen.Still need to read a bit more and might just write my own small json client for parsing the commands as that way we can rule out any bugs in the API currently used.
Btw uploaded the source to the new repo:
https://github.com/ambilight-4-mediaportal/AtmoHue/tree/master/AtmoHue
What I'm wondering is if you see the following message in your log window more than once:
"HUE has been intialized on COLOR CHANGE"
It should only show up once during first start but if not then something is wrong.
Last edited:
Yeah - no - that'sclear - what I mean is - when going down to a smaller value (like 2250) where is the delay of the colour being sent to the bridge and displayed at the bulb? Why does this happen with 4250 immediatly? And what does teh bridge do in the meantime - as everything below these 2250 will cause it to buffer - so the 2250 seems - at least now - the minimum delay between two colours with teh bridge starting to buffer ...
No - it only shows one time initialized. And it's holding connection rather aggressive. When I try to take over with another app it will hold the bridge until your app is stopped. Even when teh other App was connected using the Center Button of the Bridge.
No - it only shows one time initialized. And it's holding connection rather aggressive. When I try to take over with another app it will hold the bridge until your app is stopped. Even when teh other App was connected using the Center Button of the Bridge.
- January 7, 2006
- 1,335
- 1,006
- Home Country
-
Netherlands
Why it works the other way around with 4250ms I've no idea at the moment, the bridge will do nothing during that time other than waiting for new commands.
According the Hyperion implementation a lower value resulted in direct color change and higher in slower(fading to new color) so don't get why it would work differently in the current setup.
The aggressive connection part can be changed later btw , currently have it open all the time for testing the color change speed.
/Edit: found the problem, little typo...
Probably happened when I did the settings setup and didn't check the VS auto completion for that one (doh!).
Now just need to edit the brightness function and add better connection control, cleaned up some obsolete code as well so now everything is nice and tidy except the rotate color test but that one is temporary anyway.
Changelog
- Fix for transition time, now selects the correct settings value
Download AtmoHue 0.011
http://1drv.ms/1vXlcGk
According the Hyperion implementation a lower value resulted in direct color change and higher in slower(fading to new color) so don't get why it would work differently in the current setup.
The aggressive connection part can be changed later btw
, currently have it open all the time for testing the color change speed./Edit: found the problem, little typo...
Probably happened when I did the settings setup and didn't check the VS auto completion for that one (doh!).
Now just need to edit the brightness function and add better connection control, cleaned up some obsolete code as well so now everything is nice and tidy except the rotate color test but that one is temporary anyway.
Changelog
- Fix for transition time, now selects the correct settings value
Download AtmoHue 0.011
http://1drv.ms/1vXlcGk
Last edited:
Version 11 is not opening.
- January 7, 2006
- 1,335
- 1,006
- Home Country
-
Netherlands
Just tried on an different machine but it started up right away, are you getting any specific error?
Also make sure you use an new folder just in case some old DLL is conflicting.
Latest version from github below with the obsolete code removed, shouldn't make any difference but can try it
Download AtmoHue 0.012
http://1drv.ms/1njqBXI
Also make sure you use an new folder just in case some old DLL is conflicting.
Latest version from github below with the obsolete code removed, shouldn't make any difference but can try it
Download AtmoHue 0.012
http://1drv.ms/1njqBXI
Last edited:
Hm - gave me a .net error - but 0.012 is starting fine. Made only a short test - transition time ist still (on my system) 4250 to get immediate colorchange.
What slower - the transition time is slower - but the colorchange is done immediatly as with 4250.
It's hard to describe - when I set it to 2250 (everything below results in buffering on teh bridge after a few changes) it's
with 2250
color send to Bridge -> approy 500ms delay -> color set on Lamp
transition time 2250ms
color send to Bridge -> approy 500ms delay -> color set on Lamp
with 4250
color sent to bridge -> color set on Lamp (approx 10ms delay)
transition time 4250ms
color sent to bridge -> color set on Lamp (approx 10ms delay)
everything below ends in delay between send and set, everything above ends in only longer transition times.
It's hard to describe - when I set it to 2250 (everything below results in buffering on teh bridge after a few changes) it's
with 2250
color send to Bridge -> approy 500ms delay -> color set on Lamp
transition time 2250ms
color send to Bridge -> approy 500ms delay -> color set on Lamp
with 4250
color sent to bridge -> color set on Lamp (approx 10ms delay)
transition time 4250ms
color sent to bridge -> color set on Lamp (approx 10ms delay)
everything below ends in delay between send and set, everything above ends in only longer transition times.
- January 7, 2006
- 1,335
- 1,006
- Home Country
-
Netherlands
Thanks for the explanation, this clears things up.
Will have to see if we can get a few other people to test it out as well, if the result is the same I'll make 4250ms its 0 / start value until we figure out why it's doing this ofc
Will have to see if we can get a few other people to test it out as well, if the result is the same I'll make 4250ms its 0 / start value until we figure out why it's doing this ofc
Last edited: