Analog Lab v. 5.12 Not Compatible With Logic Pro?

Software Instruments Analog Lab
#1

Not sure what has happened, but Analog Lab Pro suddenly has become non-compatible with Logic Pro 11? I am mid-project and have lost several instruments I was using for a client as after updating to version 5.12 of Analog Lab Pro, I got an error message within Logic Pro 11 that is telling me its not compatible. I reinstalled, restarted, all the usual things, and went inside the Logic Pro audio unit folders and its right there stating it’s not compatible. Does Arturia know about this? I did submit a ticket to Arturia. Has anyone else had this issue or have a work-around?

1 Like
#2

Hi @PunkPump,

That’s not good.
I don’t use Logic or MAC.
You can always download previous versions of Arturias software here - click Show Archives:
https://www.arturia.com/support/downloads-manuals

Then you can finish your project.

#3

Hi,

Try launching the Arturia Software Center before loading up Logic. See if that prompts the licensing system. Otherwise, hang tight and I’m sure the support team can investigate that one for you.

#4

I’m having a similar problem. I’m on Logic 11.2.2. I installed the update via Arturia Software Center. I then uninstalled and tried again. I then uninstalled and try to install with the download (so outside of Arturia Software Center).

Every time, I would get an alert from Logic:

“The plug-in named “Analog Lab” isn’t available on your system. Choose another plug-in, or quit Logic Pro and install the plug-in on your Mac Studio in order to use it in the project.”

EDIT: It did install the standalone version, but the plugin for Logic is not being recognized as valid.

2 Likes
#5

Someone from Arturia Support reached out and had me do the reset within Logic and it fixed the plug.

1 Like
#6

Thanks for letting us know @comfortstarr.

#7

Arturia finally replied to me as well. They made the same recommendation. I had been able to locate the answer to the situation somewhere online (honestly I forget where… it may have even been on YouTube, but I was scouring everywhere for a solution, and I should have kept better track of what was most helpful).

At the end of the day, yes, doing a full scan of plug-in’s inside of Logic Pro (plug in reset) and then reloading LogicPro did seem to correct the issue for me as well. Arturia did ultimately also provide this same solution… so Arturia support DID in fact provide the correct fix.

I never ran into this type of problem, so this was uncharted waters for me lol

1 Like