[FFmpeg-trac] #986(avutil:new): windows named pipe seek

FFmpeg trac at avcodec.org
Thu Feb 9 14:20:06 CET 2012

#986: windows named pipe seek
             Reporter:  setosha      |                    Owner:  michael
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:  avutil
              Version:  unspecified  |               Resolution:
             Keywords:  windows      |               Blocked By:
  named pipe seek                    |  Reproduced by developer:  0
             Blocking:               |
Analyzed by developer:  0            |

Comment (by setosha):

 Replying to [comment:4 compn]:
 > is it possible to create a named pipe just using the command prompt? or
 do you have to use some kind of program? a lot of people have been asking
 how to do named pipes on windows. it will help a lot of people if you
 share the secret or easy way to do it ;)
 I don't know way to crate it from cmd.exe but seems it possible from
 PowerShell using c#. I'm create pipes from my program.
 [http://qt.nokia.com Qt] implements {{{QLocalServer}}} trough named pipes.
 Win API-way [http://msdn.microsoft.com/en-
 us/library/windows/desktop/aa365780(v=vs.85).aspx here].

 It's not unix pipes and not usual files. Here server side creates pipe and
 listen for incoming connections. So every client, opens different
 connection to pipe. So server can tranfer different data to every
 connection trough same pipe.

 Also pipe can be unnamed. It creates once. And you got two HANDLEs for
 May be exist some way to create unnamed pipe and give handles to

 > anyways, to your question, i think the problem is that most indexes are
 at the end of the file. so ffmpeg tries to seek to the end to get the

 It's bugtracker here :) I think it's a bug.

 > mplayer has -noidx option, i dont think ffmpeg has such ability yet?

 It's not just index. pipe means that stream not support seek operations.
 And can't be open twice.

Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/986#comment:6>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list