On 11-11-24 07:32 AM, David Horwitz wrote:

> I would also add a small bug that the device always seems to report 2
> capabilities:
>  - screen-and-audio
> - camera
> 
> Whatever channels you have enables. Like Leslaw our potential use cases
> would call for seperate chanel selection and might well be deployed in a
> venue with video.

Yes, this is a known issue.  It's on my list, but as of yet is not complete.

G

> Thanks
> 
> David
> 
> On 11/24/2011 03:13 PM, Dr Leslaw Zieleznik wrote:
>>
>>
>> I did a number of capture tests today morning, and it seems to me that
>> the device is working (almost).
>> Here my observations so far:
>>
>> what is working:
>>     i) the device starts and complete the capture up to the second,
>> and the nice thing (I did not noticed before) is the blue light coming
>> on the box during the capture
>>    ii) the screen capture quality on the DVI channel is very good even
>> for the bitrate 600kbits and 15 frames/sec
>>         but for the acceptable video channel quality, the bitrate must
>> be at least 2500kbits with 25 frames/sec
>>   iii) picture-in-picture recording is working fine for:
>>                     video outside DVI and video inside DVI
>>        
>> what is not working:
>>      i)  the independent streams selection is not working  properly
>> showing only one channel, like that:
>>          when the both channel are selected then Screen is only
>> recorded (not Screen and the Camera)
>>          when the Screen is selected the Video cannel is recorded!  I
>> did this test twice to be sure.
>>          but when Camera is selected the video channel is recorded (so
>> OK).
>>
>> I would like to have two independent streams recorded and played if
>> this is possible.
>>
>> I have not tested the audio channel yet.     
>>
>> The main problem still is the long time lag before the processing has
>> started. The captured recording are staying in the 'Capturing' table
>> showing the status 'capturing' (the workflow instance state is PAUSED
>> then).
>> In one case all jobs have started after 35min, but in another case the
>> jobs started after about 45 min or even longer. 
>>
>> Is it a setup somewhere, which obviously I don't know, that can
>> shorten this lag?
>> There is a warning I am getting frequently, which might be responsible:
>>    WARN(ScheduleServiceImpl:930)  Could not validate Calendar:
>>  Calendar must contain at least one component.
>>
>> In summary, the EDC is finally working, and the above I believe are
>> minor issues that can be easily rectified.
>>
>> So many thanks to Greg for his work!
>>
>> Leslaw
>>
>>
>>
>> On Nov 23, 2011, at 5:16 PM, Greg Logan wrote:
>>
>>> Hi folks,
>>>
>>> The updated firmware was released yesterday, and after testing overnight
>>> the update appears to have fixed the current issues.  Please update your
>>> device with the firmware from
>>> www.epiphan.com/downloads/firmware/Davinci_Matterhorn/beta.php
>>> <http://www.epiphan.com/downloads/firmware/Davinci_Matterhorn/beta.php>.
>>>
>>> G
>>>
>>> _______________________________________________
>>> 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


Attachment: signature.asc
Description: OpenPGP digital signature

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

Reply via email to