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.