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
AtmoHue - BETA - Philips Hue support for AtmoLight & AtmoWin
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="Lightning303" data-source="post: 1110349" data-attributes="member: 97876"><p>The delay is actually negative. AtmoLight gets called as soon as a frame is rendered. It then resizes it (to typically 64x48 or 64x64) and converts it into a byte array. This byte array then gets send to all enabled target handlers (e.g. AtmoWin and Hue). In the AtmoWin handler for example it gets send directly to AtmoWin. In Hue the array gets analyzed for the average color and then this color gets send to AtmoHue. This all takes no longer that 1-2ms. And as you saw with AtmoWin, you actually need to add delay, because otherwise your leds change color before your tv screen does.</p><p>So any delay you see in the hue lights is comming from Hue itself. There are limitations in Hue that do not allow for fast color changes. It seems Phillips is afraid of an epileptic person to get an attack from their product.</p><p></p><p></p><p></p><p>Sure, lets build our own videoplayer <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue :p" loading="lazy" data-shortname=":p" /></p><p></p><p><img src="http://img3.wikia.nocookie.net/__cb20130113033207/adventuretimewithfinnandjake/images/5/5d/Nope.png" alt="" class="fr-fic fr-dii fr-draggable " style="" /></p></blockquote><p></p>
[QUOTE="Lightning303, post: 1110349, member: 97876"] The delay is actually negative. AtmoLight gets called as soon as a frame is rendered. It then resizes it (to typically 64x48 or 64x64) and converts it into a byte array. This byte array then gets send to all enabled target handlers (e.g. AtmoWin and Hue). In the AtmoWin handler for example it gets send directly to AtmoWin. In Hue the array gets analyzed for the average color and then this color gets send to AtmoHue. This all takes no longer that 1-2ms. And as you saw with AtmoWin, you actually need to add delay, because otherwise your leds change color before your tv screen does. So any delay you see in the hue lights is comming from Hue itself. There are limitations in Hue that do not allow for fast color changes. It seems Phillips is afraid of an epileptic person to get an attack from their product. Sure, lets build our own videoplayer :p [IMG]http://img3.wikia.nocookie.net/__cb20130113033207/adventuretimewithfinnandjake/images/5/5d/Nope.png[/IMG] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Hardware
Ambient Lighting System
AtmoHue - BETA - Philips Hue support for AtmoLight & AtmoWin
Contact us
RSS
Top
Bottom