Date: Mon, 21 Sep 2009 02:32:08 +0000 From: "b. f." <bf1783@googlemail.com> To: freebsd-multimedia@freebsd.org Cc: Christian Weisgerber <naddy@mips.inka.de> Subject: Re: Downloading RTSP stream? Message-ID: <d873d5be0909201932o55b07faay3c52cf370963e3ae@mail.gmail.com> In-Reply-To: <d873d5be0909201215t6f2c7f27qe36bfcab72a029dd@mail.gmail.com> References: <d873d5be0909201215t6f2c7f27qe36bfcab72a029dd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Christian Weisgerber wrote: >Plain openRTSP creates separate audio and video files. I don't >think this is useful for later playing. Useful for editing, but not perhaps as convenient for playing. However, mplayer has the -audiofile switch, and various synchronization options, for the case of separate audio and video files. By the way, when you were attempting to download this with mplayer, did you use -dumpstream in conjunction with -dumpfile, and did you experiment with the -rtsp-* switches? And do any other players (e.g. xine, vlc) play the output files -- or do they fail, too? > mplayer doesn't find >anything in the output of openRTSP -4 (or -q). Yes, I think that the sample openRTSP client is very flexible, but doesn't adapt well to different streams when no settings are specified. I've gotten garbage under default settings, and had to tinker with various knobs. I got mplayer to play the output of the first 30 seconds of your stream, albeit with a stream of error messages (I used tcp transport to allow passage through a firewall, and had to bump the buffer sizes as a result): openRTSP -4 -B 100000 -b 100000 -d 30 -D 110 -Q -n -t rtsp://ondemand.quicktime.zdf.newmedia.nacamar.net/zdf/data/quicktime/zdf/09/09/090920_untergang_szent_istvan_tex_vh.mp4 > naddy30.mp4 > but I'd prefer MP4 over WMV. > Just because. :) Yes, using a proprietary format sticks in my craw, too. b.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d873d5be0909201932o55b07faay3c52cf370963e3ae>