Bug 28154 - [Binding]AVFoundation API Scrub needed
Summary: [Binding]AVFoundation API Scrub needed
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Library (Xamarin.Mac.dll) ()
Version: 1.12.0
Hardware: PC Mac OS
: Normal normal
Target Milestone: master
Assignee: Manuel de la Peña [MSFT]
Depends on:
Reported: 2015-03-18 11:26 UTC by Chris Hamons
Modified: 2016-09-19 12:36 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Chris Hamons 2015-03-18 11:26:46 UTC
There are APIs now available on OS X, such as:

		CMTime ActiveVideoMinFrameDuration { get; set; }
		CMTime ActiveVideoMaxFrameDuration { get; set; }

that need to be bound. An existing binding is available for iOS.
Comment 1 Ram Chandra 2015-03-18 13:36:43 UTC
I have checked this issue and I am also getting the same behavior.

When I checked the definition of "AVCaptureDevice" class in assembly browser, I observed that "ActiveVideoMinFrameDuration" and "ActiveVideoMaxFrameDuration" properties are missing.

Additional info: I have also checked the both property "ActiveVideoMinFrameDuration" and "ActiveVideoMaxFrameDuration" in iOS and observed that both properties are bounded in "AVCaptureDevice".

Screencast: http://www.screencast.com/t/7WZ6phkD

Environment Info:

=== Xamarin Studio ===

Version 5.9 (build 245)
Installation UUID: 011d70a5-dede-428b-ab04-ef451c2e539d
	Mono 4.0.0 ((detached/1605a60)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 400000083

=== Apple Developer Tools ===

Xcode 6.2 (6776)
Build 6C131e

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: c10b5e4
Branch: master
Build date: 2015-03-17 00:04:39-0400

=== Xamarin.Android ===

Version: (Business Edition)
Android SDK: /Users/MM/Desktop/android-sdk-macosx
	Supported Android versions:
		2.3    (API level 10)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
Java SDK: /usr
java version "1.7.0_65"
Java(TM) SE Runtime Environment (build 1.7.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

=== Xamarin Android Player ===

Version: Unknown version
Location: /Applications/Xamarin Android Player.app

=== Xamarin.Mac ===

Version: (Business Edition)

=== Build Information ===

Release ID: 509000245
Git revision: e249c35434b118ed16bae67d35f756b3119bef4b
Build date: 2015-03-17 15:49:56-04
Xamarin addins: a2b515f29d591552e7c5f978c03d9c75efc820aa

=== Operating System ===

Mac OS X 10.9.5
Darwin MacMini.local 13.4.0 Darwin Kernel Version 13.4.0
    Sun Aug 17 19:50:11 PDT 2014
    root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64
Comment 3 narayanp 2016-09-19 12:36:38 UTC
I have checked this issue with latest master Xamarin.Mac and observed that now the issue is working fine as shown in the screencast.

Screencast: http://www.screencast.com/t/5hIKfeXMQv2

Environment Info:
gist: https://gist.github.com/lal360/9070f991f5433e51bab81c64bf45fa3f

Hence, I am closing this issue.