2010-02-09, 10:55
Well it has been discussed and it all comes down to that reading the backbuffer at a significant speed takes up way to much resource so you'd get a significant impact on the htpc. Also transfering the screenshots / movie thing will take alot of bandwith and adding compression to that would probably not be beneficial since it will take even more cpu cycles on both client and htpc, although it would be needed to be investigated.
regarding 3 and 4, we don't have that code in place in xbmc by normal so no way of detecting it. when XBMC supports dirty regions and event based rendering this would be revisable.
WIth that being said rendering the video @ 64x64 might be added since ambilight daemons could use that data.
I do find the idea interesting but unfortuanatly I doubt we can do it better than vnc and such already do, essentially have the same problems. Although since the data fetching will be so easy it will be a snap for other clients to display the data instead.
regarding 3 and 4, we don't have that code in place in xbmc by normal so no way of detecting it. when XBMC supports dirty regions and event based rendering this would be revisable.
WIth that being said rendering the video @ 64x64 might be added since ambilight daemons could use that data.
I do find the idea interesting but unfortuanatly I doubt we can do it better than vnc and such already do, essentially have the same problems. Although since the data fetching will be so easy it will be a snap for other clients to display the data instead.