millicast / millicast-native-sdk

SDK to build native clients using the Millicast platform.
Other
17 stars 5 forks source link

[iOS] MCVideoSource.getCapabilities() reduced in MillicastSDK 1.4 (no 16:9 resolution) #6

Closed eungkyu closed 1 year ago

eungkyu commented 2 years ago

If I dump result of MCVideoSource.getCapabilities() from MillicastSDK 1.3.1 (iOS iPhone X - rear camera)

outputs are following.

[0]:Cap:192x144 fps:60 PixelFormat:Unknown
[1]:Cap:352x288 fps:60 PixelFormat:Unknown
[2]:Cap:480x360 fps:60 PixelFormat:Unknown
[3]:Cap:640x480 fps:60 PixelFormat:Unknown
[4]:Cap:640x480 fps:60 PixelFormat:Unknown
[5]:Cap:960x540 fps:60 PixelFormat:Unknown
[6]:Cap:1024x768 fps:60 PixelFormat:Unknown
[7]:Cap:1280x720 fps:30 PixelFormat:Unknown
[8]:Cap:1280x720 fps:60 PixelFormat:Unknown
[9]:Cap:1280x720 fps:60 PixelFormat:Unknown
[10]:Cap:1280x720 fps:240 PixelFormat:Unknown
[11]:Cap:1440x1080 fps:60 PixelFormat:Unknown
[12]:Cap:1920x1080 fps:30 PixelFormat:Unknown
[13]:Cap:1920x1080 fps:60 PixelFormat:Unknown
[14]:Cap:1920x1080 fps:60 PixelFormat:Unknown
[15]:Cap:1920x1080 fps:120 PixelFormat:Unknown
[16]:Cap:1920x1080 fps:240 PixelFormat:Unknown
[17]:Cap:1920x1440 fps:60 PixelFormat:Unknown
[18]:Cap:2592x1936 fps:30 PixelFormat:Unknown
[19]:Cap:3264x2448 fps:30 PixelFormat:Unknown
[20]:Cap:3840x2160 fps:30 PixelFormat:Unknown
[21]:Cap:3840x2160 fps:60 PixelFormat:Unknown
[22]:Cap:4032x3024 fps:30 PixelFormat:Unknown

But outputs from MillicastSDK 1.4.0 are following.

[0]:Cap:4032x3024 fps:30 PixelFormat:I420
[1]:Cap:3264x2448 fps:30 PixelFormat:I420
[2]:Cap:2592x1936 fps:30 PixelFormat:I420
[3]:Cap:1920x1440 fps:60 PixelFormat:I420
[4]:Cap:1440x1080 fps:60 PixelFormat:I420
[5]:Cap:1024x768 fps:60 PixelFormat:I420
[6]:Cap:960x540 fps:60 PixelFormat:I420
[7]:Cap:640x480 fps:60 PixelFormat:I420
[8]:Cap:480x360 fps:60 PixelFormat:I420
[9]:Cap:352x288 fps:60 PixelFormat:I420
[10]:Cap:192x144 fps:60 PixelFormat:I420

Especially, all 16:9 resolutions are missing. Is there any ways to capture as 16:9 resolution?

Santiago-Souto commented 1 year ago

This issue was addressed in the latest release (1.4.2)