Moonlight freezes after a few seconds

[Substring]

@Anon aye ! What is your GFE version ? 4.0.2 can run Moonlight only until GFE 3.2 or 3.1

[Anon]

@Substring Thx! As said I downgraded to 2.11 and got even worse. So I should try 3.2? Will get on it tmrw.

[Anon]

@Substring Already had time now and installed 3.2, just like before sound but blackscreen.

[Substring]

@Anon haven't used moonlight for a while on a 4.0. Might as well be GFE 3.1, i guess searching in the forum should do it

[Anon]

Right 3.1 works, for maybe the first 5-10 seconds even before the "Start" button for Zelda Wind Waker appears.

[Anon]

So yeah, I had 3.1.2 and even downgraded to 3.1.0 now, screen freezes completly within a few seconds on TV but still works fine on PC. Any idea?
@Substring

[Anon]

Can the title be renamed to "Moonlight freeze after a few seconds" or do I need make a new topic to maybe seek some more attention? Thx.

[Substring]

@Anon edited.
Still, i'm surprised by this behaviour. Mind forgetting devices on GFE, then run the Moonlights.sh with options clean then pair then init ? So that you start from a "blank" client

By the way, does it freeze for steam games ?

[Anon]

@Substring Hey and sry I was a bit inactive lately. After the clean it ends for me currently at this point..

Succesfully paired
./Moonlight.sh init
Fetching games from ...
Scraping games ...
cat: can't open '/recalbox/share/system/configs/moonlight/gamelist.txt': No such file or directory
./Moonlight.sh init
Fetching games from ...
Scraping games ...
cat: can't open '/recalbox/share/system/configs/moonlight/gamelist.txt': No such file or directory
touch /recalbox/share/system/configs/moonlight/gamelist.txt
./Moonlight.sh init
Fetching games from ...
Scraping games ...
cat: can't open '/recalbox/share/system/configs/moonlight/gamelist.txt': No such file or directory
ls -al /recalbox/share/system/configs/moonlight/gamelist.txt
ls: /recalbox/share/system/configs/moonlight/gamelist.txt: No such file or directory
ls -al /recalbox/share/system/configs/moonlight/
total 28
drwxr-xr-x 3 root root 4096 Jun 9 08:32 .
drwxr-xr-x 7 root root 4096 Jan 1 1970 ..
drwx------ 2 root root 4096 Jun 9 08:31 keydir
-rw-r--r-- 1 root root 627 May 28 18:31 mappingP1.conf
-rw------- 1 root root 541 May 28 18:31 mappingP2.conf
-rw------- 1 root root 541 May 28 18:31 mappingP3.conf
-rw-r--r-- 1 root root 1803 May 26 14:55 moonlight.conf
vi /recalbox/share/system/configs/moonlight/gamelist.txt
./Moonlight.sh init
Fetching games from ...
Scraping games ...
cat: can't open '/recalbox/share/system/configs/moonlight/gamelist.txt': No such file or directory
ls -al /recalbox/share/system/configs/moonlight/
total 28
drwxr-xr-x 3 root root 4096 Jun 9 08:32 .
drwxr-xr-x 7 root root 4096 Jan 1 1970 ..
drwx------ 2 root root 4096 Jun 9 08:31 keydir
-rw-r--r-- 1 root root 627 May 28 18:31 mappingP1.conf
-rw------- 1 root root 541 May 28 18:31 mappingP2.conf
-rw------- 1 root root 541 May 28 18:31 mappingP3.conf
-rw-r--r-- 1 root root 1803 May 26 14:55 moonlight.conf

Cut that, that happens without proper reading.. forgot cleaning GFE. Have to try again then soon.

[Anon]

Only blackscreen now.

[Substring]

@Anon said in Moonlight freezes after a few seconds:

cat: can't open '/recalbox/share/system/configs/moonlight/gamelist.txt': No such file or directory

this error message is tricky ...

[Anon]

@Substring Well as you see in the message I tried to create the file which didn't work and it was fixed after I cleaned GFE and re-paired again with cleaning, now it's blackscreen again.

[Substring]

@Anon This rather looks like pair / init is not working. So, forget paired devices on GFE, and on recalbox, run the script once with each of these parameters : clean then pair then init

[Anon]

@Substring That's exactly what I did and what I said after I had the error with the file. I fully forgot all devices in GFE, cleaned Moonlight and paired them again. You want me to do it again?

So did it again with reboot and now it's only showing version 4.0.2 and "recalbox" with logo at the bottom.
/etc/init.d/S31emulationstation stop
cd /recalbox/scripts/moonlight
./Moonlight.sh clean
You can now pair again your recalbox with a PC
./Moonlight.sh clean
You can now pair again your recalbox with a PC
./Moonlight.sh pair
Moonlight Embedded 2.2.2 (EMBEDDED;CEC;PI)
Too many options: No such file or directory
Moonlight Embedded 2.2.2 (EMBEDDED;CEC;PI)
Searching for server...
Connect to 192.168.178.21...
Generating certificate...done
NVIDIA GeForce GTX 770, GFE 3.1.0.44 (protocol version 7)
Please enter the following PIN on the target PC: 2150
1017 / 1017
Succesfully paired
./Moonlight.sh init
Fetching games from ...
Scraping games ...
shutdown -r now

Broadcast message from root@RECALBOX (pts/1) (Mon Jun 12 13:43:10 2017):

The system is going down for reboot NOW!

[Substring]

@Anon still the same problem ? Have you edited the moonlight.conf file ?

[Anon]

@Substring Isn't a full blackscreen anymore, it has the recalbox footer and stays black. But yes, config should be standard:

##Hostname or IP-address of host to connect to
##By default host is autodiscovered using mDNS
#address =

##Video streaming configuration
width = 1920
height = 1080
fps = 60

##Bitrate depends by default on resolution and fps
##Set to -1 to enable default
##20Mbps (20000) for 1080p (60 fps)
##10Mbps (10000) for 1080p or 60 fps
##5Mbps (5000) for lower resolution or fps
bitrate = -1

##Size of network packets should be lower than MTU
#packetsize = 1024

##Default started application on host
#app = Steam

##Default used mapping for streaming
##Searched for in $XDG_DATA_DIRS/moonlight or /usr/share/moonlight and /usr/local/share/moonlight
##Mapping can also be user overrided in $XDG_CONFIG_DIR/moonlight or ~/.config/moonlight or current directory
#mapping = mappings/default.conf

##Enable selected input devices
##By default all available input devices should be used
##Only evdev devices /dev/input/event* are allowed
##To use a different mapping then default another mapping should be declared above the input
#input = /dev/input/event1

##Let GFE change graphical game settings for optimal performance and quality
sops = true

##Play audio on host instead of streaming to client
#localaudio = false

##Select audio device to play sound on
#audio = sysdefault

##Select the audio and video decoder to use
##default - autodetect
##omx - hardware video decoder for Raspberry Pi
##imx - hardware video decoder for i.MX6 devices
##sdl - software decoder
##fake - save to file (only available in debug builds)
platform = default

##Directory to store encryption keys
##By default keys are stored in $XDG_CACHE_DIR/moonlight or ~/.cache/moonlight
keydir = /recalbox/share/system/configs/moonlight/keydir

##Load additional configuration files
#config = /path/to/config

[Substring]

I'm clueless ... Woumd need to manually launch moonlight

[Anon]

@Substring Mh, I will try some things then. What do you mean with "Woumd need to manually launch moonlight"?

[Substring]

@Anon I need you to start moonlight the way recalbox does it so that we can check the output of moonlight.

[Anon]

@Substring Hey, not quite sure what you mean. Mind explaining?

What I did now was editing the Moonlight conf, set a bitrate of 50000 and set the platform to "pi", sops to false.
I installed the newest drivers from a few days ago and installed GFE 3.1.2.31, cleaned everything and paired with still the same result.

The only error output when launching is:
Failed to initialize libcec interface

The rest is just a mass spam of:
Returning RTP packet queued for too long
Network dropped middle of a frame
Returning RTP packet queued for too long
Returning RTP packet queued for too long
Returning RTP packet queued for too long
Returning RTP packet after queue overgrowth
Returning RTP packet after queue overgrowth
Network dropped end of a frame
Returning RTP packet after queue overgrowth
Network dropped end of a frame
Returning RTP packet queued for too long
Network dropped middle of a frame
Returning RTP packet queued for too long
Network dropped middle of a frame
Returning RTP packet queued for too long
Returning RTP packet queued for too long
Returning RTP packet queued for too long
Returning RTP packet after queue overgrowth
Returning RTP packet queued for too long
Network dropped middle of a frame
Returning RTP packet queued for too long
Returning RTP packet after queue overgrowth
Returning RTP packet queued for too long
Network dropped middle of a frame
Returning RTP packet queued for too long
Returning RTP packet queued for too long
Returning RTP packet queued for too long
Waiting for IDR frame
IDR frame request sent
Returning RTP packet queued for too long
Network dropped middle of a frame
Returning RTP packet queued for too long
Returning RTP packet queued for too long
Returning RTP packet queued for too long
Returning RTP packet queued for too long
Waiting for IDR frame
Waiting for IDR frame
IDR frame request sent
Returning RTP packet queued for too long
Network dropped middle of a frame
Returning RTP packet queued for too long

It's still just the recalbox footer in a black screen with sound.