@Peter-Senior1644

I gather you have gone to the settings in the images below? (screencaptured)

If you have not reset, try a reset and restart the app or reset then a manual attempt if you haven't done this already.

https://prnt.sc/uaf7t6

VST Path and VST RESET

https://prnt.sc/uafa0c

A user in the German language section of this forum solved this issue by adding the paths to the VSTs manually in file VstScanSetup_x64.ini in the folder AppData\Roaming\MAGIX\mm29\ inside the Users-Folder.

@Peter-Senior1644

Hi

Which 3rd party VSTs are you referring to - full names would help?

John EB
Forum Moderator

I own more than 60. Instruments include Zebra2, Absynth, SynthMaster, Helix by Audjoo, etc. I don't see why names matter as MMP 2013 and the two other DAWS I menti

oned all use the same vst file path and all of them quickly recognize all of my VST instruments and effects. I have also downloaded other DAWS to test them and they also recognize my VSTs.

A user in the German language section of this forum solved this issue by adding the paths to the VSTs manually in file VstScanSetup_x64.ini in the folder AppData\Roaming\MAGIX\mm29\ inside the Users-Folder.

Thanks. I just tried that and then quit the programme and started again but it doesn't work. I may need to do an uninstall and then install again but I'm not sure it's worth the hassle.

@Peter-Senior1644

 

I gather you have gone to the settings in the images below? (screencaptured)

If you have not reset, try a reset and restart the app or reset then a manual attempt if you haven't done this already.

https://prnt.sc/uaf7t6

 

VST Path and VST RESET

https://prnt.sc/uafa0c

 

 

 

 

Yes. I tried a reset but it was a no go. I will probably just divide work between MMP 2013 and MMP 2021. Third party VSTs are such a crucial part of music nowadays that this glitch is truly baffling.

@Peter-Senior1644

I wonder if the support can help you ? @SP. might have the right idea. SP seems to be onto it. It also works for anyone using full x64 using jbridge and manually entering the MyBridgedVST folder works fine also.

For some reason - Absynth 5 works fine on mine https://prnt.sc/uaki6a - ALSO - I found Zebra when I tried to load the 64bit version - It trashes Music Maker (see screenshot). Every time.https://prnt.sc/uakftt - @johnebaker is this a uh-e or windows or a Music Maker issue? Additionally, I notice when it crashes no matter how you close it, the application remains (in memory only) until you reboot. Task manager refuses to allow you to end the process.

My detection issue seems to be the current version of Kontakt. I renamed the older dll's to Kontakt 5.8 and the same with the Kontakt.exe some time back, so I could run either while it went through teething problems. Kontakt 6 it just does not see. Kontatkt 5.8 is detected and anything large (I have 48GB RAM) it says is too big while my CPU is barely moving and my RAM has 75% left. So there's a problem there too.

EDIT - For support - All the plugins work seamlessly in Cubase Pro 10.5 so it's not the plugins. Have your developers considered making a vst3 of Music Maker Premium so it can load inside any DAW? This removes the necessity of loading already existing plugins into Music Maker if people already have a DAW that does it and use Music Maker as a sync'd application that only loads its own plugins, Vita, etcetera.

@Andrew-Atwill

Hi

Please post screen shots and images in the forum - it is a pain having to click away from the topic to see what you are referring to.

To upload images click the above.

. . . . Zebra when I tried to load the 64bit version - It trashes Music Maker . . . . is this a uh-e or windows or a Music Maker issue? . . . .

It could be either a VST issue or a Music Maker (MMM) issue, the only 64 bit u-he VST I have works fine in MMM 2021.

Have you contact the makers of Zebra and Kontakt?

. . . . when it crashes no matter how you close it, the application remains (in memory only) until you reboot. Task manager refuses to allow you to end the process. . . . .

Task Manager, unfortunately, is not the panacea it is often assumed to be - it cannot end every process that has frozen.

John EB
Forum Moderator

@johnebaker apologies, I am so used to light shot screenshots and each forum is different...will do in future with images and save then upload instead of opening as a link.

Ok, I can give you a little more detail, Just to clarify, all the VST's and VSTi's work perfectly in Cubase Pro 10. Additionally, the Windows 10 FLS slot allocation ceiling removes plugin allocation issues it previously had with loading. Just because they all work in one program does not mean etc etc ...correct.

The most difficult aspect in determining an issue like this is that there is no plugin log to say 'Zebra failed to load at address C0001FEBC432" etc etc unless windows itself crashes. If it did, I could then match process ID's etcetera but really, nobody wants Windows to crash in the middle of an open session.

Task manager. This is the all-important one. I have applications that can unlock ANY file and any Hard disk. Music Maker does not even show up on the list of locked processes or applications. That's the cause for concern. As you might know, when you open another, it says Musicmaker is already open. I tend to cancel and reboot.

taskkill /F /im <MusicMaker.exe> fails too with Musicmaker with admin rights. So it might be an issue.

(I could be wrong, but I'm wondering if being logged in to MAGIX through the app might be refusing to let it terminate locally?)

Cheers

@Andrew-Atwill

Hi

. . . . Music Maker does not even show up on the list of locked processes or applications . . . .taskkill /F /im <MusicMaker.exe> fails too with Musicmaker with admin rights.. . . .

That would suggest that you are seeing either a 'ghost' process or the debugger itself has crashed.

I would suggest you contact Native Instruments and u-he.

John EB

Thanks for the additional comments and suggestions. I installed Music Maker Premium 2021 on my work pc and also installed the latest patch update as exists on my music pc. I experienced the identical problem: no recognition of my VST instruments and effects. I suspect this has something to do with my email address and logged in status but that is a just a guess.

I have opened a support ticket.
 

I forgot to mention that I also installed Reaper and Mixcraft Pro 8 on my work pc to compare their identification of VSTs with MMP 2021. Both identified all my VST instruments and effects immediately using the same file path as MMP 2021. This is identical to the situation/performance on my music pc. So this is definitely a Magix problem,and customers should not need to try to find work-arounds by installing via jbridge or in the user appsdata M29 folder. The VST support and Bridge product description in the store state very clearly that seamless identification of 32 and 64 bit VST instruments and effects is guaranteed. This is not the case.

@Peter-Senior1644

Hi,

I've been trying to follow this but I'm a bit lost. It's not obvious to me that you have activated, downloaded and installed everything. I get VST instruments and effects.

So, please answer the following:

1. You say that you have MMM2021 Premium. I presume that you activated this in MMM using the activation code that you received from Magix, correct?
2. And you are logged in? Your email address will appear at the upper right of the screen.
3. And you downloaded and installed everything under the Downloads button at the upper right of the Media Pool?
4. And then you went to Program Settings, Folders tab, clicked on the "Add VST plug-in path" button at the bottom and navigated to the location of your VST's, starting with either 32 or 64 bit locations and then clicking on the Add VST plug-in path button and adding each other location in turn?

John CB

Everything is activated. I specifically mentioned that "I can see Music Maker Premium 2021 "scanning for VSTs". This would be impossible if MMP2021 was not activated as VST Support and VST Bridge are included in MMP2021. I see them listed as "Acquired" among my Store items. I also stated that the same file paths which MMP2021 is set to (program settings VST folder for plug-in path) is used by MMP2013 , Reaper and Mixcraft Pro 8 to find the VST instruments and effects on both my music and work pcs which MMP2021 cannot find. I also stated that " I suspect this has something to do with my email address and logged in status". This means that I am logged in at all times with my email address when I start MMP2021.. I followed all the steps you listed (including downloading installing all soundpools, effects, Livepad, Magix instruments, etc) and additional steps suggested in reply to my post. I have been using DAWS for over a decade (including MMP since 2009) and have quite a good understanding of several different types of apps..

@Peter-Senior1644

Hi,

Good.

You have version 29.0.2.17?

Windows 10 version 1903 or 2004?

Just to confirm, you get

• No third party VST instruments showing in the Instruments tab or under the list when you press on + in the track header? See below.
• No VST FX under the Inspector tab when you select an audio object and click on the + at the bottom of the screen? See below.

Can you post screen shots of what you do see?

John CB

I received a reply from the manager of Magix support today. It has solved my problem. I had put put the plug-ins on a manually chosen path on my hard drive. As support states, there is an issue with MMP2021 in "picking up external 3rd-party VST instrument plug-ins from any location of your own choice." The location of my choice is my D drive. Support also states that " the issue with the option to manually add a VST folder of your choice will be fixed in a future update." I am happy it will be fixed in the future. I have followed their advice by putting 64 and 32 bit bit plug-ins in the paths they specify and, hoorah hoorah, my plug-ins are now recognized.

Thanks again to everyone who took the time to reply to my query. I greatly appreciate your thoughtful and kind efforts to help me.

This is the reply from support which I hope others will find as helpful as I have.
" Thank you for your message.

There is currently still an issue picking up external 3rd-party VST instrument plug-ins from any location of your own choice. You will need to place your VST instrument (i.e. the actual plug-in DLL) into one of the following default folders, depending on whether it's a 32bit or 64bit plug-in. For a 32bit one please use this:

C:\Program Files (x86)\Vstplugins\

For a 64bit plug-in, you might want to place it here:

C:\Program Files\VSTPlugins\

These are then default paths that would be used be the program and where it should be picked up automatically. This way, you would get it to show up in my instrument list and to successfully work in the program. The issue with the option to manually add a VST folder of your choice will be fixed in a future update. This will also generally entail other improvements regarding the handling of external VST plug-ins.

Alternatively, you should get the 3rd-party plug-ins to work if you add the full path to the plug-in DLL to the program's configuration file "VstScanSetup_x64.ini" for the plug-ins paths in the following location:

C:\Users\<UserName>\AppData\Roaming\MAGIX\mm29

You can edit this in a text editor (e.g. Notepad) and add a path by following the same pattern that you can see for other paths already listed in the file (i.e. prefacing each path with "ScanPath:").

I hope this helps."

@Peter-Senior1644

Thanks for telling us what happened.

I had assumed that you had placed VST plugins under the Program files and Program files (x86) which is where they normally go. I have VSTs in these normal locations and under Steinberg, but always under Program Files. That bit of information would have been useful at the outset, saved us from guessing, and we could have tried it out.

John CB

Interesting point but, as support stated, and as my three other DAWS including MMP2013 proved through their identification of the plugins which were not in the "normal locations"; where the plugins are put should not matter as long as the program settings/preferences points to the right path re their location. As support made clear they will fix the issue in an upgrade because owners of MMP2021 have the right to put the VST plugins anywhere they choose. They are not in Program files on two of my computers yet three different DAWS had no problem in recognizing all of them in the folders I placed them in.

I received a reply from the manager of Magix support today. It has solved my problem. I had put put the plug-ins on a manually chosen path on my hard drive. As support states, there is an issue with MMP2021 in "picking up external 3rd-party VST instrument plug-ins from any location of your own choice." The location of my choice is my D drive. Support also states that " the issue with the option to manually add a VST folder of your choice will be fixed in a future update." I am happy it will be fixed in the future. I have followed their advice by putting 64 and 32 bit bit plug-ins in the paths they specify and, hoorah hoorah, my plug-ins are now recognized.

Thanks again to everyone who took the time to reply to my query. I greatly appreciate your thoughtful and kind efforts to help me.

This is the reply from support which I hope others will find as helpful as I have.
" Thank you for your message.

There is currently still an issue picking up external 3rd-party VST instrument plug-ins from any location of your own choice. You will need to place your VST instrument (i.e. the actual plug-in DLL) into one of the following default folders, depending on whether it's a 32bit or 64bit plug-in. For a 32bit one please use this:

C:\Program Files (x86)\Vstplugins\

For a 64bit plug-in, you might want to place it here:

C:\Program Files\VSTPlugins\

These are then default paths that would be used be the program and where it should be picked up automatically. This way, you would get it to show up in my instrument list and to successfully work in the program. The issue with the option to manually add a VST folder of your choice will be fixed in a future update. This will also generally entail other improvements regarding the handling of external VST plug-ins.

Alternatively, you should get the 3rd-party plug-ins to work if you add the full path to the plug-in DLL to the program's configuration file "VstScanSetup_x64.ini" for the plug-ins paths in the following location:

C:\Users\<UserName>\AppData\Roaming\MAGIX\mm29

You can edit this in a text editor (e.g. Notepad) and add a path by following the same pattern that you can see for other paths already listed in the file (i.e. prefacing each path with "ScanPath:").

I hope this helps."

I edited the "VstScanSetup_x64.ini" file so there was a path to my VST's but instead of adding anything it deleted all the VST's including the bundled ones.

I re-edited the "VstScanSetup_x64.ini" back to what it was but when I opened MM there were no VST's at all. I had to download all the bundled VST's again and re-install them. I have tried to install 2 so far and they are not appearing under the instruments tab.

I'm using MM 2021 with the latest patch.

Any help would be appreciated. Thank you.

@Wistmans-Wood

Why did you do any of that?

Editing the ini files was suggested a workaround, not a normal procedure.

You say that MMM deleted your VST's? I highly doubt that. MMM does not go deleting files.

Why don't you simply use the Program Settings, Folders tab, "Add VST plug-in path" button? That is how you are supposed to do it. Make sure that you have put your third party VST's in subfolders under:

For a 32bit:

C:\Program Files (x86)\Vstplugins\

For a 64bit plug-in:

C:\Program Files\VSTPlugins\

John CB

@Wistmans-Wood

Why did you do any of that?

Editing the ini files was suggested a workaround, not a normal procedure.

You say that MMM deleted your VST's? I highly doubt that. MMM does not go deleting files.

Why don't you simply use the Program Settings, Folders tab, "Add VST plug-in path" button? That is how you are supposed to do it. Make sure that you have put your third party VST's in subfolders under:

For a 32bit:

C:\Program Files (x86)\Vstplugins\

For a 64bit plug-in:

C:\Program Files\VSTPlugins\

John CB

I tried adding the VST path from the programme settings but it didn't work hence why I tried the work around.

When I said MM deleted the bundled VST's I meant they were no longer in the instruments tab, it was empty.

@Wistmans-Wood

Do you mean third party instruments or Magix instruments are no longer under the Instruments tab?

Are you logged in to the Store?

John CB

@Wistmans-Wood

Do you mean third party instruments or Magix instruments are no longer under the Instruments tab?

Are you logged in to the Store?

John CB

The Magix instruments.