DP 10.11 Project from macOS to Windows - Plug-in missing

[rp88.2]

Wasn't sure in which forum to put this, so I will start here.

I moved a project from macOS to Windows and when I start it up, I get the popup that says a plug-in (Tube Amp (stereo)) is missing.

Well... it isn't. I have my Mac and PC setup as identical as I can:
VST3 Primary
VST2 Secondary
All the same plug-ins on both systems.

There was no issue with the Flux, Klangheim plug-ins or Serum.
(Unfortunately, my Mac is a few thousand miles away right now and I can't see if there is a slight name difference; for what ever reason)
But for this Voxengo plug-in, I have a 'Tube Amp (stereo)' version in the plug-ins manager on the PC.

Have others noticed this with certain plug-ins when copying a project over - is there a rule of thumb to prevent this in the future?

[MIDI Life Crisis]

Is the plug missing from the sequence or from the machine entirely? IOW, an you re-select the plug to apply it or does Windows day it doesn’t exist?

[FMiguelez]

Wasn't sure in which forum to put this, so I will start here.

I moved a project from macOS to Windows and when I start it up, I get the popup that says a plug-in (Tube Amp (stereo)) is missing.

Well... it isn't. I have my Mac and PC setup as identical as I can:
VST3 Primary
VST2 Secondary
All the same plug-ins on both systems.

There was no issue with the Flux, Klangheim plug-ins or Serum.
(Unfortunately, my Mac is a few thousand miles away right now and I can't see if there is a slight name difference; for what ever reason)
But for this Voxengo plug-in, I have a 'Tube Amp (stereo)' version in the plug-ins manager on the PC.

Have others noticed this with certain plug-ins when copying a project over - is there a rule of thumb to prevent this in the future?

Can you open the missing plugins in the target machine in a new project?
Is it registered properly within DP in the preferences? I think you can force a rescan for selected plugins. Otherwise, temporarily trash the VST cache file so DP creates a new one. Does that work?

[rp88.2]

Yes, the plug-in is properly registered and I can use it in a new project. In addition, I can also insert it in the moved over project -- and it shows in the insert as 'Tube Amp (stereo)'

For whatever reason, the 'Tube Amp (stereo)' must look different between macOS and Windows -- unfortunately, I don't have my macOS machine available to see if it is a 'VST2/VST3' issue.

It is the only 3rd-party plug-in that had an issue in the moved over project.

I've already updated the tracks where the plug-in was "missing".

[CharlzS]

Is it possible that you may have selected the AU plug in your Mac session by mistake? If you didn't deselect MAS AU support in the plugin prefs that can happen.

[rp88.2]

I do not think so. The only plug-ins that are AU under macOS are two plug-ins from Black Rooster - that I am not using in this project.

FYI, MOTU confirmed the bug I filed with Black Rooster VST plug-ins under macOS - that is why they are AUs.

When I get access to my mac I will verify. Thanks for idea.