[rtmpdump] Akamai patch
david.keeffe at rivustv.com
Sun Sep 26 22:44:51 CEST 2010
On 27/09/10 02:21, Andrew wrote:
> Hi David,
> I tried adding the -re flag and that didn't make a difference.
> I also tried using the Flash player you linked to, but like the other
> one, it just continues to loop music that I had previously encoded
> while testing Akamai with Flash Media Encoder.
> Do we need to unpublish the existing content in order to send new
> audio or anything like that? Additionally, I am on FreeBSD, is your
> patch Linux-only?
> Any help would be greatly appreciated. I'd be more than happy to
> provide further information or testing.
> On 2010-09-26, at 4:08 AM, David Keeffe wrote:
>> On 26/09/10 08:05, Andrew wrote:
>>> I've been looking for a way to send audio content to Akamai in a
>>> Unix environment. I recently came across this post on the mailing list:
>>> I was able to successfully connect to Akamai using this command:
>>> ffmpeg -loglevel debug -i audiofile.wav -acodec libmp3lame -f flv
>>> conn=S:encoder:1.1.12:USERID live=true akUserid=USERID
>>> akPass=PASSWORD playpath=poc_x_x at xxxxx'
>>> It connects and shows the following:
>>> HandleInvoke, onStatus: NetStream.Publish.Start
>>> Then it appears to stream, however when I go to the Akamai test
>>> there is no content.
>>> Am I doing something wrong? Has anyone else had success with this patch?
>> Hi Andrew
>> As the author of this patch I can confirm it worked for me on a linux
>> host with a video+audio file.
>> You might want to try the option '-re' (realtime samples) - that made
>> a difference for me. There are delays in the way Akamai streams and
>> if you dump everything out as fast as possible it seems that the
>> stream terminates before the content propagates. At least that's my
>> There is also a different Akamai test player that might be more
>> suitable for your (apparently) audio-only stream:
>> that gives you a lot of detail about what arrives.
>> David K
The patch should be platform neutral.
If something is looping still, that suggests you are still streaming
with the other encoder at the same time. And looping suggests the stream
broadcaster is looping as well. I normally see a stream run then stop.
Silly question time: are you publishing to a proper "live" entrypoint?
Or to an "ondemand" entrypoint (which doesn't really exist)? Your
playback URLs will look like these for live:
live - rtmp://cpNNNNN.live.edgefcs.net/live/myprov@1234
while the entrypoints will be
You could always provision a new stream from Akamai. You can have as
many as you like, I believe. What does your Akamai control panel tell you?
More information about the rtmpdump