On 2/22/2012 3:27 PM, [email protected] wrote: > Just to clarify, since I reported this bug: > > Confidence monitoring *is* working stable, if we avoid using a > customProducer for the camera (which in our case is still necessary, > since I haven't found the tool to set the width of it).
I can't remember, is this a v4l or v4l2 device? v4l2-ctl should do the trick, and comes with the ivtv-utils (or something similar) package. G > At least here in Vienna, we have used it sucessfully for the vga2usb > captures, that is, with Epiphan vga2usb and Bluecherry videocard, Ubuntu > 10.10 and MH 1.3rc... > > Regards, Andreas > > Christopher Brooks schrieb am Wed, 22 Feb 2012 betreff "Re: [Opencast...": >> Hey Adam, >> >> We covered this topic in the dev meeting; folks agree that it's a >> feature in high demand, but no one had immediate cycles to look into it >> and the decision was to push it off to 1.4 (or beyond) so that 1.3 >> could get out. I agree that the communication around confidence >> monitoring not working needs to be clear. >> >> With our installation here we haven't had a high demand for confidence >> monitoring, despite thinking we would. But, there is a little trick - >> you can mount the drive of the capture agent on your local machine and >> play back (using VLC) the captured file as it is capturing. This gives >> you a slightly delayed confidence monitoring, and is bad for >> performance and a PIA to implement, but it does work. Alternatively, >> you might want to look into streaming using a custom gstreamer >> pipeline. This has not been tested to work within the hardware >> constraints though, so your mileage may vary (akm can provide more >> thoughts when he is back next week), >> >> Chris >> >> On Wed, 22 Feb 2012 09:00:23 -0800 >> Adam Hochman <[email protected]> wrote: >> >>> Regarding >>> http://opencast.jira.com/**browse/MH-8367<http://opencast.jira.com/browse/MH-8367>, >>> >>> I know the confidence monitoring feature has been promised for quite >>> some time. This issue is currently marked as major. In terms of >>> setting expectations, if this bug isn't going to be addressed we >>> should make it clear that this feature isn't supported in 1.3. I >>> know UC Berkeley could really use this feature but we don't have the >>> resources to fix this bug. We can however help test the fix once the >>> bug has been addressed. How are others dealing with capture >>> monitoring in the absence of an official solution? >>> >>> >>> On Tue, Feb 21, 2012 at 7:55 AM, Christopher Brooks >>> <[email protected]>wrote: >>> >>>> Greg, >>>> >>>> I'd like to -1 this until we can determine if this can be verified: >>>> >>>> >>>> http://lists.opencastproject.org/pipermail/matterhorn-users/2012-February/002110.html >>>> >>>> >>>> Unfortunately, Adam McKenzie who is best able to verify and fix this >>>> issue is away until next week. >>>> >>>> Chris >>>> >>>>> Hi committers, >>>>> >>>>> As per our practice, it's my pleasure as release manager to >>>>> #propose that revision 11897 of the 1.3.x branch (also known as >>>>> 1.3-rc6), plus whatever changes are required to be done as part >>>>> of the release process, be released as 1.3.0. >>>>> >>>>> The voting time for this proposal normally ends 72 hours from now; >>>>> roughly Tuesday February 10th 2011 at 9:00am GMT -6:00, or once >>>>> any committer has voted -1 to the release. I'd like to take this >>>>> opportunity to remind you that any -1 votes are expected to be >>>>> accompanied by details of the objection and plans to move forward >>>>> towards a new release candidate. >>>>> >>>>> I feel that the 1.3.x branch has been sufficiently tested and is >>>>> ready for production. There are no outstanding release blockers, >>>>> four outstanding critical issues, sixteen outstanding major >>>>> issues, four outstanding minor issues, and no outstanding trivial >>>>> issues. >>>>> >>>>> G >>>>> _______________________________________________ >>>>> Matterhorn mailing list >>>>> [email protected] >>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn >>>>> >>>>> >>>>> To unsubscribe please email >>>>> [email protected] >>>>> _______________________________________________ >>>> >>>> >>>> >>>> -- >>>> Christopher Brooks, BSc, MSc >>>> ARIES Laboratory, University of Saskatchewan >>>> >>>> Web: http://www.cs.usask.ca/~cab938 >>>> Phone: 1.306.966.1442 >>>> Mail: Advanced Research in Intelligent Educational Systems >>>> Laboratory Department of Computer Science >>>> University of Saskatchewan >>>> 176 Thorvaldson Building >>>> 110 Science Place >>>> Saskatoon, SK >>>> S7N 5C9 >>>> _______________________________________________ >>>> Matterhorn mailing list >>>> [email protected] >>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn >>>> >>>> >>>> To unsubscribe please email >>>> [email protected] >>>> _______________________________________________ >>>> >> >> >> >> -- >> Christopher Brooks, BSc, MSc >> ARIES Laboratory, University of Saskatchewan >> >> Web: http://www.cs.usask.ca/~cab938 >> Phone: 1.306.966.1442 >> Mail: Advanced Research in Intelligent Educational Systems Laboratory >> Department of Computer Science >> University of Saskatchewan >> 176 Thorvaldson Building >> 110 Science Place >> Saskatoon, SK >> S7N 5C9 >> _______________________________________________ >> Matterhorn mailing list >> [email protected] >> http://lists.opencastproject.org/mailman/listinfo/matterhorn >> >> >> To unsubscribe please email >> [email protected] >> _______________________________________________ >> > > ----------------------- > [email protected] > 01/58801 DW 41523 > mobil: 0664/60 588 4523 > TU Wien > DVR-Nummer: 0005886 > ----------------------- > _______________________________________________ > Matterhorn mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > [email protected] > _______________________________________________ > _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
