akallabeth

@pthoelken try adding /network:auto and if that does not work well only /gfx or /rfx The first one activates bandwidth detection, the second one lrss cpu hungry codecs. You should...

There is no log, just terminal output. Leave out the avc444 for the second one.

Well, the test cases with only /rfx and only /gfx are missing ;)

@pthoelken ok, looks like you have a really interesting server side ;) windows 8.1 (or the server equivalent) based? Better use something like `/rfx /gfx` or just `/rfx` in this...

@pthoelken try checking out master and build yourself. (and compile against OpenH264 to have a faster H264 decoder)

@pthoelken I´ve forgotten to ask, we´re talking about a 1080p monitor here and not 4k? The former should work quite fine, 4k though is a bit too much for the...

@pthoelken ok, then you should check your graphics driver, there are great differences there too. I have a PI3 and can run with ~15FPS so the PI4 should definitely be...

@henk717 software decoding only. with `FFMPEG` you might be able to offload (some) decoding work, but RDP uses some customized codecs/extensions that have no hardware acceleration available. If you already...

@kishorv06 `FreeRDP` currently does not utilize `vulkan` or any other method to move decoding load to the `GPU` (raspberry is not very good there either) Most of the load a...

@lollo0296 bad news then, `xfreerdp` did not change the way it does drawing for a decade, you can stop experimenting with different versions. This looks like the newer hardware (or...