> Excellent, so it sounds like the issue is resolved as of 2.2.0e? Does > the device have two inputs when scheduling a capture?
Unfortunately, I only have DVI input at the moment. > he Epiphan agent does not have that file, it's configuration data is > stored on the device itself. The administration UI on the device can be > found at http://$MY_DEVICE/admin. The file you are speaking of controls > the settings for the demo CA. In a production environment this CA is > not used because it uses pre-captured media rather than physical devices. OK, I did play with the device setup to get optimum result from DVI input, when viewing output on the browser. I have deleted the end in file capture.impl.Configuration.Manager.properties for the mock device definitions and the MA stopped working: it is in idle stage only, and under the heading 'Capabilites' says 'Not capabilities found? When I am leaving the capture.impl.Configuration.Manager.properties without any change I can see the mock capabilities and the MA is capturing from the mock inputs. ?? Leslaw On Sep 27, 2011, at 5:53 PM, Greg Logan wrote: > On 11-09-27 10:40 AM, Dr Leslaw Zieleznik wrote: >> I currently have the MA device with 2.2.0e connected to the 1.2 server. >> The server can see it, I mean the name of the agent, and I can also >> change the status of the agent from 'idle' to 'capturing' and vice versa. >> So I expect the MA it is working fine. > > Excellent, so it sounds like the issue is resolved as of 2.2.0e? Does > the device have two inputs when scheduling a capture? > >> By the way, I have not changed the >> ...capture.impl.Configuration.Manager.properties yet, therefore I can >> see on epiphan_agent Capabilities setups as for the mock device. >> Would you tell me please what should I set for the MA device? > > The Epiphan agent does not have that file, it's configuration data is > stored on the device itself. The administration UI on the device can be > found at http://$MY_DEVICE/admin. The file you are speaking of controls > the settings for the demo CA. In a production environment this CA is > not used because it uses pre-captured media rather than physical devices. > > G > >> >> Leslaw >> >> >> >> >> On Sep 27, 2011, at 5:22 PM, Greg Logan wrote: >> >>> On 11-09-27 12:40 AM, Dr Leslaw Zieleznik wrote: >>>> >>>> I have just received one with the 2.2.0e on it, which logically >>>> should be a never version than .0d ? >>> >>> I have heard from users with 2.2.0d who suffer from the same issue. I'm >>> assuming .0d and .0e are versions which just haven't been posted on the >>> website yet, but they do not (as far as I know!) contain the fixes. If >>> they do happen to work for you please let us know! >>> >>> G >>> >>>> Leslaw >>>> >>>> On Sep 27, 2011, at 6:27 AM, Kristof Keppens wrote: >>>> >>>>> Is there any info available on when we can expect the 2.2.0d >>>>> firmware on the epiphan site. Without it our epiphan capture >>>>> appliances are useless and we would very much like to start testing >>>>> them with our opencast 1.2 server. >>>>> >>>>> Thanks >>>>> >>>>> Kristof >>>>> >>>>> On 09/22/2011 05:40 PM, Greg Logan wrote: >>>>>> On 11-09-22 12:43 AM, Kristof Keppens wrote: >>>>>>> I've just tried the upgrade after disabling most features and setting >>>>>>> streaming settings to the fastest + without a dvi connection >>>>>>> active and >>>>>>> now the upgrade succeeded. Thanks for the help. >>>>>>> >>>>>>> However after the update the device is still unable to register itself >>>>>>> with the server. It seems that no request arrive at the server. Should >>>>>>> we wait for the 2.2.0d firmware for this to work? >>>>>> >>>>>> It won't work without it unfortunately. I'm surprised I haven't seen >>>>>> more complains on list, this bug affects (as far as I know) all recent >>>>>> versions of the firmware and I only recently caught it. >>>>>> >>>>>>> I've one more question about the appliance, there is the menu >>>>>>> maintenance with settings for the maintenance server. What does >>>>>>> this do >>>>>>> and should we enable it ? >>>>>> >>>>>> This is an Epiphan function, but I believe it allows remote support of >>>>>> the device from Epiphan's tech support staff. I've left mine enabled >>>>>> since it doesn't seem to hurt anything. >>>>>> >>>>>>> Also is there any way to monitor these devices ( through zabbix or >>>>>>> nagios )? >>>>>> >>>>>> Not yet. This has been requested, but I have not seen any movement in >>>>>> that regard. >>>>>> >>>>>> >>>> _______________________________________________ >>>> 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
