No Video Engine in PT 2021.6 on M1 Mac

[budster]

No video engine. Of course, I am running an unsupported Mac mini with the M1 chip, but it was running well on 21.3.

[BScout]

No video engine for M1.

It's written on every note of this version release.

[budster]

Avid DnX HD 36 23.976

It worked in PT 2020.11 and 2021.3

[BScout]

Originally Posted by budster

Avid DnX HD 36 23.976

It worked in PT 2020.11 and 2021.3

M1 no video engine. Right there in the notes on 2021.6.

There's a whole thing about native code vs translation code (rosetta 2) concerning the M chips. If Avid moved 2021.6 to more native code, then certain modular components that are still only translation code won't work with it. That's just how it is. All on one side or the other.
2021.3 and 2020.11 were 100% translation code.
2021.6 is Avid moving Pro Tools to native code. Not everything is ported at once and they put the specific note that video engine is NOT supported. So this shouldn't be a surprise and it's a pointless waste of time to try to get it to work because it simply won't. Wait for the next release. Stick with older versions.

(this is just like other things -- Logic native M1 won't run with Eucon because Eucon was only translation code so you had to run the translation code version of Logic to use Eucon. Eventually all these things will be on the same side but that is not now.)

This is not the OP's problem so I'd like to stick with their issue that should be solvable.

[theAlien]

Originally Posted by BScout

M1 no video engine. Right there in the notes on 2021.6.

2021.6 is Avid moving Pro Tools to native code. Not everything is ported at once and they put the specific note that video engine is NOT supported.

Release Notes explicitly states *supported via Rosetta 2*. So, which part of Pro Tools' code is executing ARM instructions in what situations?

I'm asking bc I'm waiting for full support for my HDX purchase/move.

Thx.

[BScout]

Originally Posted by theAlien

Release Notes explicitly states *supported via Rosetta 2*. So, which part of Pro Tools' code is executing ARM instructions in what situations?

I'm asking bc I'm waiting for full support for my HDX purchase/move.

Thx.

Read the release notes again. No HDX (no drivers yet) and No Video Engine.

Not supported on M1 Macs at this time:

• Avid Video Engine is not available on M1 Macs at this time. However, we are working with Apple to resolve known issues to be compatible in the future.
• Pro Tools | HDX, Pro Tools | HD Native, and DADman software (MTRX & MTRX Studio) are not supported on M1 Macs at this time.
• Before updating, check to see if your third-party plugins and other programs are officially supported on a new OS.

Pro Tools System Usage CPU count on M1 Macs

• Due to the innovative combination of Performance cores & High Efficiency cores in M1 machines, the Pro Tools Hardware Monitor will only display 4 CPUs as the majority of the processing needs to be accomplished in the Performance domain.

https://avid.secure.force.com/pkb/ar...m-Requirements

[theAlien]

BScout, you seem not to understand me.

Your post gives the impression that you say they have *partially* ARM code in PT, which is not possible (I am a former SW developer and I know what I am talking.)

Your statement is wrong. Either PT is compiled to ARM, to Intel or both as universal. Either it needs Rosetta or it can be run natively. Intel code with some ARM instructions hiding somewhere does surely not represent the real world(*).

Edit: This can be easily checked. In Terminal enter

file /Applications/<app name>/Contents/MacOS/<binary name>

which will immediately reveal all supported architectures.

And as I understand, the whole PT package is still distributed as Intel code. (I don't have PT currently installed to test it.)

But what we may observe in the near future is, Avid could release the PT package in layers; PT still Intel (as this needs most development resources) and drivers, daemons etc. as ARM (as subsystems cannot be run via Rosetta.)

(*) speaking practically not technically. Technically it is possible to embed any binary into your code, of course, including opcodes and instructions of any architecture.