Audio input API extension
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- api, audio-video-rtc
Research direction
This issue names no files, entry points, or tests and is framed as an open discussion. Start by locating the existing emulator input API and reviewing how microphone permissions would be represented. Before implementation, the project needs agreement on audio representation, metadata, resampling or normalization, and privacy permission behavior.
Written by the indexing model from the issue text.
Description
Some platforms support microphone input devices, the most well-known being the original Famicom controller. Emulators currently handle it via button presses, but true audio input could be made available through the API, which would allow emulators to at least implement some basic processing without having to handle capture themselves.
My initial thought is to simply provide raw audio frames with metadata (number of channels, frequency range, depth, etc.). Alternatively, resample/normalize input and provide data in a simpler representation, e.g. amplitude mean and extrema for each frame. I would like to open a discussion with this issue.
<Autechre> if we do add it hough
<Autechre> it has to become a Privacy feature
<Autechre> that people have to give permission to
- Dominant language
- C
- Stars
- 180
- Forks
- 99
- Avg merge
- 7d 5h
- Merged PRs (30d)
- 2
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 libretro/libretro-common
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
libretro/libretro-common#220 · 1 comment · 1 reaction ·
-
RETRO_ENVIRONMENT_ clash in libretro.hMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libretro/libretro-common#89 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
libretro/libretro-common#223 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
libretro/libretro-common#221 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
libretro/libretro-common#213 ·
All issues in libretro/libretro-common
Similar issues
-
native-cpu: -Wreturn-type in skainet_row_threads.c:150 (worker fn has no return)Possibly taken @Doomguy-BFG9000 claimed this today. Opengood first issue size:xs skill:native
Difficulty 1/5 Under an hour Newbie friendliness 78/100
SKaiNET-developers/SKaiNET#1358 · 1 comment ·
Maintainers usually reply within 1 day
-
I/O internal correctness medium priority rt_lib
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
libsdl-org/SDL#16539 ·
Maintainers usually reply within 1 day
-
git-workflow task-4
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day