8/30/2023 0 Comments Mulab factory file folderSo, removing freedom and explicitly preventing a flexible configuration does not seem to be the best choice. But that's just too much simplification, costing valuable flexibility.)ĪFAIK, it has otherwise had basically everything to do the right thing (to support portable installs). user-level state/data can still be problematic to manage, especially when shared across Windows users). confined to one fixed path (which still isn't true, BTW: e.g. can make life easier, with all the factory data folders and user stuff etc. (Mandating a single location in the VST3 specs. (Even some that don't offer a custom location still work fine after I just move them manually.) So, the nicer VST3 suppliers gently keep fixing the specs for us.Īnd so do the DAWs: the ones I use, from big to small (Ableton, FL, S1, Reaper, MuTools) have zero issues supporting arbitrary custom VST3 locations, they just work fine with whatever you configure, as expected (regardless of what the narrow-minded Steinberg specs have concocted). material, where they truly belong (in case of a robust portable setup), e.g. (For the record: basically none of my VST3s are kept in their super annoyingly hardwired default location at the system drive, but are on my portable SSD along with most of the prod. Thankfully, most VST3 projects do understand this and still allow custom destinations, where they continue to work just fine. They just overshot and now all the portable setups got out of the frying pan, into the fire. It's a really lazy "solution" in the VST specs.Īdding a standard location (again: as a mandatory default, rather than an exclusive fixed one) in itself would have been a welcome improvement. That is the dumb part (as others have said). Of course it was plagued, but not because of the lack of a mandatory central location, but because of the lack of a standard default location! VST3 fell off the other side of the horse, and instead of fixing the situation by just mandating a standard default, it actually removed all the flexibility VST2 nicely allowed (albeit kinda accidentally.) for users who actually knew what they were doing. VST2 was plagued with "I can't see my plugin that I've just installed" issues by many many users throughout the years, because different plugin vendors had different ideas about where the plugin should go. To do that, run cmd.exe as an administrator and go: Is that supposed to be hardcoded to "C:" or does %CommonProgramFiles% work if your system drive letter is something else? As a user, what you might want to do instead of building a potentially sizeable VST3 library on the system drive (which is often hurting for free space to begin with), is relocating it via symlinking. So, that's dumb and in no way the Surge team's fault. 32-bit VST3 plug-ins on 64-bit Windows: C:\Program Files (x86)\Common Files\VST3.All your VST3 plug-ins should be installed here: The VST3 format has a dedicated installation path all VST3 plug-ins must comply with. Surge being my first VST3 ever, I had to dig deeper and what I found in was: VST3 Plug-in path There's only a simple on/off toggle there. Then I found the Nightly ZIP releases and happily skipped the installer altogether only to discover my host (Renoise) specifically doesn't allow you to define a location for VST3s. By the way, thank you Surge Synth Team for all the hard work, 1.7.0 is amazing.įirst I was confused about not being able to set the installation directory. But it shouldn't take me this much work, and I'm posting this in hopes that the next time I have to install it will be smoother. I had to guess it was installed on Program Files/Common Files/VST3 (and not, say, Program Files/VstPlugins, Program Files/VST or something similar), and that took me a little while.Īll in all, happy ending, I got Surge to work, on the folder it was meant to be. Thankfully, that is definitely not a lot of work (would be much better if it was no work at all, but i'll take it), but there remained the problem that the installer didn't actually inform me where the VST3 was installed in the first place. But instead, it prompted me nothing about destination folder and just installed itself where it wanted.Īfter the initial confusion, I read on the manual that Surge has a "portable mode", and that the user had to manually do a bit of tweaking to get working. I opened the installer, hoping that at the very least, Surge would let me install it in the folder I keep the VST2 in (which is a custom folder where I keep all of my other VST in, 64-bit, 32-bit, VST2, VST3, what gives you). Now, here's my experience installing 1.7.0 (on Windows): Surge already has a portable mode, so that should not be a challenge. This should be a no brainer let the user pick installation folder when installing Surge, instead of having it install in a generic, undisclosed folder.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |