Pocket 4K Aperture Value Issues

[BTM_Pix]

6 hours ago, CaptainHook said:

If you can let me know exact MFT lens models and describe the issue in repo steps I can follow it up. There is one known issue at the moment that some times the lens won't set the correct aperture we tell it to, but for the aperture number to stay the same on the camera UI display but the lens actually change sounds like something different. Will look into what you mention nRF Connect too.

I'll give you an example of each of the three main MFT manufacturer's native lenses and three speed boosted ones from different manufacturers, listing the apertures at which they have repeats.

NATIVE LENSES

Panasonic 14mm f2.5

1. f11
2. f14
3. f16
4. f21

Sigma 30mm f1.4

1. f1.4
2. f1.7
3. f10
4. f11
5. f14
6. f15

Olympus 45mm f1.8

1. f10
2. f11
3. f14
4. f15
5. f16
6. f21

ADAPTED LENSES (using Metabones T Ultra 0.71x)

Canon 50mm f1.8

1. f1.3
2. f1.7
3. f10
4. f11
5. f14
6. f15

Sigma 18-35mm ART f1.8

1. f1.3
2. f1.4
3. f1.7
4. f10
5. f11

Tamron SP 17-50mm f2.8

1. f10
2. f11
3. f14
4. f15
5. f16

The Metabones has the latest firmware and from the responses by the other two users in the thread, the same behaviour is also happening with Viltrox adapters.

Obviously, none of these native lenses or adapted lens combinations shows the same issues when tested on either a "regular" MFT hybrid camera (Panasonic G7 and GX80) or my other MFT mount camera the JVC LS300.

With regard to the steps to reproduce, just turn the aperture wheel one step at a time (or you can do it on the app as its the same behaviour) and you will see the points at which the indicated value does not change and these points will remain consistent in either direction.

As f10 and f11 are two of the common points of repetition across all lenses, you should also these two byte arrays for each version of f10 and f11 being returned from UUID: B864E140-76A0-416A-BF30-5876504537D9 in any logs you capture in nRF Connect whilst doing this.   

f10

1. (0x) FF-06-00-00-00-02-80-02-26-35
2. (0x) FF-06-00-00-00-02-80-02-40-36

f11

1. (0x) FF-06-00-00-00-02-80-02-59-37
2. (0x) FF-06-00-00-00-02-80-02-5A-38

This shows that the parameter value itself is not a repetition (0x3526 and 0x3640 for f10 /  0x3759 and 385A for f11) but the interpretation of it is. 

So if you write those arrays to UUID: 5DD3465F-1AEE-4299-8493-D2ECA2F8E1BB you will see that you will also get two versions of f10 and f11 respectively.

[webrunner5]

I hope there is not a test for all of this! ?

[BTM_Pix]

4 hours ago, webrunner5 said:

I hope there is not a test for all of this! ?

Don't worry, it will be quite an easy multiple choice one like this.

Q. Assuming an ISO value of 800 and a shutter speed of 1/48th of a second, what is the correct aperture setting for the scene below ?

1. f10
2. The other f10

[graphicnatured]

It's the other f10. Everyone knows that!

[webrunner5]

2 hours ago, BTM_Pix said:

Don't worry, it will be quite an easy multiple choice one like this.

Q. Assuming an ISO value of 800 and a shutter speed of 1/48th of a second, what is the correct aperture setting for the scene below ?

1. f10
2. The other f10

You know I have never had to interview on a set like that. I can't imagine how a person would not be intimidated, and could relax, and be yourself!

[graphicnatured]

39 minutes ago, webrunner5 said:

You know I have never had to interview on a set like that. I can't imagine how a person would not be intimidated, and could relax, and be yourself!

It would be even more difficult when the person you're engaging with seems to have Mickey Mouse ears. ?

[CaptainHook]

Looked into this and the steps that some lenses report will result in a value that's smaller than the precision of the numbers we show. So for instance the lens may allow two settings around f14 where the "second" one is still closer to f14 than f15 so we display both as f14. The opposite can also happen where some lenses will report settings where it DOES fit in a our precision to show two different values but the lens doesn't actually change aperture enough to see any difference. We assume Panasonic etc know of these settings across the lenses and compensate/ignore them etc as necessary in their cameras.

[BTM_Pix]

6 hours ago, CaptainHook said:

 

 We assume Panasonic etc know of these settings across the lenses and compensate/ignore them etc as necessary in their cameras.

Aren't BM themselves part of that  'Panasonic etc' group though as the original Pocket camera works in that way too?

I do understand that there isn't actually a 'fault' here as such (aside from the odd glitch when fast scrolling or the occasional mismatch on the iOS app) as its expected behaviour because of the way the values are being interpreted but there is an argument to be made regarding the difference between expected behaviour and desired behaviour.

Obviously, I might well possibly be in a small minority of one over this not being desired behaviour as it doesn't seem to unduly concern other owners that they have these anomalies.

However, the question would be if it will remain this way in the Pocket4K or be changed to the way in which it works with other manufacturers including yourselves with the original Pocket?