Question / Help Look over my logfile, what to look for in a logfile?

Pandaluvin

New Member
So I recently learned how to open a logfile, but when I read the thing its all a bunch of jibberish.

Was wondering if anyone knew a place that explained, or helped you understand it, I also can't analyze the file there's an error that pops up?

Here's the log file if anyone want to look over it:
https://gist.github.com/b97c3c659a0bece3bb92
 
Cheers bud, now to figure where those pesky logfiles are located :3 <3

EDIT: Duuuh, you can just copy the text and pase *Facepalm*

EDIT: So I managed to analyze my file, and apparently the only problem is the server I've chosen, which is weird cause I ran an ping tool called ''Twitch Bandwidth Test'' and it clearly shows that frankfurt would be the best choice.

But when I run the software recommended on the analyze page (TwitchTV Ingest latency checker) it does idd show that I have the lowest ms on stockholm.

Now I have no idea how either of these softwares work, and I prly should be trusting the program obs recommends themselves, but I can't help but feeling uneasy and seeking second opinions :)
 
Last edited:
I get the same error with my log file even though the other programs would suggest otherwise. I hear the Frankfurt server isn't as reliable as others though. I usually roll with the London or Amsterdam one. (I'm assuming you're in Europe).

Are you having problems with anything else that you were expecting to find in the log file?
 
When I check out a logfile, I typically want to know what the issue is so I can target what could be wrong, but things I always look at are:
1. bitness of OBS (32 or 64 bit)

2. CPU type: is the CPU strong enough to run x264 at the resolution, fps, and preset?

3. if aero is disabled (windows 7 only) it should be enabled in most cases

4. the windows build:
7601 is Windows 7
9600 is Windows 8/8.1
10240 is Windows 10

5 GPU type: is there multiple GPUs? is the GPU D3D10 compliant? is this a laptop with optimus (switchable graphics) also, if its integrated only, even though the CPU specs are fine, might cause slowdown due to GPU scaling and other things the GPU does in OBS

6. the base resolution and downscale

7. the audio format (does this align with windows audio?)

8. Scenes: are there multiple graphics (game) capture?, capture cards or monitor captures?
Each one of the above should have their own scene. Multiple window captures, text, video, graphics is alright.

9. Video encoding: x264 (software/cpu encode), NVENC, VCE, Quicksync

10. fps: 25,30, 45, 48, 60 are typical

11. preset: only for x264 only (default is veryfast)

12.profile: main for streaming, high for local recording

13. keyint: this is typically 2x fps but if its 250, its set to auto (250 is fine for local recording, it needs to be 2x for streaming.

14. CBR: yes for streaming, no for local recording

15. bitrate: 3500 or less for streaming (preferred 2000-2500), higher for local recording

16. buffer: should be same as bitrate for streaming, 0 is only for local recording, which gives unlocked bitrate

17. RTMP server: which ingest, and check out the connection handshake (600 and less is typical), more could mean high traffic to ingest or from ISP

18. Ethernet adapter: should be 1000 for Ethernet and avoid wireless at all cost for streaming

19. After twitch connects, check for connection stalling alerts

20. Total frames duplicated and late frames: should be both below 1% each, if above, lower the resolution downscale, fps or preset

21. number of b/p/total dropped frames: this should all be at 0, if not check network card drivers, cat5, router/modem, ISP or even twitch ingest

22. At the end it shows the last graphic (game) capture, I look for it talking about mutliple hook programs taking either the dx or opengl hook. if it shows the path to the software, consider, disabling it or uninstalling it.
 
Back
Top