Doesn't work randomly using OBS

Question

Doesn't work randomly using OBS

Opened this issue 2 years ago · 10 comments

Hi, all commands works, but when I switch to game, and come back to desktop, the commands don't respond, so I have to reconnnect OBS with icon bottom left.
I'm using last version. Is there a log file to check?
thank youu

Answer 1 · 2023-01-08T17:59:00.000Z

It happens for all games ? Or only a specific one ?

Answer 2 · 2023-01-08T18:06:46.000Z

Warzone for sure, I try to test with other windows or applications Il giorno dom 8 gen 2023 alle 18:59 RENAUD-GOUD Arnaud < ***@***.***> ha scritto:

It happens for all games ? Or only a specific one ? — Reply to this email directly, view it on GitHub <#27 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABS5P2ISRASHJBSI3RWXMITWRL565ANCNFSM6AAAAAATUVBFNU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Sent from Gmail Mobile

Answer 3 · 2023-01-09T09:51:16.000Z

It happens for all games ? Or only a specific one ?

ok, it is random. After 10 seconds or after 2 minutes..... in the OBS log I can't see anything.
When it happens, usually moving the volume up or down, the toggle move for 2mm, than all commands stop working

Answer 4 · 2023-01-09T12:54:14.000Z

Seems to be a time-out of the websocket.
When it happens, before you try to reconnect, could you check on OBS under the "Websocket server settings" if there is still an existing session ?

Answer 5 · 2023-01-09T13:01:40.000Z

is this related to using the LATEST obs version ? because they introduced .. 5.01 websocket .. in the latest update.. i will not update to this version untill i know MidiControl works with it ..

Answer 6 · 2023-01-09T13:16:22.000Z

MidiControl should be compatible with latest version of OBS.

Answer 7 · 2023-01-09T13:22:33.000Z

really? even if they have announced using a NEW version of websocket? which they have ..

Answer 8 · 2023-01-09T13:44:26.000Z

sense-amr commented 2 years ago

Answer 9 · 2023-01-11T10:51:50.000Z

Seems to be a time-out of the websocket. When it happens, before you try to reconnect, could you check on OBS under the "Websocket server settings" if there is still an existing session ?

oh, I see your anwer now. I'll check this evening

Answer 10 · 2023-01-11T21:46:05.000Z

this is the log

22:41:22.216: [obs-websocket] [WebSocketServer::onOpen] New WebSocket client has connected from [::ffff:192.168.1.2]:57740
22:42:02.389: User switched to scene 'Desktop'
22:42:06.369: warning: Could not update timestamps for discarded samples.
22:42:15.433: [obs-websocket] [WebSocketServer::onClose] WebSocket client [::ffff:192.168.1.2]:57740 has disconnected with code 1006 and reason: Connessione in corso interrotta forzatamente dall'host remoto.
22:42:16.290: [obs-websocket] [WebSocketServer::onOpen] New WebSocket client has connected from [::ffff:192.168.1.2]:57762
22:42:50.810: User switched to scene 'Game'
22:42:54.802: warning: Could not update timestamps for discarded samples.`

I tryed to lowering khz from 96000 to 48000 according to OBS settings, this is the new message log after unresponsive
22:50:26.172: WASAPI: Device '[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]' [48000 Hz] initialized

this is the setting for my Audient audio card:
Sample rate 48.000 khz
Asio Buffering 2048 samples

I'm thinking is something related to Audio, do you agree? or the code "1006" error