Call recording seems to ignore camera orientation/aspect
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure
- Domain
- audio-video-rtc
Research direction
Use the issue description and attached ACS_Recording screenshot to confirm the portrait crop and quality concerns. No files, entry points, or tests are named, so first identify the call-recording implementation and relevant tests, then define acceptance criteria for aspect-fit behavior and preserved resolution.
Written by the indexing model from the issue text.
Description
Call recording is really cool!
Minor issue: the screenshot attached is from a recording of a group call, with just one participant(iphone). This participant had his camera in portrait mode, but recording seems to cut top and bottom and force a landscape frame from the "middle" of the original feed. I hope there can be a way to specify that you want "aspectfit" for participants feeds!
Also: the feed seemed more grainy and with less quality than what we expected, is there a loss of resolution when saving the video?
- Dominant language
- No language data
- Stars
- 339
- Forks
- 113
- Avg merge
- 36m
- Merged PRs (30d)
- 1
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 Azure/Communication
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Azure/Communication#600 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/Communication#599 · 4 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Azure/Communication#598 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure/Communication#543 ·
-
Needs: triage :mag:
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/Communication#447 ·
All issues in Azure/Communication
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelscope/FunASR#3762 ·
Maintainers usually reply within 1 day
-
comp/plugins P3 tool/tts type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#133131 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
savonet/ocaml-ffmpeg#120 ·
-
publish: since #3934 every getUserMedia rejection is terminal, so a transient NotReadableError (device busy) is never retried, although Retry still documents that a failed reopen spends budgetPossibly taken A pull request linked to this issue is open or already merged. Openquest
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
check:passed streams:remove
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day