Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Landscape recording is cropping the screen width (content) of the android application #98

Open
sagarpatel288 opened this issue Jun 24, 2021 · 1 comment

Comments

@sagarpatel288
Copy link

sagarpatel288 commented Jun 24, 2021

Changing the orientation mode from portrait to landscape in an Android application while screen recording is going on, is cropping the screen width (content) of the Android application for the landscape mode in the generated recording file

  1. Chime android SDK version: 0.11.4
  2. [Screen recording api] (https://github.com/aws-samples/amazon-chime-sdk-recording-demo)
  3. Device: Samsung SM-E625F (Galaxy F62)
  4. Device Resolution: 1080 width * 2400 height (Portrait Mode)
  5. Device Android Version: 11

What we are doing?

We are making a meeting application for Android that has a recording feature (record meeting) similar to Amazon chime and zoom.

The screen recording is happening from our Android Application (within Android application) using amazon screen recording API(https://github.com/aws-samples/amazon-chime-sdk-recording-demo) and it is there to record the screen of the Android application only. We are asking the end-user to grant permission to record the screen. So, what we are doing is:

  1. We start sharing the content from our Android application as described here: https://github.com/aws/amazon-chime-sdk-android/blob/master/guides/content_share.md
  2. We are calling the screen recording start and stop API from within the Android application.
  3. It is recording the screen and audio (of the chime meeting) too.
  4. However, if the application is in portrait mode when we start screen recording and if the orientation keeps getting changed from portrait to landscape and vice-versa, the screen of the android application (not of the web page, not of any inbuilt android browser too) in the recorded file is being cut (cropped) for the landscape mode.

This can be a cross-platform issue where both the Android team and the web team may need to work collaboratively.

Describe the solution you'd like

  1. Changing the device orientation frequently from portrait to landscape mode and vice-versa while screen recording is going on should not crop the screen width for the landscape mode in the recorded file.
  2. Resolution in portrait mode for an Android application can be improved. If there are some fonts having a text size of 14sp, they are not properly readable, not clear in the recorded file.
  3. If this is happening because of the scale and aspect ratio Amazon is using with FFmpeg, then this is the link that can be helpful

https://superuser.com/questions/547296/resizing-videos-with-ffmpeg-avconv-to-fit-into-static-sized-player/1136305#1136305

We want similar behaviour.

  1. Amazon can provide an optional "FFmpeg" configuration in start post request failing which will fall into default configuration.

Describe alternatives you've considered
N/A.

Additional context
Unfortunately, I cannot upload screenshots as it is a private and protected property.

Let me know if you need more information and thank you so much for the amazing chime SDK.

@tenge-amzn
Copy link

Chime SDK team has launched a new service to provide meeting capture capabilities with original video resolution and frame rate. You will not need to provision your own container infrastructure. Instead, just call the API from AWS SDK and provide a prepared S3 bucket to receive the artifacts.

To know more, please check out the blog:
https://aws.amazon.com/blogs/business-productivity/capture-amazon-chime-sdk-meetings-using-media-capture-pipelines/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants