Streaming shows one frame and goes back to loading screen on Raspberry Pi 4 Bookworm 64-bit #1480
Comments
|
Are you booting directly into TTY, or are you switching to TTY1 from the GUI? Make sure it's the former. Also, you can remove the
|
Done, nothing changed I'm afraid.
You got me: the log was from a SSH session - sorry, my bad. Here is from a TTY session: The command line was: eglfs.json (in a desperate attempt to make this work :-): {
"device": "/dev/dri/card0",
"outputs": [
{
"name": "HDMI1",
"mode": "3840x2160"
}
]
}I have nothing else running that uses the GPU: it's a barebone Raspberry Pi OS Lite installation with nothing else but Moonlight. I also tried moonlight-embedded but with different results: streaming works, but only at low bitrate (<= 20 mbit) and only in H264. I'd rather use moonlight-qt anyway. |
|
Weird. I have pretty much the exact same setup*, in multiple places. *EDIT: Not quite, I'm on Bullseye 6.1.19. What about this stuff? I've never needed any of those options, except maybe the last two. And here's what I have for driver overlays: Is it any different if you launch into the moonlight GUI with no additional options, instead of issuing the |
|
This seems suspect too. My RPis always use |
Those were options from a previous installation, legacy options which are for the most part ignored (except for the last two, as you said, which should still be valid). I commented all out to no avail.
I tried with the cma overlay (I didn't know about it), both with
The eglfs configuration file was actually a desperate test too. A new log moonlight.log is attached with:
No, those were options I added later as an experiment: the first thing I did was launch moonlight-qt without any parameter like I always do on the other system. |
|
As a later experiment, I tried to replicate as much as possible what the Kodi extension does - the one I use in the other (working) system. Here is my script: #!/bin/bash
export QT_SCALE_FACTOR=0.9
export QT_QPA_EGLFS_PHYSICAL_WIDTH=$( awk "BEGIN { print int($QT_SCALE_FACTOR*437)}" )
export QT_QPA_EGLFS_PHYSICAL_HEIGHT=$( awk "BEGIN { print int($QT_SCALE_FACTOR*250)}" )
export QT_LOGGING_RULES="qt.qpa.*=true"
export QT_QPA_EGLFS_KMS_CONFIG=eglfs.json
export QT_QPA_EGLFS_ALWAYS_SET_MODE=0
export SDL_AUDIO_DRIVER=alsa
moonlight-qt -platform eglfs stream gaming 'Steam Big Picture'I tried with both values of eglfs config file: cmdline.txt: config.txt: EDIT: at this point, if we can determine that the problem is not with my system configuration, I can help debugging this in a more advanced way if needed. |
|
Very strange. It should just work out of the box. I'll have to try a fresh Bookworm image at some point. Are there any related messages in |
|
I didn't think about that, here it is with With Same logs continue to appear until I (forcibly) kill Moonlight. I wonder why the weird resolutions: I can understand 1920x1088, but where did 1280x736 and 1344x736 come from? |
|
That's all normal, except for the fact that they keep repeating continuously when it should be staying at the Does the OSMC build support HEVC, or was it using H264? Is your host actually able to provide an HEVC stream? The way you (we) are setup, Moonlight will only support HEVC. What do the Sunshine logs on your host look like? |
|
Moonlight was configured with codec autodetection, but I'm pretty sure it would autoselect HEVC. Anyway I configured it to force hardware encoding and HEVC codec. On the server I can see it is sending HEVC: I don't understand how other people can run it perfectly fine. I could try another installation from scratch and try following #1484 to the letter, maybe I'll have more luck. |
Describe the bug
When I try to start a stream (from Sunshine host), Moonlight constantly switches between the "Resuming" screen and the stream: the stream shows only a single frame and then goes back to the "Resuming" screen.
Steps to reproduce
Just start a stream on a Raspberry Pi 4 running Raspberry Pi OS 64-bit Bookworm.
Other Moonlight clients
On the same hardware, using the latest version of OSMC, Moonlight works perfectly. I'm trying to replicate the same configuration in my Bookworm installation.
Moonlight settings (please complete the following information)
No changes from default except resolution (1080p).
Client PC details (please complete the following information)
Server PC details (please complete the following information)
Moonlight Logs (please attach)
moonlight.log
Additional context
I also installed Pulseaudio (following the instructions on the wiki page) and rebooted but nothing changed.
If I use latest OSMC (based on Debian Bullseye so running a very old 5.x kernel), Moonlight works perfectly. I tried many things, I don't know what else to do:
video=cmdline optionOn both systems (OSMC and Raspberry Pi OS), I start Moonlight from a bare TTY.
Bookworm config.txt:
OSMC config.txt (perfectly working system):
Might be similar to #1336, and I recently saw a user reporting a very similar issue on Discord.
The text was updated successfully, but these errors were encountered: