Hello,

Thank you for taking the time to respond. I would prefer not to use flash, however, this is an exercise in moving existing content from an external to internal solution; the pre-existing media is all flash.

The ‘quickest’ route was to keep everything as flash. With regards to the rtmp stream, firstly, its via rtmps and secondly, it requires username/password authentication. On the media server side, this works (via a tool like rtmpdump). The page with the fv player is itself password protected. So whilst it is true that the rtmp url contains the username / password, at least the page itself is authenticated. There are many other more appropriate approaches, but it is a trade off against time to implement.

I cannot seem to persuade the FV Player plugin to accept a rmtp stream of the form:

rtmps://xxx.xxx:port/live?username@password .. I have seen other plugin with syntax similar to

rtmps://username:password@xx.xx:port/live:flv:/path/n.flv

For rtmpdump, this suffices:

rtmpdump -r rtpms://xxx.xx:port/live/file.flv -C S:username -C S:password.

Regards