On the development server, though, you should have only needed to copy the dvrcast_origin directory from the ZIP into your applications directory as the directions say; you don’t need the dvrcast_edge for anything. I’d rename the directory to dvrcast, too.

That should be all you need there. To check, you can run the fmscheck tool that ought to be in the tools directory where fms was installed, use something like:
./fmscheck --host localhost --app dvrcast --play flv:test --logfile test-dvrcast.txt
If you correctly installed dvrcast (use –app dvrcast_origin in the above command you didn’t rename it) the test-dvrcast.txt file should fail to play the file unless you’re sending that test stream to your server, but it should give you a NetConnection.Connect.Success when it hits the dvrcast app. If it’s not correctly installed, it would give you a NetConnection.Connect.Rejected.

Assuming that’s good, the next problem is probably that you don’t have the flvplayback 2.5 component installed correctly. It’s a little bit more involved than this article makes it sound, but there’s an installation guide for the flvplayback 2.5 component that came with dvrcast 1.1. The rest of that article is pretty straightforward and should get you where you need to go with your development server.

It didn’t work on local using Adobe Flash Media Development Server either.

It there any special configuration that is not described in the documentation?

Any help is much appreciated.

Thanks,
Anton