audacity-devel

[Audacity-devel] Windows 10, error reported running mod-script-pipe

[Steve t. F. <ste...@gm...>]

A forum user on Windows 10 has reported this error message when running
either pipeclient or pipe_test:

FileNotFoundError: [Errno 2] No such file or directory: '\\\\.\\pipe\\ToSrvPipe'

I'm not able to reproduce the error, and as far as I can tell they appear to be
doing everything right. Can anyone suggest how to diagnose the problem?

If you'd like to discus with this user directly, their user name is
Gibbz, and their original
post is here: https://forum.audacityteam.org/viewtopic.php?p=370024#p370024


Steve

Re: [Audacity-devel] Windows 10, error reported running mod-script-pipe

[Robert H. <aar...@gm...>]

Steve
I have no version with the pipe available at the moment.
was the error you got after disabling the module exactly the same (for
both programs)?
It is a bit strange that the test confirms the existence in the first place.
What's with the read-only pipe, is that available?
Robert



On 29/05/2019, Steve the Fiddle <ste...@gm...> wrote:
> A forum user on Windows 10 has reported this error message when running
> either pipeclient or pipe_test:
>
> FileNotFoundError: [Errno 2] No such file or directory:
> '\\\\.\\pipe\\ToSrvPipe'
>
> I'm not able to reproduce the error, and as far as I can tell they appear to
> be
> doing everything right. Can anyone suggest how to diagnose the problem?
>
> If you'd like to discus with this user directly, their user name is
> Gibbz, and their original
> post is here: https://forum.audacityteam.org/viewtopic.php?p=370024#p370024
>
>
> Steve
>

Re: [Audacity-devel] Windows 10, error reported running mod-script-pipe

[Steve t. F. <ste...@gm...>]

Mod-script-pipe is shipped with Audacity 2.3.2 for Windows and macOS. You
just have to enable it in Preferences > Modules.

It's not me that gets the error, it's a user on the forum.

I've been able to reproduce the problem on Linux by having more than one
version of mod-script-pipe installed at the same time (one installed for
the current user, and one installed system wide), but the forum user says
they only have one version installed. On Windows 10 I have not been able to
reproduce the problem.

The error message in both cases (pipeclient and pipe_test) says:
FileNotFoundError: [Errno 2] No such file or directory:
'\\\\.\\pipe\\ToSrvPipe'

It's not surprising that the same error message occurs, as both scripts use
the same code to open the "write" pipe.

In both cases, the error occurs when attempting to open the "write" pipe
for sending commands.
In both cases, the script attempts to open the "write" pipe before
attempting to open the "read" pipe, and the script quits before it gets to
opening the "read" pipe.

Steve

On Wed, 29 May 2019 at 16:15, Robert Hänggi <aar...@gm...> wrote:

> Steve
> I have no version with the pipe available at the moment.
> was the error you got after disabling the module exactly the same (for
> both programs)?
> It is a bit strange that the test confirms the existence in the first
> place.
> What's with the read-only pipe, is that available?
> Robert
>
>
>
> On 29/05/2019, Steve the Fiddle <ste...@gm...> wrote:
> > A forum user on Windows 10 has reported this error message when running
> > either pipeclient or pipe_test:
> >
> > FileNotFoundError: [Errno 2] No such file or directory:
> > '\\\\.\\pipe\\ToSrvPipe'
> >
> > I'm not able to reproduce the error, and as far as I can tell they
> appear to
> > be
> > doing everything right. Can anyone suggest how to diagnose the problem?
> >
> > If you'd like to discus with this user directly, their user name is
> > Gibbz, and their original
> > post is here:
> https://forum.audacityteam.org/viewtopic.php?p=370024#p370024
> >
> >
> > Steve
> >
>
>
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>

Re: [Audacity-devel] Windows 10, error reported running mod-script-pipe

[Henric J. <sof...@he...>]

Sysinternal's "PipeList" can show which pipes currently exist.
    https://docs.microsoft.com/en-us/sysinternals/downloads/pipelist

"Process Monitor" might show more details about the actual API call
returning the error (and the preceding calls).
    https://docs.microsoft.com/en-us/sysinternals/downloads/procmon

Also, sometimes those error codes can be misleading.  I don't know
if that is the case here, but take a close look at the API docs
before concluding that "No such file or directory" can only happen
if that pipe does not exist at all.


On Wed, May 29, 2019 at 09:27:36AM +0200, Robert Hänggi wrote:
> Steve
> I have no version with the pipe available at the moment.
> was the error you got after disabling the module exactly the same (for
> both programs)?
> It is a bit strange that the test confirms the existence in the first place.
> What's with the read-only pipe, is that available?
> Robert
> 
> 
> 
> On 29/05/2019, Steve the Fiddle <ste...@gm...> wrote:
> > A forum user on Windows 10 has reported this error message when running
> > either pipeclient or pipe_test:
> >
> > FileNotFoundError: [Errno 2] No such file or directory:
> > '\\\\.\\pipe\\ToSrvPipe'
> >
> > I'm not able to reproduce the error, and as far as I can tell they appear to
> > be
> > doing everything right. Can anyone suggest how to diagnose the problem?
> >
> > If you'd like to discus with this user directly, their user name is
> > Gibbz, and their original
> > post is here: https://forum.audacityteam.org/viewtopic.php?p=370024#p370024
> >
> >
> > Steve
> >
> 
> 
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel

Re: [Audacity-devel] Windows 10, error reported running mod-script-pipe

[Steve t. F. <ste...@gm...>]

On Wed, 29 May 2019 at 16:45, Henric Jungheim <sof...@he...> wrote:

>
> Sysinternal's "PipeList" can show which pipes currently exist.
>     https://docs.microsoft.com/en-us/sysinternals/downloads/pipelist
>
> "Process Monitor" might show more details about the actual API call
> returning the error (and the preceding calls).
>     https://docs.microsoft.com/en-us/sysinternals/downloads/procmon


Thanks for these two suggestions. I'll try them on my VM, then suggest them
to the forum user.


>
>
> Also, sometimes those error codes can be misleading.  I don't know
> if that is the case here, but take a close look at the API docs
> before concluding that "No such file or directory" can only happen
> if that pipe does not exist at all.
>

I suspect you're right about this.
In pipe_test.py we have:

if not os.path.exists(TONAME):
    print(" ..does not exist.  Ensure Audacity is running with
mod-script-pipe.")
    sys.exit()

and that test passes without error. It's only when the script tries to open
the pipe with:

TOFILE = open(TONAME, 'w')

that the error occurs.

I see that James has replied on the forum (thanks James), suggesting that
it  could be a security or group policy setting causing the problem
(
https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-access-restrict-anonymous-access-to-named-pipes-and-shares
)
That looks like a real possibility.

Steve



>
>
> On Wed, May 29, 2019 at 09:27:36AM +0200, Robert Hänggi wrote:
> > Steve
> > I have no version with the pipe available at the moment.
> > was the error you got after disabling the module exactly the same (for
> > both programs)?
> > It is a bit strange that the test confirms the existence in the first
> place.
> > What's with the read-only pipe, is that available?
> > Robert
> >
> >
> >
> > On 29/05/2019, Steve the Fiddle <ste...@gm...> wrote:
> > > A forum user on Windows 10 has reported this error message when running
> > > either pipeclient or pipe_test:
> > >
> > > FileNotFoundError: [Errno 2] No such file or directory:
> > > '\\\\.\\pipe\\ToSrvPipe'
> > >
> > > I'm not able to reproduce the error, and as far as I can tell they
> appear to
> > > be
> > > doing everything right. Can anyone suggest how to diagnose the problem?
> > >
> > > If you'd like to discus with this user directly, their user name is
> > > Gibbz, and their original
> > > post is here:
> https://forum.audacityteam.org/viewtopic.php?p=370024#p370024
> > >
> > >
> > > Steve
> > >
> >
> >
> > _______________________________________________
> > audacity-devel mailing list
> > aud...@li...
> > https://lists.sourceforge.net/lists/listinfo/audacity-devel
>
>
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>

Re: [Audacity-devel] Windows 10, error reported running mod-script-pipe

[Robert H. <aar...@gm...>]

Sysinternals has a lot of tools (130).
I've installed an network drive for it via live.sysinternals.com.
It is handy to have the tools available without having to locally store them.

Robert

On 29/05/2019, Steve the Fiddle <ste...@gm...> wrote:
> On Wed, 29 May 2019 at 16:45, Henric Jungheim <sof...@he...> wrote:
>
>>
>> Sysinternal's "PipeList" can show which pipes currently exist.
>>     https://docs.microsoft.com/en-us/sysinternals/downloads/pipelist
>>
>> "Process Monitor" might show more details about the actual API call
>> returning the error (and the preceding calls).
>>     https://docs.microsoft.com/en-us/sysinternals/downloads/procmon
>
>
> Thanks for these two suggestions. I'll try them on my VM, then suggest them
> to the forum user.
>
>
>>
>>
>> Also, sometimes those error codes can be misleading.  I don't know
>> if that is the case here, but take a close look at the API docs
>> before concluding that "No such file or directory" can only happen
>> if that pipe does not exist at all.
>>
>
> I suspect you're right about this.
> In pipe_test.py we have:
>
> if not os.path.exists(TONAME):
>     print(" ..does not exist.  Ensure Audacity is running with
> mod-script-pipe.")
>     sys.exit()
>
> and that test passes without error. It's only when the script tries to open
> the pipe with:
>
> TOFILE = open(TONAME, 'w')
>
> that the error occurs.
>
> I see that James has replied on the forum (thanks James), suggesting that
> it  could be a security or group policy setting causing the problem
> (
> https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-access-restrict-anonymous-access-to-named-pipes-and-shares
> )
> That looks like a real possibility.
>
> Steve
>
>
>
>>
>>
>> On Wed, May 29, 2019 at 09:27:36AM +0200, Robert Hänggi wrote:
>> > Steve
>> > I have no version with the pipe available at the moment.
>> > was the error you got after disabling the module exactly the same (for
>> > both programs)?
>> > It is a bit strange that the test confirms the existence in the first
>> place.
>> > What's with the read-only pipe, is that available?
>> > Robert
>> >
>> >
>> >
>> > On 29/05/2019, Steve the Fiddle <ste...@gm...> wrote:
>> > > A forum user on Windows 10 has reported this error message when
>> > > running
>> > > either pipeclient or pipe_test:
>> > >
>> > > FileNotFoundError: [Errno 2] No such file or directory:
>> > > '\\\\.\\pipe\\ToSrvPipe'
>> > >
>> > > I'm not able to reproduce the error, and as far as I can tell they
>> appear to
>> > > be
>> > > doing everything right. Can anyone suggest how to diagnose the
>> > > problem?
>> > >
>> > > If you'd like to discus with this user directly, their user name is
>> > > Gibbz, and their original
>> > > post is here:
>> https://forum.audacityteam.org/viewtopic.php?p=370024#p370024
>> > >
>> > >
>> > > Steve
>> > >
>> >
>> >
>> > _______________________________________________
>> > audacity-devel mailing list
>> > aud...@li...
>> > https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>
>>
>> _______________________________________________
>> audacity-devel mailing list
>> aud...@li...
>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>
>

Re: [Audacity-devel] Windows 10, error reported running mod-script-pipe

[Steve t. F. <ste...@gm...>]

Thanks Robert, that's a handy link.

Steve

On Wed, 29 May 2019 at 19:17, Robert Hänggi <aar...@gm...> wrote:

> Sysinternals has a lot of tools (130).
> I've installed an network drive for it via live.sysinternals.com.
> It is handy to have the tools available without having to locally store
> them.
>
> Robert
>
> On 29/05/2019, Steve the Fiddle <ste...@gm...> wrote:
> > On Wed, 29 May 2019 at 16:45, Henric Jungheim <sof...@he...>
> wrote:
> >
> >>
> >> Sysinternal's "PipeList" can show which pipes currently exist.
> >>     https://docs.microsoft.com/en-us/sysinternals/downloads/pipelist
> >>
> >> "Process Monitor" might show more details about the actual API call
> >> returning the error (and the preceding calls).
> >>     https://docs.microsoft.com/en-us/sysinternals/downloads/procmon
> >
> >
> > Thanks for these two suggestions. I'll try them on my VM, then suggest
> them
> > to the forum user.
> >
> >
> >>
> >>
> >> Also, sometimes those error codes can be misleading.  I don't know
> >> if that is the case here, but take a close look at the API docs
> >> before concluding that "No such file or directory" can only happen
> >> if that pipe does not exist at all.
> >>
> >
> > I suspect you're right about this.
> > In pipe_test.py we have:
> >
> > if not os.path.exists(TONAME):
> >     print(" ..does not exist.  Ensure Audacity is running with
> > mod-script-pipe.")
> >     sys.exit()
> >
> > and that test passes without error. It's only when the script tries to
> open
> > the pipe with:
> >
> > TOFILE = open(TONAME, 'w')
> >
> > that the error occurs.
> >
> > I see that James has replied on the forum (thanks James), suggesting that
> > it  could be a security or group policy setting causing the problem
> > (
> >
> https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-access-restrict-anonymous-access-to-named-pipes-and-shares
> > )
> > That looks like a real possibility.
> >
> > Steve
> >
> >
> >
> >>
> >>
> >> On Wed, May 29, 2019 at 09:27:36AM +0200, Robert Hänggi wrote:
> >> > Steve
> >> > I have no version with the pipe available at the moment.
> >> > was the error you got after disabling the module exactly the same (for
> >> > both programs)?
> >> > It is a bit strange that the test confirms the existence in the first
> >> place.
> >> > What's with the read-only pipe, is that available?
> >> > Robert
> >> >
> >> >
> >> >
> >> > On 29/05/2019, Steve the Fiddle <ste...@gm...> wrote:
> >> > > A forum user on Windows 10 has reported this error message when
> >> > > running
> >> > > either pipeclient or pipe_test:
> >> > >
> >> > > FileNotFoundError: [Errno 2] No such file or directory:
> >> > > '\\\\.\\pipe\\ToSrvPipe'
> >> > >
> >> > > I'm not able to reproduce the error, and as far as I can tell they
> >> appear to
> >> > > be
> >> > > doing everything right. Can anyone suggest how to diagnose the
> >> > > problem?
> >> > >
> >> > > If you'd like to discus with this user directly, their user name is
> >> > > Gibbz, and their original
> >> > > post is here:
> >> https://forum.audacityteam.org/viewtopic.php?p=370024#p370024
> >> > >
> >> > >
> >> > > Steve
> >> > >
> >> >
> >> >
> >> > _______________________________________________
> >> > audacity-devel mailing list
> >> > aud...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >>
> >>
> >> _______________________________________________
> >> audacity-devel mailing list
> >> aud...@li...
> >> https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >>
> >
>
>
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>

Re: [Audacity-devel] Windows 10, error reported running mod-script-pipe

[Steve t. F. <ste...@gm...>]

Update:
I tested https://live.sysinternals.com/pipelist64.exe from Robert's page
link.

When Audacity 2.3.2 is running with mod-script-pipe enabled, two items are
added to the bottom of the list produced by running pipelist64.exe in the
command prompt:

ToSrvPipe    1  1
FromSrvPipe  1 -1

When Audacity is not running, or if mod-script-pipe is disabled, these two
items are absent from the list.

Good to know there's a way to detect the pipes on Windows.

On Linux it's easier to see the pipes as they are visible as "files" in the
/tmp directory as:
/tmp/audacity_script_pipe.from.1000
/tmp/audacity_script_pipe.to.1000

Steve


On Wed, 29 May 2019 at 19:50, Steve the Fiddle <ste...@gm...>
wrote:

> Thanks Robert, that's a handy link.
>
> Steve
>
> On Wed, 29 May 2019 at 19:17, Robert Hänggi <aar...@gm...>
> wrote:
>
>> Sysinternals has a lot of tools (130).
>> I've installed an network drive for it via live.sysinternals.com.
>> It is handy to have the tools available without having to locally store
>> them.
>>
>> Robert
>>
>> On 29/05/2019, Steve the Fiddle <ste...@gm...> wrote:
>> > On Wed, 29 May 2019 at 16:45, Henric Jungheim <sof...@he...>
>> wrote:
>> >
>> >>
>> >> Sysinternal's "PipeList" can show which pipes currently exist.
>> >>     https://docs.microsoft.com/en-us/sysinternals/downloads/pipelist
>> >>
>> >> "Process Monitor" might show more details about the actual API call
>> >> returning the error (and the preceding calls).
>> >>     https://docs.microsoft.com/en-us/sysinternals/downloads/procmon
>> >
>> >
>> > Thanks for these two suggestions. I'll try them on my VM, then suggest
>> them
>> > to the forum user.
>> >
>> >
>> >>
>> >>
>> >> Also, sometimes those error codes can be misleading.  I don't know
>> >> if that is the case here, but take a close look at the API docs
>> >> before concluding that "No such file or directory" can only happen
>> >> if that pipe does not exist at all.
>> >>
>> >
>> > I suspect you're right about this.
>> > In pipe_test.py we have:
>> >
>> > if not os.path.exists(TONAME):
>> >     print(" ..does not exist.  Ensure Audacity is running with
>> > mod-script-pipe.")
>> >     sys.exit()
>> >
>> > and that test passes without error. It's only when the script tries to
>> open
>> > the pipe with:
>> >
>> > TOFILE = open(TONAME, 'w')
>> >
>> > that the error occurs.
>> >
>> > I see that James has replied on the forum (thanks James), suggesting
>> that
>> > it  could be a security or group policy setting causing the problem
>> > (
>> >
>> https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-access-restrict-anonymous-access-to-named-pipes-and-shares
>> > )
>> > That looks like a real possibility.
>> >
>> > Steve
>> >
>> >
>> >
>> >>
>> >>
>> >> On Wed, May 29, 2019 at 09:27:36AM +0200, Robert Hänggi wrote:
>> >> > Steve
>> >> > I have no version with the pipe available at the moment.
>> >> > was the error you got after disabling the module exactly the same
>> (for
>> >> > both programs)?
>> >> > It is a bit strange that the test confirms the existence in the first
>> >> place.
>> >> > What's with the read-only pipe, is that available?
>> >> > Robert
>> >> >
>> >> >
>> >> >
>> >> > On 29/05/2019, Steve the Fiddle <ste...@gm...> wrote:
>> >> > > A forum user on Windows 10 has reported this error message when
>> >> > > running
>> >> > > either pipeclient or pipe_test:
>> >> > >
>> >> > > FileNotFoundError: [Errno 2] No such file or directory:
>> >> > > '\\\\.\\pipe\\ToSrvPipe'
>> >> > >
>> >> > > I'm not able to reproduce the error, and as far as I can tell they
>> >> appear to
>> >> > > be
>> >> > > doing everything right. Can anyone suggest how to diagnose the
>> >> > > problem?
>> >> > >
>> >> > > If you'd like to discus with this user directly, their user name is
>> >> > > Gibbz, and their original
>> >> > > post is here:
>> >> https://forum.audacityteam.org/viewtopic.php?p=370024#p370024
>> >> > >
>> >> > >
>> >> > > Steve
>> >> > >
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > audacity-devel mailing list
>> >> > aud...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/audacity-devel
>> >>
>> >>
>> >> _______________________________________________
>> >> audacity-devel mailing list
>> >> aud...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>> >>
>> >
>>
>>
>> _______________________________________________
>> audacity-devel mailing list
>> aud...@li...
>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>
>

Re: [Audacity-devel] Windows 10, error reported running mod-script-pipe

[Henric J. <sof...@he...>]

On Mon, Jun 03, 2019 at 04:26:18PM +0100, Steve the Fiddle wrote:
> Update:
> I tested https://live.sysinternals.com/pipelist64.exe from Robert's page
> link.
> 
> When Audacity 2.3.2 is running with mod-script-pipe enabled, two items are
> added to the bottom of the list produced by running pipelist64.exe in the
> command prompt:
> 
> ToSrvPipe    1  1
> FromSrvPipe  1 -1

Since this is a global namespace, it might not be a bad idea to
include "Audacity" or some-such in the pipe names.  If there are
protocol versioning concerns, some kind of version identifier could
also be included.

...or would that create backwards compatibility problems?

> 
> When Audacity is not running, or if mod-script-pipe is disabled, these two
> items are absent from the list.
> 
> Good to know there's a way to detect the pipes on Windows.
> 
> On Linux it's easier to see the pipes as they are visible as "files" in the
> /tmp directory as:
> /tmp/audacity_script_pipe.from.1000
> /tmp/audacity_script_pipe.to.1000
> 
> Steve
> 
> 
> On Wed, 29 May 2019 at 19:50, Steve the Fiddle <ste...@gm...>
> wrote:
> 
> > Thanks Robert, that's a handy link.
> >
> > Steve
> >
> > On Wed, 29 May 2019 at 19:17, Robert Hänggi <aar...@gm...>
> > wrote:
> >
> >> Sysinternals has a lot of tools (130).
> >> I've installed an network drive for it via live.sysinternals.com.
> >> It is handy to have the tools available without having to locally store
> >> them.
> >>
> >> Robert
> >>
> >> On 29/05/2019, Steve the Fiddle <ste...@gm...> wrote:
> >> > On Wed, 29 May 2019 at 16:45, Henric Jungheim <sof...@he...>
> >> wrote:
> >> >
> >> >>
> >> >> Sysinternal's "PipeList" can show which pipes currently exist.
> >> >>     https://docs.microsoft.com/en-us/sysinternals/downloads/pipelist
> >> >>
> >> >> "Process Monitor" might show more details about the actual API call
> >> >> returning the error (and the preceding calls).
> >> >>     https://docs.microsoft.com/en-us/sysinternals/downloads/procmon
> >> >
> >> >
> >> > Thanks for these two suggestions. I'll try them on my VM, then suggest
> >> them
> >> > to the forum user.
> >> >
> >> >
> >> >>
> >> >>
> >> >> Also, sometimes those error codes can be misleading.  I don't know
> >> >> if that is the case here, but take a close look at the API docs
> >> >> before concluding that "No such file or directory" can only happen
> >> >> if that pipe does not exist at all.
> >> >>
> >> >
> >> > I suspect you're right about this.
> >> > In pipe_test.py we have:
> >> >
> >> > if not os.path.exists(TONAME):
> >> >     print(" ..does not exist.  Ensure Audacity is running with
> >> > mod-script-pipe.")
> >> >     sys.exit()
> >> >
> >> > and that test passes without error. It's only when the script tries to
> >> open
> >> > the pipe with:
> >> >
> >> > TOFILE = open(TONAME, 'w')
> >> >
> >> > that the error occurs.
> >> >
> >> > I see that James has replied on the forum (thanks James), suggesting
> >> that
> >> > it  could be a security or group policy setting causing the problem
> >> > (
> >> >
> >> https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-access-restrict-anonymous-access-to-named-pipes-and-shares
> >> > )
> >> > That looks like a real possibility.
> >> >
> >> > Steve
> >> >
> >> >
> >> >
> >> >>
> >> >>
> >> >> On Wed, May 29, 2019 at 09:27:36AM +0200, Robert Hänggi wrote:
> >> >> > Steve
> >> >> > I have no version with the pipe available at the moment.
> >> >> > was the error you got after disabling the module exactly the same
> >> (for
> >> >> > both programs)?
> >> >> > It is a bit strange that the test confirms the existence in the first
> >> >> place.
> >> >> > What's with the read-only pipe, is that available?
> >> >> > Robert
> >> >> >
> >> >> >
> >> >> >
> >> >> > On 29/05/2019, Steve the Fiddle <ste...@gm...> wrote:
> >> >> > > A forum user on Windows 10 has reported this error message when
> >> >> > > running
> >> >> > > either pipeclient or pipe_test:
> >> >> > >
> >> >> > > FileNotFoundError: [Errno 2] No such file or directory:
> >> >> > > '\\\\.\\pipe\\ToSrvPipe'
> >> >> > >
> >> >> > > I'm not able to reproduce the error, and as far as I can tell they
> >> >> appear to
> >> >> > > be
> >> >> > > doing everything right. Can anyone suggest how to diagnose the
> >> >> > > problem?
> >> >> > >
> >> >> > > If you'd like to discus with this user directly, their user name is
> >> >> > > Gibbz, and their original
> >> >> > > post is here:
> >> >> https://forum.audacityteam.org/viewtopic.php?p=370024#p370024
> >> >> > >
> >> >> > >
> >> >> > > Steve
> >> >> > >
> >> >> >
> >> >> >
> >> >> > _______________________________________________
> >> >> > audacity-devel mailing list
> >> >> > aud...@li...
> >> >> > https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> audacity-devel mailing list
> >> >> aud...@li...
> >> >> https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >> >>
> >> >
> >>
> >>
> >> _______________________________________________
> >> audacity-devel mailing list
> >> aud...@li...
> >> https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >>
> >


> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel

Re: [Audacity-devel] Windows 10, error reported running mod-script-pipe

[Steve t. F. <ste...@gm...>]

On Mon, 3 Jun 2019 at 16:47, Henric Jungheim <sof...@he...> wrote:

> On Mon, Jun 03, 2019 at 04:26:18PM +0100, Steve the Fiddle wrote:
> > Update:
> > I tested https://live.sysinternals.com/pipelist64.exe from Robert's page
> > link.
> >
> > When Audacity 2.3.2 is running with mod-script-pipe enabled, two items
> are
> > added to the bottom of the list produced by running pipelist64.exe in the
> > command prompt:
> >
> > ToSrvPipe    1  1
> > FromSrvPipe  1 -1
>
> Since this is a global namespace, it might not be a bad idea to
> include "Audacity" or some-such in the pipe names.  If there are
> protocol versioning concerns, some kind of version identifier could
> also be included.
>
> ...or would that create backwards compatibility problems?
>

For Python to be able to connect to the pipes, it has to know what the pipe
name is.  For example, in pipeclient.py lines 83 to 87:
# Platform specific constants
if sys.platform == 'win32':
    WRITE_NAME = '\\\\.\\pipe\\ToSrvPipe'
    READ_NAME = '\\\\.\\pipe\\FromSrvPipe'
EOL = '\r\n\0'

There's probably not many users that have written Python scripts for
Audacity, but all scripts that do exist will break if the pipe names are
changed.

The same applies to Perl scripts (and I'd expect any other scripting
language that may have been used).

Steve



>
> >
> > When Audacity is not running, or if mod-script-pipe is disabled, these
> two
> > items are absent from the list.
> >
> > Good to know there's a way to detect the pipes on Windows.
> >
> > On Linux it's easier to see the pipes as they are visible as "files" in
> the
> > /tmp directory as:
> > /tmp/audacity_script_pipe.from.1000
> > /tmp/audacity_script_pipe.to.1000
> >
> > Steve
> >
> >
> > On Wed, 29 May 2019 at 19:50, Steve the Fiddle <ste...@gm...
> >
> > wrote:
> >
> > > Thanks Robert, that's a handy link.
> > >
> > > Steve
> > >
> > > On Wed, 29 May 2019 at 19:17, Robert Hänggi <aar...@gm...>
> > > wrote:
> > >
> > >> Sysinternals has a lot of tools (130).
> > >> I've installed an network drive for it via live.sysinternals.com.
> > >> It is handy to have the tools available without having to locally
> store
> > >> them.
> > >>
> > >> Robert
> > >>
> > >> On 29/05/2019, Steve the Fiddle <ste...@gm...> wrote:
> > >> > On Wed, 29 May 2019 at 16:45, Henric Jungheim <sof...@he...>
> > >> wrote:
> > >> >
> > >> >>
> > >> >> Sysinternal's "PipeList" can show which pipes currently exist.
> > >> >>
> https://docs.microsoft.com/en-us/sysinternals/downloads/pipelist
> > >> >>
> > >> >> "Process Monitor" might show more details about the actual API call
> > >> >> returning the error (and the preceding calls).
> > >> >>
> https://docs.microsoft.com/en-us/sysinternals/downloads/procmon
> > >> >
> > >> >
> > >> > Thanks for these two suggestions. I'll try them on my VM, then
> suggest
> > >> them
> > >> > to the forum user.
> > >> >
> > >> >
> > >> >>
> > >> >>
> > >> >> Also, sometimes those error codes can be misleading.  I don't know
> > >> >> if that is the case here, but take a close look at the API docs
> > >> >> before concluding that "No such file or directory" can only happen
> > >> >> if that pipe does not exist at all.
> > >> >>
> > >> >
> > >> > I suspect you're right about this.
> > >> > In pipe_test.py we have:
> > >> >
> > >> > if not os.path.exists(TONAME):
> > >> >     print(" ..does not exist.  Ensure Audacity is running with
> > >> > mod-script-pipe.")
> > >> >     sys.exit()
> > >> >
> > >> > and that test passes without error. It's only when the script tries
> to
> > >> open
> > >> > the pipe with:
> > >> >
> > >> > TOFILE = open(TONAME, 'w')
> > >> >
> > >> > that the error occurs.
> > >> >
> > >> > I see that James has replied on the forum (thanks James), suggesting
> > >> that
> > >> > it  could be a security or group policy setting causing the problem
> > >> > (
> > >> >
> > >>
> https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-access-restrict-anonymous-access-to-named-pipes-and-shares
> > >> > )
> > >> > That looks like a real possibility.
> > >> >
> > >> > Steve
> > >> >
> > >> >
> > >> >
> > >> >>
> > >> >>
> > >> >> On Wed, May 29, 2019 at 09:27:36AM +0200, Robert Hänggi wrote:
> > >> >> > Steve
> > >> >> > I have no version with the pipe available at the moment.
> > >> >> > was the error you got after disabling the module exactly the same
> > >> (for
> > >> >> > both programs)?
> > >> >> > It is a bit strange that the test confirms the existence in the
> first
> > >> >> place.
> > >> >> > What's with the read-only pipe, is that available?
> > >> >> > Robert
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> > On 29/05/2019, Steve the Fiddle <ste...@gm...>
> wrote:
> > >> >> > > A forum user on Windows 10 has reported this error message when
> > >> >> > > running
> > >> >> > > either pipeclient or pipe_test:
> > >> >> > >
> > >> >> > > FileNotFoundError: [Errno 2] No such file or directory:
> > >> >> > > '\\\\.\\pipe\\ToSrvPipe'
> > >> >> > >
> > >> >> > > I'm not able to reproduce the error, and as far as I can tell
> they
> > >> >> appear to
> > >> >> > > be
> > >> >> > > doing everything right. Can anyone suggest how to diagnose the
> > >> >> > > problem?
> > >> >> > >
> > >> >> > > If you'd like to discus with this user directly, their user
> name is
> > >> >> > > Gibbz, and their original
> > >> >> > > post is here:
> > >> >> https://forum.audacityteam.org/viewtopic.php?p=370024#p370024
> > >> >> > >
> > >> >> > >
> > >> >> > > Steve
> > >> >> > >
> > >> >> >
> > >> >> >
> > >> >> > _______________________________________________
> > >> >> > audacity-devel mailing list
> > >> >> > aud...@li...
> > >> >> > https://lists.sourceforge.net/lists/listinfo/audacity-devel
> > >> >>
> > >> >>
> > >> >> _______________________________________________
> > >> >> audacity-devel mailing list
> > >> >> aud...@li...
> > >> >> https://lists.sourceforge.net/lists/listinfo/audacity-devel
> > >> >>
> > >> >
> > >>
> > >>
> > >> _______________________________________________
> > >> audacity-devel mailing list
> > >> aud...@li...
> > >> https://lists.sourceforge.net/lists/listinfo/audacity-devel
> > >>
> > >
>
>
> > _______________________________________________
> > audacity-devel mailing list
> > aud...@li...
> > https://lists.sourceforge.net/lists/listinfo/audacity-devel
>
>
>
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>