Recognizing Third Party VSTs

TRSpencer
TRSpencer Member Posts: 3 Member
edited October 2024 in Maschine

Cant get Maschine to recognize Apeshyt.dll or renamed Apeshyt.vst3 a Third Party plugin

Best Answer

  • TRSpencer
    TRSpencer Member Posts: 3 Member
    Answer ✓

    Its working fine now had to rescan plug-in folder 3-4 times!

Answers

  • LostInFoundation
    LostInFoundation Member Posts: 5,100 Expert

    Renamed? If you just manually rename to vst3, it doesn’t become a vst3

  • Kymeia
    Kymeia NKS User Library Mod Posts: 5,359 mod
    edited May 2023

    Actually - funny story. When Steinberg (who invented VST and VST3) first brought out Padshop Pro they did their usual thing of only bringing it out on Mac as a VST3 because as usual they wanted everyone to forget about VST2 and move to VST3. Which was annoying because at the time Komplete Kontrol only supported VST2 and it didn't seem it would ever support VST3. I worked out you could rename the padshop.vst3 to padshop.vst and it would actually load in Komplete Kontrol as a VST2 plugin. Even made a template and saved out NKS patches with it. Which meant basically that the VST2 and VST3 for Padshop at that time were the same thing. Must have been rather embarrassing for Steinberg because they soon fixed it so that trick didn't work but rather amusing and hugely ironic :)

  • JesterMgee
    JesterMgee Member Posts: 3,089 Expert
    edited May 2023
    https://community.native-instruments.com/discussion/comment/68434#Comment_68434

    There are some plugins which also seem to just "wrap" the VST2 plugin in a VST3 shell so it will work. I think some of the latest Korg plugins will do this, the VST2 plugin is always installed and if you delete it the VST3 does not load as it is dependant on the VST2, i've had another one do the same thing which was a pain when testing VST3 compatibility with NKS libraries because I ahve to remove the VST2 version so like you found, in some cases you can change VST3 to VST2 and it works but unlikely the other way around because VST3 has a different plugin call.

    https://community.native-instruments.com/discussion/12812/recognizing-third-party-vsts

    Are you sure you have the 64bit version installed and not the 32 bit version?

    Unlikely you can rename to vst3 and have it work. If no VST3 is supplied then it is not VST3 compatible but the 64bit should work, reinstall and check where you are installing the 64bit plugin.

  • LostInFoundation
    LostInFoundation Member Posts: 5,100 Expert
    https://community.native-instruments.com/discussion/comment/68539#Comment_68539

    I suppose you are not talking to me, since I said the same thing 😉

  • JesterMgee
    JesterMgee Member Posts: 3,089 Expert
    https://community.native-instruments.com/discussion/comment/68618#Comment_68618

    No, sorry quoted the wrong post, fixed.

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 13,848 mod

    @TRSpencer Any update?

  • TRSpencer
    TRSpencer Member Posts: 3 Member
    Answer ✓

    Its working fine now had to rescan plug-in folder 3-4 times!

This discussion has been closed.
Back To Top

Categories