Closed krokodyl1220 closed 2 years ago
@krokodyl1220 There was indeed an old define for the most recent GFX version A0600
instead of A0601
but I can still connect and have AVC444
from a 21H2 windows 10.
FYI:
AVC420
is only supported by windows 8.1 (and equivalent server os versions) and no longer available with windows 10AVC444
usually requires some adjustments with gpedit
to be enabled (I usually set Prioritize H.264/AVC 444 graphics mode for Remote Desktop Connections
but not sure this is the only key required)RFX
or PROGRESSIVE
codecsThank you for the clarification regarding AVC420.
Regarding the configuration on Windows side, I already tried different configurations, what I tried first were all modifications from this reddit thread, but no success. I also tried disabling the Use hardware graphics adapters
to see if this is an issue with Nvidia drivers, but no change. FYI, this is a screen from my Group Policy:
And RemoteFX settings:
@krokodyl1220 ok, sorry, don´t know the exact conditions when windows enables and when disables the AVC444 mode (I did test against a real hardware installation, maybe something with VMs is different?)
As for FreeRDP
with 2.7.0
it contains Backported #6786: Use /network:auto by default
which means if you don´t add any /rfx, /gfx, /bpp or /network
options it will announce everything we´ve got (so you end up with graphics of the latest GFX mode supported by the client and server)
For previous versions you had to use /network:auto
to get that.
@krokodyl1220 one small advice maybe:
Reset all RDP
policies to default and start with only the 2 settings containing AVC
, maybe some RFX
related options override something
Right, I will try that and let you know. According to ncomputing, it is enough to select Prioritize h264...
and that should work. We will see.
ok, good luck. closing this as it is more support than issue.
Right, thank you for your help.
Just a quick info: I compiled the FreeRDP from master branch, after running ./xfreerdp /v:192.0.2.24 /u:ap /workarea /gfx:avc444
I get The client supports version 0xA0502 of the RDP graphics protocol, client mode: 2, AVC available: 0, Initial profile: 2. Server:
So it seems that this define is fixed (just for sanity - should it be detected as 0xA0502?), but from my side the FreeRDP client seems to not advertise the AVC codec available. I also tried with +gfx-thin-client
, but I got the same effect. Am I missing something? I compiled the FreeRDP using default flags (cmake ../ & make
)
@krokodyl1220 there are different GFX
versions, your example detects as RDPGFX_CAPVERSION_105
. Details here: https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpegfx/da5c75f9-cd99-450c-98c4-014a496942b0
but it is strange that it identifies as older version, before you had RDPGFX_CAPVERSION_106
and now also RDPGFX_CAPVERSION_107
should be available.
As for building, depends if you compiled against ffmpeg or not ;)
Thank you very much for the link, I will read into the materials after work.
but it is strange that it identifies as older version, before you had RDPGFX_CAPVERSION_106 and now also RDPGFX_CAPVERSION_107 should be available.
Maybe that is the root of the problem, can I do anything to see if this is a problem with my setup or there is an issue with the code? I will later try setting up connections from Windows to Windows, also I will try FreeRDP from Fedora to check if perhaps it is an Arch issue. Anything else you would like me to try?
As for building, this is my result:
@krokodyl1220 ok, that problem is a different one (and not the issue you face), you still have a server side configuration issue.
@akallabeth I'm replying to let you know that I got it to work.
First, I set up fresh win10 21H1 VMs and verified that I properly got 2048 mode when connecting from Windows to Windows. Next, I connected from my system's freerdp xfreerdp /v:<IP>
, also got 2048.
So now I switched to my VM that I was testing before. Got 2048, enabled Configure hardware acceleration
- got 2048 and GPU encoding is visible in Task Manager. :man_facepalming:
I honestly have no clue what changed, apart from me installing Arch update after work. Perhaps this was the solution, but I still have FreeRDP version 2.7.0.
For anybody who stumbles upon this note:
Prioritize H264 mode
if you wish to use a gpu, enable also:
Use hardware graphics adapters for all Remote desktop sessions
Configure H.264/AVC hardware encoding
Anyway, thank you very much for your help, this helped me clear up my mind
Hi,
I am trying to setup RDP connection to my Windows 10 VM to use AVC444, together with hardware encoding acceleration and currently have zero success, either with Remmina or bare freerdp. However I tried, I could not get AVC compression to work, even running on CPU.
I am testing the results of the connection using Windows' Event Viewer, and I am looking at the output of the event 162 or 163. Here are the results I got based on the different configuration options from Remmina
color depth
dialog or different freerdp options - the logs are from Applications and Services Logs -> Microsoft -> Windows -> RemoteDesktopServices-RdpCoreTS -> Operational:So from what I can see is that the supported version detected by Windows is:
So it seems like for AVC 444 RDP falls back to RFX, and even though for AVC 420 the supported version advertised by the client is higher it still shows that AVC is not available.
Is this an error on freerdp side?
Application details
xfreerdp /version
):This is FreeRDP version 2.7.0 (2.7.0)
xfreerdp /v:ip /gfx:avc444
xfreerdp /buildconfig
: buildconfig.txt/log-level:trace 2>&1 | tee log.txt
log.txtEnvironment (please complete the following information):