I don't think the XRDP server detects the scrolling events, IMHO it just re-sends the whole scrolled block. I am not quite sure what makes the difference, but scrolling in Sublime editor is just smoother. On the same box though Remotix RDP to XRDP server works better for me than your bVNC to TurboVNC. For some reason the Remotix does not connect to my TurboVNC server, your bVNC connects just fine. XRDP server does not support H264 encoding.īTW I was wrong about your client not supporting a menu from keyboard, the "Windows menu key" - the one next to the right Control key - opens the menu just fine. With this bit rate, only 16bit per pixel encoding was usable. The XRDP server (software rendering) on Ubuntu 18 produced data streams peaking at 1.6MB/sec, that is significantly lower than what the Microsoft RDP server achieved. The RDP server on Windows peaked at 2.6MB/sec, RDP server on Windows with H264 produced nice smooth animations for our 3D rendering application, however the Remotix client showed weird latency / delay in mouse handling with the H264 codec in place. I suppose this is due to the detection of scrolling events and sending just a scroll command and the screen delta. RDP server on windows produces MUCH smaller data rate bitstream when scrolling in Sublime editor on in Chrome, in the order of magnitude. Remotix supports H264, so does the Microsoft RDP client on Windows. I tested RDP connection with Remotix, which shows the data bit rate on a screen overlay. I did some tests on my VPN connection over VDSL to an Ubuntu desktop. If anybody here would like to try to bring the SPICE protocol bandwidth requirements for video playback and help me do that, please do reopen the issue and get in touch. Happy to participate in any discussions, please cc me iiordanov gmail com if you would like that. Maybe somebody other than me can strike up the discussion about a SPICE unicode channel which would make the SPICE protocol actually useful as a VNC replacement. Possibly interesting old discussions on the topic of sending unicode input to the SPICE server: I've had to code crazy workarounds for that. Your question about SPICE for use to replace VNC: (1) nobody has bothered to port the SPICE protocol for any purpose other than connecting to KVM virtual machines, and (2) the SPICE protocol has some severe limitations for keyboard input (requires scan codes, assumes that a physical keyboard is connected to the SPICE client, because it was never designed with mobile devices in mind). Only bVNC gives me smooth playback whereas aRDP and aSPICE/Opaque are pretty choppy, so possibly fewer frames are sent (haven't looked deeper). The bandwidth requirements are pretty similar between VNC and RDP, with VNC doing a bit better on the low-end. I just tested bVNC, aRDP, and aSPICE/Opaque against vino, xrdp, and oVirt respectively playing a full-screen video at 1080p resolution for all three.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |