I have Classic and Evolution plugins running in silicon but not Spectraldayjob wrote: Wed Dec 14, 2022 4:43 pmscroll up my dude.dix wrote: Wed Dec 14, 2022 4:37 pm GRM Tools versions
Version 3.11.0
News:
- Apple Silicon native compatibility
- Fixes several minor bugs
https://inagrm.com/en/store/download
edit: the standalone versions are native apple silicon but the plug ins are not. weird.
definitely not running natively.
edit: email reply from GRM:
Thank you for your feedback.
The problem has been confirmed; We are working on it, and it should be addressed shortly.
Best regards,
Emmanuel
GRM Tools Support
INA grm
store.inagrm.com
Tracking Apple Silicon Native Hosts, Plugins, Effects
- KVRAF
- 37376 posts since 14 Sep, 2002 from In teh net
-
machinesworking machinesworking https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8505
- KVRAF
- 7967 posts since 15 Aug, 2003 from seattle
kidslow wrote: Sun Dec 18, 2022 7:28 pm Your water heater and clothes washer can load M1 native plugins? Cool![]()
- KVRian
- 873 posts since 9 Jun, 2020
My washing machine sounds like Serum sometimes though. Does that count?
-
- KVRAF
- 3397 posts since 6 Nov, 2006
Last edited by dayjob on Mon Dec 19, 2022 10:12 pm, edited 4 times in total.
- KVRAF
- 7640 posts since 2 Sep, 2019
75% of the M1 native T-RackS VST3 plugins don’t load either. Same for ARC 3. In fact, they don’t even show up in the plugin menu at all.
Sometimes I wonder if these developers are even testing their M1 plugins before they release them.
Sometimes I wonder if these developers are even testing their M1 plugins before they release them.
THIS MUSIC HAS BEEN MIXED TO BE PLAYED LOUD SO TURN IT UP
- KVRAF
- 7640 posts since 2 Sep, 2019
Studio One 5. It’s loading the VST2 versions, but not VST3. I've reinstalled a few times, and have the same results each time. I listed which plugins are working and which aren’t here:
viewtopic.php?p=8577220#p8577220
viewtopic.php?p=8577220#p8577220
Last edited by jamcat on Mon Dec 19, 2022 9:46 pm, edited 1 time in total.
THIS MUSIC HAS BEEN MIXED TO BE PLAYED LOUD SO TURN IT UP
- KVRist
- 58 posts since 16 Dec, 2021
Hmm, try this. Try changing the actual filename of one of the plugins from, for example, TR5 Black 76.vst3 to TR5 Black 76a.vst3 and then open S1
For some reason there is this persistent bug in Studio One where it doesn't want to see a certain VST no matter what you do unless you change the name of the actual file
For some reason there is this persistent bug in Studio One where it doesn't want to see a certain VST no matter what you do unless you change the name of the actual file
- KVRAF
- 7640 posts since 2 Sep, 2019
I just tried that on a couple plugins (ARC 3 and Block 76) and both are showing up now. Thanks!
I think it may have to do with plugins failing to have permission when Studio One tries to load them. I have this problem with DSP56300emu every time I update. I've always renamed the folder its in to force Studio One it to scan it again.
I should note that none of these plugins show up in the Blacklist, and resetting the Blacklist doesn't help.
I think it may have to do with plugins failing to have permission when Studio One tries to load them. I have this problem with DSP56300emu every time I update. I've always renamed the folder its in to force Studio One it to scan it again.
I should note that none of these plugins show up in the Blacklist, and resetting the Blacklist doesn't help.
THIS MUSIC HAS BEEN MIXED TO BE PLAYED LOUD SO TURN IT UP
- KVRist
- 58 posts since 16 Dec, 2021
Yeah, it has nothing to do with the blacklist and it's not related to IK or any other plugin company. It's all on S1 and it's really annoying, it happens to some Softube plugins in my case.
I think that Studio One has a separate blacklist that lives within the user setting file that blocks VST3's with specific names because it thinks that they are not M1 native. I've tried multiple things but the only thing that has worked for me is changing the name of the file.
I think that Studio One has a separate blacklist that lives within the user setting file that blocks VST3's with specific names because it thinks that they are not M1 native. I've tried multiple things but the only thing that has worked for me is changing the name of the file.
- KVRAF
- 7640 posts since 2 Sep, 2019
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.)
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.)
THIS MUSIC HAS BEEN MIXED TO BE PLAYED LOUD SO TURN IT UP
- KVRist
- 312 posts since 19 May, 2017 from Ukraine, Odesa
There is one more thing, to try: Always helps for me.jamcat wrote: Mon Dec 19, 2022 10:35 pm 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.)
You do not have the required permissions to view the files attached to this post.
-
machinesworking machinesworking https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8505
- KVRAF
- 7967 posts since 15 Aug, 2003 from seattle
You all had me for a second, I have 53 IK VST3's here in Digital Performer, but no Studio One on this system.
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.
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.
- KVRAF
- 2192 posts since 8 Jan, 2005
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.machinesworking wrote: Tue Dec 20, 2022 8:10 am
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.
But u-he's stuff not working at all would be a reason to ditch DP for me, too
Last edited by sQeetz on Tue Dec 20, 2022 2:12 pm, edited 2 times in total.
MacMini M2 Pro …… MacOS Tahoe ……… Reason 14
-
- KVRAF
- 3397 posts since 6 Nov, 2006
so after all that liquid Music from WaveDNA is not running natively.dayjob wrote: Mon Dec 19, 2022 4:42 am Edit: resolved
anyway...
https://mailchi.mp/wavedna/download-liquid-music-1-8-0

