OBS stops broadcasting, even though it give no crash warning/ stopping broadcast warning

B

Bittzyy

New Member
New here,

While streaming to twitch in the past few weeks, after anywhere from a half hour to two hours in, OBS will stop broadcasting to twitch. The first occurrence this happened my whole PC blipped and beeped, but when I looked back at OBS it said it was still streaming so I thought nothing of it. I thought it also might've been a problem of trying to stream and record at the same time, so during the most recent stream I didn't record and also turned off the replay buffer. It still happened about 30 mins into stream where it stopped broadcasting completely. Does anyone have any ideas on why it's just not broadcasting, or blipping out of broadcasting after some time.

Since I had to alt+f4 to close OBS since it wouldn't close while it said it was still streaming, and I restarted stream just to end it shortly after. I could not get the upload log URL for that particular log file in which it blipped out. I have it saved as a txt file, but don't know how to upload that so someone else can troubleshoot. Also it would be nice to be able to upload/get a URL previous log files back, not just the most recent one.
 
C

cyclemat

Active Member

Please post a log with your issue! Here's how...

OBS Studio creates a log file each time you run it which contains very useful diagnostic information. Without a log file, it's much harder for any support volunteers to figure out problems and your post may be ignored. To upload a log file, go to the Help menu > Log Files > Upload Last Log...
obsproject.com obsproject.com
 
B

Bittzyy

New Member
The relevant log file is no longer available to upload, so I cant upload the OBS generated URL for the log file that would be best useful for this problem, using the normal method only gathers the latest log file, If I were to use the proposed method, it would not give anyone any actual information/log file relevant to the problem I'm having.
 
B

Bittzyy

New Member
The whole .txt log file wont fit in pastebin, and it wont even "post" to pastebin, what else can I do?

this is the error in the log thats filling the entire log
19:05:08.567: Error decoding video
19:05:08.567: warning: Found EOI before any SOF, ignoring
19:05:08.567: fatal: No JPEG data found in image

whatever this is, I think is whats causing it.
[rtmp stream: 'adv_stream'] bitrate increased to: 3600, waiting
 
Last edited:
B

Bittzyy

New Member
I don't have any plugins installed, and OBS is updated to the latest version

Pastebin wont let me post more than 1 minute of log/lines and theres 2 hours worth of log/lines.

the text below repeats in the logs multiple times a second, theres 535,060 Lines in the .txt log file

warning: Found EOI before any SOF, ignoring
fatal: No JPEG data found in image
Error decoding video

the few pastebins i did do

pastebin.com

1 - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com pastebin.com
pastebin.com

2 - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com pastebin.com
pastebin.com

3 - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com pastebin.com
 
Harold

Harold

Active Member
Provide the entire log as a single entry by uploading the log from within obs (help menu - logs) and using the link it provides.
 
B

Bittzyy

New Member
Harold said:
Provide the entire log as a single entry by uploading the log from within obs (help menu - logs) and using the link it provides.
Click to expand...

The current OBS log file that would be upload has already been deleted by the local space saving, so the OBS unloadable log file is no longer available, and the OBS log file that would be uploaded would not provide correct information or the actual problem that occurred within the log files, because that log file is now only saved to my desktop as a txt file so that it wouldn't have been lost by replacement of new log files while trying to troubleshoot the problem myself in the log files. Making the relevant log files no longer available to OBS upload
 
B

Bittzyy

New Member
This is the log file that you get when I go through the recommended steps, which in turn does not actually give any relevant logs that happened last night between 6:15pm-7:55pm


It would also be unproductive to start a livestream and wait anywhere from 30mins to 2 or more hours for the problem to occur just to get relevant log files, because the problem may also not visibly present itself. There's no visible warning or crash warning when my issue occurs
 
Harold

Harold

Active Member
Bittzyy said:
This is the log file that you get when I go through the recommended steps, which in turn does not actually give any relevant logs that happened last night between 6:15pm-7:55pm


It would also be unproductive to start a livestream and wait anywhere from 30mins to 2 or more hours for the problem to occur just to get relevant log files, because the problem may also not visibly present itself. There's no visible warning or crash warning when my issue occurs
Click to expand...
This log has no streaming or recording attempt in it at all.

Logs are per launch of obs, not per "start streaming" or "start recording" session precisely to be able to troubleshoot these issues.
 
B

Bittzyy

New Member
I completely understand that logs are created by session not by stream. Therefore the log file that's relevant is no longer uploadable because I closed and opened OBS a few time to try and troubleshoot the problem myself, which in turn made the relevant log file no longer available for upload per the recommended steps. Unless there's a way to pick certain log files to upload, at the moment I don't know or see any way to do that locally thru OBS. Also the issue is not something that is visibly presented, therefore not able to just start stream and wait till the issue arises, because the issue may not arise, and then it could take anywhere from 30mins to 6hrs for the invisible problem to show itself
 
PaiSand

PaiSand

Active Member
Within the same place in Help menu you can go straight to the folder where the logs are stored. Look for it by date and upload it here.
And if your computer "blipped and beeped" then something is bad on your computer. Refere to the manual of your computer and what beeps mean (normaly is the motherboard manual) or ask the vendor to suplay a manual explaining the blipping and beeping.
There could be many issues that cause this.
 
B

Bittzyy

New Member
I tried something by deleting all the recent irrelevant log files, and copied my copy of the relevant one in, and got this when I tried to upload the file I got this error. Its actually too large to upload.
 

Attachments

  • OBS error.PNG
    OBS error.PNG
    7.4 KB · Views: 18
B

Bittzyy

New Member
The file is too large for the server to process is what its saying

also the beep only happened once, but didn't happen on the two other separate occasions where OBS stopped broadcasting for no reason with no warning while the streaming button still said it was streaming
 
PaiSand

PaiSand

Active Member
If the file s that much large tehn you have a log full of error messages non stop.
Do a clean log of at least 30 seconds doing all you normally do and then upload it, copy the link to post it here and take a look at the analizer.

Edit
Just took a look at the pastebin you posted. The problem start with the MiraBox

18:15:53.390: [DShow Device: 'Video Capture Device'] settings updated:
18:15:53.390: video device: MiraBox Capture
18:15:53.390: video path: \\?\usb#vid_534d&pid_2109&mi_00#7&2e48d0e4&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global
18:15:53.390: resolution: 1920x1080
18:15:53.390: flip: 0
18:15:53.390: fps: 60.00 (interval: 166666)
18:15:53.390: format: MJPEG
18:15:53.390: buffering: disabled
18:15:53.516: warning: Found EOI before any SOF, ignoring
18:15:53.516: fatal: No JPEG data found in image
18:15:53.516: Error decoding video
 
Last edited:
You must log in or register to reply here.
Top