The Heavier7Strings plugin is listed in plugin manager and shown to be passed auval testing, but it is not listed in instruments insertion pop-up menu (neither the one in track, nor the one in "new project -> software instrument dialog").
However, its sibling plugin HeavierFX can be used normally.
Environment: M1 MBP, MacOS 13.0.1, Logic Pro 10.7.0
This issue happens on both native- or rosetta translated Logic Pro host.
Any clues on it? Or is there any similar issue on other plugins?
Logic Pro found H7S in plugin manager but not listing it in track
-
- KVRer
- 13 posts since 1 Jun, 2016
- KVRist
- 487 posts since 26 Oct, 2004 from U.K.
Yes. Same problem here with Analog Lab & MiniFreak VST. They are in the plug-in manager & validated but not in the track menu. Very odd.
Latest Ventura & Logic
I should add that both were recently updated so I was thinking it was a problem with Arturia, but now I’m thinking it’s a Logic problem. I’ve done a rescan etc
Latest Ventura & Logic
I should add that both were recently updated so I was thinking it was a problem with Arturia, but now I’m thinking it’s a Logic problem. I’ve done a rescan etc
'and when we got bored, we'd have a world war...'
- KVRAF
- 3051 posts since 6 Jul, 2013
There have been a few instances I've seen of this happening in Logic since about 10.5 or 10.6 or so. It seems to be a problem with Logic sometimes not correctly building the plugin menus to include the plugin. The plugins *can* be used, they just can't be selected from the menu. I'm not sure what's the cause of this behaviour, whether it's just a Logic bug, or whether something changed in the plugin handling that plugin developers have to do.
There are some workarounds - if you have a saved project that previously used the plugin, if you open it, you should find the plugin is loaded correctly. At that point, save a Channel Strip Setting, or Patch, and you should then be able to load that when you want to use the plugin (or you can just do this on a temporary track, and then drag the plugin insert to the track you want).
So it's annoying, but at least there are workarounds in the meantime. I also suggest reporting it as a bug...
There are some workarounds - if you have a saved project that previously used the plugin, if you open it, you should find the plugin is loaded correctly. At that point, save a Channel Strip Setting, or Patch, and you should then be able to load that when you want to use the plugin (or you can just do this on a temporary track, and then drag the plugin insert to the track you want).
So it's annoying, but at least there are workarounds in the meantime. I also suggest reporting it as a bug...