"The best Installation Method" Poll
- KVRian
- 1241 posts since 17 Feb, 2010
"Automatic" or "Manual"?
"Easy and quick with a double click" or "Portability at first"?
In the passed days/weeks/months I noticed a growing interest by musicians about this aspect of pro audio software/plugins.
So, to find a way wich can make everyone happy (or almost a great part)...
Wich is for you the best "Installation Method" for Pro Audio software/plugins, after many years of your experience in music making?
"Easy and quick with a double click" or "Portability at first"?
In the passed days/weeks/months I noticed a growing interest by musicians about this aspect of pro audio software/plugins.
So, to find a way wich can make everyone happy (or almost a great part)...
Wich is for you the best "Installation Method" for Pro Audio software/plugins, after many years of your experience in music making?
- KVRian
- 1157 posts since 9 Apr, 2012
I voted for zip.
I am used to do it manually. If I have the choice between an installer and a zip I always choose zip. Btw Installers hidden inside a zip don't count.
Not because of portability but I like WISIWIG. No additional features like taskbars (pretty rare feature I agree, an example), automatic [insert favourit feature here] installation etc.
Plain copy & paste if possible, a reg file or some batch *exe thingy is cool too ... (am I oldschool?)
Btw for me copying files is more like "easy and quick without a doubleclick (and browse for directory, and set VST directory etc...)" because I already have some hotkeys for my favourite folders so it's a matter of seconds.
But that's more or less a general file operation thing maybe. I don't like "Installers" in general. But have to live with them.
And thx for the Little One BE. Bought mine today. I think I will have some serious fun with it. Nice gesture and very good choice about the limitations.
Regards
Sebastian
I am used to do it manually. If I have the choice between an installer and a zip I always choose zip. Btw Installers hidden inside a zip don't count.
Not because of portability but I like WISIWIG. No additional features like taskbars (pretty rare feature I agree, an example), automatic [insert favourit feature here] installation etc.
Plain copy & paste if possible, a reg file or some batch *exe thingy is cool too ... (am I oldschool?)
Btw for me copying files is more like "easy and quick without a doubleclick (and browse for directory, and set VST directory etc...)" because I already have some hotkeys for my favourite folders so it's a matter of seconds.
But that's more or less a general file operation thing maybe. I don't like "Installers" in general. But have to live with them.
And thx for the Little One BE. Bought mine today. I think I will have some serious fun with it. Nice gesture and very good choice about the limitations.
Regards
Sebastian
-
thecontrolcentre thecontrolcentre https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=76240
- KVRAF
- 37262 posts since 27 Jul, 2005 from Scottish Borders
- KVRAF
- 2569 posts since 4 Sep, 2006 from 127.0.0.1

It doesn't matter how it sounds..
..as long as it has BASS and it's LOUD!
irc.libera.chat >>> #kvr
..as long as it has BASS and it's LOUD!
irc.libera.chat >>> #kvr
- KVRAF
- 12194 posts since 7 Sep, 2006 from Roseville, CA
There are automatic installers that give you plenty of options (e.g., where to install the .dll, location of presets). Regardless, give me a .zip/.rar over any other option.
My biggest complaint are the installers that automatically insert a VST folder and more subfolders with the developer name, plugin name, etc. When I install a plugin in my "VST Plugins/[developer]" folder, I expect to find it there, not buried in "VST Plugins/[developer]/VST Plugins/[developer]/[plugin]"!!!

My biggest complaint are the installers that automatically insert a VST folder and more subfolders with the developer name, plugin name, etc. When I install a plugin in my "VST Plugins/[developer]" folder, I expect to find it there, not buried in "VST Plugins/[developer]/VST Plugins/[developer]/[plugin]"!!!
Last edited by cryophonik on Sat Jul 06, 2013 7:47 pm, edited 1 time in total.
Logic Pro | LUNA Pro | OB-X8 | Prophet 6 | OB-6 | Rev2 | TEO-5 | Pro 3 | SE-1X | Minitaur | Deepmind 12D | Integra-7 | TR-1000 | Analog RYTM mk2 | Digitakt 2 | TD-3 MO | TD-3 | Maschine+
-
FeelingMachine FeelingMachine https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=288002
- KVRist
- 166 posts since 16 Sep, 2012
Oh man, definitely a simple drag and drop into my plugin folder.
It makes everything easier and doesn't leave any remnants strewn across your OS.
I have a huge plugin folder on WinXP 32 bit and have done a ton of installing/un-installing. I have to stay on top of it or i start seeing issues. I can never rely on in/unstallers because they are often not thorough, even Revo uninstaller doesn't get everything in your registry.
In the end you have a registry resembling a block of cheese.
Simply dragging and dropping also makes updating a breeze and going by bad experiences, that is a big deal.
Its such a simple instruction ; locate plugin folder, drag .dll into it !!
It makes everything easier and doesn't leave any remnants strewn across your OS.
I have a huge plugin folder on WinXP 32 bit and have done a ton of installing/un-installing. I have to stay on top of it or i start seeing issues. I can never rely on in/unstallers because they are often not thorough, even Revo uninstaller doesn't get everything in your registry.
In the end you have a registry resembling a block of cheese.
Simply dragging and dropping also makes updating a breeze and going by bad experiences, that is a big deal.
Its such a simple instruction ; locate plugin folder, drag .dll into it !!
- KVRAF
- 26033 posts since 20 Oct, 2007 from gonesville
almost every installer for OSX I've used puts a plugin into the folder that is provided for it, 'components' or 'vst'; certainly VST3 is going to wind up in its folder. I would be inclined slightly more to zip and self-install if only because of the rare case an installer puts it in 'user name\audio\plugins\vst...', but it doesn't much matter to me.
now if it's a plugin with a whole application such as an NI product, I would prefer it do less.
now if it's a plugin with a whole application such as an NI product, I would prefer it do less.
-
- KVRer
- 28 posts since 29 Nov, 2011
I'm against cluttered installs, like NI ones.
CommonFiles, MyDocuments,ApplicationData...everywhere.
But once devs make a nice installer, an MSI/EXE is good enough for me.
Funnier is when (like NI) they change their paths every year...a mess.
It is NOT a matter of installer, it is a matter of consistency and cohesion
CommonFiles, MyDocuments,ApplicationData...everywhere.
But once devs make a nice installer, an MSI/EXE is good enough for me.
Funnier is when (like NI) they change their paths every year...a mess.
It is NOT a matter of installer, it is a matter of consistency and cohesion
-
- KVRAF
- 4584 posts since 21 Sep, 2005
---------------
Universal Extractor is an application destined to extract virtually any type of archive available in today's market: RAR, ZIP, 7Z, EXE, TAR, NRG, ISO, DLL, you name it; this program is able to process all of them at incredible speed.
-----------------
http://legroom.net/software/uniextract/
http://www.softpedia.com/get/Compressio ... ctor.shtml
Most excellent proggy.
Doesn't always work. Very often have to try different extraction methods or override settings. But it usually comes good. And even when it fails, you can still get an idea of the structure of things.
It works for me about 70 percent of the time, at least. And it only fails on complicated stuff. If someone has packaged up a .dll and a default directory for it in an .exe, then this will do the business no probs.
And if that fails, well all is not lost.
Just dl http://www.sandboxie.com/
Sandboxie will create a sandboxed area on your hd with the full directory structure and with all files extracted so you can see what you are dealing with. Make sure you set it up properly though. It's not difficult at all to use it in a basic way like this. You can then safely delete anything you don't like. Or anything you don't want to keep because it might be just using up space.
Say you have a totally fresh sandbox to play about with. You find the .dll installs by default to c:/program files/steinberg/vstplugins. You can then extract the files out of the sandbox and place them where you want. All of this is of course assuming that the files aren't expected to be in a certain place and extra windows registry jiggery pokery. But on the whole, I find most things can be moved without too much hassle. If not, very often programs have options or preferences that can be reset.
With Uniextract and Sandboxie there are very few programs that can't be, how can I put this, split open and scrutinised, perfectly legally. At least then you know what you are dealing with. Whether they work faultlessly or not after doing this is another matter.
But between them, I have about a 90 percent success rate. Then again, from developers I trust and know how they work their installer (i.e. Camel Audio) I don't bother. I only use this for testing or for first time installs from Devs I have no experience with.
cheers.
Universal Extractor is an application destined to extract virtually any type of archive available in today's market: RAR, ZIP, 7Z, EXE, TAR, NRG, ISO, DLL, you name it; this program is able to process all of them at incredible speed.
-----------------
http://legroom.net/software/uniextract/
http://www.softpedia.com/get/Compressio ... ctor.shtml
Most excellent proggy.
Doesn't always work. Very often have to try different extraction methods or override settings. But it usually comes good. And even when it fails, you can still get an idea of the structure of things.
It works for me about 70 percent of the time, at least. And it only fails on complicated stuff. If someone has packaged up a .dll and a default directory for it in an .exe, then this will do the business no probs.
And if that fails, well all is not lost.
Just dl http://www.sandboxie.com/
Sandboxie will create a sandboxed area on your hd with the full directory structure and with all files extracted so you can see what you are dealing with. Make sure you set it up properly though. It's not difficult at all to use it in a basic way like this. You can then safely delete anything you don't like. Or anything you don't want to keep because it might be just using up space.
Say you have a totally fresh sandbox to play about with. You find the .dll installs by default to c:/program files/steinberg/vstplugins. You can then extract the files out of the sandbox and place them where you want. All of this is of course assuming that the files aren't expected to be in a certain place and extra windows registry jiggery pokery. But on the whole, I find most things can be moved without too much hassle. If not, very often programs have options or preferences that can be reset.
With Uniextract and Sandboxie there are very few programs that can't be, how can I put this, split open and scrutinised, perfectly legally. At least then you know what you are dealing with. Whether they work faultlessly or not after doing this is another matter.
But between them, I have about a 90 percent success rate. Then again, from developers I trust and know how they work their installer (i.e. Camel Audio) I don't bother. I only use this for testing or for first time installs from Devs I have no experience with.
cheers.
-
- KVRAF
- 4584 posts since 21 Sep, 2005
gLOW-x wrote:I'm against cluttered installs, like NI ones.
CommonFiles, MyDocuments,ApplicationData...everywhere.
But once devs make a nice installer, an MSI/EXE is good enough for me.
Funnier is when (like NI) they change their paths every year...a mess.
It is NOT a matter of installer, it is a matter of consistency and cohesion
If you really want to find out how NI is 'using' your hd, then download their diagnostics program. I'm not sure if it is freely available, you might even have to ask them nicely for it, or have a friend that will pm a copy to you (if it's 'legal' of course - maybe someone can say if they know).
I had some problems recently that have still to be sorted out and I must say their diagnostics program is one of the most thorough I have come across. You could use if for other trouble shooting it is so deep.
I got a 18MB file zipped up ready to send to them (my email won't handle that at the moment) when I get the time.
But boy, do they go into some strange places. There is no nook or cranny of your hd where they don't invite themselves in without knocking. If they were a real human being, decent folk would think them rude and they would be shunned by their community.
As it is, most people don't have a clue, and they get away with it. I have very few NI products, but no more for me. Having said that, I've found their technical support to be excellent and I have a lot of respect for their programming. Just remember, they don't call them 'NATIVE' instruments for nothing.
I wouldn't attempt to use an NI installer with Uniextract. I'd have smoke not just coming out of the computer but out of the power sockets. Be Jeebus, it takes half an hour to unpack the file to install.
cheers.
- KVRian
- Topic Starter
- 1241 posts since 17 Feb, 2010
I'm not surprised to see zero votes for "option 3" so far... :)
With LittleOneBE I set that kind of 'limitations' to let anyway musicians to interact with an uncutted, full synthesis engine, so the main synthesis architecture remains the same of LittleOne (Full versions).
A lot of modulation possibilities...
Pleased to know you like it Halma :)Halma wrote: And thx for the Little One BE. Bought mine today. I think I will have some serious fun with it. Nice gesture and very good choice about the limitations.
With LittleOneBE I set that kind of 'limitations' to let anyway musicians to interact with an uncutted, full synthesis engine, so the main synthesis architecture remains the same of LittleOne (Full versions).
A lot of modulation possibilities...
- KVRAF
- 19825 posts since 16 Sep, 2001 from Las Vegas,USA
I guess it depends. For a simple synth just a zip with the .dll and patch/bank files is preferable. But if it's a complicated package that contains samples, patches, midi files etc then an installer like Camel Audio uses for Alchemy is fine with me. Better than manually moving and placing all the files hoping you put them all in the right folders and sub folders............
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
-
- KVRAF
- 1763 posts since 1 Aug, 2006 from Italy
+1Teksonik wrote:I guess it depends. For a simple synth just a zip with the .dll and patch/bank files is preferable. But if it's a complicated package that contains samples, patches, midi files etc then an installer like Camel Audio uses for Alchemy is fine with me. Better than manually moving and placing all the files hoping you put them all in the right folders and sub folders............

