OBS still CRASHING!

D

DevilzKnite

Member
OBS still crashing anytime I click on anything or change scene or whatever. I am not using streamelements but some vst plug ins I have to use and all the sudden it starts crashing again. I guess I will just have to use streamlabs... OBS is dog water at this point..I don't get why it works one day and then doesn't the next. In help menu it doesn't give me any crash reports.
 
D

DevilzKnite

Member
Even after a complete uninstall and reinstall, I get my scenes and audio set up and it then crashes after a restart. Was working fine while I was adding everything back. It doesn't give me any crash reports but just keeps closing OBS. Can anyone HELP!!!???
 
.norman.

.norman.

Member
does it work without ANY plugins installed? if OBS crashes it will generate a crash report. check %appdata%\obs-studio\crashes\

without a current log or crash report there is little anyone can do to help.
 
D

DevilzKnite

Member
.norman. said:
does it work without ANY plugins installed? if OBS crashes it will generate a crash report. check %appdata%\obs-studio\crashes\

without a current log or crash report there is little anyone can do to help.
Click to expand...
It's fine after a fresh install..while setting up scenes and whatever..I did get an analysis from a log file about full color range so I changed all that back to default/auto. I then exited OBS, reopened it and as soon as I changed scenes it crashed. Log file after opening OBS back up: https://obsproject.com/logs/ZEFXAjMgx8jPl0cz I can't seem to find any crash reports. When I click on Help, Show crash reports, folder is empty. When I click on Help, upload previous crash report, it does nothing. But when I click on anything like change to a scene it crashes again. Latest log file: https://obsproject.com/logs/1C0tq2uTCrA5gDcq Thanks for any help. This has been going on for days now.
 
.norman.

.norman.

Member
logs look like something using websocket is failing.

Code: 
18:40:49.976: [obs-websocket] [WebSocketServer::onObsLoaded] WebSocket server is enabled, starting...
18:40:49.976: [obs-websocket] [WebSocketServer::Start] Not locked to IPv4 bindings
18:40:49.977: [obs-websocket] [WebSocketServer::ServerRunner] IO thread started.
18:40:49.980: [obs-websocket] [WebSocketServer::Start] Server started successfully on port 4455. Possible connect address: 10.0.0.190
18:40:51.680: [obs-websocket] [WebSocketServer::onOpen] New WebSocket client has connected from [::ffff:127.0.0.1]:63703
18:40:59.683: warning: Could not update timestamps for discarded samples.
18:40:59.696: warning: Could not update timestamps for discarded samples.
18:40:59.714: warning: Could not update timestamps for discarded samples.
18:40:59.740: warning: Could not update timestamps for discarded samples.
18:41:09.696: warning: Could not update timestamps for discarded samples.
18:41:09.710: warning: Could not update timestamps for discarded samples.
18:41:09.728: warning: Could not update timestamps for discarded samples.
18:41:09.753: warning: Could not update timestamps for discarded samples.
18:41:19.709: warning: Could not update timestamps for discarded samples.
18:41:19.723: warning: Could not update timestamps for discarded samples.
18:41:19.741: warning: Could not update timestamps for discarded samples.
18:41:19.766: warning: Could not update timestamps for discarded samples.
18:41:29.722: warning: Could not update timestamps for discarded samples.
18:41:29.736: warning: Could not update timestamps for discarded samples.
18:41:29.753: warning: Could not update timestamps for discarded samples.
18:41:29.780: warning: Could not update timestamps for discarded samples.
18:41:39.735: warning: Could not update timestamps for discarded samples.
18:41:39.749: warning: Could not update timestamps for discarded samples.
18:41:39.766: warning: Could not update timestamps for discarded samples.
18:41:39.793: warning: Could not update timestamps for discarded samples.
18:41:49.748: warning: Could not update timestamps for discarded samples.
18:41:49.761: warning: Could not update timestamps for discarded samples.
18:41:49.780: warning: Could not update timestamps for discarded samples.
18:41:49.805: warning: Could not update timestamps for discarded samples.
18:41:59.761: warning: Could not update timestamps for discarded samples.
18:41:59.775: warning: Could not update timestamps for discarded samples.
18:41:59.793: warning: Could not update timestamps for discarded samples.
18:41:59.818: warning: Could not update timestamps for discarded samples.
18:42:09.775: warning: Could not update timestamps for discarded samples.
18:42:09.788: warning: Could not update timestamps for discarded samples.
18:42:09.806: warning: Could not update timestamps for discarded samples.
18:42:09.831: warning: Could not update timestamps for discarded samples.
18:42:19.788: warning: Could not update timestamps for discarded samples.
18:42:19.801: warning: Could not update timestamps for discarded samples.
18:42:19.819: warning: Could not update timestamps for discarded samples.
18:42:19.844: warning: Could not update timestamps for discarded samples.
18:42:29.697: User switched to scene 'START'
18:42:29.801: warning: Could not update timestamps for discarded samples.
18:42:29.813: warning: Could not update timestamps for discarded samples.
18:42:29.832: warning: Could not update timestamps for discarded samples.
18:42:29.857: warning: Could not update timestamps for discarded samples.
18:42:32.591: warning: Could not update timestamps for discarded samples.
 
D

DevilzKnite

Member
.norman. said:
logs look like something using websocket is failing.

Code: 
18:40:49.976: [obs-websocket] [WebSocketServer::onObsLoaded] WebSocket server is enabled, starting...
18:40:49.976: [obs-websocket] [WebSocketServer::Start] Not locked to IPv4 bindings
18:40:49.977: [obs-websocket] [WebSocketServer::ServerRunner] IO thread started.
18:40:49.980: [obs-websocket] [WebSocketServer::Start] Server started successfully on port 4455. Possible connect address: 10.0.0.190
18:40:51.680: [obs-websocket] [WebSocketServer::onOpen] New WebSocket client has connected from [::ffff:127.0.0.1]:63703
18:40:59.683: warning: Could not update timestamps for discarded samples.
18:40:59.696: warning: Could not update timestamps for discarded samples.
18:40:59.714: warning: Could not update timestamps for discarded samples.
18:40:59.740: warning: Could not update timestamps for discarded samples.
18:41:09.696: warning: Could not update timestamps for discarded samples.
18:41:09.710: warning: Could not update timestamps for discarded samples.
18:41:09.728: warning: Could not update timestamps for discarded samples.
18:41:09.753: warning: Could not update timestamps for discarded samples.
18:41:19.709: warning: Could not update timestamps for discarded samples.
18:41:19.723: warning: Could not update timestamps for discarded samples.
18:41:19.741: warning: Could not update timestamps for discarded samples.
18:41:19.766: warning: Could not update timestamps for discarded samples.
18:41:29.722: warning: Could not update timestamps for discarded samples.
18:41:29.736: warning: Could not update timestamps for discarded samples.
18:41:29.753: warning: Could not update timestamps for discarded samples.
18:41:29.780: warning: Could not update timestamps for discarded samples.
18:41:39.735: warning: Could not update timestamps for discarded samples.
18:41:39.749: warning: Could not update timestamps for discarded samples.
18:41:39.766: warning: Could not update timestamps for discarded samples.
18:41:39.793: warning: Could not update timestamps for discarded samples.
18:41:49.748: warning: Could not update timestamps for discarded samples.
18:41:49.761: warning: Could not update timestamps for discarded samples.
18:41:49.780: warning: Could not update timestamps for discarded samples.
18:41:49.805: warning: Could not update timestamps for discarded samples.
18:41:59.761: warning: Could not update timestamps for discarded samples.
18:41:59.775: warning: Could not update timestamps for discarded samples.
18:41:59.793: warning: Could not update timestamps for discarded samples.
18:41:59.818: warning: Could not update timestamps for discarded samples.
18:42:09.775: warning: Could not update timestamps for discarded samples.
18:42:09.788: warning: Could not update timestamps for discarded samples.
18:42:09.806: warning: Could not update timestamps for discarded samples.
18:42:09.831: warning: Could not update timestamps for discarded samples.
18:42:19.788: warning: Could not update timestamps for discarded samples.
18:42:19.801: warning: Could not update timestamps for discarded samples.
18:42:19.819: warning: Could not update timestamps for discarded samples.
18:42:19.844: warning: Could not update timestamps for discarded samples.
18:42:29.697: User switched to scene 'START'
18:42:29.801: warning: Could not update timestamps for discarded samples.
18:42:29.813: warning: Could not update timestamps for discarded samples.
18:42:29.832: warning: Could not update timestamps for discarded samples.
18:42:29.857: warning: Could not update timestamps for discarded samples.
18:42:32.591: warning: Could not update timestamps for discarded samples.
Click to expand...
I just turned off websocket server and changed scene and OBS didn't close. I use Deckboard as a "stream deck" so I am just screwed on using that??? Deckboard software is all up to date...
 
.norman.

.norman.

Member
DevilzKnite said:
I just turned off websocket server and changed scene and OBS didn't close. I use Deckboard as a "stream deck" so I am just screwed on using that??? Deckboard software is all up to date..
Click to expand...

no you're not screwed. but it is true that websocket doesn't work the same as it previously did. i have a streamPI that will no longer connect as well, we are at the mercy of the plugin developers to update their stuff to work with v28, until then you can download a previous version of obs. which should get websocket up and running again. - check the download page for the previous version link (go back to v27)
 
D

DevilzKnite

Member
.norman. said:
no you're not screwed. but it is true that websocket doesn't work the same as it previously did. i have a streamPI that will no longer connect as well, we are at the mercy of the plugin developers to update their stuff to work with v28, until then you can download a previous version of obs. which should get websocket up and running again. - check the download page for the previous version link (go back to v27
Click to expand...
Previous version of OBS, got it. Just soo weird that websocket/Deckboard works sometimes and then just doesn't. At least we figured out what it was. OBS 28 has a built in websocket so just have to wait for them to fix that for version 28?? I hope I can get deckboard to work with OBS 27
 
.norman.

.norman.

Member
DevilzKnite said:
Previous version of OBS, got it. Just soo weird that websocket/Deckboard works sometimes and then just doesn't. At least we figured out what it was. OBS 28 has a built in websocket so just have to wait for them to fix that for version 28?? I hope I can get deckboard to work with OBS 27
Click to expand...
i am pretty sure you can. like i said i have the same issue with a streamPI "stream deck" after v28 websocket won't connect. it is frustrating.
 
D

DevilzKnite

Member
.norman. said:
i am pretty sure you can. like i said i have the same issue with a streamPI "stream deck" after v28 websocket won't connect. it is frustrating.
Click to expand...
Well I downgraded OBS, everything was fine, setting stuff back up...got websocket and deckboard working. restarted computer and now once again..any scene change OBS just closes. Talk about frustrating. Latest log file is all it is giving me, no crash reports https://obsproject.com/logs/KuwW3kHH1WhWZdwA Also when I disable the websocket server in OBS 27.2.4, I can change scenes, or do whatever and OBS doesn't crash. SO obvisouly it is the websocket but idk what else to do, I need to use websocket for Deckboard.
 
D

DevilzKnite

Member
Also, Just connected OBS Blade to same websocket and it works fine. OBS doesn't crash. So I guess it is something with deckboard. I really want to use deckboard. I am not sure how easy it is to contact deckboard support. I still think it is an obs issue. Deckboard works sometimes and other times it closes obs..Frustrating. Any help is obvisouly appreciated.
 
You must log in or register to reply here.
Top