Oh, BTW, if you want to turn it on to see the server side CPU savings, uncomment rdpXvInit(pScreen) in rdpmain.c.
To get back to the original question for this thread, we could still do everything in software and use this extension to know when to compress the bitmaps or not. Instead of analyzing the image data, use a hint to know when video is playing and not try to compress. Jay On Fri, Jun 21, 2013 at 8:29 PM, Jay Sorg <jay.s...@gmail.com> wrote: > Hi Gustavo, > >> How can we test this feature? Which rdp client did you use and how? Does the >> client use the client side Xv when available and CPU scaling / conversion >> otherwise? > > All I did was add the virtual adaptor to X11rdp to see what apps call it. > It's off by default because if you don't handle it, the player window is > blank. > > It would not be that difficult to use the same client virtual channel > that we use for vrplayer to remote the yuv data to the client. The > client can then use Xv or whatever it wants to do the yuv to rgb > conversion and the stretch blit locally. > > The server would still be doing the H264 or MPG4 or MPG2 decode but > the client would be doing the yuv to rgb and stretch locally. > A quick test, the CPU dropped from 88% to 12% for one session 720p video test. > Also, note, you can full screen on the client at no additional cost > for the server. > > Lets work to get this done. I might need to raise some funding for this. > > Jay ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ xrdp-devel mailing list xrdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xrdp-devel
