Important… where is the latest DVRS for Apple Silicon

I have been trying to find it under the support page. The latest 19.1.4 DVR Studio MacOS link downloads the version but on the Mac Silicon (M1-M4) it wants to install Rosetta. Can someone please help as I need to get my system going? Thanks to everyone and those who knows how to get this issue resolved.

Some portions of 3rd party components need Rosetta. You’ll need to install Rosetta 2.

Some portions of 3rd party components need Rosetta. You’ll need to install Rosetta 2.

Thanks Steve. So Resolve Studio on the Mac Silicon is just emulating Intel instructions and not direct to Silicon instructions. That’s sad.

Some portions of 3rd party components need Rosetta. You’ll need to install Rosetta 2.

Thanks Steve. So Resolve Studio on the Mac Silicon is just emulating Intel instructions and not direct to Silicon instructions. That’s sad.

Most of Resolve is native M series code but some components require Rosetta.

The bulk of Resolve is running natively. Some minor third party parts require Rosetta.

Rest assured DVR will be fast as it is optimised for the Silicon Macs and is running natively.

If you want to check by yourself, see the info for DR (CMD+i).

I tried cmd-i but it just brought up the Import window.

What am I doing wrong?

I tried cmd-i but it just brought up the Import window.

What am I doing wrong?

CMD + I on the Resolve.exe

Doesn't work with the .dmg on a Mac.

Just get the basic name, version and size.

Dmg? The installer?

Sorry, I meant the application executable - DaVinci Resolve.app

If you CMD+I on DaVince Resolve.app you will see that it a universal binary and that it is not set to open with Rosetta.

Got it. Thanks Steve.

Does version 20 still require Rosetta on Silicon?

Does version 20 still require Rosetta on Silicon?

I assume so but since I already have Rosetta 2 installed for previous versions of Resolve, I can't be 100% sure.

....So Resolve Studio on the Mac Silicon is just emulating Intel instructions and not direct to Silicon instructions. That’s sad.

100% of the Resolve.exe process is running native Apple Silicon code. Rosetta does not work on a mixed Apple Silicon/Intel process. IOW a process must be all Apple Silicon or all Intel. The Resolve process includes many private Apple Silicon binary frameworks contained in the Resolve .app bundle.

The parts of the Resolve product package that require Rosetta are external to the Resolve process. They are a few infrequently-used old codecs, etc. that run in an *external* Intel process.

E.g, on MacOS the encoders and decoders run in a series of external processes named VTDecoderXPCService and VTEncoderXPCService. It's possible to have some Intel and some Apple Silicon codecs. Activity Monitor's CPU tab has a column named "Kind." That will say Intel or Apple. If you query on "VT" you'll see almost all Apple Silicon processes but maybe (rarely) a few Intel ones, and most of those will not be taking any significant CPU time.

I don't know why some of the codecs are still Intel. It's possible that some of those are maintained only for a few old third-party MacOS Intel utilities written to the earlier Quicktime framework, and almost all current software uses Apple Silicon codecs embedded elsewhere in the modern AV Foundation framework.

Joe, Thanks for that technical explanation. Totally makes sense to me.

If you want to check by yourself, see the info for DR (CMD+i).

There's not much info there... so cmd+I it doesn't report the build info or anything that will indicate its use of Rosetta. I'm just sharing what I found out (see screenshot below of cmd+I on DVR app. If anything, it's a large app.

Screenshot0525.png (224.8 KiB) Viewed 1068 times

That's the folder. If you do it on the executable inside the folder you will get the Rosetta checkbox. Likely it's disabled for the reasons Joe outlined.

There's not much info there... so cmd+I it doesn't report the build info or anything that will indicate its use of Rosetta...

In Finder if you do CMD+I on Resolve.app it will show an option for "Open using Rosetta." Resolve is a universal binary and contains both Intel and Apple Silicon versions. It is rarely a good idea to force a universal app to run under Rosetta.

Some MacOS Apple Silicon apps suppress that option by having an entry in the Info.plist file within the .app bundle that says

Code: Select all

LSRequiresNativeExecution = true

You can view a plist file using BBEdit, TextMate, etc or the built-in MacOS command-line tool plutil -p <pathname to Info.plist file>
You an examine an on-disk application binary to see if it's Intel, Apple Silicon or Universal by using the command-line utility "file" on the actual binary executable inside the .app bundle. You can get to that by doing right-click on the .app in Finder and picking "Show Package Contents," then drilling down. You can drag/drop the executable to the terminal window and that will insert the pathname, so you don't have to type it. Example showing Resolve is a universal binary:

file /Applications/DaVinci\ Resolve/DaVinci\ Resolve.app/Contents/MacOS/Resolve

/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/MacOS/Resolve: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64]
/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/MacOS/Resolve (for architecture x86_64): Mach-O 64-bit executable x86_64
/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/MacOS/Resolve (for architecture arm64): Mach-O 64-bit executable arm64

Example of an Intel-only app:

file /Applications/PDF\ Compress\ +.app/Contents/MacOS/PDF\ Compress\ +

/Applications/PDF Compress +.app/Contents/MacOS/PDF Compress +: Mach-O 64-bit executable x86_64

In Activity Monitor, on Apple Silicon, the "Kind" column should state "Apple" for Resolve. If it states "Intel" then somebody forced it to run under Rosetta, which often causes problems. There's nothing wrong with Resolve in this regard, it causes problems for FCP also. Those are universal binaries, and on Apple Silicon they should always run in native format as an ARM64 process.