These are good OBS troubleshooting resources to be aware of ![]() The OBS Stats window CPU is for the OBS process ONLY, not NDI, not the OS, etc. ![]() I recommend real-time monitoring hardware resource (CPU, GPU, RAM, Disk I/O, etc) utilization to see if your system is being maxed out with your settings [which I'm sure it is. Dang, I'm impressed it has worked for you up til now. That is an ancient CPU for real-time video encoding which is VERY computationally demanding and you don't have a Turing NVENC GPU for encoding offload (though you do on an input source?).Īnd you are adding NDI processing workload on top of that. ![]() Please clarify - you said no dropped frames but the screenshot you shared shows 1.4% dropped frames (Network) and 0.2% due to encoding lag?ġ0:52:27.350: Output 'simple_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 9676 (13.0%)Ĭlearly you were having network congestion issues
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |