Hi Martin,
only hardware support is currently though ffmpeg H264 decoding but due to the way RDP uses H264 the yuv to rgb conversion is still done on the CPU best regards Armin On 1/8/19 2:57 PM, Martin Ciglan wrote: > Hi Armin > > Thanks a lot for your valuable answers. > > Does freeRDP2 support HW H.264 or H.265 decoding on client GPU? Any > particular chip? Thanks. > > Best Regards > > Martin > _<http://www.sino-zc.com/>_ > > > > Dňa 6. 1. 2019 o 9:34 Armin Novak via FreeRDP-devel napísal(a): >> Hi Martin, >> >> 1. +gfx-h264:avc420 is invalid syntax, better use /gfx:avc444 or /gfx- >> h264:avc44 (avc420 is not used by newer microsoft servers, but avc444 >> still falls back to that) >> >> /buildconfig of your client would be interesting (assume debian? NEON >> acceleration should be activated, but I'm not sure) >> >> 1a. /sound is better off without any additional arguments. (except you >> disabled pulse on your installation this is ususally the better choice) >> >> 2. As for displaying protocol versions, that is not that easy and not >> implemented in the X11 client. You can use /log-level:debug (or /log- >> filters:<some tag>:debug) to get an idea which codecs are used. >> >> 3. FreeRDP is an RDP protocol implementation, we support a lot of the >> protocol, but not everything (most prominently we currently only use >> TCP for transport). Features start appearing in certain versions which >> are mentioned there. What I can tell the `RDP 10` Term refers to all >> protocol features supported by a current windows 10 machine, so >> strictly speaking we don't support the full set. (For example, graphics >> wise we do support the current standard, but we lack DRM support in >> audio channels) >> >> 4. The feature is announced, but it is up to the server configuration >> to actually use it >> >> 5. gpedit.msc 'Computer Configuration > Administrative Templates > >> Windows Components > Remote Desktop Services > Remote Desktop Session >> Host' is where all the settings are. Check if RFX and GFX features are >> activated, sometimes they are not. >> >> best >> Armin >> >> On Fri, 2019-01-04 at 12:52 +0100, Martin Ciglan via FreeRDP-devel >> wrote: >>> Hi >>> >>> I am testing >>> freerdp2-x11_2.0.0~git20181120.1.e21b72c95+dfsg1-1_arm64.deb on 64- >>> bit >>> ARMv8 machines. >>> This is the way I run it in order to achieve best performance on >>> client >>> (ODROID C2, ubuntu bionic): >>> >>> xfreerdp /u:<user> /p:<password> /v:<ip-address> /f /sound:sys:alsa >>> /microphone:sys:alsa /network:auto +multitransport +gfx-h264:AVC420 >>> +fonts /rfx >>> >>> I test general work on targeted Windows machine, WebGL and youtube >>> videos. Performance is quite OK. >>> >>> My questions: >>> 1. Is there anything else what could help client to perform even >>> better? >>> 2. Is it possible to force freeRDP to display used >>> protocol/version/details, etc during session? I've tried /disp but >>> that >>> doesn't do anything. >>> 3. I thought freeRDP2 is an open-source implementation of Microsoft >>> RDP >>> 10. If I look at help of h264 support, I see RDP 8.1 mentioned. >>> Can someone make this clear to me please? >>> 4. Is remoteFX actively used if I allow it with /rfx switch? >>> 5. Is it necessary to do any changes to policies/registry on >>> targeted >>> machine in order to achieve better performance? >>> >>> Many thanks >>> >>> Martin >>> >>> >>> _______________________________________________ >>> FreeRDP-devel mailing list >>> FreeRDP-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/freerdp-devel >> _______________________________________________ >> FreeRDP-devel mailing list >> FreeRDP-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freerdp-devel > _______________________________________________ FreeRDP-devel mailing list FreeRDP-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel