Quote:
Originally Posted by sbt
With this report, I wondered whether the client I was using would matter, so I tried the same one blood.eaglz used (iViewNapper from June). However, I still had the same issue connecting. Oh well.
|
You sure something isn't broken on your end, like something blocking port 1935. For example:
- another video playing in a browser at the same time
- firewall permission or antimalware blocking port
- hung program
- more than one instance of RTMPdump or downloader running
Specifying "-c 80" means you are overriding the port that was specified in the RTMP URL to rtmpdump. I don't think any of the D/Ler's actually specify the port number for the reason mentioned in the following paragraph.
By default, rtmpdump will use port 1935 because that is the specification. I'm not too sure, but I think rtmpdump will fall back to port 80 or else port 443 if it cannot get access to 1935 (will that's what should happen IIRC).
However, I might just ask for confirmation on the RTMPdump mailing list that RTMPdump does actually fall back to other than port 1935 if it's not available.
Quote:
By the way, which downloader switches between Akamai and Hostworks? I'd want to be careful not to get too much unmetered 
|
They all do. It gets the cue from ABC's server. It's specified in the HOST field of
this page.