X264 Vs Apple H264 Hardware Encoder | OBS Forums

Menu

• Home
• Forums New posts Search forums
• Plugins Latest reviews Search plugins
• Resources Latest reviews Search resources

Log in Register What's new Search

Search

Everywhere Threads This forum This thread Search titles only By: Search Advanced search…

• New posts
• Search forums

Menu Log in Register

• Home
• Forums
• OBS Studio Support
• Mac Support

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. x264 vs apple H264 hardware encoder

• Thread starter gglife
• Start date Jun 9, 2022

G

gglife

New Member

I have not really understood whether I am leveraging the full potential of the M1 hardware encoder yet. For instance when I do 4k recording of 4k canvas keeping all other settings the same using apple H264 hardware encoder will result in choppy video (also obs indicates overload of hardware encoder during recording). Using x264 will result in good quality but significant cpu load. I thought M1 hardware encoder should be able to handle 4k encoding with ease. What am I missing? -- Running latest nightly build 27.2.0 for arm64 M1 with basic M1 MacBook Air + external 4K Monitor T

Talonis

Member

Do you really need 4K? I find high frame rate, high bit rate 1080p via H.264 hardware encoder (internal) scales very well (rather than trying to record directly at 4K). Another solution: hook up OBS to an external hardware encoder/streamer and take the load off the Mac CPU. G

gglife

New Member

The quality with scaling is very poor so far. I played around with bit rate also. What do you consider high bit rate and what scaling method do you use? Sure, I could use additional hardware. I was just under the assumption that M1 could handle this task. Maybe its still an obs optimization issue to some extend. I am new to this forum and I could not find any M1 OBS benchmarks to compare against. L

Lawrence_SoCal

Active Member

The issue is native M1 code (which is different from x86 code OBS is written in.. to over-simplify issue). Other threads in this forum discuss original external dependencies that were holding up native M1 compiled OBS Studio code. do a search on M1 - quick and easy, lots of info [though most likely not what you want to hear]. Last I recall (which I do NOT follow closely), OBS development team plan was for next OBS release (v28) to have native Apple M-series CPU support?? in my experience and opinion, such a development timeline is completely reasonable especially given OBS Studio's FOSS (free, open source software) nature G

gglife

New Member

Hey, thanks for your reply. I was querying the forum before posting. That is how I found the link to the nightly builds 27.2.0 for arm64 M1. So technically I am running OBS with code compiled for M1 in my understanding. I also read that from v28 on it will be included in the official builds. T

TFE

Member

What MacOS are you running? I run OBS 27.2.4 on an M1 Mac mini with only 8gb RAM running Monterey and can stream/record 1080p 60fps using the H264 hardware encoder — no problem and low (25% or so) CPU usage. Not tried 4K but will at some point and report back. G

gglife

New Member

Hi, I am running MacOS 12.4. Is your OBS 27.2.4 compiled for arm64 / M1? T

TFE

Member

No, using standard OBS 27.2.4 on the M1 Mac mini running Monterey 12.4 with Rosetta 2 translation. G

gglife

New Member

I am afraid my external monitor setup is one of the issues. I recently learned that GPU will do 5k upscaling and 1440p downscaling afterwards if you use 4k monitor with macos scaled to 1440p - what I usually do. You must log in or register to reply here. Share: Reddit Pinterest Tumblr WhatsApp Email Share Link

• Home
• Forums
• OBS Studio Support
• Mac Support

• This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register. By continuing to use this site, you are consenting to our use of cookies. Accept Learn more…

Top