-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x264 not working #3141
Comments
@thexperiments - H.264 isn't yet supported in v0.10.x. From the release notes
|
I know, but arch is building from the devel branch sources thus I was hoping it is in there already. Is there a branch I can use to test it? |
There's nothing for this in What will become the next version of xrdp is documented on this wiki page. v0.10.x was a big release graphics-wise, and we're still working on the issues that are being reported against it. |
Ok thanks, understand that. |
@Nexarian - is there any way you can make use of @thexperiments offer above? I'll admit I'm not fully up to speed on where you and Jay have gotten to with this. |
x264 was merged into devel awhile ago? I'll take a look |
I built and installed devel on Ubuntu 24.04/VirtualBox.
Accessed from both Windows 10 (mstsc.exe) and Windows 11.
It looks working. |
@thexperiments: @Hiero32's testing matches mine. Can you try again on a clean VM? |
Interesting, what config are you using? (damn always posting from wrong account) |
You need to build with Try this gist to install it. |
I have both as can be seen in the initial issue. I was thinking about any config for xorg or similar. I can't see anything in the gist that I currently don't have... can't easily apply it as I'm on arch with KDE |
Looks like both clients I was using do not support h264... investigating...
|
it becomes more mysterious, debugging with GDB now Thread 6 "xrdp" hit Breakpoint 2, xrdp_mm_egfx_caps_advertise (user=0x77cb4e6ca110, caps_count=9, versions=<optimized out>, flagss=<optimized out>)
at /usr/src/debug/xrdp-devel-git/xrdp-devel-git/xrdp/xrdp_mm.c:1380
1380 version = ver_flags[index].version;
(gdb) print best_pro_index
$1 = <optimized out>
(gdb) print best_h264_index
$2 = <optimized out> |
You have to recompile XRDP with --enable-all-debug |
Really wired, build log tells me it is compiled with the right configure resulting in right defines...
|
also after building with --enable--all-debug I still can't set a breakpoint to xrdp_mm.c:1414 it jumps to 1418 (next thing that is not optimized away) |
You may have to change the |
If you're on Ubuntu, you might want to add |
I built and installed xrdp-devel-git and xorgxrdp-devel-git on arch linux. desktop is gnome. h264 is working.
I just added --enable-vsock and --enable-x264 to PKGBUILD of xrdp-devel-git.
|
It started working after changing the optimization yesterday night. I see GPU use (although I think h264 is still software right) but the performance is still meh maybe 5-10 FPS with quite some latency, any hints at what performance to expect. Connection is local to a VM |
Switched back to vsock and performance is a bit better. Had switched to tcp earlier to try clients from differnt machines |
xrdp version
devel
Detailed xrdp version, build options
Operating system & version
arch
Installation method
other
Which backend do you use?
xorgxrdp
What desktop environment do you use?
KDE
Environment xrdp running on
VM with Nvidia 1080 TI via HyperV Partitioning
What's your client?
HyperV Enhanced session / Windows 11 RDP client
Area(s) with issue?
Performance
Steps to reproduce
sudo less /var/log/xrdp.log | grep xrdp_encoder
[INFO ] xrdp_encoder_create: starting gfx rfx pro codec session
✔️ Expected Behavior
Session uses h264
❌ Actual Behavior
session is using rfx pro instead of h264
Anything else?
Using AUR
Can't find any references to XRDP_USE_HELPER in the inis or code.
Are there any other magic things I need to configure or is there simply some code missing still?
Wondering if there is something wrong with the flags to not fall into this:
xrdp/xrdp/xrdp_mm.c
Line 1412 in 1d927ad
The text was updated successfully, but these errors were encountered: