Suggested Description
Describe the bug
Since version 0.6.10, a cutoff delay was introduced after pressing the recording button. For power/fast users, this feels like a physical interruption and significantly degrades the experience.
Expected behavior (pre-0.6.10)
In version 0.6.9, pressing the button immediately started recording with no cutoff delay. This allowed for quick, spontaneous dictation — especially valuable for users who trigger recordings in rapid succession.
Actual behavior (0.6.10+)
A cutoff now occurs after the button is pressed. As a fast user, this creates a noticeable and frustrating pause before recording starts.
Context / Root cause hypothesis
I understand the cutoff was introduced to prevent double-pressing... i.e., the red indicator showing twice and locking the app. However, double-pressing was not a common issue for me and did not require a fix. In my opinion, the cure is worse than the disease: the fix sacrificed spontaneity to solve a problem most fast users never encounter.
Steps to reproduce
Press the recording hotkey quickly and repeatedly
Notice the delay/cutoff between button press and recording start
Version
Affected: 0.6.10+
Working: 0.6.9
Request
Consider making the cutoff optional via a setting, or reverting the behavior for users who want the raw, instant-response experience of 0.6.9.
Suggested Description
Describe the bug
Since version 0.6.10, a cutoff delay was introduced after pressing the recording button. For power/fast users, this feels like a physical interruption and significantly degrades the experience.
Expected behavior (pre-0.6.10)
In version 0.6.9, pressing the button immediately started recording with no cutoff delay. This allowed for quick, spontaneous dictation — especially valuable for users who trigger recordings in rapid succession.
Actual behavior (0.6.10+)
A cutoff now occurs after the button is pressed. As a fast user, this creates a noticeable and frustrating pause before recording starts.
Context / Root cause hypothesis
I understand the cutoff was introduced to prevent double-pressing... i.e., the red indicator showing twice and locking the app. However, double-pressing was not a common issue for me and did not require a fix. In my opinion, the cure is worse than the disease: the fix sacrificed spontaneity to solve a problem most fast users never encounter.
Steps to reproduce
Version
Request
Consider making the cutoff optional via a setting, or reverting the behavior for users who want the raw, instant-response experience of 0.6.9.