# ParaView on new Macs with M1 chips?

**URL:** https://discourse.paraview.org/t/paraview-on-new-macs-with-m1-chips/5909
**Category:** ParaView Support
**Created:** [November 27, 2020, 5:31am UTC](https://discourse.paraview.org/t/paraview-on-new-macs-with-m1-chips/5909 "2020-11-27T05:31:29Z")
**Posts on this page:** 6
**Page:** 2

<div class="post-metadata">

### Author: ![Randy\_Heiland](https://discourse.paraview.org/user_avatar/discourse.paraview.org/randy_heiland/32/909_2.png) [@Randy\_Heiland](https://discourse.paraview.org/u/Randy_Heiland)
#### Post date: [June 24, 2022, 1:46pm UTC](https://discourse.paraview.org/t/paraview-on-new-macs-with-m1-chips/5909/21 "2022-06-24T13:46:44Z")

</div>

It doesn’t seem to work for me with 5.10.1 with M1/macOS 12.0 and would welcome any advice:

```auto
$ export VTK_DISABLE_VISRTX=1
$ export VTK_DISABLE_OSPRAY=1
$ file /Applications/ParaView-5.10.1-Intel.app/Contents/MacOS/paraview 
/Applications/ParaView-5.10.1-Intel.app/Contents/MacOS/paraview: Mach-O 64-bit executable x86_64
$ /Applications/ParaView-5.10.1-Intel.app/Contents/MacOS/paraview 
( 2.971s) [paraview] vtkPVRenderView.cxx:3242 WARN| vtkPVRenderView (0x7f857f0116d0): Refusing to enable OSPRay because it is not supported running in this configuration.

```

---

<div class="post-metadata">

### Author: ![jourdain](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jourdain/32/11_2.png) [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [June 24, 2022, 5:31pm UTC](https://discourse.paraview.org/t/paraview-on-new-macs-with-m1-chips/5909/22 "2022-06-24T17:31:14Z")

</div>

If you download and use the arm version of ParaView, it should work out of the box.

---

<div class="post-metadata">

### Author: ![Randy\_Heiland](https://discourse.paraview.org/user_avatar/discourse.paraview.org/randy_heiland/32/909_2.png) [@Randy\_Heiland](https://discourse.paraview.org/u/Randy_Heiland)
#### Post date: [June 24, 2022, 6:13pm UTC](https://discourse.paraview.org/t/paraview-on-new-macs-with-m1-chips/5909/23 "2022-06-24T18:13:13Z")

</div>

Thanks! Yes, indeed it does. Sorry, I should have mentioned I was doing that already. However, I was hoping the x86\_64 PV would also work under Rosetta. This would have also resolved other issues I had with Anaconda, like missing PyQt5 and VTK on the arm64 distro (but available on the x86 distro). Anyway, I was able to install those pkgs on arm64 for now, so I’m good… until I’m not.

---

<div class="post-metadata">

### Author: ![wascott](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/w/8e8cbc/32.png) [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [July 5, 2022, 10:51pm UTC](https://discourse.paraview.org/t/paraview-on-new-macs-with-m1-chips/5909/24 "2022-07-05T22:51:19Z")

</div>

I just picked up a new M1 Macbook. The Kitware 5.10.1 arm64 works fine, and x86 also works fine under Rosetta 2. You can’t tell the difference. Note this is on 12.4, Monterey.

---

<div class="post-metadata">

### Author: ![Randy\_Heiland](https://discourse.paraview.org/user_avatar/discourse.paraview.org/randy_heiland/32/909_2.png) [@Randy\_Heiland](https://discourse.paraview.org/u/Randy_Heiland)
#### Post date: [July 13, 2022, 5:15pm UTC](https://discourse.paraview.org/t/paraview-on-new-macs-with-m1-chips/5909/25 "2022-07-13T17:15:35Z")

</div>

I would LOVE to resolve this - why does the x86 version work for you and not me? I just upgraded from Monterey 12.0 to 12.4 to match your OS. I get the same results as previously, i.e.:

```auto
$ /Applications/ParaView-5.10.1-Intel.app/Contents/MacOS/paraview
( 2.392s) [paraview] vtkPVRenderView.cxx:3242 WARN| vtkPVRenderView (0x7fc7e99ee350): Refusing to enable OSPRay because it is not supported running in this configuration.

```

then I tried to set the env vars and re-run, but same result.

```auto
$ export VTK_DISABLE_VISRTX=1
$ export VTK_DISABLE_OSPRAY=1

```

I’ve got:

```auto
Apple M1 Pro:
  Chipset Model:	Apple M1 Pro
  Type:	GPU
  Bus:	Built-In
  Total Number of Cores:	16
  Vendor:	Apple (0x106b)
  Metal Family:	Supported, Metal GPUFamily Apple 7

```

```auto
$ file /Applications/ParaView-5.10.1-Intel.app/Contents/MacOS/paraview

/Applications/ParaView-5.10.1-Intel.app/Contents/MacOS/paraview: Mach-O 64-bit executable x86_64

```

---

<div class="post-metadata">

### Author: ![Randy\_Heiland](https://discourse.paraview.org/user_avatar/discourse.paraview.org/randy_heiland/32/909_2.png) [@Randy\_Heiland](https://discourse.paraview.org/u/Randy_Heiland)
#### Post date: [July 14, 2022, 7:20pm UTC](https://discourse.paraview.org/t/paraview-on-new-macs-with-m1-chips/5909/26 "2022-07-14T19:20:48Z")

</div>

To add to the mystery (and frustration), I _am_ able to run the x86 ParaView on a M1 (not M1Pro) on a Mac Mini. I do get the same OSPRay warning, but the GUI does display. (And I do not set the VTK\_DISABLE\* env vars). Also running Monterey 12.4

```auto
~/Downloads$ file /Applications/ParaView-5.10.1.app/Contents/MacOS/paraview
/Applications/ParaView-5.10.1.app/Contents/MacOS/paraview: Mach-O 64-bit executable x86_64
~/Downloads$ /Applications/ParaView-5.10.1.app/Contents/MacOS/paraview
( 2.407s) [paraview] vtkPVRenderView.cxx:3242 WARN| vtkPVRenderView (0x7fbf2e0f3120): Refusing to enable OSPRay because it is not supported running in this configuration.

```

```auto
Apple M1:

  Chipset Model:	Apple M1
  Type:	GPU
  Bus:	Built-In
  Total Number of Cores:	8
  Vendor:	Apple (0x106b)
  Metal Family:	Supported, Metal GPUFamily Apple 7

```

[Previous page](https://discourse.paraview.org/t/paraview-on-new-macs-with-m1-chips/5909.md?page=1)