Yes, I definitely did, and rebooted after my setup, I did also rebooted the server. It worked fine before the f.w update. It should not be affected that I am still on 1.2?
Leslaw On 10 Feb 2012, at 16:58, Greg Logan wrote: > On 12-02-10 09:35 AM, Dr Leslaw Zieleznik wrote: >> Greg, >> >> I have installed the patched f/w today and I have found, that: >> >> i) there is quite visible improvement in quality on both video and >> VGA/DVI channels, which is a nice surprise! >> ii) it is a slight shift to the right on both channels, which frame >> grabber settings can't eliminate, bit I can live with it. >> >> But the problem is that, I can't start the capture agent though it is >> registered on the core. It stays idle all the time, and at the capture >> start time I am getting the message: >> >> ""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"" >> >> I did try to start recording many times with different setup on the >> agent, changing the pooling interval, ingest interval and also stream >> setups, without any success. > > Did you reset the device to factory defaults after updating the > firmware? This is something that needs to be done every time you flash. > The version I posted works as expected for me... > > G > >> >> Is it anything else I can try? >> >> Thanks, >> >> Leslaw >> >> >> >> On Feb 8, 2012, at 10:20 PM, Greg Logan wrote: >> >>> On 12-02-05 11:52 AM, Dr Leslaw Zieleznik wrote: >>>> >>>> I'd like to notify about the problem we have noticed during the last >>>> week recordings. >>>> >>>> Our observation is that when the capture time is longer then 45min, >>>> the workflow remains in the PAUSE state - the Capturing displays the >>>> status Capturing - and it stays like that forever. >>>> Otherwise the capture agent behaves properly, changing the status >>>> from Idle to Capturing and back to Idle correctly with the recording >>>> time. >>>> >>>> I suspect this is something to do with the current ECD f/w, so we >>>> simply need to wait for the coming rel 2.3? >>> >>> This is really odd, I'm seeing that behavior as well. The file is >>> captured, but during ingest it is not included in the zip file. This >>> causes an exception during ingest if you check your core's logs. This >>> functionality worked before, so the only thing I can think of is that >>> the zip tool changed underneath me. The current firmware version >>> contains an error in the ingest scripts which is actually losing that >>> data. I have created a patched firmware version available at >>> http://aries.usask.ca/epiphan/ which will prevent the loss of data, >>> however the underlying issue of passing the data to the core remains. >>> I've sent an email to Epiphan about this and I hope to hear back soon. >>> >>> In the mean time, I would install the above firmware (which includes the >>> new features I outlined at Oxford). >>> >>> G >>> >>>> Leslaw >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Matterhorn-users mailing list >>>> [email protected] >>>> <mailto:[email protected]> >>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >>>> >>> >>> >>> _______________________________________________ >>> Matterhorn-users mailing list >>> [email protected] >>> <mailto:[email protected]> >>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >> >> >> >> _______________________________________________ >> 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 _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
