Today I tried to load a project containing Archetype Nolly. I got a message saying that Logic Pro had failed to load the audio unit “ArchetypeN”, and that i should contact teh manufacturer or update the plugin. there is no new update for the plugin on the site. I rescanned the plugin ansd this was the resyult.
validating Audio Unit Archetype Nolly by Neural DSP:
AU Validation Tool
Version: 1.7.0
Copyright 2003-2019, Apple Inc. All Rights Reserved.
Specify -h (-help) for command options
Hey So I opened iLok and it prompted me for an update. I completed the update, and now it is saying this. Before i wrote the initial post, I downloaded the Nolly installer and ran it again, assuming it would replace my old files. Could this be the issue?
I am also running into this issue The plug-in named “Archetype N” isn’t available on your system. for all of my logic sessions that I used Archetype Nolly v1 in prior to upgrading.
I have a bunch of different sessions previously tracked with Nolly version 1. When I open those sessions, Logic prompts me with that error. When I click ok, the session finishes to load, but my guitar tracks look like this with an orange circle in the middle of it. When you play the track, all you hear is the DI signal.
I can however instantiate a new Archetype Nolly version 2 on a track that has a disabled Archetype Nolly v1 instance on it. It shows up as normal in Plugin Manager as version 2. However, upgrading to version 2 essentially has wiped out all of my guitar tracks in most of my sessions which I am really sad about (an album, and a bunch of singles and demos). If I knew that would have happened, I probably would have just stayed on version 1.
I updated my iLok as well and have rescanned Plugin Manager many times, and this had no effect.
I am curious if those old instances are pointing to AU/Component 1.0.1 files. If that is the case, are there any download links for Nolly v1.0.1? That way I can uninstall 2.0.0, recover the sessions, backup the presets, install 2.0.0 again, and then have the converted 2.0.0 versions of the presets.
The issue you’re encountering happens because the new version gets recognized as a new plugin due to all the new features. This is exclusive to the AU format (all the other formats should work as expected).