Recent problems and rtmpdump

[zaphod]

There's a link on this page,
http://rtmpdump.mplayerhq.hu/
to a windows version of rtmpdump 2.4

http://rtmpdump.mplayerhq.hu/download/rtmpdump-20110723-git-b627335-win32.zip

It hasn't failed yet, after about 10 downloads using flashhigh1 and 2
but most of the time the warning message appears several times
during the download
(WARNING: Stream does not start with requested frame, ignoring data...)

Extract rtmpdump.exe from the archive and put it in the folder:
C:\Program Files\get_iplayer\rtmpdump-2.2d, optionally rename
the old version.

zaphod


----- Original Message ----- 
From: "David Woodhouse" <dwmw2 at infradead.org>
To: "Chris Yearsley" <cinfo at yearsley.org>
Cc: <get_iplayer at lists.infradead.org>
Sent: Wednesday, August 03, 2011 10:14 AM
Subject: Re: Recent problems and rtmpdump


> On Wed, 2011-08-03 at 09:31 +0100, Chris Yearsley wrote:
>> In any case the success reports from rtmpdump2.4 are promising. Is
>> there a build for Windows?
> 
> There are resume-related fixes in 2.4 which are very promising, since
> resumption of interrupted downloads has been one of the big problems.
> 
> However, rtmpdump 2.4 isn't actually complete yet. They're still working
> on a few things before they make the release. That's why there are no
> official tarballs (and builds) yet. When it *is* released, it should end
> up in http://rtmpdump.mplayerhq.hu/download/ with the rest of the
> releases.
> 
> In the meantime, it shouldn't be hard to build it for yourself if you
> want. Probably hard to do it natively on Windows (isn't *everything*
> harder on Windows?), but if you have a real computer you can simply
> cross-compile it for Windows using mingw32.
> 
> On a Fedora box, with a copy of the rtmpdump source checked out from git
> (git clone git://git.ffmpeg.org/rtmpdump), it seems to be as simple as:
> 
> sudo yum install mingw32-zlib-static mingw32-openssl-static mingw32-gcc
> make CROSS_COMPILE=i686-pc-mingw32- SYS=mingw XLDFLAGS=-static
> 
> The OpenSSL licence prevents me from distributing the resulting binary
> linked statically against the OpenSSL library. But hopefully you'll be
> able to build your own fairly easily? Since it's a prerelease that's in
> active development, you're better off that way anyway, because it means
> you can then build tomorrow's snapshot for yourself, and the next day's,
> and so on until 2.4 is actually declared stable and released.
> 
> -- 
> dwmw2
> 
> 
> _______________________________________________
> get_iplayer mailing list
> get_iplayer at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/get_iplayer