Thanks Chap.
So, the problem is solved. It is, in fact not about the version of
RTMPdump that's being used. It is, however, about the error itself (10013), which represents a port forwarding error in Windows. It appears in many occasions (two apps that use the same port, port blocked for some reason, requested port not available, IP issues, and so on).
Basically all I had to do was indicate another port for the stream to be routed through. The line should appear as
Code:
rtmpdump -r "rtmp://wdig.fcod.llnwd.net:80/a339/o2/disneych/DJBB_dxd_junc1-03_eng-92067801_sv003" -a"a339/o2/disneych/DJBB_dxd_junc1-03_eng-92067801_sv003" -f "WIN 10,3,181,26" -W"http://a.dolimg.com/en-US/disneyjunior/swf/videoplayerShell_MPF.swf" -p "http://disney.go.com/disneyjunior/jungle-junction/jungle-junction-videos-episodes/sneeze-fire-1914628" -y "disneych/DJBB_dxd_junc1-03_eng-92067801_sv003" -o DJBB_dxd_junc1-03_eng-92067801_sv003.flv
in which port 80 was added at the end of the URL, addition that renders it as suitable for stream routing.
Thanks for the help, Chap. Seeing that you could record it made me study the matter a little further. 10013 no more an issue.
