Appreciate Some Help with Understanding Mod-Script-Pipe

Preface: I am hoping that this topic will help others as well.

mod-script-pipe clarification

I am trying to get a clearer grasp of what is going on with mod-script-pipe.
[Yes I do have the python-audacity interactions going successfully. This is just to get my understanding anchored correctly].

I assume mod-script-pipe is a code within Audacity that is implementing a [named] pipe server and exposing two pipes.

one or reading (by Audacity)

TONAME = ‘\\.\pipe\ToSrvPipe’ (from the python sample code)
which without escapes is \.\pipe\ToSrvPipe [P]

the other for sending (by audacity).
FROMNAME = ‘\\.\pipe\FromSrvPipe’ (from the python sample code)
which without escapes is \.\pipe\ToSrvPipe [Q]

The syntax of P and Q suggests that they are network end points similar to
typing \myLenovo\ on the start->run command box to see the file shares exposed from that machine.

I assume with P and Q, . [dot] means the IP address of the machine where python and audacity are running
and \pipe\ToSrvPipe is adding further path items.

I thought that P and Q would be visible via Start->Run->

or Windows File Explorer. But with both I get an access error.

_Windows cannot access \.\pipe_

Can someone correct/clarify my understanding and point me to where I am off?

Thanks Sri.


That is for Windows only.

On Linux / macOS it’s something like:


On Linux / macOS, named pipes are visible in a file browser.
For Windows, see:

Steve thanks for the prompt clarification. It is very clear now.

Thanks for the pointer, I used Windows Power Shell and I was able to see the Audacity pipes in the long list of pipes. Beautiful.


regards Sri.


Just thought it would be nice to have the pipes named distinctively audacity.

May be like,


or anything that clearly belongs to Audacity.

I assume names are hardcoded and not configurable at this time.
Would be nice to get this nicely pinned down, before the names get buried in lots of client code.

br Sri.

I assume that you mean “on Windows”.

Yes. It’s coded in /modules/mod-script-pipe/PipeServer.cpp

Perhaps a bit late for that. mod-script-pipe has been around for nearly three years, and if changed now, all existing scripts will break.