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

[BUG] Rotation incorrect when using Raw Media Stream #1519

Open
3 tasks done
kylefoley opened this issue Apr 14, 2023 · 4 comments
Open
3 tasks done

[BUG] Rotation incorrect when using Raw Media Stream #1519

kylefoley opened this issue Apr 14, 2023 · 4 comments
Assignees
Labels
Communication customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@kylefoley
Copy link

kylefoley commented Apr 14, 2023

Describe the bug
When using the Getting Started repo and adding the Add Raw Media Access code to it, the rotation viewed on the receiving end is incorrect.

To Reproduce
Here is a fork with the "Raw Media Access" code added. To run it on iOS, don't forget to add your ID Token in ContentView.swift.

To reproduce, deploy/run this code on iOS. You may need to tweak the roomId to have it go to your own room. You can then join the room with a desktop browser to view the incorrectly rotated video.

https://github.com/Imajion/communication-services-ios-quickstarts/tree/main/Add%20Video%20Calling

Code Snippet
Not sure where the issue lies. The video looks properly cropped, just the rotation is incorrect

Expected behavior
The iPhone video correctly renders on the remote end, including rotation and scaling.

Screenshots
Screenshot 2023-04-13 at 8 35 42 PM

Screenshot 2023-04-13 at 8 35 57 PM

Setup (please complete the following information):

  • OS: iOS 16.5
  • IDE : XCode 14.3
  • Version of the Library used:
    • AzureCommunicationCalling (2.3.0-beta.4):
    • AzureCommunicationCommon (1.1.1)

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

  • Bug Description Added
  • Repro Steps Added
  • Setup information Added
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Apr 14, 2023
@tjprescott
Copy link
Member

@raosanat can you please take a look?

@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Apr 14, 2023
@kylefoley
Copy link
Author

@raosanat Let us know if you need any more information, thanks!

@kylefoley
Copy link
Author

Hi @raosanat, any update on this issue? Thank you

@raosanat
Copy link
Member

raosanat commented May 9, 2023

Hi, we are working on a releasing a version with fix. Will update you soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Communication customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

3 participants