MuTools

liquidsound · Post by **liquidsound** » Tue Jul 28, 2009 9:13 pm

I have the latest beta of the great Helix synth. It works beautiful in MuLab as usual. Now here is the thing:

I downloaded the Real deal Demo and it works fine: new sounds, new GUI etc.
The Real has the same name as the beta.

I could not load the Beta anymore because for some reason MuLab would choose the Real no matter if I browse my self to it and hand picked.

So I deleted the Real Demo from the hard drive and empty the trash.
It still appear in MuLab

and the Beta is not coming up.
Is not even in the VST folder!!!

When I finally deleted both dll from within the VST Plugin Manager and rescan than I got the Beta back.

How is it possible? Is MuLab loading the VST in a internal file?
I can't get it

anubis2010 · Post by **anubis2010** » Wed Jul 29, 2009 8:40 am

Hi liquidsound,

I am a master at "missing the point", "getting the wrong end of the stick". If the olympics had a medal for this I would hold many Golds.

Anyway this may help or only prove the above, either way I cannot loose, I help you (great) or I get Gold in 2012.

MU.LAB seems to use an internal database engine and references/stores data in a file called "VstPlugins.Xml". In a sub folder of MULAB..../Settings

When you manually delete a dll from the harddisk it is still listed in the "xml" file.

Using the Vst plugin manager to delete the reference is the way to go. But when you rescan it will look at your vst folder etc and ammend the "xml" file.

If you ever wanted to start from scratch copy the "xml" file elsewhere and use the VST Plugin manager to rescan fresh.

You seem to be a clever chap, the above may lead you in the right direction.

Hope this helps.

anubis2010

liquidsound · Post by **liquidsound** » Wed Jul 29, 2009 1:24 pm

Sure that's the way to go but if you drill down to one of the point I made you'll noticed a impossible behavior:
A list of plugins is just a list, not the plugins themselves. So if the plugin has been deleted from the hard drive how in heaven is MuLab able to load it and play with it? Is that means that it is stored in the xml file? I am not an expert in xml but I doubt it very much.

Hei, you never know. I hope Jo has an explanation. I am very curious.

anubis2010 · Post by **anubis2010** » Wed Jul 29, 2009 3:20 pm

Hi liquidsound,

The "xml" file is just a text file and can be opened in notepad/wordpad.

So the VST is not actually in the "xml" file.

Probably leave this one for Jo.

anubis2010

liquidsound · Post by **liquidsound** » Wed Jul 29, 2009 3:30 pm

I think he's busy with v2.999

MuTools · Post by **MuTools** » Sun Aug 02, 2009 10:17 am

MU.LAB indeed uses Vstplugins.Xml to store basic info about vst plugs.

Uninstalling/deleting a VST from the HD does not automatically remove it from Vstplugins.Xml. You have to remove it manually via the Vst Plugin Manager. (or by editing Vstplugins.Xml)

I cannot see how MU.LAB (or any other host) could load a plug that has been uninstalled/deleted. Are you sure that's what happened?

liquidsound · Post by **liquidsound** » Sun Aug 02, 2009 7:42 pm

Yep.
Unless audjoo is doing something to attach their Beta version. Infact once you install the Demo your beta is suppressed. I know they regret having given such a good beta out. It is almost a complete project

Thank you for answering the Xml puzzle. Still is a mystery.

MuTools

KVR Audio

Unusual result