search

OneLiberty / moonlight-chrome-tizen

A WASM port of Moonlight for Samsung Smart TV's running Tizen OS (5.5 and up)
GNU General Public License v3.0
185 stars 15 forks source link

Client disconnects after a few seconds of black screen with audio. #30

Closed MrOrange9-JCT closed 4 months ago

MrOrange9-JCT commented 5 months ago

Yesterday this was working so I don't know:

I am using the Samsung Tizen version (which is based on the chrome os version) and I can't stream anything. It connects fine, but after about 5 seconds the client disconnects. The screen is always black but I can hear the audio. I've ruled out it being a Sunshine issue because it works on another device (My Android phone)

Logs

OneLiberty commented 5 months ago

Seeing some WSASendMsg() failed: 10022. Could you get moonlight's logs ? #9

Also, what's your stream config ? Did you try different codecs ? Try setting the bitrate to 29.

MrOrange9-JCT commented 5 months ago

I've tried all codecs with no solution. I've also tried setting the bitrate to 29. My stream config is: 6 Mbps bitrate (My internet is not that great), 1080p, 60 FPS, HEVC Main 10.

Here are Moonlight's logs (I've let out some parts I don't consider important, but if you feel that they are necessary, please tell me so):

startStream host: 192.168.1.10 w: 1920 h: 1080
messages.js:68 [messages.js, handleMessage] Message data:  Setting stream width to: 1920
messages.js:68 [messages.js, handleMessage] Message data:  Setting stream height to: 1080
messages.js:68 [messages.js, handleMessage] Message data:  Setting stream fps to: 60
messages.js:68 [messages.js, handleMessage] Message data:  Setting stream host to: 192.168.1.10
messages.js:68 [messages.js, handleMessage] Message data:  Setting stream bitrate to: 6000
messages.js:68 [messages.js, handleMessage] Message data:  Setting rikey to: 3826da1eb4b53a198523c0f7468d114d
messages.js:68 [messages.js, handleMessage] Message data:  Setting rikeyid to: -346117177
messages.js:68 [messages.js, handleMessage] Message data:  Setting appversion to: 7.1.431.-1
messages.js:68 [messages.js, handleMessage] Message data:  Setting gfeversion to: 
messages.js:68 [messages.js, handleMessage] Message data:  Setting RTSP url to: rtsp://192.168.1.10:48010
messages.js:68 [messages.js, handleMessage] Message data:  Setting frame pacing to: 1
messages.js:68 [messages.js, handleMessage] Message data:  Setting audio syncing to: 1
messages.js:68 [messages.js, handleMessage] Message data:  Setting HDR to:0
messages.js:68 [messages.js, handleMessage] Message data:  Setting videoCodec: 0x0200
messages.js:68 [messages.js, handleMessage] Message data:  Starting connection to 192.168.1.10
moonlight-wasm.js:1 RTSP port: 48010

moonlight-wasm.js:1 Initializing platform...
messages.js:68 [messages.js, handleMessage] Message data:  ProgressMsg: Starting platform initialization...
moonlight-wasm.js:1 done

moonlight-wasm.js:1 Resolving host name...
messages.js:68 [messages.js, handleMessage] Message data:  ProgressMsg: Starting name resolution...
moonlight-wasm.js:1 done

moonlight-wasm.js:1 Initializing audio stream...
messages.js:68 [messages.js, handleMessage] Message data:  ProgressMsg: Starting audio stream initialization...
moonlight-wasm.js:1 done

moonlight-wasm.js:1 Starting RTSP handshake...
messages.js:68 [messages.js, handleMessage] Message data:  ProgressMsg: Starting RTSP handshake...
moonlight-wasm.js:1 setsockopt(TCP_MAXSEG, 536) failed: 50

moonlight-wasm.js:1 setsockopt(TCP_MAXSEG, 536) failed: 50

moonlight-wasm.js:1 setsockopt(TCP_MAXSEG, 536) failed: 50

moonlight-wasm.js:1 Audio port: 48000

moonlight-wasm.js:1 setsockopt(TCP_MAXSEG, 536) failed: 50

moonlight-wasm.js:1 Video port: 47998

moonlight-wasm.js:1 setsockopt(TCP_MAXSEG, 536) failed: 50

moonlight-wasm.js:1 Control port: 47999

moonlight-wasm.js:1 setsockopt(TCP_MAXSEG, 536) failed: 50

moonlight-wasm.js:1 setsockopt(TCP_MAXSEG, 536) failed: 50

moonlight-wasm.js:1 done

moonlight-wasm.js:1 Initializing control stream...
messages.js:68 [messages.js, handleMessage] Message data:  ProgressMsg: Starting control stream initialization...
moonlight-wasm.js:1 done

moonlight-wasm.js:1 Initializing video stream...
messages.js:68 [messages.js, handleMessage] Message data:  ProgressMsg: Starting video stream initialization...
moonlight-wasm.js:1 done

moonlight-wasm.js:1 Initializing input stream...
messages.js:68 [messages.js, handleMessage] Message data:  ProgressMsg: Starting input stream initialization...
moonlight-wasm.js:1 done

moonlight-wasm.js:1 Starting control stream...
messages.js:68 [messages.js, handleMessage] Message data:  ProgressMsg: Starting control stream establishment...
moonlight-wasm.js:1 done

moonlight-wasm.js:1 Starting video stream...
messages.js:68 [messages.js, handleMessage] Message data:  ProgressMsg: Starting video stream establishment...
moonlight-wasm.js:1 MoonlightInstance::VidDecSetup

moonlight-wasm.js:1 done

moonlight-wasm.js:1 Starting audio stream...
messages.js:68 [messages.js, handleMessage] Message data:  ProgressMsg: Starting audio stream establishment...
moonlight-wasm.js:1 MoonlightInstance::AudDecSetup

moonlight-wasm.js:1 done

moonlight-wasm.js:1 Starting input stream...
messages.js:68 [messages.js, handleMessage] Message data:  ProgressMsg: Starting input stream establishment...
moonlight-wasm.js:1 done

messages.js:68 [messages.js, handleMessage] Message data:  Connection Established
moonlight-wasm.js:1 Terminating connection due to lack of video traffic

moonlight-wasm.js:1 ENet wait interrupted

moonlight-wasm.js:1 Control stream connection failed: -1

moonlight-wasm.js:1 Stopping input stream...
moonlight-wasm.js:1 done

moonlight-wasm.js:1 Stopping audio stream...
moonlight-wasm.js:1 No audio traffic was ever received from the host!

moonlight-wasm.js:1 done

moonlight-wasm.js:1 Stopping video stream...
moonlight-wasm.js:1 No video traffic was ever received from the host!

moonlight-wasm.js:1 done

moonlight-wasm.js:1 Stopping control stream...
moonlight-wasm.js:1 ENet peer acknowledged disconnection

moonlight-wasm.js:1 done

moonlight-wasm.js:1 Cleaning up input stream...
moonlight-wasm.js:1 done

moonlight-wasm.js:1 Cleaning up video stream...
moonlight-wasm.js:1 done

moonlight-wasm.js:1 Cleaning up control stream...
moonlight-wasm.js:1 done

moonlight-wasm.js:1 Cleaning up audio stream...
moonlight-wasm.js:1 done

moonlight-wasm.js:1 Cleaning up platform...
moonlight-wasm.js:1 done

messages.js:68 [messages.js, handleMessage] Message data:  streamTerminated: -100
index.js:259 [index.js, snackbarLog] Connection terminated

I find it weird that it says No video traffic was ever received from the host!, as it perfectly works with other devices, so I don't think its a host problem.

MrOrange9-JCT commented 5 months ago

I fixed the No audio traffic was ever received from the host! by setting the audio device manually in sunshine, but I can't seem to fix the video.

OneLiberty commented 5 months ago

Well, it's seems you're trying to stream from a local device, so your internet speed should not be an issue. It's the speed of the local network that matters. Maybe increasing the bitrate could help, tho i don't think this is the issue.

Could this issue comes from the cmd running when you try to connect ?

MrOrange9-JCT commented 4 months ago

Okay, so I feel a bit stupid now. This issue was most likely an issue with the network connection of the TV, as it is connected to a Wi-Fi mesh device that is not precisely new.