Have something to say?

Tell us how we could make the product more useful to you.

Completed

Hands free mode(?) / Accessibility issue with sites like Google Docs

Hi! i've been trying to use the software as an alternative to Wispr. I noticed when I'm using hands free mode, haven't tested it out with the other modes because of physical disability - when I tap the hotkey to have it start transcribing it will stop registering me as on a Google doc for example. The blinking typing indicator will freeze essentially. Like, I will have to re click on the google doc to have it be aware to actually send the transcribed material onto it. If I don't, nothing will be typed and I'll have to redo everything. I'm using this with foot pedals as an accessibility aid because I can't type well due to issues with my wrists so having to click to coordinate where my words are sent is a bit of an issue!

Throwaway5325 7 days ago

3

Completed

Start a new paragraph with custom instructions

Ciao guys, love Vowen, coming from Wispr Flow. The biggest missing feature, for an e-mail writer like me, is for sure the skill of creating a new paragraph when it recognizes a new topic. I tried to force it with Custom Instruction (paste below it), but I’m still forced to manually refine it before sending. Am I missing something maybe, or could this be considered as a new feature? For context: I’m using Whisper Large v3 Turbo by Groq + Gemini 2.5 flash lite via Openrouter. Thanks! Custom Instruction given: { "system_instruction": { "role_definition": { "role": "Structural Text Architect & UX Content Editor", "objective": "Transform raw, noisy voice-to-text transcriptions into professionally formatted Italian text with aggressive paragraph segmentation and zero leading whitespace." }, "technical_constraints": { "no_leading_spaces": "CRITICAL: The output must start exactly at character index 0. Absolutely no spaces, tabs, or newlines before the first word.", "aggressive_paragraphing": "Force segment the text into short, readable paragraphs using double newlines (\\n\\n). Trigger a new paragraph at every topic shift or transition word (e.g., 'Inoltre', 'Quindi', 'Per quanto riguarda').", "signature_rule": "In email closings, the name must be on a new line and MUST NOT be followed by a period or any punctuation.", "clean_output_only": "Output only the processed text. Do not include conversational filler, meta-talk, or introductions." }, "operational_workflow": { "step_1": "De-noising: Remove Italian vocal fillers (ehm, allora, cioè, diciamo) and speech self-corrections.", "step_2": "Syntax Repair: Fix Italian grammar, verb agreements, and punctuation within sentences.", "step_3": "Structural Splitting: Identify semantic breaks and apply double newlines (\\n\\n) to ensure visual separation.", "step_4": "Signature Sanitization: Ensure the final line (the name) is punctuation-free.", "step_5": "Final Trimming: Strip all leading/trailing whitespace from the entire payload." }, "few_shot_examples": [ { "input": "buongiorno allora per il progetto va bene tutto però dobbiamo aggiungere quella clausola inoltre mi serve che mi mandi i documenti grazie claudio.", "output": "Buongiorno,\n\nper il progetto va bene tutto, però dobbiamo aggiungere quella clausola.\n\nInoltre, mi serve che mi invii i documenti.\n\nGrazie\nClaudio" } ], "output_configuration": { "encoding": "UTF-8", "newline_character": "\\n\\n", "start_index": 0 } } }

Claudio Grimoldi 22 days ago

4

Rejected

Make it Open Source

Hey. Thanks for the awesome tool. Not exactly a feature request. And I believe you have your reasons for not open sourcing it. But nevertheless I wanted to share a perspective you may not have considered. There are a ton of other similar solutions out there of various degrees of polish. And the heart of all of them (including Vowen) is those open-weight models anyway. So the fundamental technology you and others use is not a trade secret. While commitment to do the processing locally and/or with the user-configured providers, and not send user data to the developers sounds great, it's not really easily verifiable. It basically makes Vowen impossible to get a permission to use Vowen in an enterprise environment where information security standards are high. For closed source solutions the matter of trust is often solved through certifications (SOC2, ISO etc). However this is clearly not a viable solution for a side project worked by a team of 2 (both due to overhead to manage processes and cost of such certifications). This effectively narrows down the possible user base. Now,if you're looking to monetize your app in the future, it may be worth to learn from many AI-powered open source tools out there (OpenCode, Kilo Code etc.). They often have the end user app open source, but provide paid a control plane for enterprises to centrally manage their users and their licenses instead of having to issue and rotate individual tokens to each employee. So, I hope you'll at least give this idea another thought. Thanks again for building Vowen. Alex

Alexandr Zolotukhin 24 days ago

1

Completed

Unexpected behaviors in keyboard shortcut config in Windows

A couple of unexpected behaviors when trying to configure my shortucts in the Windows app: The keys show up as Mac keys (command, option, etc). I couldn’t find a setting to change them but then again, this is a Windows app, they should be Windows keys by default, no? I set up the transcription hotkey shortcut (ctrl+Win). Then I wanted to set Ctrl+Win+Space as my hands-free shortcut, emulating what I had in Wispr Flow. But when I press the combination to try to set the hands-free, since it´s already assigned to the transcription shortcut, it will activate the transcription and when I let go, it adds (Command + V) to the shortcut. After some fiddling around I discovered that I can press the keys one by one and build the shortcut that way, which worked, but it wasn’t my first thought to do it like that and I´m pretty sure for most apps you just press the combination of keys as you would when activating the shortcut. Even after setting the shorcuts the way I wanted, they don´t work as expected or as they do in Wispr Flow which I found super useful, this would be a nice addition! 1. You press Ctrl+Win to activate transcription 2. While those are held down, you can hit spacebar to “lock” it into hands-free mode 3. If you’re holding down Ctrl+Win after some time (it’s probably like 10 seconds or so) it will show a small message above the audio waveform indicator suggesting that you can press spacebar to lock it into hands-free mode.

Adrian Pauly 25 days ago

2