Question / Help Lagging/Studdering during recording

wizenfish

New Member
Up until a few weeks ago I did not run into any issues just recording screen captures of game play recently and not coinciding with any obvious update any recording comes out really really laggy video & audio are way off. Any suggestions to help us (my son mainly) out? I've tinkered with a few settings and update a few items, googled a ton but have not found that original smoothness that we had suggestions? We have tried the auto-config wizard without success as well.

Thanks in advance for pointing us in the right direction.

Log file https://obsproject.com/logs/JXTRN1QzaF5ICwYA & attached is another.
 

Attachments

  • 2019-09-02 18-30-42.txt
    10.7 KB · Views: 17
Last edited:
I troubleshot a few things that might involve this:

1. Windows 10 Paging. Microsoft updated their paging requirements for Windows 10. Please have a look. https://support.microsoft.com/en-us...opriate-page-file-size-for-64-bit-versions-of

I used a second hard drive (SSD or probably NVMe drives would be better) to handle the paging or virtual memory from Windows 10. 60 frames per second uses a LOT of virtual memory / paging. I believe this is due to how FFMpeg and the Windows Media Foundation are used. According to the link above, the maximum recommended paging size for a 64-bit OS is 3 x RAM or 4 GB, whichever is larger. I used a 100 GB drive, but have to go back in and change from System Managed to the correct size.

I had to make manual changes to this since Windows 98. This may be the reason why Windows 10 1903's requirement is "You need at least 32 GB of hard drive space to install this update." The max recommended paging size is 32 GB if you have 32 GB of memory. There is a lot of growth, trimming, deprecating, and caching that may contribute to stuttering if it's on the same disk. I am currently observing that the paging file does not perform a high amount of writing, but is doing more reading? It should write more, but I don't know. I want to try using exFAT instead of NTFS for the paging drive just to observe.

2. Process Priority. I set the process priority to High in OBS, but used ProcessExplorer to see if Windows 10 honored the change and it was left as Normal. I then used Process Lasso to force OBS to a High priority per the applications request, so I'm not sure if this is a Windows 10 bug or not. The stuttering was very minimal after this change, because something like recording or streaming should be near Realtime. If other applications are still overriding OBS and FFMpeg, then this may take more investigating. Ultimately this is one of the core issues.

3. Hard Drive Caching Policy. I used an application called PrimoCache to manage the drive caching policies (which may coexist with the virtual memory or paging operations). I don't think Microsoft changed their caching policies for hard drives....ever. With this application, I can also create L2 or a level 2 storage, which works even better with a SSD or NVMe. I turned off the drive caching policy that Windows 10 uses and let PrimoCache handle this.

4. Desktop Composite. The bottom line....apps that run in Full Screen Borderless or Windowed Borderless modes are far better than the current way that the desktop composite handles Full Screen mode. This is something that application devs, driver developers and Microsoft joint signs and must realize. There may be room for DirectX 11 improvement as well, but getting the attention of Microsoft means to throw this in the Feedback Hub....needle in the haystack. Some people have even petitioned this problem since Windows 8. Most apps are not running as a UWP app, like the ones from the Microsoft Store. Streamlabs OBS is however. I had better success discussing it on this forum.

Now this is a lot of things....but the aftermath was less stuttering and less frame drops from recordings. I haven't put this practice into live streaming yet...but I'm still gathering details including pointing out things from my logs before I make any comparisons and contrasts.
 
Last edited:

wizenfish

New Member
I troubleshot a few things that might involve this:

1. Windows 10 Paging. Microsoft updated their paging requirements for Windows 10. Please have a look. https://support.microsoft.com/en-us...opriate-page-file-size-for-64-bit-versions-of

I used a second hard drive (SSD or probably NVMe drives would be better) to handle the paging or virtual memory from Windows 10. 60 frames per second uses a LOT of virtual memory / paging. I believe this is due to how FFMpeg and the Windows Media Foundation are used. According to the link above, the maximum recommended paging size for a 64-bit OS is 3 x RAM or 4 GB, whichever is larger. I used a 100 GB drive, but have to go back in and change from System Managed to the correct size.

I had to make manual changes to this since Windows 98. This may be the reason why Windows 10 1903's requirement is "You need at least 32 GB of hard drive space to install this update." The max recommended paging size is 32 GB if you have 32 GB of memory. There is a lot of growth, trimming, deprecating, and caching that may contribute to stuttering if it's on the same disk. I am currently observing that the paging file does not perform a high amount of writing, but is doing more reading? It should write more, but I don't know. I want to try using exFAT instead of NTFS for the paging drive just to observe.

2. Process Priority. I set the process priority to High in OBS, but used ProcessExplorer to see if Windows 10 honored the change and it was left as Normal. I then used Process Lasso to force OBS to a High priority per the applications request, so I'm not sure if this is a Windows 10 bug or not. The stuttering was very minimal after this change, because something like recording or streaming should be near Realtime. If other applications are still overriding OBS and FFMpeg, then this may take more investigating. Ultimately this is one of the core issues.

3. Hard Drive Caching Policy. I used an application called PrimoCache to manage the drive caching policies (which may coexist with the virtual memory or paging operations). I don't think Microsoft changed their caching policies for hard drives....ever. With this application, I can also create L2 or a level 2 storage, which works even better with a SSD or NVMe. I turned off the drive caching policy that Windows 10 uses and let PrimoCache handle this.

4. Desktop Composite. The bottom line....apps that run in Full Screen Borderless or Windowed Borderless modes are far better than the current way that the desktop composite handles Full Screen mode. This is something that application devs, driver developers and Microsoft joint signs and must realize. There may be room for DirectX 11 improvement as well, but getting the attention of Microsoft means to throw this in the Feedback Hub....needle in the haystack. Some people have even petitioned this problem since Windows 8. Most apps are not running as a UWP app, like the ones from the Microsoft Store. Streamlabs OBS is however. I had better success discussing it on this forum.

Now this is a lot of things....but the aftermath was less stuttering and less frame drops from recordings. I haven't put this practice into live streaming yet...but I'm still gathering details including pointing out things from my logs before I make any comparisons and contrasts.

Thanks for the knowledge I'll check what I understand. Would ant of this be a progressive or compounding issue?
A few weeks ago it was recording perfect.
 

Narcogen

Active Member
18:30:23.279: Windows Version: 10.0 Build 17134 (revision: 950; 64-bit)

Update Windows. This version is quite old and has known performance issues when running OBS.

Your log does not contain an output session, so there's no performance information. Make sure you open OBS, start a recording or streaming session, observe your problem, stop the session, and then upload the log.
 

wizenfish

New Member
I've updated windows and re-run the auto config wizard, a little better but the problem still exists. Uploading the newest log file for minds greater than mine to evaluate.
 

Attachments

  • 2019-09-04 18-35-12.txt
    30.5 KB · Views: 12
Top