It would be nice to be able to apply a system-wide set of default preferences as well – for example, to set some default file paths to a dedicated, low-latency disk I’d also argue that it would be nice to be able to apply a system-wide set of default preferences as well – for example, to set some default file paths to a dedicated, low-latency disk – but that is a far more complicated feature to implement and a less pressing concern. It would be ideal if we could simply choose to disable these features by adding parameters to the installer command-line, but it would be simple enough to apply a separate LockedPrefs.ini file after installation, for example. We already have a monthly regimen of checking for, packaging, and deploying new versions of open source software such as Audacity and they’ll get the new version as long as it doesn’t violate corporate software policies. Obviously, any user can check to find the latest version, but we’re more concerned with in-application reminders that inevitably generate unnecessary help desk calls from impatient users or users ignorant of our corporate software update cadence. I am specifically concerned with builds for Windows.
By that, I mean some kind of separate configuration file that unprivileged users won’t be able to modify that would not only disable the feature in question, but either grey out or remove the option from the preferences dialogue box. Seems to be looking at plugin folder on C drive, even though running from the USB “D:” drive, in this case.įor a small selection of features, such as the new automatic check for new versions, it would be nice to be able to disable it system-wide.
(Apparently finding the 32 bit VST files in the Audacity folder on the C: drive.) When setting up on a computer that didn’t have Audacity already installed on the C: drive, it went okay…īUT, with trying to set it up, or to use it on a computer that has “Audacity 3.0.2 32 bit” already installed, it comes up with MANY dialog boxes (each one needing to be dismissed), saying “Attempting to initiate the following effect failed”, etc. Extracted the 64 bit zip file, and set up a “Portable Settings” folder at the root of the USB drive. I tried using the “Portable Settings” on a USB SSD drive.
If you’re not sure what you’re doing, then best to stick with one version: 64-bit Audacity on 64-bit Windows, otherwise 32-bit Audacity. In my opinion, it would be much better to use the ZIP versions rather than installing. You should also use a “Portable Settings” folder for one or both versions, so that 32-bit plug-in settings are separate from 64-bit plug-in settings.
0 kommentar(er)
