[FFmpeg-trac] #7316(undetermined:new): Windows named pipe output prompts to overwrite

FFmpeg trac at avcodec.org
Sun Jul 15 15:54:50 EEST 2018

#7316: Windows named pipe output prompts to overwrite
             Reporter:  Thw0rted     |                     Type:  defect
               Status:  new          |                 Priority:  normal
            Component:               |                  Version:  3.4
  undetermined                       |               Blocked By:
             Keywords:  named-pipe,  |  Reproduced by developer:  0
  Windows                            |
             Blocking:               |
Analyzed by developer:  0            |
 Summary of the bug: Using Named Pipe syntax on Windows results in an
 interactive prompt to overwrite the target file.  Named pipes aren't
 really files, they're more like a listening server socket, so this prompt
 makes no sense.

 How to reproduce: First, listen to a new named pipe.  This is outside the
 scope of this issue, but [https://stackoverflow.com/a/32172145/26286 this
 StackOverflow answer] shows how to listen via NodeJS, for example.  Say
 your pipe is {{{\\.\pipe\SomePipeName}}}, the relevant command would be
 % ffmpeg -i infile.ts -codec copy -f data "\\.\pipe\SomePipeName"
 ffmpeg version 3.4 Copyright (c) 2000-2017 the FFmpeg developers
   built with gcc 7.2.0 (GCC)
 File '\\.\pipe\SomePipeName' already exists. Overwrite ? [y/N]

 This **isn't an error condition and shouldn't result in any kind of
 prompt**. If nobody is listening on that pipe name, which is in fact an
 error, the message is instead "no such file or directory".  This sort of
 makes sense but it would be more accurate to say that the pipe couldn't

Ticket URL: <https://trac.ffmpeg.org/ticket/7316>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list