Im using my MacBook screen and one external when using OBS. Both are set to 1080p/60fps (I use SwitchResX to be able to set my MAcBook screen to 1920x1080/60fps). OBS is set to Vdeo/Base 1920x1080/60fps, Output 1920x1080/60fps, Common FPS 60 - no downscale. All works smooth for some time then after I start see the movements (I use move plugin from exeldro for my main scene) not so smooth and the way to have that movement smooth again I have to go to preferences/Video change fps to something different/ apply, then go back to 60fps/ apply again and I have my movements smooth again. Am I missing something in the setting of OBS, something I can do to have those 60fps constant?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
NO constant FPS on MacBook M1
- Thread starter Met
- Start date
Lawrence_SoCal
Active Member
Short answer - your settings and overall workload (at Operating System) level is more than you computer is capable of delivering
An M1 is great at some things, and sips power in the process... but it isn't that powerful, overall
And what you are doing is WELL outside the Apple walled garden.
So, basic under-powered device suggestions apply
1. beware background processes and workload. What exactly? can't say as it depends on your specific use case... up to you to figure out what can be turned off, etc. Standard fresh OS reboot before starting, letting system settle down, making sure unnecessary apps/process are OFF (not just in background), etc
2. Then there are the specific OBS Studio settings applicable to that CPU & GPU encoding options
Presuming you are only capturing 1 monitor, not both, have you tested when NOT using SwitchResX? just a Keep It Simple, S***** type thought.. no idea if it even might be helpful in this case.
Good luck on getting someone more knowledgeable on that specific hardware to assist
An M1 is great at some things, and sips power in the process... but it isn't that powerful, overall
And what you are doing is WELL outside the Apple walled garden.
So, basic under-powered device suggestions apply
1. beware background processes and workload. What exactly? can't say as it depends on your specific use case... up to you to figure out what can be turned off, etc. Standard fresh OS reboot before starting, letting system settle down, making sure unnecessary apps/process are OFF (not just in background), etc
2. Then there are the specific OBS Studio settings applicable to that CPU & GPU encoding options
Presuming you are only capturing 1 monitor, not both, have you tested when NOT using SwitchResX? just a Keep It Simple, S***** type thought.. no idea if it even might be helpful in this case.
Good luck on getting someone more knowledgeable on that specific hardware to assist
I use a MacBook Air M1, and I run a 1080p50 stream with one principal camera and two iPhone “walkabouts”, with 1 external monitor.
To maximise CPU, this is what I do:
1. I only install the absolute minimum number of necessary plug-ins (no “nice to haves”).
2. I shut everything extraneous down on the machine, with just OBS running.
3. I find using browser sources is a major Mac culprit for OBS failing due to too much CPU/memory usage. If I absolutely must I only ever use one.
That’s it.
To maximise CPU, this is what I do:
1. I only install the absolute minimum number of necessary plug-ins (no “nice to haves”).
2. I shut everything extraneous down on the machine, with just OBS running.
3. I find using browser sources is a major Mac culprit for OBS failing due to too much CPU/memory usage. If I absolutely must I only ever use one.
That’s it.
Hey there, first thanks for the answer.Short answer - your settings and overall workload (at Operating System) level is more than you computer is capable of delivering
An M1 is great at some things, and sips power in the process... but it isn't that powerful, overall
And what you are doing is WELL outside the Apple walled garden.
So, basic under-powered device suggestions apply
1. beware background processes and workload. What exactly? can't say as it depends on your specific use case... up to you to figure out what can be turned off, etc. Standard fresh OS reboot before starting, letting system settle down, making sure unnecessary apps/process are OFF (not just in background), etc
2. Then there are the specific OBS Studio settings applicable to that CPU & GPU encoding options
Presuming you are only capturing 1 monitor, not both, have you tested when NOT using SwitchResX? just a Keep It Simple, S***** type thought.. no idea if it even might be helpful in this case.
Good luck on getting someone more knowledgeable on that specific hardware to assist
Maybe I didn't explain my case exactly: I have constant 60 fps at the OBS monitor (Stats window) all the time. CPU Usage: about 9/10 %, no 'Missed frames due to rendering', no 'Skipped frames due to encoding lag', but still when using the scene where I use 'move' plugin moves aren't smooth sometimes - there is no spikes in the processor during the moves of the windows in that scene. I don't think is the M1.
Actually, the processor is at 10% because I have in the project 4 NDI inputs, 1 video capture card input for a camera and few scenes (background images, lower 3rds, scene for video files) and all works smoothly with no pressure at all, but when it gets to the scene where I have the 'move ' plugin involved from time to time I see the movements not smooth as almost always.Its like something disturbing the smooth graphic movements some times...I don't know if this is the OBS, the 'Move' plugin, the docking station Im using... or something in the MacOS that interrupts the smooth graphics movements. Well looks I'll never find what the issue is :)
Anyway, thanks for the answer again and don't underestimate your M1 ;)
Lawrence_SoCal
Active Member
If the CPU usage you are referring to is the one in OBS Stats window... well, not really all that meaningful in my experience
What you need to know is overall system CPU usage (ie from System Monitor or similar)
And, your description would indicate your system is fine, EXCEPT when using the 3rd party Move plugin comes into play, so either it is overloading the CPU, or it has issues on the new Apple M-series CPU and is in need of optimization (in which case, ask plugin author)
If CPU being overloaded, then could be plugin fault, or that you are simply running near maximum stable utilization before using that plugin, and its use puts you over the top. In which case, all the system optimizations apply (reduce background and overall CPU load, such that plugin does NOT drive system to overload). But if plugin is problematic, that may not be possible to free up that much spare CPU resources... I can't tell you which... that is for you to figure out
With decades of IT experience... I'm not underestimating the M1... it is great at some things... and really _not_ at others. And you are playing with code long written for a X86 code base and only recently being re-coded/compiled for new Apple ARM SOCs (M CPUs). And free, open source tends to take a while for optimized, stable code to be released for new environments, so patience will be required when using a M-series based system with X86 based applications, and in this a 3rd party plugin
What you need to know is overall system CPU usage (ie from System Monitor or similar)
And, your description would indicate your system is fine, EXCEPT when using the 3rd party Move plugin comes into play, so either it is overloading the CPU, or it has issues on the new Apple M-series CPU and is in need of optimization (in which case, ask plugin author)
If CPU being overloaded, then could be plugin fault, or that you are simply running near maximum stable utilization before using that plugin, and its use puts you over the top. In which case, all the system optimizations apply (reduce background and overall CPU load, such that plugin does NOT drive system to overload). But if plugin is problematic, that may not be possible to free up that much spare CPU resources... I can't tell you which... that is for you to figure out
With decades of IT experience... I'm not underestimating the M1... it is great at some things... and really _not_ at others. And you are playing with code long written for a X86 code base and only recently being re-coded/compiled for new Apple ARM SOCs (M CPUs). And free, open source tends to take a while for optimized, stable code to be released for new environments, so patience will be required when using a M-series based system with X86 based applications, and in this a 3rd party plugin