Re: [Audacity-devel] Plug-in path on Linux
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
Menu
▾
▴
Re: [Audacity-devel] Plug-in path on Linux
|
From: Steve t. F. <ste...@gm...> - 2017-05-16 18:56:18
|
On 16 May 2017 at 17:48, Gale Andrews <ga...@au...> wrote: > Yes, the Plug-Ins folder in the application data folder works on all > platforms for Nyquist, LADSPA and VST plugins. > OK, thanks. I thought it might be relevant to other platforms. > > Now that Audacity is all-in-one on Mac, that folder is essential on > Mac. Otherwise, users will have to drill down into the Contents > folder of the app to add plugins, and will lose their new plugins > when Audacity is upgraded. > > So unequivocal -1 from me to deleting it on Mac. > Good. That makes sense for Mac. > > On Ubuntu, your script for returning Nyquist plugin paths returns > undocumented paths: > > /home/gale/nyquist > /home/gale/plugins > /home/gale/plug-ins > > And I can't make ~/plug-ins see Nyquist plugins. Can you? Just tried it with Audacity 2.1.3 release build. I deleted pluginregistry, pluginsettings and audacity.cfg files first, then put a know good Nyquist Effect plug-in into ~/plug-ins and the plug-in was correctly loaded. It also worked with ~/nyquist and ~/plugins. > Are those > three folders not needless duplication (or the reverse, ~/.audacity-files > is needless duplication - and requires showing hidden folders)? > It looks like a lot of duplication to me. > > Is there a standard in Linux FHS for this? I can't see one: > http://www.pathname.com/fhs/pub/fhs-2.3.html http://www.pathname.com/fhs/pub/fhs-2.3.html#HOMEUSERHOMEDIRECTORIES Looking at other applications on my computer, the most common system is for an application to have a "dot directory", in which all of its configuration files, including application specific plug-ins, extensions, themes, filters, settings and so on are kept. For example, Gimp has a folder: ~/.gimp-2.8 in which there is: brushes/ curves/ dynamics/ ... scripts/ templates/ themes/ tmp/ tool-options/ tool-presets/ and then a bunch of plain text configuration files. Similarly Mozilla Firefox has its "extensions", profile, settings and so on in ~/.mozilla Dropbox uses ~/.dropbox Filezilla uses ~/.filezilla and so on. So for Audacity, the "standard" structure would be: ~/.audacity which would contain: "plug-ins/" (or "plugins/"), "autosave/", "chains/" and plain text configuration files. We're not going to be able to do that overnight. > > > > Steve wrote: > > It would be better would be for a "plug-in manager" to handle > > plug-in installation on all platforms). > > I don't understand that point. Does that not happen now on Linux? > That is, put the plugin somewhere then enable it in Plug-in Manager? > I mean for the Plug-in manager to "install" plug-ins in the appropriate location. Download the plug-in to your Desktop or anywhere, select it in the plug-in manager, and the plug-in manager installs it (copies it to an appropriate location and enabled it in Audacity). Steve > > > > Gale > > > On 16 May 2017 at 09:17, Steve the Fiddle <ste...@gm...> > wrote: > > > > > > On 16 May 2017 at 02:10, Gale Andrews <ga...@au...> wrote: > >> > >> On 15 May 2017 at 10:10, Steve the Fiddle <ste...@gm...> > >> wrote: > >> > This came up today on feedback@ and concerns the plug-in path on > Linux. > >> > > >> > The default path for shipped plug-ins is: > >> > usr/share/audacity/plug-ins > >> > or > >> > usr/local/share/audacity/plug-ins > >> > > >> > Both of these locations require root privileges to write to. > >> > > >> > Users may also install plug-ins in their home directory (only requires > >> > normal use privileges) as described in the Manual > >> > > >> > (http://manual.audacityteam.org/man/installing_effect_ > generator_and_analyzer_plug_ins_on_linux.html#nyquist_install > >> > and wiki > >> > (http://wiki.audacityteam.org/wiki/Download_Nyquist_Plug-ins#install) > by > >> > creating a folder: > >> > ~/.audacity-files/plug-ins > >> > > >> > So far so good... > >> > > >> > but we also have an undocumented folder in: > >> > ~/.audacity-data/Plug-Ins > >> > > >> > (note also the non-Linux-like capitalization) > >> > > >> > This seems to have been added 7+ years ago (by Richard Ash ?) > >> > > >> > wxString FileNames::PlugInDir() > >> > { > >> > return FileNames::MkDir( wxFileName( DataDir(), wxT("Plug-Ins") > >> > ).GetFullPath() ); > >> > } > >> > > >> > Does anyone know why? > >> > >> The Plug-Ins folder in Audacity's application data folder is documented > >> on: > >> > >> http://manual.audacityteam.org/man/installing_effect_ > generator_and_analyzer_plug_ins_on_linux.html#nyquist_install > > > > > > OK, I missed that, but that documentation is confusing: > > > > It says, or at least implies that ~/.audacity-files/plug-ins is read > only. > > It has incorrect capitalization for file names (very important on a case > > sensitive file system) > > It then contradicts itself and says that ~/.../Plug-Ins is read/write > > > >> > >> > >> It's the Wiki page that does not mention that folder. > >> > >> > >> > Do we actually want this? > >> > >> Does it violate anything on Linux apart from perhaps dubious > >> capitalisation? > > > > > > Needless duplication and confusion. > > Increased risk of user error, documentation errors (as seen in the > current > > user manual) and programming errors. > > Increased complexity to the search path. > > Increased complexity to the documentation > > > > Is the existence of ~/audacity-data/Plug-Ins intentional, or just the > result > > of a 'harmless' coding error? > > If intentional, what's the reason? > > > > As we saw in this forum topic: > > https://forum.audacityteam.org/viewtopic.php?f=50&t=95305 there are some > > other strange issues with the plug-in search path. > > > > Needless complication is bad for so many reasons that if this additional > > "Plug-Ins" path is "needless", then I think it should be removed. > > > > Is this DataDir() + "Plug-Ins" path relevant on any other platform, or > can > > it just be deleted? > > > > > >> > >> > >> It does have the merit of already existing in the user's own space. > > > > > > Not really a "merit" as we could just as easily create > > ~/audacity-file/plug-ins if we wanted to (though I don't see a great > need to > > do so, and it would be better would be for a "plug-in manager" to handle > > plug-in installation on all platforms). > > > > Steve > > > >> > >> > >> > >> Gale > >> > >> > >> ------------------------------------------------------------ > ------------------ > > > > > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > audacity-devel mailing list > > aud...@li... > > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
