Question / Help 36 core Stream PC and memory crashes
- Thread starter EDGAR_SEC
- Start date
FerretBomb
Active Member
Seems that could be the case. Have you tried running the 64-bit version? It installs at the same time as the 32, just to C:\Program Files instead of (x86). (Or if you're on a legacy-upgraded version, to the 64bit subdirectory inside the main OBS install path)
You probably also will need to limit your thread count. LethalFrag had a similar problem with his new machine, and had to toss threads=30 into the custom x264 settings to get it to work. Really though, going over 24 threads creates more sync overhead than it gains performance with the x264 encoding library anyway, as I understand it.
You probably also will need to limit your thread count. LethalFrag had a similar problem with his new machine, and had to toss threads=30 into the custom x264 settings to get it to work. Really though, going over 24 threads creates more sync overhead than it gains performance with the x264 encoding library anyway, as I understand it.
FerretBomb
Active Member
Videophile
Elgato
Have you tried OBS Multiplatform?
Also, X264 encoding starts to have massive diminishing returns after 22 threads iirc, or for you, 22 cores. Yes, it can use more, but the benefit is VERY Small. Clock speed is better at that point than cores.
Also, X264 encoding starts to have massive diminishing returns after 22 threads iirc, or for you, 22 cores. Yes, it can use more, but the benefit is VERY Small. Clock speed is better at that point than cores.
Boildown
Active Member
I agree, you should test further by saving to your hard drive and not streaming it.
If you get a chance (and have the monitor for it), I'm curious how well G-Sync'd capture on the VisionSC-DP2 works!
That's from your log file in the OP. You had two CPUs running when doing that test? It seems to me that OBS only even recognizes one of them, or the log file doesn't know what to do when there's two physical processors in the system.
Another problem I noticed:
I don't see it logged what Level you had OBS set to use, but for your resolution and framerate, it needs to be set to 5.1 or 5.2 and this error strongly implies that you had it set to less than this.
https://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Levels
Its probable that its not a memory limitation of the 32-bit version at all, and this is the actual root cause of OBS not running. I'd check this for the Multiplatform > 1080p problem too.
If you get a chance (and have the monitor for it), I'm curious how well G-Sync'd capture on the VisionSC-DP2 works!
That's from your log file in the OP. You had two CPUs running when doing that test? It seems to me that OBS only even recognizes one of them, or the log file doesn't know what to do when there's two physical processors in the system.
Another problem I noticed:
I don't see it logged what Level you had OBS set to use, but for your resolution and framerate, it needs to be set to 5.1 or 5.2 and this error strongly implies that you had it set to less than this.
https://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Levels
Its probable that its not a memory limitation of the 32-bit version at all, and this is the actual root cause of OBS not running. I'd check this for the Multiplatform > 1080p problem too.
Last edited:
x264 doesn't benefit from HT much since the code is hand written and heavily optimized assembly which is very efficient at maxing out the pipeline. It could be x264 avoids putting two threads on one core since it would reduce performance by adding additional context switches.
Boildown
Active Member
Edgar, thanks for the info about the VisionSC-DP2 vs G-Sync. I was kinda hoping it could adjust its capture framerate on the fly to manage to get all the varying timed frames, since Datapath cards are so incredibly adjustable to different resolutions and framerates, unlike everyone else that seems to have only pre-set static resolutions and framerates they support.
Be sure to check out my H.264 Level advice, I think it solves one of your problems.
Be sure to check out my H.264 Level advice, I think it solves one of your problems.