Open jeiea opened 2 years ago
Windows 11
No response
Other
28.0.1-modified (debugging)
5.0.1
https://obsproject.com/logs/4fI7d0w9iDWP4aqN
It should be correct value.
00:08:21.299: [obs-websocket] [debug] [WebSocketServer::onMessage] Outgoing message: 00:08:21.299: { 00:08:21.299: "d": { 00:08:21.299: "requestId": "c0817f9f-c6a1-44e1-a67a-ab98282413f3", 00:08:21.299: "requestStatus": { 00:08:21.299: "code": 100, 00:08:21.299: "result": true 00:08:21.299: }, 00:08:21.299: "requestType": "GetOutputStatus", 00:08:21.299: "responseData": { 00:08:21.299: "outputActive": true, 00:08:21.299: "outputBytes": 0, 00:08:21.299: "outputCongestion": 0.0, 00:08:21.299: "outputDuration": 479615345916448, <- why 00:08:21.299: "outputReconnecting": false, 00:08:21.299: "outputSkippedFrames": 0, 00:08:21.299: "outputTimecode": "133226484:58:36.448", <- why 00:08:21.299: "outputTotalFrames": 30 00:08:21.299: } 00:08:21.299: }, 00:08:21.299: "op": 7 00:08:21.299: }
I don't know reliable reproduction. I just wrote this for archiving.
This is something that I've found in my own usage. We don't do anything special and I don't know how it happens. The lack of being able to reproduce it reliably doesn't help either.
Has the problem been solved?
Operating System Info
Windows 11
Other OS
No response
OBS Studio Version
Other
OBS Studio Version (Other)
28.0.1-modified (debugging)
obs-websocket Version
5.0.1
OBS Studio Log URL
https://obsproject.com/logs/4fI7d0w9iDWP4aqN
OBS Studio Crash Log URL
No response
Expected Behavior
It should be correct value.
Current Behavior
Steps to Reproduce
I don't know reliable reproduction. I just wrote this for archiving.
Anything else we should know?
No response