If the BATTERY Factory Library is not installed on your system, please use this installation file to install the. After the reinstall, the Battery 4.component will have Creation and Modification Dates of January 6, 2023. You have two options to solve this issue. If the Creation and Modification Dates are Decemthen you need to manually delete the Battery 4.component and then reinstall Battery 4 with Native Access. To check if you have a problem, do a Get Info on the actual Battery 4.component. I could see the AUHostingCompatibilityService process start up. I verified this by creating a new DP project, opening Activity Monitor, and then creating a new instrument track with Battery 4. Again, even though PlugInfo will show it to contain Apple Silicon native code, it will launch in DP using Rosetta. A user at called "Calagan" found it.Įssentially, if you already had the Battery 4 AU in your components folder, the installer doesn’t complete overwrite it correctly. I can't take credit for discovering this. So Native Instruments released an update to Battery 4 today via Native Access which supports M1 natively for AU, VST3 *and* AAX! However there is a problem with the installer and even though PlugInfo will show the AU is UB2 (Universal Binary 2) containing Apple Silicon and Intel 64 code, it will still run in Rosetta.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |