Question / Help Encoding Overloaded & Dropped Frames

Realmistry

Realmistry

New Member
Hello!

Attached is my log file from my last session with major dropped frames. I am still fairly new to the program, and still trying to work out kinks for recording. Help would be greatly appreciated. I scowered up and down the web for solutions and now I feel it's time to approach the professionals.

Experiencing Encoding Overloading and dropped frames.

Thanks in advance for your help.
 

Attachments

  • 2016-06-28 15-04-53.txt
    14 KB · Views: 126
bilehazard

bilehazard

Member
I think your bitrate (40000) is set way too high if im understanding your log file correctly, even at 4000 thats too much, and wouldnt recommend trying to stream full 1080p60 if your not partnered unless your using a certain CPU Preset.
 
Realmistry

Realmistry

New Member
I have this set for a local recording, should I bring down my bitrate to about 3000?
As for streaming, I have it set for 720p streaming and 3500, and that seems to be running fine.

I'd prefer to have a local recording running at 1080p 60fps for editing and posting on YouTube.
 
bilehazard

bilehazard

Member
Ah ok, local recording should prob be set to 6000 or so. Streaming i would still recommend not going over 3500, 3000 is just fine for that
 
Realmistry

Realmistry

New Member
To my understanding of the settings, I have my Nvidia 660M as my encoder for local recordings. I am using the Advanced output mode because I am recording Gameplay and Audio commentary at the sametime.

I am no expert, but I figured if I used my Nvidia for local recordings it would take a load off my cpu, am I correct in assuming that?

So, in order to get what I want I should change my bitrate for a local recording to 6000? or I should lower it?
 
bilehazard

bilehazard

Member
Ah your using NVENC for your encoding instead of x.264? Might be topping out your GPU then, cause now its having to encode your video and render stuff for your games, depending on the graphics settings you've set. I'd try x264 for your stream and NVENC for your recordings, i've had the 560M on my laptop and it sure isnt no powerhouse by any means. And yes, try using 6000 for your recordings. Keep in mind x264 uses CPU usage and NVENC uses GPU for your encoding
 
Realmistry

Realmistry

New Member
So, yes I use x264 as my stream and NVENC as my local recordings. I will give 6000 bitrate a go for Local recordings. But, if I am already using 4000 as my local recording bit rate and having an encoding overload, wouldn't I have more dropped frames with a 6000 bitrate?
 
Realmistry

Realmistry

New Member
Alright, I understand Streaming bitrate should be at 3000 ( I use twitch test, and Twitch recommendation settings to determine what bitrate I can stream at).

I am starting to think I may have had too many programs running or windows open on the OS, or I don't have enough RAM to support it. This is based off the link you sent me. (Although it was just a bunch of windows with files, nothing too CPU heavy).

I just did a test run in a game of Halo 5 Guardians with a bitrate of 60000, and I didn't have much dropped frames. I will attach the log for you to see and compare.

Maybe the answer is right in front of me and I am just not seeing it.
 

Attachments

  • 2016-06-28 19-46-56.txt
    11 KB · Views: 24
bilehazard

bilehazard

Member
Think your still attaching 1 too many 0's on your local recording bitrate, but glad to hear that the link reference above helped you out a bit.
 
Realmistry

Realmistry

New Member
ohhh.... I thought you were converting the numbers in the log from Kb/s to Mb/s ... hmmm... ok so you are saying 6000 would still look good for a 1080p recording.

Damn it, I feel so dumb right now.
 
Steve Macintosh

Steve Macintosh

Member
You don't want to to be using 6000 with NVENC. It will look horrible. Keep in mind that Nvidia's own Shadowplay uses a VBR of 50mbps (on high quality preset). A much larger bitrate is required when using NVENC or Quick Sync compared to x264.

I would use CQP instead of CBR in your NVENC settings. There's really no need for you to push out 50mbps CBR non-stop. Common values for CQP seem to be 15-25, seems like people usually start out at around 22-23 and then go lower if the system can handle it.

Also, I honestly think that 1080p60 is too heavy for your rig, there is going to be times when your computer is extra stressed, and any extra there is extra dropped frames for you. Which can be quite the disappointment should it happen during footage that you actually wanted to keep. My setup is a little bit better than yours and I can just barely do 1080p60. There are games where I'm well aware that I will have to run 1080p30 instead.
 
Realmistry

Realmistry

New Member
Ok, I will give the CQP suggestion a try. I thought my rig would have been able to handle 1080p 60fps... guess it's started to become a little outdated. It worked well with the Elgato for a while until for some reason the Elgato Software started to not work ... ever.

I just tested running 12000 and have very limited dropped frames, and it looks better than I thought.

I guess it's time to start looking into saving up for another setup.
 
Steve Macintosh

Steve Macintosh

Member
I mean, your computer isn't bad, it can probably run a couple of games in 1080p with a good FPS, right? But it's not like it has tons of extra resources to spare when doing that, add to that another resource heavy task going on at the same time: video encoding. Now, while you're using NVENC, which saves a lot of performance, you are doing this on a GTX660M which is on the Kepler architecture, the first generation of NVENC, which unfortunately isn't a beast (anymore).

So lower your settings to where it works and if you in the future decide to get a new setup for recording/streaming, I would recommend tnat you go desktop instead of laptop. :)
 
Realmistry

Realmistry

New Member
I will undoubtedly be buying a desktop in the near future. Preferably with something that will have tons of extra resources to spare. Hopefully...
 
You must log in or register to reply here.
Top