# Mac OS Big Sur Compatibility

**URL:** <https://qa.fmod.com/t/mac-os-big-sur-compatibility/16427>\
**Category:** FMOD Studio\
**Created:** [November 13, 2020, 2:51am UTC](https://qa.fmod.com/t/mac-os-big-sur-compatibility/16427 "2020-11-13T02:51:09Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![danereid1024](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@danereid1024](https://qa.fmod.com/u/danereid1024)\
**Post date:** [November 13, 2020, 2:51am UTC](https://qa.fmod.com/t/mac-os-big-sur-compatibility/16427/1 "2020-11-13T02:51:09Z")

</div>

Any word on FMOD being compatible with Mac OS Big Sur?

---

<div class="post-metadata">

**Author:** ![mathew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/mathew/32/431_2.png) [@mathew](https://qa.fmod.com/u/mathew)\
**Post date:** [November 15, 2020, 9:56pm UTC](https://qa.fmod.com/t/mac-os-big-sur-compatibility/16427/2 "2020-11-15T21:56:34Z")

</div>

We’ve had no issues so far and can verify it works on Apple Silicon Macs under Rosetta 2.

---

<div class="post-metadata">

**Author:** ![danereid1024](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@danereid1024](https://qa.fmod.com/u/danereid1024)\
**Post date:** [November 20, 2020, 6:26pm UTC](https://qa.fmod.com/t/mac-os-big-sur-compatibility/16427/3 "2020-11-20T18:26:14Z")

</div>

Thanks! That’s good to know!

---

<div class="post-metadata">

**Author:** ![burnum](https://avatars.discourse-cdn.com/v4/letter/b/f4b2a3/32.png) [@burnum](https://qa.fmod.com/u/burnum)\
**Post date:** [November 22, 2020, 8:45pm UTC](https://qa.fmod.com/t/mac-os-big-sur-compatibility/16427/4 "2020-11-22T20:45:38Z")

</div>

I’m getting pretty frequent clicks and stutters using FMOD Studio 2.1.06 on M1 Mac Book Pro 13" (16GB RAM), macOS Big Sur 11.0.1. I can reproduce this playing any of the Music \> Level events in the Examples project using just the built in speakers (either trying 44.1 or 48kHZ sample rate).

---

<div class="post-metadata">

**Author:** ![mathew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/mathew/32/431_2.png) [@mathew](https://qa.fmod.com/u/mathew)\
**Post date:** [November 23, 2020, 10:10pm UTC](https://qa.fmod.com/t/mac-os-big-sur-compatibility/16427/5 "2020-11-23T22:10:13Z")

</div>

Can you try playing the Event then record in the Profiler to see what the CPU stats look like?

---

<div class="post-metadata">

**Author:** ![burnum](https://avatars.discourse-cdn.com/v4/letter/b/f4b2a3/32.png) [@burnum](https://qa.fmod.com/u/burnum)\
**Post date:** [November 24, 2020, 12:22am UTC](https://qa.fmod.com/t/mac-os-big-sur-compatibility/16427/6 "2020-11-24T00:22:57Z")

</div>

Hi Mathew,

I figured out that it seems to only happen when Perforce is online. I guess that makes sense since the Helix p4 client doesn’t officially support Big Sur or M1 yet, and maybe there’s background IO reads that are interrupting the audio stream thread? I haven’t heard the glitches since turning off perforce.

Let me know if you’d still like the profiler recording.

---

<div class="post-metadata">

**Author:** ![mathew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/mathew/32/431_2.png) [@mathew](https://qa.fmod.com/u/mathew)\
**Post date:** [November 25, 2020, 12:48am UTC](https://qa.fmod.com/t/mac-os-big-sur-compatibility/16427/7 "2020-11-25T00:48:54Z")

</div>

Thanks for the info, Perforce must have been using a lot of system resources, glad to know closing it resolved the issue. I imagine there will be quite a few issues as everyone slowly migrates to M1. I won’t need the profiler recording now the cause is isolated, let me know if any other apps cause this problem, it’s good information for everyone.