Hi Stefan,
x2gokdrive supports at the moment only JPEG and PNG compressions. PNG compressions is much slower than JPEG and don't really makes sense, but at the moment it's there. I didn't really make decision yet how I'll proceed here with the configuration dialog. Maybe for x2gokdrive I'll just leave the possibility to select the quality of images, 1-9 and disable other settings. I'm also thinking about implementing the automatic detection of the connection quality and select the quality of image "on the flight". About the artifacts on your screenshot, I'm suspecting that it's not a compression issue but the bug. I could see that sometimes in the sessions which are not using a composite (like ICEWM). Strangely, I just saw it in the QT Client, but not in HTML client. So I suspecting that this is just x2gokdriveclient bug. I'll try to fix it next weeks.
regards, Alex
Am 16.07.20 um 04:01 schrieb Stefan Baur:
Hi List, hi Alex,
Same environment as for the ten previous issues/oddities ...
This time, I tried out "Connect to Windows Terminal Server".
In NX mode, I can set the compression to "nopack", and it does have an effect.
But it looks like choosing "nopack" when KDrive is selected has no effect.
With "16m-jpeg" in NX mode, but not with "nopack", I am getting nasty JPEG artifacts when moving a window around.
In KDrive, these artifacts are always there, no matter what I select.
I have attached two screenshots, one with the contrast enhanced so the issue is easier to spot.
Is this intentional? If so, "compression" should be greyed out in KDrive mode. But, on the other hand, those artifacts are annoying, so we need to make them go away somehow. Should I file a bug?
Kind Regards, Stefan Baur
--
Oleksandr Shneyder | Email: o.shneyder@phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Schleiermacherstr. 2 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461
Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder