Question / Help OBS is choking when streaming/local recording Avermedia LGP.

R

Rubyvixen

New Member
http://pastebin.com/A67JarjB log file.

My CPU occasionally spikes to 100% for no apparent reason. What I don't understand is that my 3rd gen i7 at a lower clockspeed could record at 1280x720p60FPS and multiple cameras with no problem, but my desktop's far superior hardware chokes for like no reason.

I'd like to use my GPU for streaming but the AMD build doesn't work with LGP Stream Engine.

What's going on?
 
Rubyvixen said:
http://pastebin.com/A67JarjB log file.

My CPU occasionally spikes to 100% for no apparent reason. What I don't understand is that my 3rd gen i7 at a lower clockspeed could record at 1280x720p60FPS and multiple cameras with no problem, but my desktop's far superior hardware chokes for like no reason.

I'd like to use my GPU for streaming but the AMD build doesn't work with LGP Stream Engine.

What's going on?
Click to expand...
"3rd gen i7 at a lower clockspeed"

I'm going to assume you mean an i7-3630QM or something? There is no desktop 3rd-gen i7 at a slower speed than 3.3GHz...

Anyway... read my mobile i7 CPU information guide. That'll explain why you probably think your i7 is at a slower clockspeed.

Next, you'd need a 4GHz i5 to combat as much as a 3.2GHz i7, so your desktop is actually INFERIOR as far as OBS is concerned.

It's okay, take a minute, sit down, swallow it, come to terms with it, then resume using your laptop to stream =D.

Anyway, I'm not seeing skipped frames due to encoder lag in that log, buuuut I am seeing a lot of your LGP audio lag:
  1. 20:08:19: Audio timestamp for device 'LGP Stream Engine' was behind target timestamp by 200
  2. 20:08:21: Audio timestamp for device 'LGP Stream Engine' was behind target timestamp by 220
  3. 20:08:31: Audio timestamp for device 'LGP Stream Engine' was behind target timestamp by 220
  4. 20:08:35: Audio timestamp for device 'LGP Stream Engine' was behind target timestamp by 230
  5. 20:08:36: Audio timestamp for device 'LGP Stream Engine' was behind target timestamp by 250
  6. 20:08:39: Audio timestamp for device 'LGP Stream Engine' was behind target timestamp by 250
  7. 20:09:05: Audio timestamp for device 'LGP Stream Engine' was behind target timestamp by 280
  8. 20:10:05: Audio timestamp for device 'LGP Stream Engine' was behind target timestamp by 290
  9. 20:10:12: Audio timestamp for device 'LGP Stream Engine' was behind target timestamp by 310
 
Then explain this:

Why does OBS choke and Xsplit doesn't using the same settings?

Secondly, why is it that sometimes my Desktop can record 720p60fps perfectly fine one session, and choke another.

Thirdly, why can I record and stream at 1080p30fps and 1080p60fps on desktop games but can't when it comes to my avermedia? I've tested that the avermedia is not disfunctional by using it in its native software and in other programs.

I think something might be bottlenecking my desktop's performance. PSU or HDD are my guesses

Another question: why can a 2500k run 720p60fps flawlessly and my 4590 can't?

I'm fairly certain there's a different underlying cause than the cpu not being strong enough for 720p60fps. if the cpu was the issue it would consistently fail. Not run fine one session, then fail another.
 
Well this is what I said... I've not seen any "skipped frames" due to high CPU usage in your log file. It looks like for some reason your Avermedia is screwing up; as to what the reason is I could not guess. But if you have no problem with desktop games, then it means the problem indeed lies elsewhere.

As for Xsplit, Xsplit has better support for cap cards and such, as well as it uses the system differently. I can't exactly explain it, but Xsplit is a program that neuters your PC on a whole to stream, taking more than it needs, so it's rare that Xsplit itself will screw up, but things on the PC will run worse. It's not efficient, but it works on lower-end hardware and for console streamers pretty well.

Anyway, it does look like something else on your PC is screwing with your CPU if you really are getting so many "high CPU usage" errors. Your logfile shows very little of it though.

Either that, or your chipset modulation or clock modulation are not at 100% all the time for some reason. CPU speed is not the whole story. A 3.5GHz i5 with a chipset or clock modulation factor of 50% would be slower than a 2.5GHz i5 with 100% on both chipset & clock modulations. Unfortunately for you, you probably don't know how to check that, and that STILL might not be the problem either.

I'd say check your PC and see what uses up your CPU. Usually in my experience OBS doesn't pass about 50% usage even with high compression, and your settings are not very demanding. So... good luck.
 
You must log in or register to reply here.
Back
Top