Tracking Apple Silicon Native Hosts, Plugins, Effects

[machinesworking]

To be fair, DP and other DAWs like Live will occasionally block or not work with certain VST3's (U-He with DP etc.), so it's a more or less universal glitch in these plug in evaluation routines DAWs use.

When possible I prefer to install only the AU version of any given plugin. And I have no problem in either Live, Renoise, Logic. The lack of AU support is one of the main reasons for me ditching Bitwig.
But u-he's stuff not working at all would be a reason to ditch DP for me, too

VST3 U-He doesn't work, AU works just fine and VST2 as well. One big advantage Reaper, DP, and Live have is that they support all three Mac OS plug in formats, with reaper now supporting CLAP. Unless I'm working with someone who only uses one plug in format I mix and match at will.

I agree, the big disadvantage of Bitwig is their VST only adherence on Mac OS, they have good success with it, but it's not a secret that VST3 hosting for anyone outside of Cubase/Nuendo is problematic, to this day VST3 is the most likely format to crash or fail validation on any DAW here that supports it. I think it's no mystery why Bitwig are huge CLAP proponents.

[dayjob]

Edit: resolved

anyway...

https://mailchi.mp/wavedna/download-liquid-music-1-8-0

so after all that liquid Music from WaveDNA is not running natively.

and just to further muddy the waters.. got this response from WaveDNA when i sent them that screen grab of liquid music running as intel.

It's showing in the activity monitor as "Intel" due to the UI, but the back end guts of the app is running in Apple Native mode. if you are using LM or LR as a plugin within a DAW, the DAW itself determines whether it runs in Native or Rosetta mode and is the plugins are Native compatible they will run in that mode.

edit: edit: so had a good chat w/WaveDNA and they clarified the situation with native apple silicon compatibility and to their credit they have changed the language in the "known issues" section of the announcement. it's a tricky thing but the plug ins will run natively in apple silicon (or however the DAW/Host wants) and the UI is running as intel.

regardless i've had good performance w/it so far and the update seems to be working fine. I'm glad to have it back!

[rhye999]

I have found a better way to fix the missing plugins that seems to have worked for all of them in one go, without renaming them:

Delete Plugins-en.settings from Library > Application Support > PreSonus > Studio One 5 > ARM64 then open Studio One to rebuild the entire plugin list (which takes a little while.)

That worked great! Thanks

[cadiz]

To be fair, DP and other DAWs like Live will occasionally block or not work with certain VST3's (U-He with DP etc.), so it's a more or less universal glitch in these plug in evaluation routines DAWs use.

When possible I prefer to install only the AU version of any given plugin. And I have no problem in either Live, Renoise, Logic. The lack of AU support is one of the main reasons for me ditching Bitwig.
But u-he's stuff not working at all would be a reason to ditch DP for me, too

VST3 U-He doesn't work, AU works just fine and VST2 as well. One big advantage Reaper, DP, and Live have is that they support all three Mac OS plug in formats, with reaper now supporting CLAP. Unless I'm working with someone who only uses one plug in format I mix and match at will.

I agree, the big disadvantage of Bitwig is their VST only adherence on Mac OS, they have good success with it, but it's not a secret that VST3 hosting for anyone outside of Cubase/Nuendo is problematic, to this day VST3 is the most likely format to crash or fail validation on any DAW here that supports it. I think it's no mystery why Bitwig are huge CLAP proponents.

U-He VST3 work just fine in Ableton Live, no issues at all

[machinesworking]

To be fair, DP and other DAWs like Live will occasionally block or not work with certain VST3's (U-He with DP etc.), so it's a more or less universal glitch in these plug in evaluation routines DAWs use.

When possible I prefer to install only the AU version of any given plugin. And I have no problem in either Live, Renoise, Logic. The lack of AU support is one of the main reasons for me ditching Bitwig.
But u-he's stuff not working at all would be a reason to ditch DP for me, too

VST3 U-He doesn't work, AU works just fine and VST2 as well. One big advantage Reaper, DP, and Live have is that they support all three Mac OS plug in formats, with reaper now supporting CLAP. Unless I'm working with someone who only uses one plug in format I mix and match at will.

I agree, the big disadvantage of Bitwig is their VST only adherence on Mac OS, they have good success with it, but it's not a secret that VST3 hosting for anyone outside of Cubase/Nuendo is problematic, to this day VST3 is the most likely format to crash or fail validation on any DAW here that supports it. I think it's no mystery why Bitwig are huge CLAP proponents.

U-He VST3 work just fine in Ableton Live, no issues at all

I was talking specifically about DP11, currently Hive and Bazille are failing evaluation here. Diva, ACE, Repro 1-5 all work fine. It will always vary which DAW and which plug in doesn't pass evaluation, an earlier version of Live 11 was failing Arturia plug ins here, which all worked in DP11.. Rhyme, reason? no idea, just that VST3 suffers the most.

[Weasel-Boy]

It looks like NI bumped FM8 up to silicon today. V1.4.5 shows as silicon compliant on Archichect. Installer drops VST2, VST3 and the stand-alone.

It would appear NI broke the sustain pedal on the VST3 silicon v1.4.5 version. The stand-alone v1.4.5 works fine. Couldn't tell is the VST2 version worked in Cubase 12 because it only lists the VST3 version.

So far with the v1.4.5 version, if you hit a chord and press sustain, it'll hold the chord, but if you continue to play other
notes, they won't sustain. Not the case with the previous v1.4.4 version (which was just VST2). Sustain works as expected there.

Edit: NI fixed it in a quick turn around with version 1.4.6

[asstudioton]

The greatest EndeavorFX plugins are updated for apple silicon with new GUI and improvements

https://endeavorfx.com/index.html

[teilo]

just got email from inaGRM that the new package is 3.11 and is apple silicon native. their website is horrible at showing this info so i screen grabbed the email.
https://inagrm.com/en

This has to be the single worse plugin site I have had to deal with. What are these people thinking? Everything is bundles. Products do not have their own pages. Bundles overlap. Big gray boxes for product thumbnails. No specs.

[teilo]

[dupe]

[lights]

I have found a better way to fix the missing plugins that seems to have worked for all of them in one go, without renaming them:

Delete Plugins-en.settings from Library > Application Support > PreSonus > Studio One 5 > ARM64 then open Studio One to rebuild the entire plugin list (which takes a little while.)

Hi Jamcat, saw several posts where you suggested this solution for plugins not showing up in S1. Do you know if that deletes the midi control mapping as well?

About to try your suggestion but wanted to check first as I've got extensive midi mapping to my hardware controllers and it would be a nightmare to have to remap all that.

Thanks.

[jamcat]

I have found a better way to fix the missing plugins that seems to have worked for all of them in one go, without renaming them:

Delete Plugins-en.settings from Library > Application Support > PreSonus > Studio One 5 > ARM64 then open Studio One to rebuild the entire plugin list (which takes a little while.)

Hi Jamcat, saw several posts where you suggested this solution for plugins not showing up in S1. Do you know if that deletes the midi control mapping as well?

About to try your suggestion but wanted to check first as I've got extensive midi mapping to my hardware controllers and it would be a nightmare to have to remap all that.

Thanks.

I want to say the MIDI maps are stored elsewhere. But to be safe, I’d suggest moving plugins-en.settings out of the folder instead of deleting it, so you can restore it if something goes wrong.

You can actually open the file with a text editor, it’s just standard xml. When you do, you’ll see it’s just information related to the plugin menu, like the file name, effect type, vendor, version, date installed, etc.

Just to be clear about the location of plugins-en.settings, it is in the Library folder that you access by holding down option to see in the Go menu: Mac HD > Users > You > Library > Application Support > PreSonus > Studio One 5 > ARM64

Also, Serhii Kot pointed out this button in View > Plug-In Manager in Studio One. I'm pretty sure it deletes plugins-en.settings for you.

[dayjob]

just got email from inaGRM that the new package is 3.11 and is apple silicon native. their website is horrible at showing this info so i screen grabbed the email.
https://inagrm.com/en

This has to be the single worse plugin site I have had to deal with. What are these people thinking? Everything is bundles. Products do not have their own pages. Bundles overlap. Big gray boxes for product thumbnails. No specs.

And it’s an improvement to the old site. Lols

[aMUSEd]

just got email from inaGRM that the new package is 3.11 and is apple silicon native. their website is horrible at showing this info so i screen grabbed the email.
https://inagrm.com/en

This has to be the single worse plugin site I have had to deal with. What are these people thinking? Everything is bundles. Products do not have their own pages. Bundles overlap. Big gray boxes for product thumbnails. No specs.

And it’s an improvement to the old site. Lols

Have they fixed the missing Apple Silicon versions for some of their plugins yet?

[lights]

I have found a better way to fix the missing plugins that seems to have worked for all of them in one go, without renaming them:

Delete Plugins-en.settings from Library > Application Support > PreSonus > Studio One 5 > ARM64 then open Studio One to rebuild the entire plugin list (which takes a little while.)

Hi Jamcat, saw several posts where you suggested this solution for plugins not showing up in S1. Do you know if that deletes the midi control mapping as well?

About to try your suggestion but wanted to check first as I've got extensive midi mapping to my hardware controllers and it would be a nightmare to have to remap all that.

Thanks.

I want to say the MIDI maps are stored elsewhere. But to be safe, I’d suggest moving plugins-en.settings out of the folder instead of deleting it, so you can restore it if something goes wrong.

You can actually open the file with a text editor, it’s just standard xml. When you do, you’ll see it’s just information related to the plugin menu, like the file name, effect type, vendor, version, date installed, etc.

Just to be clear about the location of plugins-en.settings, it is in the Library folder that you access by holding down option to see in the Go menu: Mac HD > Users > You > Library > Application Support > PreSonus > Studio One 5 > ARM64

Also, Serhii Kot pointed out this button in View > Plug-In Manager in Studio One. I'm pretty sure it deletes plugins-en.settings for you.

Thanks for the reply, appreciate it. Will try moving the file instead.

[jamcat]

Thanks for the reply, appreciate it. Will try moving the file instead.

If you find for some reason you need to go back to the original file, you can actually just copy the working entries from the rebuilt plugins-en.settings and paste over the non-working versions in the original.