Multiple "Failed to Open File" reports make OBS glitchy

[ncoltharp1]

Okay everyone, we've had this problem the last couple weeks. At first I thought it was an "auto" keyframe issue but fixing that didn't help and upon examining the log file its clear something weird is going on. Everything starts off doing okay, 0 dropped frames, good CPU usage, good bandwidth and all. Then all of a sudden OBS still appears fine but the stream to YouTube gets really glitchy and even freezes for several minutes at times. A widget in YouTube pops up about resetting the keyframe interval, which I did at first. Didn't help. Anyway, I pull up the log file and notice that at the same time all this freezing is happening, it looks like OBS is failing to open several image files all at once without being prompted by the controller. Attached you'll find the log file. Any idea what could cause this and how I could prevent it from happening again?

 

[koala]

Don't host images you include in your setup on a nas or remote file server. Store them all locally on your machine.

Network access is often flaky in home or soho environments, and occasional network failures have timeouts much longer than the few milliseconds obligatory for lag-less OBS operation. UNC file access as in your log file is even slower than from a mapped network drive, because for every access a very expensive connection attempt to the remote server is performed.

 

[ncoltharp1]

Don't host images you include in your setup on a nas or remote file server. Store them all locally on your machine.

Network access is often flaky in home or soho environments, and occasional network failures have timeouts much longer than the few milliseconds obligatory for lag-less OBS operation. UNC file access as in your log file is even slower than from a mapped network drive, because for every access a very expensive connection attempt to the remote server is performed.

Right, we updated that part of the process sometime last year. Images and graphics are initially accessed via the network and when it comes time to use them they are moved to the PC. The "Failed to Open FIle" messages are all from OBS trying to access files that we haven't used in a long time, since before we updated our process. I could be wrong so please help me if I am haha

 

[koala]

I don't have any more to say about this: copy all remote files to a local directory and update the sources in OBS accordingly.

Don't access remote files. In OBS, remove every single reference to a remote file, even if that source isn't currently used. Every source in a scene collection is accessed and checked by OBS, no matter if it's invisible or in some inactive scene. Always keep your scene and source setup current. Remove obsolete sources, don't archive them. Every existing source increases system load.