DRI374
New Member
Hey all,
I've switched from Windows on a Razer Blade 15 '20 to a MacBook Pro M3 Max 48GB in hopes I could continue to use OBS like I used to.
The amount a performance related problems I've run into never seem to end. The first hurdle was to switch from a 2160p60 canvas to 1080p60, that helped a lot as I also tried driving external 4K displays with the program and I had to scale everything back which was disappointing. I have multiple scenes, cameras and media sources using bicubic scale filtering etc and for the most part the program renders in single digit milliseconds per frame. But! Out of the blue, sometimes, OBS just gets into an anaphylactic shock and toasts all CPU it can get, frame rendering in the 20-30ms domain and encoder overload and god knows what, red numbers everywhere in the "stats".
I need help understand what OBS is actually doing so I can some come up with a workaround or change something to prevent it from going into this state. Sometimes it helps turning the replay buffer off and sometimes it doesn't (recording uses same as stream encoder).
I want to be able to use x264 (not Apple VT as it sucks at low bitrates), 6000 CBR, medium, kf=2 with main profile.
Example of transition that F everything up: https://www.twitch.tv/videos/2142638065?t=0h4m44s I simply restarted the stream after this and it worked just fine afterwards. I also have the duplicate source audio issue (the volume increases in the last scene I switch to because of 3 x of the same audio source appear in the scene) that might be related?
I've switched from Windows on a Razer Blade 15 '20 to a MacBook Pro M3 Max 48GB in hopes I could continue to use OBS like I used to.
The amount a performance related problems I've run into never seem to end. The first hurdle was to switch from a 2160p60 canvas to 1080p60, that helped a lot as I also tried driving external 4K displays with the program and I had to scale everything back which was disappointing. I have multiple scenes, cameras and media sources using bicubic scale filtering etc and for the most part the program renders in single digit milliseconds per frame. But! Out of the blue, sometimes, OBS just gets into an anaphylactic shock and toasts all CPU it can get, frame rendering in the 20-30ms domain and encoder overload and god knows what, red numbers everywhere in the "stats".
I need help understand what OBS is actually doing so I can some come up with a workaround or change something to prevent it from going into this state. Sometimes it helps turning the replay buffer off and sometimes it doesn't (recording uses same as stream encoder).
I want to be able to use x264 (not Apple VT as it sucks at low bitrates), 6000 CBR, medium, kf=2 with main profile.
Example of transition that F everything up: https://www.twitch.tv/videos/2142638065?t=0h4m44s I simply restarted the stream after this and it worked just fine afterwards. I also have the duplicate source audio issue (the volume increases in the last scene I switch to because of 3 x of the same audio source appear in the scene) that might be related?