Greg,

I have tested this version, you have placed on the 26th March late pm    
http://aries.usask.ca/epiphan/frm-2-3-0e-Matterhorn-15977_1067-VGA2CPU_DM365.bfrm-CUSTOM.bfrm

I will try your latest one tomorrow if I am not too busy.

Leslaw




On 29 Mar 2012, at 18:06, Greg Logan wrote:

> Hi Leslaw,
> 
> Thanks for the reports.  Which version specifically were you using?  The
> beta version currently has a nasty configuration bug which would explain
> a bunch of these symptoms.  Do they do away when you use
> http://aries.usask.ca/epiphan/frm-2-3-0e-Matterhorn-16051_1068-VGA2CPU_DM365.bfrm-CUSTOM.bfrm?
> This build has a patch applied which fixes the bug, and works really
> well in my testing.
> 
> G
> 
> On 12-03-28 09:43 AM, Dr Leslaw Zieleznik wrote:
>> Hi Greg,
>> 
>> I did a number of tests and I think that finally your s/w is practically
>> working fine, as there are only few problems.
>> 
>> All tests I did were with 'Independent streams' layout and with all
>> inputs selected on the core.
>> 
>> I did few short tests and long tests like this:
>> i) one hour of recording then 30min pause
>> ii) another hour of recording and 30min pause
>> ii) third hour of recording. 
>> 
>> I did these series twice and once the third recording was lost - the
>> View Recording Info (from Finished jobs) is showing that no file were
>> uploaded to the core. 
>> As this is a bit worrying, we need to do more tests to eliminate this
>> one off problem (?)
>> 
>> I have also noticed few small problems:
>> 1. the VGA and DVI frames are shifted to the right giving a black left
>> margin, and the maximum correction you can do on the Frame Grabber
>> Horizontal Shift is 10, as for more the screen goes black
>> 
>> 2. all completed jobs will stay forever on the Capturing table with
>> the Status 'Capturing'  - the Workflow Instance is showing state Paused
>>    and this can only be removed by the Workflow Service REST POST /Stop
>> Method
>> 
>> 3. I did also try the Review/Trim with two jobs, which was skipped
>> twice, but this can be a bug on the core?
>> 
>> 4. the time shown on the Media Module is showing time, when I think the
>> uploading has started,
>>   for example, for 1hour recording started at 10.00 and so completed at
>> 11.00, the time is shown as 11:07 (processing on the core was started at
>> 11:26).
>>   Would it be possible to correct it so the time will be shown at
>> the start of recording (so 10:00 in that case)  or at the stop of
>> recording (so 11:00)?
>> 
>> Best wishes,
>> Leslaw
>> 
>> 
>> 
>> 
>> On Mar 27, 2012, at 3:42 AM, Greg Logan wrote:
>> 
>>> On 3/26/2012 5:37 PM, Earl Schellhous wrote:
>>>> Hi Greg,
>>>> 
>>>> 
>>>> 
>>>> Unfortunately that didn't fix whatever is going on with our instance.
>>> 
>>> Gah, that's what I get for relying on autocomplete.  Try
>>> http://aries.usask.ca/epiphan/frm-2-3-0e-Matterhorn-15977_1067-VGA2CPU_DM365.bfrm-CUSTOM.bfrm
>>> instead.  That file actually has the patch applied!
>>> 
>>> G
>>> 
>> 
>> 
>> 
>> _______________________________________________
>> 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

Dr Leslaw Zieleznik
OBIS (Oxford Brookes Information Solutions)
Oxford Brookes University
[email protected]
Tel:  +44 (0)1865 483973





_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users

Reply via email to