I’ve compiled Audacity 2.2.2 as well as mod-script-pipe.so. I’ve also run make install. For my installation, the audacity executable is located in /usr/local/bin/. I’ve tried all of the locations to copy mod-script-pipe.so to register it with no avail. When accessing the modules dialog, Audacity returns
When I execute audacity as root (i.e., sudo audacity) the module is read, but I don’t know which copy of the file is being read, nor how to fix the installation so I can run audacity as a non-priviledged user. Any tips on getting mod-script-pipe to load correctly?
and ONLY when executing Audacity as root via sudo audacity. I have successfully registered and loaded the module when executing as root. The non-privileged user can’t see the file, probably because of a permissions problem.
I don’t understand why it only works for you when running as root, so I’ve posted to the developer’s mailing list to see if anyone there has any ideas.
I’ve done some more checking and confirmed the following conditions:
The module only loads when audacity is run as root, and will load if the module is located in either:
/root/.audacity-files/modules/mod-script-pipe.so
or
/usr/local/share/audacity/modules/mod-script-pipe.so
The module will not run under the non-privileged user in any location that I have tried. I have confirmed permissions on files in all of the typical locations and am tending toward thinking it’s probably not a permissions problem.
The location in the source where the module file paths are defined is in and about:
/src/AudacityApp.cpp (1275)
I can’t see anything wrong with the code (then again, I’m not a C programmer).
At this point, I suspect that the problem is seeing/loading the module requires a process that requires elevated privileges, although I don’t know what that would be. I’m going to do some checking along these lines, but there definitely seems to be a problem, either with the configuration of my Debian system (probably) or Audacity itself (possible).
Hello,
I have a quite similar issue. I have mod-script-pipe recognized in Preferences > Modules, and enabled, but it doesn’t seem to be loaded. The pipes are not created. Though it worked the first time after installation, it did not work anymore after the computer restarts.
Are you looking in “/tmp”?
On Linux, if mod-script-pipe is enabled (as can be seen in “Edit > Preferences > Modules”, but only after restarting Audacity), then you should see two files in “/tmp”:
Yes, that is where I look for the pipes. I have this issue on two computers (Ubuntu & Linux Mint). No specific message related to mod-script-pipe in the logs. If I choose ‘ask’ for the module nothing shows up when Audacity starts.
Oh I got the thing… It’s a problem of PATH too, it does not find the module but as the first time I started audacity from the installation folder, he found it the first time and saved it in the preferences. It works again when I start audacity from the installation folder. But now I fall into the same issue as the author of the thread…
Ok I put the module in ~/.audacity-files/modules/ and now it seems to work ! (I didn’t figure out why it does not work in the same folder as plugins) thnk you
“Modules” and “Plug-ins” are different. “Plug-ins” have to go in the plug-ins path, and “modules” have to go in the modules path.
If Audacity is properly installed at:
/usr/local/share/audacity
then Audacity should be able to find files that are in: