Plugindex

Help with Plugindex

Setup and fixes for every DAW Plugindex works with. Most of it is one step in Setup & connection that hasn't been done yet.

Nothing loading? Start here.

  1. Open Setup & connection… It's in the Plugindex menu, under the icon in your menu bar (Mac) or system tray (Windows). It shows one step at a time for the DAW you're in, with that DAW's name and a step count above it. Do the step on screen and the next one appears. When there is nothing left it says your DAW is connected.
  2. Quit your DAW and open it again Ableton Live, FL Studio, Cubase and Nuendo only pick up Plugindex's script when they start. If yours was open while Plugindex set up, this is usually the whole fix. Studio Pro only picks up the Plugindex device, and any new plugin, when it starts.
  3. Check for updates… Same menu. Fixes reach the app first, like the Pro Tools Track Number fix in 1.3.9.

Not it? Press your DAW above for its own steps and fixes, with the Mac permissions and the Windows loopMIDI port after them.

The Plugindex menu. Setup & connection…, Check for updates… and Send feedback… are the three items this page sends you to.

These are all the steps Setup & connection can ask for, in the app's order. It shows one at a time, and a step that is already done is not drawn at all. On a Mac it also asks to photograph your plugins until Screen Recording is on (Mac permissions), and the last step for every DAW is Build your index: press Index.

Any DAW

Mac · Windows

If it isn't working

A plugin you just installed isn't there
Your DAW has to find it first: open it and let it finish with your plugins. Ableton Live only finds new plugins when it starts, so if Live was open during the install, quit and reopen it. Then choose Check for new plugins (after installs) from the Plugindex menu.
Loads stopped on Free
Free includes 50 loads a week, and they refill every Monday. The Plugindex menu shows how many are left.
A plugin is missing or in the wrong category
Send feedback and say which one. Your plugin list comes with it, so we can fix it for everyone.

Ableton Live

Mac · Windows · Live 11 and 12

If it isn't working

Plugindex isn't in the Control Surface list
Live only builds that list when it starts. Quit Live, open it again, then choose Plugindex.
The app asks you to plug in a drive
Live keeps its User Library on that drive, and the script lives there. Plug it in, or pick a folder on this computer in Live › Settings › Library › Location of User Library. Then choose Plugindex in Control Surface again: Live empties that row when its library goes missing.
No plugins show up from Live
Live's own browser is listing none. In Live › Settings › Plug-Ins (Options › Preferences › Plug-Ins on Windows), switch on your plugin folders and press Rescan, then press the row's button in Plugindex. Live keeps a plugin list for each user account, so a new account starts empty.
Audio Units are missing (Mac)
Live finds Audio Units in the background, and it takes a few minutes. Once they show in Live's browser, press the row's button again.

In Setup & connection

  1. Install Plugindex's remote script Press Install. It goes in Live's User Library.
  2. Connect Plugindex to Ableton Live Choose Plugindex in any free row of Live › Settings › Tempo & MIDI › Control Surface. On Windows it's Options › Preferences › Link, Tempo & MIDI › Control Surface.

Logic Pro

Mac only

If it isn't working

Nothing lands on the track
Check Accessibility is still on for Plugindex. If it is, remove Plugindex from the list with the − button, add it back with + and switch it on.
Plugins land but have no picture
Check “Open plug-in window on insertion” is on, and that Screen Recording is allowed. About Mac permissions

In Setup & connection

  1. Allow Plugindex to control Logic Pro Press Grant, then switch on the row named Plugindex in System Settings › Privacy & Security › Accessibility. About Mac permissions
  2. Enable “Open plug-in window on insertion” In Logic Pro › Settings › View › Mixer, under Plug-in Window. Plugindex needs it to take each plugin's picture when it's added. Then press I enabled it.

Pro Tools

Mac · Windows in progress

If it isn't working

Loads fail with track numbers showing
With View › Track Number on, loads could miss the track. Fixed in Plugindex 1.3.9: choose Check for updates… in the Plugindex menu.
Your plugin list stays empty
Let the session finish opening, then press Try again in the row.
Plugins have no picture
Check Screen Recording is still allowed for Plugindex. About Mac permissions

In Setup & connection

  1. Allow Plugindex to control Pro Tools Press Grant, then switch on the row named Plugindex in System Settings › Privacy & Security › Accessibility.
  2. Open a session in Pro Tools Any session. Plugindex notices it and fills in your plugin list by itself, on a scratch track it takes away after. Needs Pro Tools 2025.10 or newer; on an older one, open a session with at least one track and press My session is open.
  3. Get the Plugindex package in SoundFlow's Store Optional Only on a Mac with SoundFlow installed, with Pro or during the trial. Get it opens SoundFlow's menu: choose Install apps & packages, search Plugindex, press Install. Then press any of its commands once.

FL Studio

Mac · Windows

If it isn't working

The plugin went on a different insert
Plugins go to the insert selected in FL. Click a different one there to aim.
The row says “Waiting for FL Studio to answer”
Open a new project in FL. Plugindex connects on its own.
The row says “Quit FL Studio and open it again” (Windows)
FL only finds MIDI ports when it starts, and the Plugindex port arrived after FL did. Reopen FL and Plugindex connects on its own.
The row says “Plugindex's MIDI source isn't running”
Quit and reopen Plugindex. If it keeps happening, install it again from the download page.

In Setup & connection

  1. Install the Plugindex controller script Plugindex does this itself when it starts. If the row asks, press Install. It lets Plugindex load plugins into FL.
  2. Turn Plugindex on in FL's MIDI settings Press Open MIDI settings (or F10 in FL). Pick Plugindex in the Input list, tick Enable, and set Controller type to Plugindex. Not in the lists? Press Update MIDI scripts, then Refresh device list. Or quit FL and open it again. On Windows this step asks for the loopMIDI port first: until it exists the row says Add a MIDI port named Plugindex (loopMIDI on Windows).
  3. Start Plugindex when you log in Press Turn on. FL only sees Plugindex if it's already running when FL starts.
  4. Your FL Studio plugins Plugindex fills in the list from FL's own plugin database. If FL has never been opened, open it once and let it finish, then press the row's button.

Cubase and Nuendo

Mac · Windows

If it isn't working

Cubase or Nuendo 14 or earlier
Plugindex loads into Cubase and Nuendo 15 or later. Earlier versions give other apps no way to put a plugin on a track, so your library shows but nothing loads.
Loads do nothing
Almost always the restart. Cubase and Nuendo load MIDI Remote scripts only when they start, so one that was open while Plugindex set up can't see it yet. Quit it completely and open it again. The Restart row ticks itself once your DAW has found the script.
The row says “Reopen Plugindex”
Plugindex's MIDI link isn't running right now. Quit and reopen Plugindex, then check the row again.
No Plugindex port (Windows)
Cubase and Nuendo on Windows load through the loopMIDI port. Add a loopMIDI port, and they notice it without a restart.

In Setup & connection

Nuendo works the same way as Cubase, and its rows say Nuendo where these say Cubase. On Windows the list starts with one more step, Add a MIDI port named Plugindex, until that port exists. loopMIDI on Windows

  1. Install the Plugindex script for Cubase Plugindex does this itself when it starts. If the row asks, press Install.
  2. Restart Cubase Cubase only loads scripts when it starts. Quit and reopen Cubase, and it will find Plugindex on its own. There is nothing to set up in its preferences.
  3. Your Cubase plugins Plugindex takes the list from Cubase itself. If the row asks, press its button.

Bitwig Studio

Mac · Windows

If it isn't working

You clicked “+ Plugindex” in Controllers
That row is Plugindex's MIDI port for FL Studio, Cubase and Nuendo, not the Bitwig script. Use Add Controller at the bottom of the list.
The controller row stays unticked
Press Check again in the row. It ticks as soon as Bitwig answers.
Your plugin list stays empty
Open Bitwig once and let it finish with your plugins, then press the row's button.

In Setup & connection

  1. Install the Plugindex script for Bitwig Plugindex does this itself when it starts. If the row asks, press Install. It lets Plugindex load plugins into Bitwig.
  2. Add Plugindex in Bitwig's controller settings In Bitwig: Settings › Controllers, then Add Controller at the bottom of the list. Set Hardware Vendor to Plugindex, pick Plugindex, press Add. Once; Bitwig keeps it.
  3. Your Bitwig plugins Plugindex takes the list from Bitwig's own plugin index. Bitwig doesn't need to be open.

REAPER

Mac · Windows

If it isn't working

Your plugin list stays empty
Open REAPER once, so Plugindex can pick up the plugin list REAPER already keeps. No re-scan needed in REAPER. Then press the row's button.
“REAPER couldn't find it”
REAPER is still going through your plugins. Wait for it to finish, then press Check for new plugins in Plugindex's Settings › Library.

In Setup & connection

  1. Your REAPER plugins Nothing to install and nothing to switch on. Plugindex takes the list from REAPER itself, and REAPER doesn't need to be open.

Studio Pro

Mac · Windows · Studio Pro 8

Plugindex loads into Fender Studio Pro 8, tested on 8.1.2. It does not load into Studio One 7 or earlier, or into the free Fender Studio app.

If it isn't working

Plugindex says loaded, but the effect isn't on the track
Select a track in Studio Pro first. Effects load onto the selected track, and with none selected Studio Pro does nothing. Plugindex can't see that, so it says loaded either way.
An instrument went to a new track
That is how instruments load into Studio Pro: each one gets a new instrument track, whatever is selected.
Plugindex says “Studio Pro only picks up new plugins when it starts”
Quit and reopen Studio Pro once, then press the card again. Studio Pro takes in a new plugin, and any change to the Plugindex device, only when it starts.
The row says “Set Receive From to Plugindex Studio Pro”
Studio Pro has Plugindex added but is listening to another port, or to none: on Windows a device you just added starts at None. In Studio Pro's External Devices, open Plugindex and set Receive From to Plugindex Studio Pro. Not plain Plugindex, which is the port for FL Studio, Cubase and Nuendo.
Nothing loads while a Studio Pro dialog is open
Studio Pro doesn't listen to Plugindex while one of its own windows is waiting for you: Preferences, Options or a message box. Close it and press the card again. Plugindex says so when it can see the dialog. On a Mac it can't always, and then it says loaded when nothing did.
You added the Plugindex Studio Pro port with Studio Pro open (Windows)
Studio Pro doesn't hear a port made while it was open. Quit loopMIDI and start it again, then set Receive From to Plugindex Studio Pro again.
Windows on ARM
Setup says “Studio Pro can't be reached on Windows on ARM yet”. Studio Pro's loads go through loopMIDI, which doesn't install on Windows on ARM.

In Setup & connection

  1. Get your Studio Pro plugin list Studio Pro keeps its own list of your plugins. Open Studio Pro once and let it finish, then press Add. Studio Pro can stay closed after that.
  2. Install the Plugindex device for Studio Pro A small device file that lets Plugindex load plugins into Studio Pro. Plugindex does this itself when it starts. If the row asks, press Install.
  3. Add a MIDI port named Plugindex Windows This row shows only until the port exists. It is the same port FL Studio, Cubase and Nuendo use, and the row has a Get loopMIDI button. loopMIDI on Windows
  4. Add a second MIDI port named Plugindex Studio Pro Windows In loopMIDI, type Plugindex Studio Pro in the name field, exactly like that, and press the + button. Add it before Studio Pro starts: a port added while Studio Pro is open is not heard until loopMIDI is quit and started again. Plugindex sends Studio Pro's plugins on this port, so nothing is played in FL Studio or Cubase.
  5. Restart Studio Pro Studio Pro only picks up the Plugindex device, and any new plugin, when it starts. Quit and reopen Studio Pro.
  6. Add Plugindex in Studio Pro In Studio Pro: Preferences › External Devices › Add. Choose Plugindex, then Plugindex again. Set Receive From to Plugindex Studio Pro, then OK. Each instrument gets a new instrument track. On Windows the row says Options where the Mac's says Preferences.

Build your index comes last, as for every DAW. For Studio Pro's own devices it waits for a song: “Open a new, empty song in Studio Pro. Index starts when it is open.” Plugindex adds a track for each of Studio Pro's own devices, takes a picture of its window and removes the track again, in the song that is open. Leave Studio Pro alone until Plugindex finishes: if you click one of your own tracks while it works, Plugindex can remove that track instead.

Mac permissions

Mac only · Windows asks for none

macOS asks you to allow two things in System Settings. In each list, switch on the row named Plugindex. That's the only row it needs. It may also ask once whether Plugindex can control System Events or Finder. Allow it: that is how Plugindex closes plugin pop-ups, opens FL Studio's MIDI settings and shows files in Finder.

  1. Allow Plugindex to photograph your plugins Screen Recording, for every DAW. It's how each plugin gets its picture. System Settings › Privacy & Security › Screen Recording (Screen & System Audio Recording on macOS 15 and later).
  2. Allow Plugindex to control Logic Pro The row names your own DAW, so in Pro Tools it reads Allow Plugindex to control Pro Tools. Accessibility, for Logic Pro and Pro Tools, so plugins land on the track. Ableton Live asks for it when you index your library, to close Live's own pop-ups. System Settings › Privacy & Security › Accessibility.
  3. Then quit and reopen Plugindex Screen Recording starts working the next time Plugindex starts. Accessibility works as soon as it's on.

If it isn't working

The switch is on, but Plugindex still asks, or pictures come out blank
macOS can hold on to an old permission after an update. Select Plugindex in that list, remove it with the − button, add it back with + (it's in Applications) and switch it on. For Screen Recording, quit and reopen Plugindex after; Accessibility works straight away.

loopMIDI on Windows

FL Studio · Cubase · Nuendo · Studio Pro

On Windows, FL Studio, Cubase, Nuendo and Studio Pro take their loads over a MIDI port, and Windows can't make one by itself. loopMIDI is a free app that does. The row in Setup & connection has a Get loopMIDI button.

  1. Install loopMIDI and open it
  2. Type Plugindex in the name field at the bottom and press “+” Plugindex notices the port on its own, and the row moves on.
  3. FL Studio only: quit FL and open it again FL only finds MIDI ports when it starts. Cubase and Nuendo pick the port up without a restart.
  4. Studio Pro only: add a second port named Plugindex Studio Pro Keep the Plugindex port and add this one beside it, spelled exactly like that. Add it before Studio Pro starts: a port added while Studio Pro is open is not heard until loopMIDI is quit and started again.

Keep loopMIDI open in the background. The port only exists while it runs.

Tried your DAW's steps and it still won't work? Send us your log and we'll take it from there.

Send us your log

Mac · Windows

The quickest way to get help. Choose Send feedback… from the Plugindex menu, or at the bottom of Settings. Only see Report a problem…? That's a version before 1.3.9: choose Check for updates… first.

  1. Your log comes to us What Plugindex did recently, how it's set up, and the plugins it keeps track of (names, makers and formats). Your username and computer name are taken out first.
  2. An email opens with a Feedback ID Tell us what happened and send it. The ID tells us which log is yours.
  3. No email app? The ID is copied for you. Paste it into an email to support@plugindex.app from whatever email you use.

Want to look first? Save debug log, just below it in the menu, puts the same file on your Desktop to read or attach yourself. Logs are kept privately and deleted after 90 days. Privacy policy

Email us

support@plugindex.app

Press Send feedback… in the app first (what that sends): your log comes with it, and we can usually answer in one reply. Then write, with the Feedback ID, which DAW and version, Mac or Windows, and what you pressed.

Bought Pro?
Paste the license key from your receipt email into Settings › License and press Activate.