[FEATURE] Volume Ducking
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
The issue names no files, tests, or entry points. Start by reading the repository's audio playback and stream-handling code, then identify how audio sources and volume changes are currently managed. Before implementation, clarify the design for source priorities, configuration, and fade behavior; done means eligible background audio ducks smoothly during configured triggers and returns to its prior volume afterward.
Written by the indexing model from the issue text.
Description
Problem
Add a volume ducking feature that automatically lowers the volume of other audio sources when important audio is detected, such as a person speaking during a meeting, a notification, or system-generated speech. Once the important audio ends, the previous volume level should be restored smoothly.
Proposed solution
Implement an audio ducking system that monitors active audio streams and dynamically reduces the volume of background audio when a higher-priority audio source becomes active.
- Users should be able to configure:
- Whether volume ducking is enabled.
- How much the background audio volume is reduced.
- Which audio sources should trigger ducking.
- Which applications or audio sources should be affected.
- How quickly the volume fades down and returns to normal.
The system should restore the original volume automatically after the triggering audio ends and avoid sudden or noticeable volume jumps.
Alternatives considered
No response
- Dominant language
- Swift
- Stars
- 11.9k
- Forks
- 863
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 27
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 altic-dev/FluidVoice
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
altic-dev/FluidVoice#1149 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 40/100
altic-dev/FluidVoice#1148 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
altic-dev/FluidVoice#1147 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 55/100
altic-dev/FluidVoice#1146 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
altic-dev/FluidVoice#1144 · 1 comment ·
Maintainers usually reply within 1 day
All issues in altic-dev/FluidVoice
Similar issues
-
swift.md: `Date(myString, strategy: .iso8601)` example omits `try` — the initializer is throwingOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
core: RAC_LLM_OPTIONS_DEFAULT.min_p disagrees with the IDL's annotated defaultPossibly taken A pull request linked to this issue is open or already merged. Openbug core p3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
RunanywhereAI/runanywhere-sdks#1083 ·
Maintainers usually reply within 5 days
-
area: docs eco: swift good first issue help wanted lane: free-agent roadmap size: XS type: docs
Difficulty 1/5 Under an hour Newbie friendliness 62/100
arminazimi/evergreen#441 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nightscout/nightguard#368 ·