Jean-Sébastien Guay wrote:
Well, it's hard to get some technical info from what docs there seem to
be. Things like what formats are supported read/write/readwrite, what
the "format strings" are for av_find_input_format, etc. I needed to go
to the code for those things (avformat/allformats.c).
Try runing "ffmpeg -formats". This shows the available formats and
containers. On the left of each you'll see D for decode and E for
encode. For the codecs it will also show A for audio and V for video.
I don't remember what the last S and/or D stands for.
Note that these are the available formats. It won't show formats for
which it doesn't have support compiled in.
I'm also wondering how to specify the actual format of an rtsp feed. I
have a URL of the form
rtsp://xx.xx.xx.xx:554/img/media.sav
and for ffmpeg to be able to read that, I need to set the format to
"rtsp", but I know that the video is actually in mpeg-4. ffmpeg doesn't
seem to automatically figure that out, because even though data is
transferred, no image shows up (I'm guessing the decoder can't read the
data it gets from the camera because it thinks it's in some other
format). Do I have some way of telling it "this is mpeg-4 over rtsp"?
I would have thought rtsp would be a protocol and not a codec, but
looking at avformat/allformats.c, it's set up as a "demuxer":
REGISTER_DEMUXER (RTSP, rtsp);
Demuxer kind of makes sense. RTSP will probably act like any other
transport/program container (.mpg or .ogg file, for example). The audio
and video will still have to be separated out into elementary streams,
even if there is only one elementary stream present.
--"J"
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
