Surface Pro 7+ Recommended setting to avoid fps drops

qhobbes

Active Member
Update Windows again. Your log shows:
Windows Version: 10.0 Build 19043 (release: 2009; revision: 1110; 64-bit)
Mine shows:
Windows Version: 10.0 Build 19043 (release: 2009; revision: 1165; 64-bit)

12:40:44.158: >>> encoder scaling active, fall back to old qsv encoder
Set the base and canvas resolution to 1920x1080 and set the OBS FPS to 29.97
 

Seamndel

Member
don't know what'ds going on :
Screenshot (92).png

going to services>windows updates > Automatic (pressing 'Apply') doesn't change anything.
 

Seamndel

Member
Still performance problems at 2560x720.
I tried 29.97 as well as 30.0.
30 seems more smooth.
Is it normal that GPU will be fluctuating all over the place (I've seen numbers such as 79% in Task Manager)?
Also, during these times OBS seems to not actually save my replay buffer clips (although I'm definitely pressing the "Record" icon).
 

qhobbes

Active Member
Post new log with OBS running as Admin. To run OBS as Admin, right click on the shortcut, properties, advanced, check box, ok, apply, ok.
 

qhobbes

Active Member
Do the following:
1. Set the Base and Output resolution to 1280x720
2. Create a new Scene Collection with 1 scene with just your Surface Pro Front Camera (also at 1280x720) as your only source (no filters).
3. Close and re-open OBS so it starts with that new Scene Collection.
4. Do a recording of that Scene Collection and post a new log.
 

Seamndel

Member
Do the following:
1. Set the Base and Output resolution to 1280x720
2. Create a new Scene Collection with 1 scene with just your Surface Pro Front Camera (also at 1280x720) as your only source (no filters).
3. Close and re-open OBS so it starts with that new Scene Collection.
4. Do a recording of that Scene Collection and post a new log.

Ran as Admin, Surface Pro Front Camera, 720p , 30fps

Even if it holds steady 30 (which it does), how does that help me ? 1280x720 is not the resolution I wish to use ( I'd rather record to 720p sources at 2560x720).
 

qhobbes

Active Member
This is to establish a baseline of what your resources can do. Your log doesn't contain a complete recording session, just a start and not a stop.
Try adding a static border to your scene (such as the one attached) above your camera sources and see if that helps.
 

Attachments

  • border.png
    border.png
    943 bytes · Views: 8

Seamndel

Member
This is to establish a baseline of what your resources can do. Your log doesn't contain a complete recording session, just a start and not a stop.
Try adding a static border to your scene (such as the one attached) above your camera sources and see if that helps.

I don't understand. How does a static source help me/us solve the problem?
 

qhobbes

Active Member
Your log is incomplete. It just contains a Replay Buffer Start.
I believe it's easier for encoders to encode static content than it is for dynamic content.
 

konsolenritter

Active Member
You have a cbr target bitrate of 25.000 kbps on a non-nvenc intel graphics hardware? :o

Hi Seamndel, i'm a little bit astonished. qhobbes gave alot of hints and input to you, the thread is two pages now. But instead of accumulating his tipps you reverse most given hints instantly at the next try or hold up with questions. You go down and up with resolution, run as admin and return to non-admin mode, but you keep instantly with the Iris XE graphics. Now you try for really huge cbr bandwidth while already the log analyzer tells you
"[...] running on an Intel iGPU. This hardware is generally not powerful enough..."

At the end of July you're told already to avoid unrealistic bitrate and quality settings. And you were told the reasons for that.
The surface is equip'd with a sparse/lean (while modern 11th gen) i7-cpu with target audience for lightweight laptops like the surface.
Anyway you should give it a try. But beware: Your surface is no workhorse, and the graphics less than ever.

And qhobbes asked you to start with a fresh clean empty scene collection (without replay-buffering).
We asked for logs containing recording sessions.... we haven't seen any since then.
Your surface cam delivers at 30, the elgato at 59.94, which is bad too.
Did you tried completely without the built-in surface camera?

According to https://obsproject.com/forum/thread...setting-to-avoid-fps-drops.144528/post-537881 the things got better in August then. Why didn't you kept with better performing configuration?

Do you have a friend nearby you can ask to proof on his/her better crafted machine if your setting and workflow with two videos aside will work? Then you could probably better decide wether or why the issue sticks with your specific hardware...
 
Last edited:

Seamndel

Member
You have a cbr target bitrate of 25.000 kbps on a non-nvenc intel graphics hardware? :o ... At the end of July you're told already to avoid unrealistic bitrate and quality settings...

I have not been using VBR or CBR for several months now, rather CQP. So the 25,000 bitrate is not a factor these days.

You go down and up with resolution, run as admin and return to non-admin mode,

I'll explain why I do that:

First, it seems that while I run OBS as an admin , OBS "highjacks" the computer and does not let me interact with non-chosen-window programs I have running in the background. 'Why would it matter?' you ask? Well... I use a program called "XIM Link" to play on my Playstation consoles (mainly PS3) with non-playstation peripherals, such as mouse, keyboard and nunchuks (essentially Imagine the "XIM Link" program running, with the PC connected to the Console via a special cable) .

For the occasion of using a mouse I have intentionally left out a button on my mouse and made it wholly dedicated to the action of switching between gameplay on the console and regular PC use ( such as momentarily answering chats or adjusting settings).

if I let OBS highjack my setup by going admin, I cannot insta-switch between Console and PC. Instead, I will have to let go of the console-mouse , switch to a different PC-connected mouse / touch controls, choose the XIM Link window as my active window and ONLY THEN will the program register my input and switch the console-mouse to PC.

Such accommodation is not workable.

Second, I feel as if adim mode has worse performance. There is significant stutter and tearing on screen when doing 2560X720 30fps (CQP, no extra sampling or scaling enabled)

qhobbes gave alot of hints and input to you.... qhobbes asked you to start with a fresh clean empty scene collection (without replay-buffering).We asked for logs containing recording sessions.... we haven't seen any since then.

Make no mistake. I'm not ungrateful for qhobbes' help. In fact, I have a "Tiger" from Winnie the pooh shrine dedicated to him in my parents' house; for putting up with me.

The reason why did not come back is because - perhaps out of frustration - I had decided to strike out on my own then.

And I made disturbing discoveries.

First, it would seem as though qhobbes never asked me to change my Battery Status to "better performance".

Second, Did you know that checking your update setting on Windows 10 and seeing you're up to date does not mean you necessarily have the latest Graphics drivers installed?

Furthermore, did you know that going to "device manager" and seeing "there are no new drivers for your graphics card" does not mean there are no new drivers?

They certainly did not teach us that in school.

So I went to Intel's website , downloaded some app , installed the latest graphics driver, made sure I was on better performance and voila! As I recall I was so satisfied with the results I saw no reason to contact the fourm with any logs or questions. Gone were the 1 frames per second ; Hello stable thirty!

Alas, it was not to last.

Evil had bobbed its' head yet again.

Slowly, I began to notice inconsistencies. I attributed them to perhaps me being more experimental with the resolutions, like 2592x720 , or 2872x720. The further I went , the more inconsistent it got. These weren't only dropped frames, sometimes it it was the audio that got distorted/delayed. Sometimes only a few beginning frames or/and last few frames of a clip would exhibit dropped frames, while other frames were stable.


Today my CPU usage got to the 30's% (on 2560x720, 30 fps). I have not seen such numbers since first trying OBS' default settings when I first got the computers. What's more , when I opened up Task Manger my CPU usage showed 20%. Both 30% and 20% literally showed side by side !

Your surface cam delivers at 30, the elgato at 59.94, which is bad too.
Did you tried completely without the built-in surface camera?

I have a GoPro Hero 3+ Black as well. I can connect it to OBS via an adapter (called the 'Elgato Cam Link 4k') , but I can't attest to it netting me consistent frame rate either.



To be clear: I have in my possession clips depicting - at least to my naked, un-trained eye - stable frame rates. We are talking about scenes of 2560x720|30fps&combos|2 sources , even 2592x720|30fps&24fps combos|extra browser sources.

It just the inconsistency that is killing me...
Why in the world would CPU usage fluctuate between ~ -10% and +30% ? Why would frame rate be stable one time , while all-over-the-place another (same scene; different sessions)?
 
Last edited:

qhobbes

Active Member
@Seamndel after reading your post, I went to Intel's site and download some app too. I updated the graphics drivers and after some initial testing, I should be able to stream at 1080 59.94 FPS. All thanks to you (and Intel). You da man.
 

Seamndel

Member
@konsolenritter, @qhobbes

I just moved to Windows 11 and guess who I met?
My old Ex; Microsoft's vanilla graphics driver.​

He seems to have got his life in check now. He's working on his problems and while he's far from perfect I daresay that -when he works- he knows the job.

Still, I fear that the old him still in there. Maybe he's just too bi-polar/capricious to my taste. It's sort of hard to ease him in when we begin our play seesion ; I'm all ready but he sort of muddling in the 17fps (720p,30fps). Later it usually becomes better. We sometimes get stable 30 for several hours before he just looses the -no pun- drive. He's sort of all over the place towards the end.

He's a nice driver , but am not sure I want to rely on him to sustain my needs. Then again, Intel's irisX graphics' driver isn't that much better. It also exhibits performance problems.

I dunno. Maybe I deserve this. Maybe I'm just the type of guy who's attracted to drivers who are a little more .... unstable?

Tell you what. I thought- maybe as to take the burdon off of my driver's shoulders- I'll get a Software to help around the setup. Taking care of a capture card and small CamLink adapter isn't easy you know...

Regardless, I noticed the GoPro Hero 3+ Black has a SD card slot, my dad is a practitioner of GoPros and had said there's a way we can use it to our advantage:

What if I find a software that would "send" a signal to my GoPro Hero 3+ Black to "replay buffer" a 30 second clip to the SD card the exact same time a signal is sent to OBS "replay buffer" a clip of it's own? That way OBS doesn't need to render both my cam and video at the same time at bizzare resolutions (2560×720 etc.)

I know this might an area of expertise for others, shuch a Elgato or GoPro consultants, but I feel it's worth a shot to ask here.
 

Seamndel

Member
I got pretty good clips recently. Some where even in 2560x720p,60 fps. But the audio is out of synch. How do I fix this so it won't happen in the future?
 
Top