Audacity Forum

oregon rub wrote:Someone

Who?

While there, I saw that there were two files in there owned by root: audacity_script_pipe.from.0 audacity_script_pipe.to.0 They would be created when you ran Audacity (with mod-script-pipe) as root. (user id for root is 0) These are not normal files, they are named fifo pipes. When you launched Aud...

Ensure that you have the version of GSnap "for 32-bit VST hosts".

I didn't figure out why it does not work in the same folder as plugins "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/aud...

I don't think the problem has anything to do with "Noise Gate".
Try applying the "Amplify" effect to the track - do you get the same error?
If no error with "Amplify", try the "Low Pass Filter" effect.

Like this?

Ixnay, If you launch Audacity and then open the Preference page for modules, does it say that the module "mod-script-pipe" is "Enabled"?

I put the quotation marks because I've had it autocorrect to an emoji before if I don't To avoid that, use the "Code" tag button (in the set of buttons above the message composing box). The "code" tags present literal characters (and preserve spaces): Audacity failed to read a f...

The pipes are not created 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": /tmp/audacity_script_pipe.from.1000 /tmp/audaci...

Thanks for the report. A crash has previously been reported on Mac and Windows when the macro includes "Export to MP3". Could you test if the crash still occurs if: You remove the "Export to MP3" step If you replace "Export to MP3" with some other export If you remove o...