MeldaProduction

mabian · Post by **mabian** » Fri Aug 17, 2012 2:29 pm

Hello,

even though I appreciate a lot the fact that your plugins are updated fairly often, I find it a little drag that, when using the full installers as updaters, they don't show as default install paths the ones used for the version already installed (I have custom folder structure for my plugins, so I never install them in the default suggested location).

Since it seems that a portable version isn't in sight, any chance to have the installers recognize an existing installation and show its path as default, thus making the whole update process much smoother?

Thank you very much,
Mario

TabSel · Post by **TabSel** » Fri Aug 17, 2012 2:44 pm

Indeed

+1

Gone soft · Post by **Gone soft** » Fri Aug 17, 2012 3:25 pm

+ another, nice if it can be done.

MeldaProduction · Post by **MeldaProduction** » Fri Aug 17, 2012 3:54 pm

Well, I'll check that out, but quite frankly this is basically one of the few things that I like about Apple - you cannot do that! I mean you may be obsessed by structure, but why cannot you just use the default C:/program files/vstplugins path?? For VST3 you don't even have a choice. I find this a really huge and unnecessary complication

... Nevermind will see...

TabSel · Post by **TabSel** » Fri Aug 17, 2012 4:10 pm

Understand fully.

However this grew as VST2 standard...

MeldaProduction · Post by **MeldaProduction** » Fri Aug 17, 2012 4:16 pm

TabSel wrote:Understand fully.

However this grew as VST2 standard...

Yes, unfortunately...

TabSel · Post by **TabSel** » Fri Aug 17, 2012 4:23 pm

It's somehow in the hands of the plugin devs more than of us customers to finally get up to speed with the vst3 standard, by "pressuring" hosting devs supporting vst3 standard, isn't it?

MeldaProduction · Post by **MeldaProduction** » Fri Aug 17, 2012 4:29 pm

Not really, it's more like in your hands pushing your host devs

. But VST3 has some other problems, though it's probably way better than VST2. The thing is, if all host devs start to integrate VST3, it would take time anyway and older projects of the customers would use VST2 anyway (there is some way for transition from VST2 to VST3, but I don't think it would work in general).

TabSel · Post by **TabSel** » Fri Aug 17, 2012 4:33 pm

However

plugin devs are easier to push implementing a remembered install paths than host devs are implementing vst3 hosting support

MeldaProduction · Post by **MeldaProduction** » Fri Aug 17, 2012 4:34 pm

Yes, that's true

mabian · Post by **mabian** » Sat Aug 18, 2012 6:33 pm

To the original question by Vojtech: I wouldn't like to use the original suggested plugins folder because many plugin installers suggest their own supposed right folder, and I use both x64 and x86 DAWs (and plugins) in an x64 OS.

So, to prevent having a unique messed up folder with mixed 64 and x86 plugins dll, I set up my own folder structure.

If you can manage to handle with little annoyance for you this I would be quite happy

- Mario

MeldaProduction · Post by **MeldaProduction** » Sun Aug 19, 2012 1:41 pm

I hope it should be possible. And the good thing is that this could mean the end of updaters

.

mabian · Post by **mabian** » Sun Aug 19, 2012 6:04 pm

Yup, that would be a win-win situation then; hope you can make it

Cheers,
Mario

MeldaProduction

KVR Audio

Full installers don't detect and suggest location of already installed plugins