Thanks, that is useful. I have reduced the Calendar polling interval, hoping that it may reduce the time lag. Can please explain the meaning of all these parameters with recommended setup?
Leslaw On 8 Dec 2011, at 17:01, Greg Logan wrote: > On 11-12-08 03:00 AM, Dr Leslaw Zieleznik wrote: >>> Calendar Polling Interval: 1 minuet >>> Agent State Push Interval: 60 seconds >>> Ingest Interval : 2 minutes (I changed it from 60 minutes to 2 minute to >>> speedup the ingest) >> >> I am using a similar setup: 2, 60, 5. > > For the record, the reason the calendar polling interval is so large by > default is that it is a fairly expensive operation internally. If your > calendar data is not changing that quickly (eg: production use) then a > larger polling interval should be used. > > G > >> Best, >> Leslaw >> >> >> On 1 Dec 2011, at 14:30, Dr Leslaw Zieleznik wrote: >> >>> >>> I have finally the ECD working fine, recording two independent streams. >>> And it is diffucult to believe how this has happened? :) >>> >>> I have simply connected a microphone, activated the audio and then >>> rebooted device, just for the purpose of testing the audio. And this >>> somehow did trigger two streams recording. I think it means that the >>> audio need to be enabled (!) >>> I wonder if you can repeat the same on your device? >>> >>> As far as the video quality is concern, the recording quality is much >>> better when 'independent streams' option is selected - the video >>> quality is much worse when the 'video outside DVI/VGA' is used. >>> >>> By the way, I am using the f/w version v2.2.3 which I have downloaded >>> on Monday. >>> This has not been advertised for download yet - I am sorry Greg! >>> >>> >>> Leslaw >>> >> >> >> >> On 8 Dec 2011, at 07:45, VISIONAIRE-Reza Toghraee wrote: >> >>> Hi folks >>> >>> I got a Epiphan MatterHorn Capture Appliance (made for MatterHorn aka >>> MCA) >>> 3 days back. I was struggling to make it working with MatterHorn, which >>> finally I did it, but Im facing some issues which appreciate your thoughts >>> on that. >>> >>> I installed a very clean MatterHorn 1.2 on Ubuntu 10.10 server-i386 >>> 32bit, >>> on my VMware Workstation 8 installed on my Windows 7 (host). >>> On MCA (firmware 2.2.0e) , I configured my server URL (ie >>> 192.168.110.87:8080) and the account username and password which was >>> specified in my config.properties. (matterhorn_system_account, CHANGE_ME) >>> So the first couple of hours I was trying to Register the MCA inside the >>> Core server, which was not happening. I played a lot with URL, >>> username and >>> password, but no luck. >>> So finally I ran the wireshark on my NIC card and saw that the MCA is >>> trying >>> to register into MCA by seding a POST HTTP request to >>> http://192.168.110.87:8080/capture-admin/agents/rest. >>> Finally I understood that this URL is not valid in matterhorn and is >>> changed >>> to http://192.168.110.87:8080/capture-admin/agents. >>> So finally I was very lucky to find the Epiphan download page for Beta >>> software, and I downloaded the Firmware version 2.2.3 which is a beta one. >>> (http://www.epiphan.com/downloads/firmware/Davinci_Matterhorn/beta.php) >>> >>> >>> After installation of firmware and rebooting the MCA (by the way I >>> rebooted >>> the MCA manually, as MCA doesn't reboot by itself after software upgrade, >>> neither doesn't show any message for successful receiving the new >>> firmware) >>> the MCA registered in MatterHorn CORE. (Yes what a lovely time, at 2AM). >>> Then I stuck in another thig which was Capturing. I was scheduling the >>> recording, but MCA was not being informed to record. >>> Finally I found that there is a Calendar service, which the MCA has to >>> poll >>> (by default every 60 minutes!) to retrieve its recoding schedule. >>> I changed the Calendar Polling Interval from 60 minutes to 1 minute, >>> and it >>> fixed the problem. >>> >>> Now I can schedule the recordings, and MCA starts the recording. But I >>> have >>> some issues which seek your geeky help: >>> >>> 0- till now, after recording more than 10 times, I couldn't manage to have >>> the complete result of recording (Video + VGA + Audio) in Engage. >>> 1- sometimes when recording has to be finished, the server still shows >>> that >>> the MCA is in Capturing state. I don't understand why the status is not >>> being updated. >>> 2- sometimes after the recording, it shows the recording as Finished, >>> but I >>> cannot see it on Engage, it shows media is not available. >>> 3- almost most of the times, when the MCA ingests the file to the Core and >>> Core starts digesting, usually it fails in 'Text Extraction" Phase. Is >>> there >>> any way to skip the text extraction phase while digesting? >>> 4- When I try to test the Text Analysis REST docs, I upload a image (jpeg, >>> bmp, tif, gif) to system, but it gives me an error caused by URLDECODER >>> because of finding the '%' (percentage) character in URL. Since the >>> file is >>> being POST ed to the server the URLDECODER analyses the whole file as >>> a URL, >>> and since file is binary, there are lots of '%' inside it. >>> >>> >>> Here is the MatterHorn configuration on MCA: >>> >>> Calendar Polling Interval: 1 minuet >>> Agent State Push Interval: 60 seconds >>> Ingest Interval : 2 minutes (I changed it from 60 minutes to 2 minute to >>> speedup the ingest) >>> >>> >>> Any help, comment highly appreciated. >>> >>> Thanks >>> Reza Toghraee >>> >>> >>> >>> _______________________________________________ >>> 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
