Hardware encoding falls back to Fluid 2.0 on Radeon Pro 580 / Boot Camp
I’m running Jump Desktop Connect 10.15.31.0 on a 2017 27-inch iMac running Windows 11 through Boot Camp.
Host GPU:
-
Radeon Pro 580
-
Driver: 30.0.13045.22003
-
AMD AMF runtime is present
Client is an Apple Silicon Mac using Fluid, with hardware decoding working normally.
When I select Hardware under Remote → Codec, it immediately falls back to Fluid 2.0. The live statistics continue to show:
-
Decoder: Hardware Apple
-
Encoder: Fluid 2.0
This reproduces with:
-
Physical host displays
-
Jump virtual displays
-
Privacy Mode on and off
-
Good / 4:2:0 8-bit color
-
60 FPS selected
The Jump diagnostic logs appear to show that the Radeon hardware encoder is detected and initialized, but then fails during H.265 encoding:
Created encoder: amd.enc.2
Initialized adapter: Radeon Pro 580
Initialized on Radeon Pro 580
Failed to set AMF property: 3
Failed to set AMF property: 4
Failed to set AMF property: 4
Failed to set AMF property: 12
SubmitInput failed: 18
Encoder error: 4
Encoder failed ... Codec name: H265
Encoder broken for track: desktopvideo
Created encoder: jump.aom.av1
Based on AMD's AMF result definitions, SubmitInput failed: 18 appears to correspond to AMF_DIRECTX_FAILED.
Is there a known compatibility issue with AMD AMF / H.265 hardware encoding on Radeon Pro 580 Boot Camp systems?
I’m also curious whether there is any way to force Jump to try AMD H.264 hardware encoding instead of H.265, since the hardware encoder itself appears to be detected successfully before the H.265 path fails.
I can provide the full JumpConnectDiagLogs.zip if useful.
Please sign in to leave a comment.
Comments
0 comments