using mod script pipeline on ubuntu

hello, ive used mod script pipe on windows before and it was very easy to enable (just check mod-script-pipe to enabled in the options menu and restart), i’m trying to set this up on my ubuntu laptop now but am not sure how to do it. things I read online say I need to build audacity with mod-script-pipe enabled? Do i need to download the audacity source-code from github, add mod-script-pipe, and install it that way?

Need some help please, thank you

Which version of Ubuntu do you have?
On a scale of “total novice” to “total geek”, how would you rate your abilities with computers?

oh yeah i should have included my version my bad; Ubuntu 20.04 LTS

id say im pretty experienced, if i can get directed to instructions on how to set up mod-script-pipe in ubuntu audacity i could probably figure it out. from my google searching on the topic though i dont get any official documentation on steps / commands to run, just forum posts like this.

im thinking i need to download the audacity source-code, build it with mod-script-pipe, and install this custom mod-sciprt-pipe enabled version on my ubuntu computer?

Just seems like so much more work for something that is checking a box on windows

okay so there was a very obvious documentation page i’ve been following:

I got the wxwWidgets/ folder, and I have cmake version 3.16.3 on my ubuntu command line.

but im stuck on this step:

. Generate the makefiles

  cmake -DCMAKE_BUILD_TYPE=Release ..

I am running this command in the audacity git repo I cloned, inside the build-cmake folder I made, so my filepath is:

~/Documents/project/wxWidgets/wxWidgets/buildgtx/audacity/build-cmake$ cmake -DCMAKE_BUILD_TYPE=Release ..

But running this command produces the err:

-- Check size of size_t - done
-- Check size of wchar_t
-- Check size of wchar_t - done
-- Check size of void*
-- Check size of void* - done
-- Building for 64-bit target
-- Found Python3: /usr/bin/python3.8 (found version "3.8.2") found components: Interpreter 
-- ========== Configuring wxwidgets ==========
CMake Error at /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message):
  Could NOT find wxWidgets (missing: wxWidgets_LIBRARIES
Call Stack (most recent call first):
  /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 (_FPHSA_FAILURE_MESSAGE)
  cmake-proxies/cmake-modules/FindwxWidgets.cmake:1018 (find_package_handle_standard_args)
  cmake-proxies/wxWidgets/CMakeLists.txt:21 (find_package)

-- Configuring incomplete, errors occurred!
See also "/home/martin/Documents/project/wxWidgets/wxWidgets/buildgtx/audacity/build-cmake/CMakeFiles/CMakeOutput.log".
See also "/home/martin/Documents/project/wxWidgets/wxWidgets/buildgtx/audacity/build-cmake/CMakeFiles/CMakeError.log".

Going to try and trouble shoot this some more, thanks

I’d suggest that you start over and follow these instructions:

thx i will try that. I recently tried again following a seemingly different set of isntructions on the wiki, got a little further and was able to build audacity, but couldnt launch it.

I’ve posted a reply.

thx I went over those instructions and got my build audacity to launch, when I launch it with the command “./audacity” like in the instructions it will open the audacity program. I can see the mod-script-pipe option in preferences and i set it to enabled. restarted audacity (checked that the mod-script-pipe is still enabled, then I download from githube [ ] download the file in my documents folder, and run it with sudo, but I get the error:

$ python3, running on linux or mac
Write to  "/tmp/"
 ..does not exist.  Ensure Audacity is running with mod-script-pipe.

There is another thing I need to do in order to use mod-script-pipe in ubuntu aside from the instructions here right? : [ ] I think I need to download a mod-script-pipe file, add it to my audacity build folder, then re-run the build steps, any advice on where to find goof instructions on this

Don’t use sudo.
Sudo should only be used when you need to modify the system (such as installing or updating), otherwise run everything with your normal user credentials.