[BUG]
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by tracing the push-to-talk release flow and the code that transfers dictated text into the active app, especially where FluidVoice interacts with the macOS clipboard. Reproduce the issue by copying unrelated text or an image before recording, then releasing the button. Done means dictated text is inserted reliably without replacing it with the previous clipboard contents.
Written by the indexing model from the issue text.
Description
Describe the bug
with the new version: When I release the push to talk button, it pastes in whatever I had previously copied. It does not do this regularly; it is quite sporadic.
Today I rolled back to the previous version and it stopped doing this, so the newest version is definitely the problem.
Reproduction steps
Copy something like text or an image completely unrelated to FluidVoice.
Press the record button on FluidVoice and do some talking.
Release the push to talk button when you're done talking, and it just pastes in whatever you had previously copied.
It does not put in the text that I was dictating.
Expected behavior
The text that I just spoke should be placed into the area when I release the push to talk button.
Actual behavior
Copy something like text or an image completely unrelated to FluidVoice.
Press the record button on FluidVoice and do some talking.
Release the push to talk button when you're done talking, and it just pastes in whatever you had previously copied.
It does not put in the text that I was dictating.
App Version
latest
macOS Version
Tahoe 26.6.2
Architecture
Apple Silicon
Logs or crash report
Screenshots or screen recording
No response
- Dominant language
- Swift
- Stars
- 11.9k
- Forks
- 863
- Avg merge
- 1d 12h
- 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
-
[BUG] File transcription skips audio chunks shorter than one secondPossibly taken @sabbah13 claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
altic-dev/FluidVoice#1161 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
altic-dev/FluidVoice#1170 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
altic-dev/FluidVoice#1169 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
altic-dev/FluidVoice#1168 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
altic-dev/FluidVoice#1165 · 1 comment ·
Maintainers usually reply within 1 day
All issues in altic-dev/FluidVoice
Similar issues
-
ace documentation
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
githubnext/desktop-tools#104 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
type: cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
googleapis/google-cloud-swift#1477 ·
Maintainers usually reply within 1 day
-
product / auth product / console product / databases product / messaging product / self-hosted product / sites product / storage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
P1 status: first-line-handled status: needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
a2ui-project/a2ui#3282 · 1 comment ·
Maintainers usually reply within 2 days