Upgrading Flash Streaming Server for Echo 360 (Apreso) March 24, 2008
Posted by ficial in Instructional Technology, lecture capture.trackback
Due to a relatively recent security hole in Adobe’s Flash Server 2 we had to upgrade the one driving our Echo360 (nee Apreso) system. It was a little scary to contemplate, but in fact went smoothly.
- Downloaded the latest version Flash Media Streaming Server 3 from Adobe - Flashmedia3_Int_Strm_ALP.zip - it was a bit disconcerting since this is about 160 megs and the previous version was about 8, but it’s OK.
- Ran a full back up of the host machine
- Unpacked the FMS zip file
- Ran the installer, accepting all the default choices and creating the same admin account and password as for the previous version (I don’t know if that’s strictly necessary, but seemed easiest)
- Edited the server configuration file (C:\Program Files\Adobe\Flash Media Server 3\conf\fms.ini) to set the VHOST.APPSDIR property (our Echo360 streaming folder is on a different partition from the FMS install)
- Restarted the FMS
- Tested a previously recorded presentation and it worked.
- Haven’t yet tried recording a new presentation, but given that the existing ones worked fine I don’t foresee any difficulties
We are thinking of using the Echo360 system. What are the problems you have encounter with it?
The most serious problems we’ve encountered have all been on the social side (i.e. trying to get faculty to use lecture capture) rather than the technical side. Once the system was installed and we were practiced with it we haven’t had any problems. I can’t speak as to how it would operate under heavy load since we’ve not had that situation at all.
The downsides I see to the Echo360 product are:
- expensive (I think this is the main reason one would chose another product over Echo360)
- initial set up was complicated
- fixed installation in a given room makes a pilot project difficult to run, however we’re planning on converting one or two of our fixed installs to deployable systems which I think will make that easier
- the scheduling software is less than ideal, but I hear the new version (coming out soon, this summer perhaps…?) is a lot better.
- the presentation playback isn’t quite as flexible as I’d like (in terms of which captured stream is displayed at what size), but again I hear the new version fixes that issue.
The single biggest reason I’d recommend Echo360 is that their people have been extremely helpful and friendly. No matter what product you choose, lecture capture and delivery is a fairly complex process. It’s worth a lot to me to know that I can call them and my problems will be fixed and my questions answered.
Also, see http://ficial.wordpress.com/2008/01/10/lecture-capture-pitfalls/ for a post about Echo360 when I was in a worse mood :)
Thank you for the comments about Echo360. I’m sure we’ll have the same difficulties with lecturers but this seems to be what the student want.
Do you have details of the server that you use?
We’re running the Content Manager and a Flash streaming server on the same machine, a Windows Server 2003 box with a 2.8G processor and 2G of RAM and a 150G hard drive.
I thought that you would have to have more RAM and a larger hard drive. How many hours of lectures, on average, do you stream in a week?
Also I have been told that the Echo360 system does not need to have a video streaming server so why did you find it necessary to have one?
Thank you for taking the time to answer my questions. Using Echo360 will take up a lot of time and resources and we are short of both.
At this point, we’re streaming maybe 1/4 hour per week on average. Not much at all - no actual academic lectures, only IT workshops. Once we actually get professors to use the system we’re expecting 5-10 hours per week.
I’d been told a streaming server was a necessary component, which is why we have one. It never occurred to me to try it without one. Perhaps without one the system will still do non-streamed content delivery? Definitely a question for the Anystream folks.
Sorry I didn’t get back to you sooner. It’s been a busy week :)