Forum Discussion
Blur Background on Mac OS
Both of my macs reported in "machdep.cpu.features" only AVX1.0. I executed this command
sysctl - a | grep avx
On one mac (blur disabled) I got
hw.optional.avx1_0: 1
hw.optional.avx2_0: 0On another mac (blur enabled) I got
hw.optional.avx1_0: 1
hw.optional.avx2_0: 1
While I would have preferred to not have to run a terminal command to figure this out, I believe I know why this isn't working.
My Macbook Pro does not support AVX 2.0.
sysctl -a | grep machdep.cpu.features
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC POPCNT AES PCID XSAVE OSXSAVE TSCTMR AVX1.0 RDRAND F16C
Let me know if you think this is not the case.
doug4772 I got the same result on my MacBook Pro (i5 2018) too. Odd, as AVX2 dates back several years. Turns out there's another command to show extended instruction sets:
sysctl -a | grep machdep.cpu.leaf7_features machdep.cpu.leaf7_features: RDWRFSGS TSC_THREAD_OFFSET SGX BMI1 AVX2 SMEP BMI2 ERMS INVPCID FPU_CSDS MPX RDSEED ADX SMAP CLFSOPT IPT MDCLEAR TSXFA IBRS STIBP L1DF SSBDBoth of my macs reported in "machdep.cpu.features" only AVX1.0. I executed this command
sysctl - a | grep avx
On one mac (blur disabled) I got
hw.optional.avx1_0: 1
hw.optional.avx2_0: 0On another mac (blur enabled) I got
hw.optional.avx1_0: 1
hw.optional.avx2_0: 1Grandswiss
I have same issue on my Mac(iMac 2020(27inch).
My Mac support AVX/AVX2.
------------------------------------------% sysctl -a | grep machdep.cpu.feature
machdep.cpu.feature_bits: 9221960262849657855
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C
------------------------------------------
% sysctl -a | grep machdep.cpu.leaf7_features
machdep.cpu.leaf7_features: RDWRFSGS TSC_THREAD_OFFSET SGX BMI1 AVX2 SMEP BMI2 ERMS INVPCID FPU_CSDS MPX RDSEED ADX SMAP CLFSOPT IPT SGXLC MDCLEAR IBRS STIBP L1DF ACAPMSR SSBD
------------------------------------------
But, I can't select background.
My issue capture is here.
Please let me know any idea.To test it on my Teams version (1.3.00.23764), I did the following:
- In the bar on the left hand side, click on "Calendar"
- In the top row, click on "Meet now" (just to the left of "+New meeting")
- Now activate the camera; you should see yourself.
- On my screen, between the camera on/off button and the mute on/off button there is the "background effects" on/off button.
This works now even on my MacBook Pro, where "sysctl -a | grep -i avx2" returns "hw_optional.avx2_0: 0". Hope this helps.
Grandswiss Thanks for further confirmation that AVX2.0 is the discriminator.
Now if only we can get someone at Microsoft to discuss why they changed the code to require it when blur worked fine on AVX1.0 devices on the previous version of Teams.
doug4772 That's weird. I used to have the background blur option avaiable on my iMac teams app, but it's gone now. I checked the terminal command line and do not show AVX2.0 either.
manoelguedes, I just saw your comment. I had the same experience--the blur working at one point, and then disappeared. Did you ever get that resolved? I have a MacBook Pro (Retina, 13-inch, Early 2013) with 3 GHz Dual-Core Intel Core i7. And the result I get from sysctl -a | grep machdep.cpu.features is this:
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC POPCNT AES PCID XSAVE OSXSAVE TSCTMR AVX1.0 RDRAND F16C
- What’s the output of this command?
sysctl -a | grep avx2
manoelguedes I see the same thing on my 2013 Macbook Air.
The blur feature in Teams was present and worked a couple weeks ago but it disappeared after an update.
Looks like Microsoft chose to disable it if you only have AVX1.0.kathysgeek I'm sorry, however I don't believe taht's the reason. It is working for me on my MacBook Pro and it has only AVX1.0. Something else nedds to be there.
