Jonathan J.

Ohhhh, good catch! It actually doesn't depend on the codec. My phone doesn't support bitrates higher than 80 Mbps. Since I didn't set a default bitrate, it was taking the...

Wow, you're so fast! 😊 I just tested. Unfortunately, I encountered another error. ``` {"cause": {"message": "Error retrieving camcorder profile params", "stacktrace": "java.lang.RuntimeException: Error retrieving camcorder profile params at android.media.CamcorderProfile.native_get_camcorder_profile(Native...

It works with this format `{ ...other, "videoHeight": 2056, "videoWidth": 3648 }` but not with `{ ...other, "videoHeight": 2736, "videoWidth": 3648 }`.

Actually, the format with { "videoHeight": 2736, "videoWidth": 3648 } works fine. I just checked the resolution of the recorded video, and it's correct (2736x3648), so we can keep this...

Just to make sure we understand each other well, I say it's not supported because calling CamcorderProfile.get(cameraIdInt, quality) with quality=QUALITY_4KDCI throws an exception (Error retrieving camcorder profile params ...). But...

Hey, I've just started integrating react-native-vision-camera v3 into my project (i'm currently using react-native-camera) and encountered some issues related to aspect ratio on Android (similar to the problem described in...

I don't know what's the best way to look at it. Currently, in "portrait" mode (let's say you hold the phone normally in your hands) : - on a device...

Yes, you're right, so it makes more sense to use the true orientation (the one that takes into account the sensor's orientation). As long as the rotations are the same...

**About the accelerometer** The values reported by the accelerometers are measured in increments of the gravitational acceleration, with the value 1.0 representing an acceleration of 9.8 meters per second (per...

I updated my pull request to include the various changes and to fix other issues I hadn’t noticed yesterday. I tested on different iOS devices (iOS 17 or earlier), with...