Reply to thread

Message: [QUOTE="Bombastus, post: 91366, member: 2178"] Animation Station Pro can host VST3 instruments and effects inside Logic Pro while Logic itself still deals in Audio Units. The VST3 is not becoming a Logic plug-in. Logic loads Animation Station Pro first, then that plug-in loads the VST3 inside its own shell. That creates two separate places where things can go wrong. Logic has to see the Audio Unit version of Animation Station Pro, while Animation Station Pro has to find the VST3 or AU software you want to run inside it. Mixing up those two jobs is an easy way to waste half an hour rescanning the wrong thing. [HEADING=2]The VST3 stays inside Animation Station Pro[/HEADING] Once Animation Station Pro is open on a Logic instrument channel, you stop looking for the VST3 in Logic's normal plug-in menus. Run Animation Station Pro's Plug-in Manager, scan the installed formats it supports, then pick the instrument or effect from inside that interface. That is the useful part of the [B]VST3 hosting workflow inside Logic[/B]. The boundary is pretty strict. A VST3 loaded this way remains inside Animation Station Pro, so Logic sees the outer Audio Unit rather than a fresh VST3 entry of its own. Save the project, and you are saving that nested setup, not converting the hosted plug-in into something Logic suddenly understands natively. Effects work the same way. You can load a VST3 effect inside Animation Station Pro and animate its parameters with the FX Animation engine, but that effect does not appear as a normal Logic insert on every channel strip. If you bought a VST3-only processor, this gets it into the session, not into Logic's native effects browser. That is why [B][URL='https://goldmidi.com/community/threads/sample-logic-introduces-animation-station-pro.76739/']Animation Station Pro's internal plugin hosting[/URL][/B] is more than a format label. Logic is still doing what Logic normally does. Animation Station Pro is the extra host sitting between Logic and the VST3, and that middle layer is where the hosted plug-in is scanned, loaded, animated, and recalled. [HEADING=2]The two plugin managers fix different problems[/HEADING] If Animation Station Pro itself is missing from Logic, Logic's Plug-in Manager is the right place to look. Apple uses that manager to validate and manage Audio Units, so it is relevant when the outer Animation Station Pro AU has failed validation or simply does not appear where an instrument should. A missing VST3 inside Animation Station Pro is a different problem. Sample Logic tells users to run Animation Station Pro's own Plug-in Manager to scan and populate the AU and VST3 instruments and effects installed on the Mac. Resetting Logic's Audio Unit scan over and over will not magically make Logic start managing a format it does not host directly. File location can trip you up too. Steinberg defines standard VST3 locations on macOS, while Audio Unit components live in separate Components folders. A VST3 can therefore be installed somewhere a VST3 host never checks, even when another format of the same product shows up perfectly well elsewhere. The build itself still has to be right. A Windows VST3 and a Mac VST3 can share a product name, but they are not interchangeable files. If you copied a plug-in folder across from another machine instead of installing the Mac version properly, the scan may have nothing usable to load. [HEADING=2]Nested hosting does not remove compatibility limits[/HEADING] Animation Station Pro removes one format barrier. It does not erase every other requirement attached to the plug-in you are trying to run. The hosted VST3 still has its own macOS support, processor architecture, copy protection, license state, and vendor-specific quirks. That changes how you troubleshoot the setup. If Animation Station Pro is absent from Logic, fix the Audio Unit layer first. If Animation Station Pro opens normally but one VST3 is missing, stop poking at Logic and check that plug-in's install path, Mac build, authorization, and internal scan result instead. A plug-in that appears in the list but refuses to open narrows things down further. At that point, the scan has already found it, so repeatedly rebuilding the plug-in list is unlikely to solve the actual fault. Architecture support, licensing, or the plug-in's own compatibility becomes the better place to look. There is one more easy mistake. Sample Logic lists VST3 as the hosted VST format, not VST2, so an older plug-in described only as VST is not automatically covered. You need a Mac VST3 build that Animation Station Pro can actually see and load, not merely a similarly named legacy version sitting elsewhere on the drive. [/QUOTE]

Name