When checking for the compatibility with Apple M1 computers, there are different things to consider, we detail this below, but very briefly, we can tell that, while our applications run mostly fine on M1 chip (either Natively or with Rosetta depending on the application), the main things to know currently is that:
- most video devices manufacturers still have to provide drivers that are compatible with M1 chips. At the time of writing, only Blackmagic-Design has one (12.0, beta). So cards from AJA, or Deltacast (M|Family) will not work on M1 computers.
- if you are using NDI, it will work for output only, not for input, when starting the application with Rosetta only, not an application running "natively. Newtek still has to provide a library that is compatible with the M1 chip for input.
But read below for more details...
About Big Sur
As the M1 computers will only run with Big Sur, first make sure to check which applications and video device drivers are supported by this macOS version.
Rosetta or Native?
When running applications on computers with M1 chips, there are two possible types:
- Intel: the application is not built for M1 chips and thus it runs with the Rosetta translation. The performances won't be as good.
- Universal: the application has been built to run natively, so without translation. These applications are called "Universal" as they include a version for Intel and one for M1 processors. This should result in better performances.
By default, if an application is "Universal", it will run "Natively". But in some cases, you may want to force the application to start with Rosetta. For this, select the application in the Finder, then use the command + i keyboard shortcut, and enable the following option:
Supported Applications Versions
IMPORTANT: If you use a video input/output (AJA, Blackmagic-Design, Deltacast, NDI), make sure to check the compatibility list in the next point below.
|Application||Supported Version with Rosetta||First "Universal" Version|
|OnTheAir Video Express||4.0*||4.0b233*|
* check the video drivers compatibility list below.
Compatibility with video inputs and outputs
For our applications that don't use a video device from AJA, Blackmagic-Design or Deltacast, or don't use NDI, it is easy: if our application is Universal, you will run as Universal, if not, macOS will use Rosetta.
But with applications that use a video device from AJA, Blackmagic-Design or Deltacast or NDI, we depend on them to provide drivers and librairies. So the first thing to check is if the device you use is compatible.
Video inputs/outputs compatibility with M1
The first thing to make sure is that a "Universal" version of the driver is available, indeed drivers can not use Rosetta, so older drivers will not work on M1 chips. As soon as a driver is available from the manufacturer, you will be able to use it with our applications when started with Rosetta (see above if you need to force it).
|AJA||Not compatible yet||Not compatible yet|
|12.0* (beta version available)||12.0* (beta version available)|
|M|Family (Deltacast)||Not compatible yet||Not compatible yet|
|NDI Output||All our applications since 2019**||Not compatible yet|
|NDI Input||Not compatible yet **||Not compatible yet|
* or later
** while NDI output works when starting the application with Rosetta, NDI inputs will only work once we have the Universal Libraries.
Application versions that have Universal Libraries
Once there is a M1 compatible driver for your device, you will be able to use most of our applications using Rosetta. But if you want to use the device in "Native" mode, you will need to use a version that has the "Universal" Library. See below when the universal libraries are added to our applications for each device type.
|OnTheAir Video Express||4.0b233*|
* or later...
About hardware acceleration for H.264 and HEVC
As you may know, Intel computers have some hardware acceleration available to encode/decode H.264 and HEVC. Thanks to that hardware acceleration, which offloads the encoding/decoding off the CPU, an Intel Mac mini can be very efficient to encode or decode H.264 or HEVC, all that without using the CPU, and thus leaving the CPU available for other tasks.
The computers using the M1 chip also have a hardware acceleration, and we see that Apple has made a push on HEVC. So performances will be much better when encoding/decoding HEVC, but note that they won't be as good for H.264. So if you intend to encode multiple channels to H.264, the best solution is still an Intel Mac mini, but if you can use HEVC, then the ones using the M1 chip are the way to go.
Usual and important recommendations
As usual, when doing major system or hardware upgrades on critical pieces of equipment for broadcast or production, it is always best to run tests with a backup equipment so you can make sure that all the pieces of your specific workflow are working well together. We run many tests, and different combinations, but we don't have your files and all cameras.