Cristiano Coelho

Most likely related that one mode takes the picture from the camera, and another one just captures from the preview. The preview is always lower quality than the final capture....

Here's another "danger" of using the fast capture options: 

Another comparison using none and boost. You can see the boost mode pretty much skips any software processing from the camera. This is very noticeable on a pixel 2 that...

Thanks for the updates @Boris-c !. About picture quality, the difference is really not that significant. It becomes more obvious when using the focus feature since that makes a whole...

> @kperreau The `mirrorImage` option could easily be handled by patching the code. > > But more generally, my personal opinion is that the set of options is a bit...

Interesting, is this from the latest version? I haven't really noticed any delay after authorization is granted. Would this trigger a double render?

Looks great! What about iOS? Do we have the same issue there?

@chiubaka do you really need all the orientation detection code? The camera views/implementation already use an existing class/helper to do so (https://github.com/react-native-camera/react-native-camera/blob/master/android/src/main/java/com/google/android/cameraview/DisplayOrientationDetector.java). Have you checked if there's a performance impact...

Hey, great answers, I think it makes sense! About DisplayOrientationDetector, it is already being used for as long as the camera is mounted (camera1 and camera2), so I thought it...

I haven't had linking errors, not sure what's the problem. El jue., 13 de febrero de 2020 18:02, Sibelius Seraphini < [email protected]> escribió: > @cristianoccazinsp is this a > problem...