Trouble installing third party VST instruments.

exstarsis wrote on 3/26/2017, 2:03 PM

Hi there. I just picked up Music Maker Premium (2017?). I'm running Windows 10. I found some interesting virtual instruments from Alan Vista (http://www.alanvista.com/marimbaphonic/) and I downloaded them. After looking around at the Magix blog and this forum, I put them in a directory and pointed Music Maker at said directory in the settings (and using the 'add new instrument' dialog, too.) The instrument window refreshes, but my new instruments don't show up. I have a couple questions:

1.) Are there limitations on where I can put them? I chose an existing Music Maker directory that seemed to also contain the included Magix instruments. (C:\Users\Public\Documents\MAGIX\Common\MxSynth)

2.) The download from Alan Vista unzipped into a format I'm unfamiliar with (I'm brand new to music software). I'm wondering if I need to arrange it differently. For examble: BellsEbuth unzipped into

BellsEbuth_x64 (folder)
- BellsEbuth.dll
- BellsEbuth.instrument (folder)
  - BellsEbuth.mse

I've both left the BellsEbuth folder as it is in the MxSynth directory, and extracted the BellsEbuth.dll so it's in the MxSynth directory. None of this seems to make the new instruments appear. Any advice is appreciated.

Comments

johnebaker wrote on 3/26/2017, 4:05 PM

. . . . BellsEbuth_x64 . . .

This suggests you downloaded the 64 bit version of the VST - you need the 32 bit version - Music Maker is 32 bit and will not recognise 64 bit VST's.

My VST dll's and the MSE (or SEM) folders are arranged as shown below

I created a VST folder in C:\ProgramData\MAGIX\Common\ and then placed third party VST's in this and added the filepath to Music Maker, this way they are easily backed up and kept separate from the MMM synths and VST's

Note the VST's I have require the sub folder to be the same name as the DLL, you may have to use the original foldername, if this does not work change the folder name as stated in the image above.

HTH

John EB

exstarsis wrote on 3/26/2017, 6:00 PM

I knew it had to be something basic like that. Using the 32 bit instruments worked perfectly. Thanks so much for the swift reply.

hazencruz wrote on 2/7/2018, 8:48 AM

I've got the 32 bit version and put it in the same folder as the other VST plugins and instruments and magix still won't find it.

hazencruz wrote on 2/7/2018, 8:56 AM

Nevermind, apparently just moving it another folder, and then scanning that folder, is what Magix wanted?

TatoPotato wrote on 2/10/2018, 3:08 PM

I created a VST folder in C:\ProgramData\MAGIX\Common\ and then placed third party VST's in this and added the filepath to Music Maker, this way they are easily backed up and kept separate from the MMM synths and VST's

How did you add the filepath? Just asking.

johnebaker wrote on 2/10/2018, 6:34 PM

. . . . How did you add the filepath? . . . .

Open the program settings dialog (P key), Folders tab - the option - Add VST plug-in path - is near the bottom of the Folders pane.

HTH

John EB

TatoPotato wrote on 2/10/2018, 8:02 PM

For me there is only

Projects
Imports
Exports
Recordings
Soundpools

Is there a reason for this or am I just making a stupid mistake?

johnebaker wrote on 2/11/2018, 5:38 AM

If you are using the free version of Music Maker then it does not have the option to add in extra VST paths.

However you can try dropping the VST files into the following location

C:\Program Files (x86)\Common Files\MAGIX Services\MxSynth

Follow the folder structure in the above location - note depending on the VST you want to install, there may be required extra folder structures, naming conventions and support files needed.

HTH

John EB

Larry98 wrote on 2/11/2018, 6:27 AM

You have to unlock the vst function using the included coupons in the plus or premium version or by using a older serial number (MX-2017).
You can also buy it seperately on the store for 9,99€.

TatoPotato wrote on 2/11/2018, 1:33 PM

That makes sense.

RendCycle wrote on 3/20/2018, 1:45 AM

Just doing some more research. Is there a plug-in available that will enable importing of 64-bit VSTs (from third-party or from Magix) in Music Maker versions bought from this website or from Steam?

emmrecs wrote on 3/20/2018, 5:12 AM

@RendCycle

There is only one utility that I am aware of that might allow the use of 64 bit VSTs or VSTis in Music Maker. It is jBridge. I say "might" because I haven't yet tested it in MM but it certainly works in other audio software to allow 32 bit VSTs in 64 bit apps and vice versa.

HTH

Jeff

RendCycle wrote on 3/20/2018, 9:57 AM

@RendCycle

There is only one utility that I am aware of that might allow the use of 64 bit VSTs or VSTis in Music Maker. It is jBridge. I say "might" because I haven't yet tested it in MM but it certainly works in other audio software to allow 32 bit VSTs in 64 bit apps and vice versa.

HTH

Jeff

Ok, will check that plugin when I reach that requirement. It's good to know that it might be possible. Thank you!

emmrecs wrote on 3/20/2018, 10:04 AM

@RendCycle

Just to avoid any confusion, jBridge is an app rather than a plug-in.

Nobody-None wrote on 3/20/2018, 12:07 PM

@Larry98

You can also buy it seperately on the store for 9,99€.

If you are talking about the Creative Suite function available from the in-app store, so you should know that this element is highly incompatible with some VSTi, for example, those from SONiVOX. It's a pity that I discover this detail AFTER purchasing this element... 😑

johncarlo-flores wrote on 12/15/2018, 2:19 AM

How do i install third party vst for audio effect such as gsnap for autotune or such like vst

emmrecs wrote on 12/15/2018, 3:21 AM

Hi, welcome to the Magix forums.

First, please read this post; we really do need to know a lot more about your computer, the version and variant of MM you have and what you have already tried.

The very simple answer to your question is, assuming you have a variant of MM that allows you to do this, you need to point the program to the folder where the VSTs are stored; but, as hinted, there are other things to consider, which is why we need that additional information from you.

Jeff