The VideoLAN Forums

Posted: **28 Jul 2009 22:41**

Hi folks,

I'm using VLC on windows to serve some streams, with a sout to a windows named pipe... something like

:sout=#transcode{vcodec=mp2v,vb=4096,acodec=mp3,ab=128,channels=2}:std{access=file,mux=ts,dst="\\.\pipe\VLC1234"}

it was working fine on VLC 0.98, but unfortunately, with the 1.01, I'm getting this issue:

access_output_file access out error: cannot open `\.\pipe\VLC1234' (No such file or directory)
stream_out_standard stream out error: no suitable sout access module for `file/ts://\.\pipe\VLC1234'

seems VLC is now adding file/ts:// by default, which fails here at some point... if someone has any help to offer :p

Posted: **16 Nov 2009 22:18**

Hahaa, is it this reason Windows pipes stop working in v1.0.x versions. I hope this is just a small quirk introduced in new source code and not bigger change in the architecture to make pipes harder to implement.

Posted: **05 Dec 2009 01:13**

ahhh.. that explains a few things.. bummer.. I gotta downgrade!

Posted: **05 Dec 2009 02:32**

could always upgrade to linux.

i keeed i keeed.

Posted: **15 Dec 2009 15:59**

Hello,

Is there a workaround to this problem ?
How can we do a sout to a windows named pipe with VLC 1.03 ?

Posted: **15 Dec 2009 16:14**

Double the antislashes, I guess.

Posted: **16 Dec 2009 17:54**

It works with \\\.\pipe\VLC1234

Thank you very much.

The VideoLAN Forums

VLC 1.01 and Windows named pipes

VLC 1.01 and Windows named pipes

Re: VLC 1.01 and Windows named pipes

Re: VLC 1.01 and Windows named pipes

Re: VLC 1.01 and Windows named pipes

Re: VLC 1.01 and Windows named pipes

Re: VLC 1.01 and Windows named pipes

Re: VLC 1.01 and Windows named pipes