I tried the same setting and it works for me. The only difference was that i gave the stream name without the .flv extension
Try your setting without the .flv extension for the file name.
Let me know if it works.
This still hasn't worked for us. We have been given a server name in this format: rtmp://server.name.net/ and an application name in the format app/name, which together form a url: rtmp://server.name.net/app/name
Then I have the move file in a subdirectory (/test) from this base url and finally the filename: myvideo.flv
So putting it together I have tried in Captivate:
field 1: rtmp://server.name.net/app/name
field 2: /test/myvideo.flv
and other combations of these three. I've eliminated the flv extension, tried with and without preceding (/) and trailing (/) (eg: /test/... vs test/... or).
None of these seem to work. I can play the flv directly using a client called WIMPY so I know the streaming service works. With that client I enter a fully qualified path such as: rtmp:/server.name.net/app/name/test/myvideo.flv and it works flawlessly.
Thanks for your assistance.
WE are having TERRIBLE problems with a CDN service using extension .flv.smil.
We can use the service when the SWF file is created through FLASH but we cannot then get it to show video controls unless we use the published HTMNL page so embedding the video in the actual web page has not worked. When created with CAPTIVATE thye swf file appears but the video will not stram from the folder reserved for FLASH streaming. When using the published HTML all works fine. If anyone knows how to get around these issues please let me know.
Have just managed to get this working.
Here is an example of how I did it:
Stream Name: myvideo
Note that I have removed the trailing slash in the first part, and the .flv from the stream name.
I hope that this helps