rtmpdump updates for Ubuntu and derivatives

[dinkypumpkin]

On 21/01/2013 18:51, JB Caruth wrote:
> Are these changes something which should be fed back to the rtmpdump
> developers and checked in to the original source? I have no idea how
> to do that but it seems that this might be a bug others would benefit
> from (and, selfishly, I have no idea how to build my own version under
> raspbian).

It's a one-line change to rtmpdump, but whoever wants to push it 
upstream will need to verify that it works and perhaps explain how it 
works. Right now, we have a magic number that is only known to work on 
one particular system - nobody else has verified that it works for them. 
  The effect of that magic number may be dependent on system spec, 
loading, etc.  You posted that you're rocking FTTP on a Raspberry PI 
with your system's rtmpdump so this change  clearly isn't required in 
all cases to access iPlayer over super-fast broadband.  Also, anyone 
using rtmpdump built from code older than Nov 2012 (likely true for 
anyone who hasn't made their own build) may have been plagued by runaway 
rtmpdump processes due to an entirely different - albeit infrequent - 
problem (see the link Neill posted here: 
http://www.mail-archive.com/get_iplayer@lists.infradead.org/msg03568.html).

Whatever happens upstream, I'll keep the code around on Github for 
anyone who wants to roll their own. rtmpdump is very easy to build, 
though I don't know if that translates to the Pi. I can also put it into 
the next Windows release, just in case.