Reply to thread

Message: [QUOTE="Bombastus, post: 92321, member: 2178"] AutoTune Go can install through FL Cloud and still appear with an Error status when FL Studio scans the plugin. The two stages are separate enough that a completed download does not prove FL Studio has verified the effect correctly. If you installed [B][URL='https://goldmidi.com/community/threads/image-line-and-antares-have-added-autotune-go-to-fl-studio.77657/']AutoTune Go inside FL Studio[/URL][/B] through FL Cloud, and the scan failed afterward, resist the urge to uninstall everything first. Image-Line has already documented a real AutoTune Go case where the plugin installed, showed an error during scanning, and worked after the user went back through FL Studio's Plugin Manager. FL Cloud plugins normally add themselves to the Plugin Database after installation, complete with their normal access points. For AutoTune Go, manually inventing new VST search folders should therefore be a later move, not your first reaction to a fresh scan error. [HEADING=2]The error state starts after installation, not before[/HEADING] FL Cloud handles the package installation, while FL Studio still has to recognize and classify what it has been given. A scan failure can therefore mean the files exist but FL Studio has not accepted the plugin cleanly into its own database. Open Options, then Manage Plugins, and search for AutoTune Go before changing anything else. If the entry is present with Error instead of OK, you already know more than a reinstall would tell you because FL Studio can see something at the expected stage of discovery. Image-Line's current guidance for plugins showing Error starts with the plugin type. Select the problem entry, open its Plugin tab, and check whether the type is Unknown rather than Effect. AutoTune Go processes incoming audio, so Effect is the appropriate classification, and applying that change can clear a bad database state without touching the installation itself. The distinction matters because AutoTune is fundamentally an audio-processing effect rather than a sound generator. Antares' older [B][URL='https://patents.google.com/patent/US5973252A/en']pitch-detection and intonation-correction design[/URL][/B] describes detecting the pitch of incoming voice or instrument audio and shifting it toward a target pitch, which is the processing role FL Studio is trying to classify. [HEADING=2]FL Studio's Plugin Manager is the real repair point[/HEADING] A normal scan is not always enough once FL Studio has already marked a plugin as problematic. Enable Verify plugins along with the options to rescan previously verified plugins and rescan plugins with errors, then run Find Installed Plugins again. Verify plugins does more than make the list look tidy. FL Studio uses verification to collect identifying information and classify software as an effect or generator, while a fast scan does less checking. A plugin that was installed correctly but recorded badly in the database needs the deeper pass, not another identical quick scan. AutoTune Go has an extra advantage because it arrives through the FL Cloud plugin system. The FL Cloud application exposes a Repair state for installed products when installation problems are detected, so use Repair before hunting through random system folders or deleting plugin files by hand. Keep the order narrow. Check the AutoTune Go entry, correct an Unknown type if present, run a verified rescan that includes failed entries, then use FL Cloud Repair if the package itself still looks suspect. Changing several plugin paths, reinstalling FL Studio, and deleting databases at once only destroys the clues that tell you which layer actually failed. If AutoTune Go is missing completely rather than listed with Error, the diagnosis changes slightly. Confirm FL Cloud still shows the product as installed, then run the verified scan and look under the installed effects area afterward. FL Cloud plugins are supposed to populate the Plugin Database automatically, so absence from both places points more strongly toward installation or database trouble. [HEADING=2]Apple Silicon adds one separate failure path[/HEADING] Mac users on Apple Silicon have one extra variable because FL Studio can run natively or through Rosetta 2. Image-Line notes that plugin scans are maintained per runtime mode, so changing between Apple Silicon and Rosetta can require another scan even when the plugin is already on disk. Image-Line also currently documents a Plugin Manager issue affecting some Apple Silicon users on FL Studio 26.1.3 and earlier when Rosetta is not installed. Its workaround involves installing Rosetta, returning FL Studio to the intended runtime mode, then rescanning with Verify plugins and both rescan options enabled. Once AutoTune Go appears as an Effect and loads from an insert slot, stop troubleshooting. Leave previously verified and error rescanning disabled for routine future scans unless you need them again, because repeatedly forcing FL Studio to revisit known entries adds work without fixing anything new. [/QUOTE]

Name