KVR Audio

plexuss · Post by **plexuss** » Tue Aug 31, 2021 3:42 pm

I moved from Logic Pro awhile ago (to Reaper). I have an old track I did in LPX want to open and work on. When I open Logic and go through hours of plugin scanning, crashing, failures, dialogues etc. and finally get to the main UI, any 3rd party VI I instantiate shows up in the channel strip "greyed out" (its still blue but faded out) and I can't open the UI and the plugin makes no sound. I can instantiate the Logic VIs no problem and they respond to MIDI and make sound.

I've tried rebooting and re-scanning (lord help me) but no go. I also checked all audio settings and tried different configurations. Core audio is working normally otherwise.

I am now trying to get Logic running on my laptop to see if I can open it there so I can just export the tracks into Reaper and make music, instead of doing IT.

Does anyone have any suggestions on how/why Logic is disabling 3rd party VIs?

jancivil · Post by **jancivil** » Tue Aug 31, 2021 4:07 pm

it could be confused from corruption. I would trash preferences somewhere unless that's proved to be a cure worse than the disease

fmr · Post by **fmr** » Tue Aug 31, 2021 4:10 pm

If you remember what presets you used in the VIs, I would just export the file as MIDI, and open it in RAPER, starting over from there. I think it would be a safer solution than using something old and which probably will keep giving you troubles.

plexuss · Post by **plexuss** » Tue Aug 31, 2021 4:40 pm

fmr wrote: Tue Aug 31, 2021 4:10 pm If you remember what presets you used in the VIs, I would just export the file as MIDI, and open it in RAPER, starting over from there. I think it would be a safer solution than using something old and which probably will keep giving you troubles.

I dont remember the presets and settings so I would not be able to recreate it.

I am now trying to get Logic up on my macbook. It just fails like a dead animal trying to scan AUs. It was basically impossible on my main mac pro music machine. Now on my macbook I have resorted to removing all AUs and only installing those used in this track.

Logic POS X

*resisting the urge to slag logic as it so deserves* *thanking the gods that I switched to Reaper*

fmr · Post by **fmr** » Tue Aug 31, 2021 4:52 pm

Logic Pro X now entered the same "logic" as macOS. You keep updating macOS, and therefore, you need to keep updating Logic. In the process, it breaks compatibility with a lot of things (mainly plug-ins), forcing users to ditch those. It's a neverending story. Apple aim is forcing users to stay inside the macOS/Logic ecosystem, that way ensuring they can never leave.

pdxindy · Post by **pdxindy** » Tue Aug 31, 2021 5:00 pm

plexuss wrote: Tue Aug 31, 2021 3:42 pmDoes anyone have any suggestions on how/why Logic is disabling 3rd party VIs?

You would likely need to provide more info... which OS version? which Logic version? how old is your computer (which model)?

jancivil · Post by **jancivil** » Tue Aug 31, 2021 5:02 pm

the last time I opened Logic, it had been a while, with OS updates, and its AU scanning was distastrous, not all of it but it really put the chill on me using it, the time wasting. I had it for compatibility with video people and FCPX, not dependent on it to make anything. AU scanning is a little bit dodgy all over IME.

apoclypse · Post by **apoclypse** » Tue Aug 31, 2021 5:05 pm

You probably need to disable the system notarization for those plugins. Catalina and Big Sur require the plugin be notarized.

You can do that by doing the following for each plugin

Run terminal and type this:

spctl --add "/Library/Audio/Plug-Ins/Components/[plugin name]"

replace [plugin name] with actual plugin name in the Components folder. Relaunch Logic and it should scan the plugin.

You are basically telling GateKeeper to disregard notarization for those plugin by using the SPCTL command.

plexuss · Post by **plexuss** » Tue Aug 31, 2021 6:27 pm

I'm running macPOS 10.13 (H Sierra) and Logic POS X 10.4.8. This was the last config before I switched to Reaper. I simply stopped using Logic at that point but nothing else changed other than plugin software updates. In other words, the same copy of Logic was running fine.

I just tried it on my 2012 MBP running 10.14 and LPX 10.15.1. I was able to get that copy of Logic to work with the project. With this, after a lot of work, I was able to get the project open so I could export the info and re-create in Reaper.

What a fiasco with Logic! It makes me feel good about abandoning it. I've been using Logic forever, since 1987 when it was CLAB Creator on Atari. No more!

Ploki · Post by **Ploki** » Wed Sep 01, 2021 6:49 am

fmr wrote: Tue Aug 31, 2021 4:52 pm Logic Pro X now entered the same "logic" as macOS. You keep updating macOS, and therefore, you need to keep updating Logic. In the process, it breaks compatibility with a lot of things (mainly plug-ins), forcing users to ditch those. It's a neverending story. Apple aim is forcing users to stay inside the macOS/Logic ecosystem, that way ensuring they can never leave.

you're assuming i want to leave and that it's not better to ditch those plugins.
I don't have to pay atrocious upgrade fees every half a month, the updates usually make things better/faster, and the plugins i ditched are more or less garbage i'm doing fine without and never needed in the first place.

plexuss wrote: Tue Aug 31, 2021 6:27 pm What a fiasco with Logic! It makes me feel good about abandoning it. I've been using Logic forever, since 1987 when it was CLAB Creator on Atari. No more!

Afaik that version of logic started using "only load plugins that are needed for the project", enabled by default, and it was a documented bug with those versions, that was fixed soon after.
I vaguely remember this happening, opening projects settings and disabling that function then reopening the project fixed it.

plexuss · Post by **plexuss** » Sat Sep 04, 2021 5:54 am

Ploki wrote: Wed Sep 01, 2021 6:49 am
fmr wrote: Tue Aug 31, 2021 4:52 pm Logic Pro X now entered the same "logic" as macOS. You keep updating macOS, and therefore, you need to keep updating Logic. In the process, it breaks compatibility with a lot of things (mainly plug-ins), forcing users to ditch those. It's a neverending story. Apple aim is forcing users to stay inside the macOS/Logic ecosystem, that way ensuring they can never leave.
you're assuming i want to leave and that it's not better to ditch those plugins.
I don't have to pay atrocious upgrade fees every half a month, the updates usually make things better/faster, and the plugins i ditched are more or less garbage i'm doing fine without and never needed in the first place.

plexuss wrote: Tue Aug 31, 2021 6:27 pm What a fiasco with Logic! It makes me feel good about abandoning it. I've been using Logic forever, since 1987 when it was CLAB Creator on Atari. No more!
Afaik that version of logic started using "only load plugins that are needed for the project", enabled by default, and it was a documented bug with those versions, that was fixed soon after.
I vaguely remember this happening, opening projects settings and disabling that function then reopening the project fixed it.

Just to follow up, yes, none of that worked for me. The 3rd party VIs still show as disabled where-as 3rd party insert effects show up just fine. It's another Logic mystery and why Logic will never be a professional level tool unless you stick with built-in plugins and dont push it too hard.

Ploki · Post by **Ploki** » Sat Sep 04, 2021 9:52 am

plexuss wrote: Sat Sep 04, 2021 5:54 am
Just to follow up, yes, none of that worked for me. The 3rd party VIs still show as disabled where-as 3rd party insert effects show up just fine. It's another Logic mystery and why Logic will never be a professional level tool unless you stick with built-in plugins and dont push it too hard.

idk, rocking 10.6.3 on Big Sur with a handful of 3rd party plugins and pushing it to the limits and i get by just fine.

i find it just as professional as any other DAW.

jancivil · Post by **jancivil** » Sat Sep 04, 2021 3:39 pm

Apple tries to coerce me into adopting the two-step verification, and won't leave me alone about updating the OS even as I have automatic updates deselected, but none of the things they do to bring users in line to their ways have any effect on me using Cubase.

(most things are simple, right click and open from the menu, TDR Proximity needs help because VE Pro gets an extra message from the OS it's dangerous.*)
And its AU I never got to work under Catalina. I found a workaround for the VST to pass validation in VEP, instantiate in Cubase which is not having that problem.

It's counterintuitive, if they want people under control like that you'd think they would have a scanning AU that works notably better.
It's a problem in VE Pro, it's a problem for many in Logic, right now FCPX is not having that issue but it has. Actually NI AUs (edit: FX) in VE Pro usually have a broken GUI, so I had a Guitar Rig VST that was at some time refused validation (first time I've instantiated it, I really needed it here and its AU GUI disappeared after closing the window) and had to run its scanner. Finally everything was sorted but not the first time (and the troubles are Apple troubles (*: eg., the protect from unverified developers trip).
But I don't think Apple is all about Logic like that at all. I had Logic 8, I kept it past when I was no longer considering it as my workstation, for compatibility with video people, but really the AU scanning failures will have meant me not adapting Logic to run instruments (and the VE Pro implementation is still a no go), straight up.

jancivil · Post by **jancivil** » Sat Sep 04, 2021 3:44 pm

there are super-power VE Pro-reliant composers that use Logic nonetheless

Tj Shredder · Post by **Tj Shredder** » Wed Sep 08, 2021 3:53 pm

jancivil wrote: Tue Aug 31, 2021 5:02 pm the last time I opened Logic, it had been a while, with OS updates, and its AU scanning was distastrous, not all of it but it really put the chill on me using it, the time wasting. I had it for compatibility with video people and FCPX, not dependent on it to make anything. AU scanning is a little bit dodgy all over IME.

We have to remind devs about this completely unnecessary „technology“ to hopefully get rid of it for ever in the future…
I even created a thread about this annoyance…
viewtopic.php?f=33&t=561639

Logic Pro issue: 3rd party VIs showing disabled