rtmp:// urls need to be handled slightly differently for FlowPlayer compared to other urls. The server and directory has to be specified separately from the file name on the server, so AutoView splits this up based on the last /. My guess is that FlowPlayer can't cope with the url you initially tried in this split up format, so it might be worth doing some experiments using FlowPlayer and a static page to find out if there is a way of getting the URL to work with FlowPlayer in this format.
Why FlowPlayer seems to need to handle rtmp URL's differently is a mystery to me, I would much prefer to just be able to bang the url in as is, which would probably solve these problems. If you can find a way, please tell me, I spent a lot of time on this without any result.
As for the .flv file extensions, I'm very reluctant to strip them off automatically. Whether or not a file extension is needed is more of an implementation issue in the streaming server which you are using, as a sysadmin it is really up to you to make sure that you provide correct streaming server URL's to your users. It might be worth putting in a warning box but allowing users who really want the file extension to leave it on.
I really hate software that tries to be clever by automatically correcting anything it thinks is wrong, because there's always the 5% of circumstances when the automatic correction gets it wrong and then the user is left fighting the system to get it to accept the data they really want without the 'correction'
Why FlowPlayer seems to need to handle rtmp URL's differently is a mystery to me, I would much prefer to just be able to bang the url in as is, which would probably solve these problems. If you can find a way, please tell me, I spent a lot of time on this without any result.
As for the .flv file extensions, I'm very reluctant to strip them off automatically. Whether or not a file extension is needed is more of an implementation issue in the streaming server which you are using, as a sysadmin it is really up to you to make sure that you provide correct streaming server URL's to your users. It might be worth putting in a warning box but allowing users who really want the file extension to leave it on.
I really hate software that tries to be clever by automatically correcting anything it thinks is wrong, because there's always the 5% of circumstances when the automatic correction gets it wrong and then the user is left fighting the system to get it to accept the data they really want without the 'correction'