[FFmpeg-devel] ffmpeg and streams
nicolas.george at normalesup.org
Wed Mar 30 22:45:46 CEST 2011
Le decadi 10 germinal, an CCXIX, Laurent Goderre a écrit :
> First of all, ffmpeg works great as is and I do not want to modify its
> inner working. That being said, the tool's main function: av_transcode
> relies heavily on file input. This has been a problem for me because the
> tool I am developing require an exclusive lock for distributed computing
> purposes. The file being locked, I can't send that file but could send the
> stream that is acquired by the lock. As a work-around I had to create a
> copy of the input file in the temp folder and send that file instead.
(I am not sure this belongs to -devel and not to -user, but still.)
Can you be more accurate in your words? In ffmpeb vocabulary, a stream is a
sequence of packets extracted from an audio-video container format. For
example, an AVI file usually holds a video stream and an audio stream,
possibly several. It does not look like that is what you are talking about.
Furthermore, ffmpeg mostly does not rely on files, except for occasional
parts (statistics for multipass, presets), but on URL contexts, which can
read from files or from various protocols (raw TCP, HTTP, pipes, RTP, etc.).
Writing support for a new protocol is reasonably easy.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: Digital signature
More information about the ffmpeg-devel