Frame image size issue
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- audio-video-rtc, mobile
Research direction
Start from the camera2 source setup in the CameraFragment example, where the image listener, width, height and rotation are configured, and check how rotation 90 changes the reported output size. Reproduce with width 1920, height 1080, rotation 90 and confirm the image comes back 1080x1080. Done means the output keeps the rotated dimensions (1080x1920) without changing the landscape behaviour at rotation 0.
Written by the indexing model from the issue text.
Description
Describe the bug
When I set the rotation to 90, the width and height of the image obtained from the camera2 source are the same.
To Reproduce
Steps to reproduce the behavior:
- Go to 'CameraFragment' and add imageListener
- Set: width = 1920, height = 1080, rotation = 90
- The resulting image has a width and height of 1080
Smartphone (please complete the following information):
- Library version [e.g. 2.6.6]
- Device: [Honor X50, vivo Y36c]
- OS: [Android13/14]
Additional context
- I changed the rotation to 90 because I wanted to get a vertical recorded video, and I accidentally discovered this problem.
- If I don't change it, for example, if the preview resolution is 1920x1080 and rotation=0, the recorded video resolution is 1920x1080, but I want the video to be 1080x1920, is there any other way to achieve this?
- If I don't directly modify the code, but instead manipulate Orientation through the UI, the above problem won't occur, and the image size will be 1920x1080.
- Dominant language
- Kotlin
- Stars
- 3k
- Forks
- 946
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 9
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pedroSG94/RootEncoder
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
pedroSG94/RootEncoder#2213 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
pedroSG94/RootEncoder#2207 · 1 reaction ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
pedroSG94/RootEncoder#2203 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
pedroSG94/RootEncoder#2192 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
pedroSG94/RootEncoder#2177 · 44 comments ·
Maintainers usually reply within 2 days
All issues in pedroSG94/RootEncoder
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
SLNE-Development/surf-chat#134 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100