On 3/23/2012 12:34 PM, Charles Turner wrote: > Hello, > > We're new to this list and are experiencing problems with Epiphan's > Matterhorn capture appliance. From earlier list traffic it seems like > others have experienced similar problems, but it isn't clear to us what > the current state is. We are using Epiphan firmware 2.2.3 and Matterhorn > server 1.3.0 (details below). > > The problem is that we schedule a recording (1 minute) and when the > recording is finished it remains in "Capturing" mode indefinitely. > Clicking on the Matterhorn Admin tools -> Inspect Workflow screen shows > that it is in a PAUSED state. > > If we then go into the /admin/maintenancecfg (maintenance page) of the > Epiphan device admin and click on "Reboot Now" after a few minutes the > recording changes out of the paused state and begins processing normally > and when finished we can click on "Play" and the video will play.
This, to me, says that you aren't waiting long enough after it stops capturing. The ingest script runs every 60 minutes by default, so if you capture a one minute lecture right after the ingest script runs then you have to wait another 59 minutes before the ingest script fires again. The script also fires on reboot, so I'm betting that's why you see it suddenly start working after restarting the box. > This is true of Epiphan firmware 2.2.1a and 2.2.3. > > If we use firmware 2.3.0e we get the following message instead of > “Capturing”: > “WARNING: Recording may have failed to start or ingest! It seems the > core system did not receive proper status updates from the Capture Agent > that should have conducted this recording.” Two options: Either the capture did not start properly or the device did not update its calendar before the capture should have started. Again, like the ingest script, the calendar script fires every X minutes. If you schedule something to start sooner than X minutes out then the device won't start capturing since the event will have started in the past (mid-event starts are still coming). For what it's worth, I've been working with 2.3.0e (which should be a full release, just hasn't been copied to the right place) all week verifying some memory issues and things have been working fine for me. Have you been resetting the device to factory defaults when you change firmware versions? G > Does anybody know of a way to resolve the issue, or are we still waiting > on a new release of the firmware from Epiphan? > > Configuration details: > > Matterhorn svn info: > Last Changed Author: greg_logan > Last Changed Rev: 12007 > Last Changed Date: 2012-03-14 21:52:05 -0700 (Wed, 14 Mar 2012) > > From the admin/info page of the device: > Matterhorn MTH92145 info > FIRMWARE_VERSION="2.2.3" > FIRMWARE_BUILD_HOST="tochilka 2.6.38-8-server" > FIRMWARE_BUILD_DATE="2011-11-27" > FIRMWARE_PLATFORM=VGA2CPU_DM365 > FIRMWARE_ARCH=arm > FIRMWARE_SVNPATH=/branches/VGABROADCASTER_DAVINCI/2_2_3/epiphan/vga2web/subsys/base > > We have tried firmware 2.2.1a, 2.2.3 and 2.3.0e and are currently using > 2.2.3. > > Thank you! > Charlie Turner > Earl Schellhous > IET-Academic Technology Services > UC Davis > > > > > _______________________________________________ > 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
