Open jpietek opened 4 years ago
Moreover even when the Linux stream is working fine, there are stil console errors in the client, which does not happen when streaming with windows/obs plugin.
datadog-rum-us.js:1 Reporting error: Saga exception during channel: Request failed with status 404. Error: Request failed with status 404
at main.0e84174d49d31b4e33b9.js:1
at c (libraries.4e62538ab6231263c402.js:1)
at Generator._invoke (libraries.4e62538ab6231263c402.js:1)
at Generator.e.<computed> [as next] (libraries.4e62538ab6231263c402.js:1)
at n (libraries.4e62538ab6231263c402.js:1)
at a (libraries.4e62538ab6231263c402.js:1) {level: "warning", layer: "saga", action: "channel", actionPayload: {…}, error: Error: Request failed with status 404
at https://www.caffeine.tv/main.0e84174d49d31b4e33b9.js:1…}
At backend side I've seen 502 errors while reporting RTC stats, turned off stats reporting in StatsObserver class, but it did not help with unstable streaming.
Streaming via libcaffeine (over linux) results with a random frontend error, js console:
received error { "message": "unable to encode json response: json: error calling MarshalJSON for type json.RawMessage: invalid character 'x' in string escape code" }
Even though the backend webrtc streaming app seems to work fine, executing sendVideo and sendAudio methods in appropriate threads with encode_fps ~= input_fps etc.
The main part of the client app is as follows:
And the streaming log, which seems fine: