Today, I installed the DVRCast application on the Flash Media Server at work and ran into a little bit of an underdocumentation problem. We run our FMS in an origin/edge architecture and the supplied documentation for DVRCast only explains how to install on a single-node, origin-only server setup. The installation archive comes with two different application folders, dvrcast_origin and dvrcast_edge. It was pretty obvious what the two were for, but didn’t have anything to go off of on how to install dvrcast_edge to the edge servers.
A quick internet search revealed that someone else had encountered the same problem, but didn’t see a solution given.
What I did was install dvrcast_origin to the origin server per the instructions, but renamed it dvrcast. Then I rewrote the host.ini file in dvrcast_edge from this:
#name primaryIP;secondaryIP
server1 localhost;localhost dvrcast_origin
to this, using the correct name and IP address for the origin server, of course:
#servername primaryIP;(secondaryIP) app_name
origin.server.com 123.456.789.012 dvrcast
Works like a charm. The parents are going to be so happy at commencement…
As a side effect of getting this up and running, I also have multi-rate streaming ready to go. Pretty successful day one of programming week.
I am trying to run dvrcast_origin on Amazon, but it is not working.
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
I can’t help you with the Amazon part, since I know nothing about what they offer.
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.txtIf 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.