DietPi-Software | Moonlight Qt : GUI game streaming client for Sunshine and NVIDIA GameStream

[mtekman]

This is based on PR #6303 as discussed here #6303 (comment)

[MichaIng]

So this can run with full KMS, but only from console, or with fake KMS from desktop. I guess it could even run from desktop as well, but would need to be forced to run in DRM/KMS mode. I'll run some tests.

[mtekman]

I guess it could even run from desktop as well, but would need to be forced to run in DRM/KMS mode.

Are you referring to the H264_DECODER_HINT=h264_v4l2m2m DRM_FORCE_DIRECT=1 moonlight-qt command from here?

I'll run some tests.

Appreciated!

[MichaIng]

Are you referring to the H264_DECODER_HINT=h264_v4l2m2m DRM_FORCE_DIRECT=1 moonlight-qt command from here?

Yes, or something like the -platform CLI options of Moonlight embedded.

[MichaIng]

I tried starting it from console on RPi 2 with fKMS and KMS, with and without H264_DECODER_HINT=h264_v4l2m2m DRM_FORCE_DIRECT=1. In all cases, it starts up, but it has a large black border at the top with overlays parts of the GUI. However, it auto-detects the Sunshine server. I can pair it and connect, then select the Desktop app there, but it starts and stops immediately... Ah lol, now when I tried the exact same from SSH, it suddenly worked. Again, here I finish the text from keyboard and monitor attached to the RPi.

This was with full KMS and without any environment variable. It tells me on the SSH console that I should switch to fKMS and/or apply the rpivid-v4l2 overlay. But it does steam now.

00:00:03 - FFmpeg: [hevc_v4l2m2m @ 0x2940c20] v4l2 output format not supported
00:00:03 - FFmpeg: [hevc_v4l2m2m @ 0x2940c20] Could not find a valid device
00:00:03 - FFmpeg: [hevc_v4l2m2m @ 0x2940c20] can't configure decoder
00:00:03 - FFmpeg: [hevc_v4l2m2m @ 0x2940c20] V4L2 Codec end
00:00:03 - FFmpeg: V4L2 Context destroyed
00:00:03 - SDL Error (0): Unable to open decoder for format: 100
00:00:03 - SDL Error (0): Unable to load FFmpeg decoder
00:00:03 - SDL Info (0): V-sync disabled
00:00:03 - SDL Error (0): Full KMS Mode is enabled! Hardware accelerated H.264 decoding will be unavailable!
00:00:03 - SDL Error (0): Change 'dtoverlay=vc4-kms-v3d' to 'dtoverlay=vc4-fkms-v3d' in /boot/config.txt to fix this!
00:00:03 - SDL Warn (0): Raspberry Pi HEVC decoder is not enabled! Add 'dtoverlay=rpivid-v4l2' to your /boot/config.txt to fix this!
00:00:03 - SDL Info (0): Using SDL renderer

Again, I'm missing a magic key to exit streaming. Other than the embedded version, it does not even listen to SIGTERM or SIGINT but only to hard SIGKILL.

EDIT: Ah, from the overlays README:

Name:   rpivid-v4l2
Info:   This overlay has been deprecated and deleted as the V4L2 stateless
        video decoder driver is enabled by default.
Load:   <Deprecated>

So adding this is not required anymore. AFAIK full GPU support for this was on RPi 4 only, so I cannot really test the full KMS hardware acceleration, I guess. Testing with fake KMS again.

The quit CLI command does not work for me with embedded as well as Qt version. The list command in Qt version hangs forever and can only be stopped via SIGKILL, same as the desktop stream.

[MichaIng]

FFmpeg is used for hardware accelerated video decoding, actually. Shall we install it OOTB?

aSOFTWARE_DEPS[$software_id]=7

EDIT: A nope those FFmpeg parts seem to be embedded, so no external library needed.

When starting from the desktop, the GUI btw is all correct, so only the DRM console variant has this issue with the too large black top border.

[MichaIng]

@mtekman
The README actually shows the name "Moonlight PC": https://github.com/moonlight-stream/moonlight-qt
Shall we use that as well? It might be a little confusing since we currently offer the APT packages for RPi only, where "PC" is just a misleading term 🤔. On the other hand, "Moonlight" is shown on their GitHub repo and website as "Moonlight Embedded": https://moonlight-stream.org/

I'm wondering whether we should use own names to make the difference pretty clear, like "Moonlight (CLI)" and "Moonlight (GUI)" or so, to make sure that one is a pure CLI variant and the other is a pure GUI variant? Or follow the official naming from their repos? Or just ask THEM for a preference? 🙂

[mtekman]

I'm wondering whether we should use own names to make the difference pretty clear, like "Moonlight (CLI)" and "Moonlight (GUI)" or so, to make sure that one is a pure CLI variant and the other is a pure GUI variant?

I'm up for this, it's a pretty clear distinction that will only help users decide what they want. My first impression of moonlight was that it would have a GUI like the android app, and it was only later that I realised what moonlight-qt was

[MichaIng]

Okay, let's do it that way. Usually I'm for following the developers/manufacturers official naming but in this case it is confusing indeed, especially as long as we offer the RPi compatible packages only.