On 11-12-08 11:26 AM, Dr Leslaw Zieleznik wrote: > 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?
Most of them should be fairly self-explanatory. -Calendar polling interval is the number of minutes between calendar data refreshes. This is a fairly expensive operation, so setting this too low may have adverse affects. Production data tends not to change frequently so a one hour interval is the default. -Agent State Push Interval is the number of seconds between sending agent state updates to the core. Setting this to a higher value may cause the admin UI to inform you that a capture has failed, only to have it start properly later on. Lower values are excessive since the internal clock which controls the captures runs in one minute increments. -Skip Conflicting Captures defaults to disabled. When enabled, instead of shrinking captures to fit (best effort, same algorithm as the normal Java CA) the second of two conflicting captures will be skipped entirely. -Maximum Capture Duration prevents runaway captures. 8 hours is far longer than anything we've seen captured before, so it's a safe default. If a single capture runs over 8 hours then the capture will be stopped automatically, but no other capture will be started (aside from the pre-scheduled ones) -Ingest Interval is the number of minutes between attempts to ingest a capture. A capture can only be ingested once it has finished capturing completely. Defaults for the capture inputs themselves will be highly situation dependent. Mine run with the following settings: Type: Flash Video (H.264 codec) Preset: High Speed Profile: Main DVI: Frame Size: 1024x768 Key Frames: 60 Frame Rate: 30 Bitrate : 4000 Video: Frame Size: 720x480 Key Frames: 30 Frame Rate: 30 Bitrate : 1200 Independent Streams Audio: Format : Raw PCM Sample Rate: 22050 Channels : Mono A couple of notes about the internals: -Encoding MP3 is expensive, and done in software. PCM is by far preferred, although MP3 is certainly possible. MP3 may require a compromise on video. -Setting the Picture-in-picture layout to anything other than Independent Streams is supported, however your video will appear jerky. This is because of the way that Matterhorn currently processes the videos, and is a known issue. G > 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
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
