![]() Expecting people to have ongoing success with installation is unnecessarily aggravating. I agree that it ought to either be ‘repaired’ to its previous mechanic, or the feature for additional directories ought to be added. on top of Live only allowing a single directory for plugins. and it’s already a very sensitive work area. If they’re all installed in the same place……. Having a pool of all the shortcuts made it really easy also to troubleshoot problematic plugins. Simply moving files afterwards is definitely something I’ve learned not to tamper with unless the plug-in itself is very simple. So then the next plug-in from that brand, perhaps I’ll put it into that folder… but now it’ll make a folder inside that folder. But some companies have some weird ways of installing things where you end up having to go back and re-install if you’re not realizing certain characteristics.Ī big example for me is how some companies might install an entire folder that the plug-in will be nested inside of. It wouldn’t be so bad if plugins were more simple and consistent with installation. Makes things so much cleaner and easier to manage. If you forget, most cases you can simply move the plug-in or just reinstall it correctly. it is simple, you created a directory (in the root), with shortcuts (is that the english terms) to the directories that contain the VST2 versions of the. to use multiple VST2 plugin directories, within one VST 2 custom folder does not work anymore. It’s simple to do and to change the path in each installer. Ableton 11.1 is here and the VST2 workaround, i.e. I don’t understand why people don’t simply install all their plugins to a common folder. Symlinks do work, if someone want to do that, less space and less maintenance.īut as always, whay you are used to, and like, or simply used to. well it isn't a problem for cubase, bitwig, reaper, maschine, reason, etc.Īnd it wasn't a problem for ableton. Why i have 4 vst2 plugin directories? could at least be 2 or even 1. ![]() It is indeed a way to copy all, or there are different solutions, dragging with dll's. as everyone said.Īnd i believe, but i am not a DSP programmer, the VST3 sdk, or JUCE, can still complile VST2? the support, or new licenses for VST2 didn't also kill VST2. Over 2 years, indeed, but there will still be a few VST2 left, i think, most i have will be VST3, or recently has VST3 versions. Additional consumption of drive space and more maintenance work if these VST2 are updated. I've copied the VST2s into Ableton's VST2 folder.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |