home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
HTPC Projects
Hardware
Ambient Lighting System
Support for Philips Hue System
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Rick164" data-source="post: 1103477" data-attributes="member: 17766"><p>Seems the Hyperion implementation for Hue had the same delay issue:</p><p></p><p><a href="https://github.com/tvdzwan/hyperion/issues/103" target="_blank">https://github.com/tvdzwan/hyperion/issues/103</a></p><p></p><p>---------</p><p><strong>Quote from ntim:</strong></p><p></p><p>"Ah, regarding the delay, we could try setting the "transitiontime" attribute (defaults to 4 i.e. 400ms) to something shorter. When I did the initial implementation I tried to set this to zero which correctly results in a instantaneous change but then each remaining delay is more noticable. Thus a transitiontime of 200ms might be better. On the other it is an additional command which has to be processed by the bridge which could result in a lower "framerate". I will implement a config file option for the transitiontime, so everyone can try to find a good compromise."</p><p>---------</p><p></p><p>So in theory an transition time of 0 would make it an instant change but could "flood" the Hue bridge with requests which results in slower processing/frame rate, haven't found an way to record timings from the Hue Bridge as it seems to be one way communication when sending colors (no callback).</p></blockquote><p></p>
[QUOTE="Rick164, post: 1103477, member: 17766"] Seems the Hyperion implementation for Hue had the same delay issue: [url]https://github.com/tvdzwan/hyperion/issues/103[/url] --------- [B]Quote from ntim:[/B] "Ah, regarding the delay, we could try setting the "transitiontime" attribute (defaults to 4 i.e. 400ms) to something shorter. When I did the initial implementation I tried to set this to zero which correctly results in a instantaneous change but then each remaining delay is more noticable. Thus a transitiontime of 200ms might be better. On the other it is an additional command which has to be processed by the bridge which could result in a lower "framerate". I will implement a config file option for the transitiontime, so everyone can try to find a good compromise." --------- So in theory an transition time of 0 would make it an instant change but could "flood" the Hue bridge with requests which results in slower processing/frame rate, haven't found an way to record timings from the Hue Bridge as it seems to be one way communication when sending colors (no callback). [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Hardware
Ambient Lighting System
Support for Philips Hue System
Contact us
RSS
Top
Bottom