Hi Jack How you made the ad hoc recording using ECD??
Thanks Reza -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jack Vant Sent: Tuesday, February 14, 2012 7:14 PM To: Matterhorn Users Subject: Re: [Matterhorn-users] Epiphan ECD 2.2.3 production worthy? We have this appliance with the firmware you mention. I tested it thoroughly over the Christmas holiday and our results were as follows: 3 captures in a series of 10 were successful. The other 7 actually showed up in the core and showed as capturing. They are in fact in capturing limbo. 5 ad hoc lengthy captures (90 minutes) were scheduled, 3 of them consecutively. Only the first one worked correctly. The other 4 went off into capturing limbo. We are hoping for yet another firmware update to give this appliance another go. On Tue, Feb 14, 2012 at 12:54 AM, Kristof Keppens <[email protected]> wrote: > Hi all, > > Yesterday we tried to use the ECD in a production environment, > confident that the hard and software was mature enough to do some > recordings in an actual class environment. Our experience however was > everything but satisfactory and led us to do a last minute replacement > of the ECD with the default opencast capture agent. > > We found that since the last firmware ( the one for download on > epiphan site and the one provided by Greg on the list here ) only 1 > stream is processed on the server. The recordings we made only show > the video stream in the engage player, however the original file on > the server shows a multistream avi with 3 streams. This problem is > inconvenient but not that problematic since we could recover the > original multistream ( hopefully we can recover the independant > streams from the avi ). The following recordings had more major > problems. We had to do 3 recordings in a row, one 30 minutes long ( > which we can recover from the server ) and 2 following that of 1h30 that both failed. > > The second recording disappeared from the capturing list on the admin > server after some minutes, and went to processing, resulting in an > empty directory on the server. The recording had more than 1 hour to > go at that point. The third recording started successfully and changed > status to sending for processing ( or something similar ) after less > than an hour, more than 30 minutes needed to be captured at that > point. This recording was unrecoverable as well, since there is no way > to access the files on the ECD and see what is actually happening on that machine. > > This experience leads us to wonder if this machine is production > worthy and if anyone is using this in a reliable way. We understand > that this is still in active development but also believe that basic > functionality and reliability should be expected. The fact that there > is no way to see the files on the ECD and download them from the > device in case something goes wrong is also a big problem for us, > questioning the fact if we can rely on this in a production environment. > > Maybe someone on the list can shed some light on what to expect from > the device in the future and if someone has different experiences with > this, please let us know. At the moment we don't feel confident to use > this device in any classroom environments. > > Thanks > > Kristof Keppens > Ghent University > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users -- Jack Vant System Engineer - Unix Office of Information Technology Boise State University 208-426-4446 208-863-0031 _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
