The idea is to replace the hue+ambilight app that you have to run on a smartphone for this feature to work with Philips TVs (all ambilight models released after 2011 with JointSpace API).
I understand that it may be of a low priority in the context of this plug-in as it would be useful for a limited amount of the hardware owners, also it might be a better idea to implement it as a standalone daemon, rather than a plug-in for XBMC (so that it works no matter what app or input source you are using).
It's just an idea to consider and the option that would be appreciated by ambilight TV users. Smartphone battery would not be drained and you will not have to run/stop the app on a phone while watching the movie, a plugin can do it automatically.
Probably it can also reduce the lag as the standalone app can query API and control the lamps with a higher frequency than the smartphone app (and using a wired connection). Querying API is also faster and less CPU intensive than processing a screen capture.
http://jointspace.sourceforge.net/projectdata/documentation/jasonApi/1/doc/API-Method-ambilight-processed-GET.html
The idea is to replace the hue+ambilight app that you have to run on a smartphone for this feature to work with Philips TVs (all ambilight models released after 2011 with JointSpace API).
I understand that it may be of a low priority in the context of this plug-in as it would be useful for a limited amount of the hardware owners, also it might be a better idea to implement it as a standalone daemon, rather than a plug-in for XBMC (so that it works no matter what app or input source you are using).
It's just an idea to consider and the option that would be appreciated by ambilight TV users. Smartphone battery would not be drained and you will not have to run/stop the app on a phone while watching the movie, a plugin can do it automatically.
Probably it can also reduce the lag as the standalone app can query API and control the lamps with a higher frequency than the smartphone app (and using a wired connection). Querying API is also faster and less CPU intensive than processing a screen capture.