Google Calendar Integration and Automatic Recording
I'd like Vowen to connect to Google Calendar so that when a scheduled meeting starts, Vowen starts recording it. At the moment every recording depends on me remembering to open the app and press start. If I forget, the meeting is gone. There's no going back for it afterwards. This is the main thing I'm missing from Granola. The meeting sits in my calendar, Granola knows it's happening, and the recording starts with the meeting. I don't have to think about it. What I'm asking for: Read-only access to Google Calendar Vowen recognises that a scheduled meeting is starting It begins recording, either automatically or with a one-click prompt if you'd rather not start unattended The note is titled from the calendar event, so I can find it later Most of this already exists. There's meeting detection that triggers when an app starts using the microphone, and it can prompt to take notes. What it can't do is know that a meeting was scheduled, when it was due to start, or what it's called. The calendar connection looks like the missing piece rather than a rebuild. Read-only would be enough. I don't need Vowen writing to my calendar, joining calls or contacting attendees. I'm assessing Granola and Vowen side by side, specifically on meeting note capture and summarisation of transcripts. This is the main gap.
Ian 5 days ago
Google Calendar Integration and Automatic Recording
I'd like Vowen to connect to Google Calendar so that when a scheduled meeting starts, Vowen starts recording it. At the moment every recording depends on me remembering to open the app and press start. If I forget, the meeting is gone. There's no going back for it afterwards. This is the main thing I'm missing from Granola. The meeting sits in my calendar, Granola knows it's happening, and the recording starts with the meeting. I don't have to think about it. What I'm asking for: Read-only access to Google Calendar Vowen recognises that a scheduled meeting is starting It begins recording, either automatically or with a one-click prompt if you'd rather not start unattended The note is titled from the calendar event, so I can find it later Most of this already exists. There's meeting detection that triggers when an app starts using the microphone, and it can prompt to take notes. What it can't do is know that a meeting was scheduled, when it was due to start, or what it's called. The calendar connection looks like the missing piece rather than a rebuild. Read-only would be enough. I don't need Vowen writing to my calendar, joining calls or contacting attendees. I'm assessing Granola and Vowen side by side, specifically on meeting note capture and summarisation of transcripts. This is the main gap.
Ian 5 days ago
Small Improvement
Hey — found Vowen through a Reddit thread today and have been trying it out. Really liking it so far. One small transcription gap I noticed: when I say something like “August nineteenth,” it outputs “August nineteenth” rather than “August 19th.” Would be great if spoken dates could automatically normalize into their natural written format. Just wanted to flag it since it stood out while using it.
Millionaire 5 days ago
Small Improvement
Hey — found Vowen through a Reddit thread today and have been trying it out. Really liking it so far. One small transcription gap I noticed: when I say something like “August nineteenth,” it outputs “August nineteenth” rather than “August 19th.” Would be great if spoken dates could automatically normalize into their natural written format. Just wanted to flag it since it stood out while using it.
Millionaire 5 days ago
Enter pressed decided per transcription
There's an option to always have enter pressed after the transcription is done. It'd be nice if there were two different shortcuts/paths during transcription that could enable or disable the enter press just because most of the times I want enter to be pressed, but sometimes it's a more sensitive message that I will be revising.
Emily 11 days ago
Enter pressed decided per transcription
There's an option to always have enter pressed after the transcription is done. It'd be nice if there were two different shortcuts/paths during transcription that could enable or disable the enter press just because most of the times I want enter to be pressed, but sometimes it's a more sensitive message that I will be revising.
Emily 11 days ago
Export transcript as word-level JSON with per-word timestamps
The transcribe tool already exports as text, subtitles, PDF, plain text, Markdown, SRT, and VTT — that covers most of what I need. The one format I'd love to see added is a word-level JSON export, where every single word has its own start/end timestamp, rather than grouping multiple words or sentences into one timestamp block (like SRT/VTT do). Adobe Premiere Pro already supports this kind of export. Having it in Vowel would help in two main cases: YouTube chapter/timestamp generation. Feeding an AI the current subtitle export gives it far fewer timestamp anchors, since each block often spans multiple sentences. A word-level JSON gives the AI enough granularity to place chapter markers exactly when a topic starts — instead of chapters that start or end mid-sentence because the underlying block was too coarse. Motion graphics / animation timing. When converting a design into a motion graphic to sync with a video, having every word's exact timestamp means I know precisely when to trigger each animation, instead of estimating from a block-level subtitle. This is achievable today by exporting from Premiere Pro instead, but since I'm already using Vowel's transcription for the whole session, having this JSON export available directly from Vowel would save a full extra step.
Dio 14 days ago
Export transcript as word-level JSON with per-word timestamps
The transcribe tool already exports as text, subtitles, PDF, plain text, Markdown, SRT, and VTT — that covers most of what I need. The one format I'd love to see added is a word-level JSON export, where every single word has its own start/end timestamp, rather than grouping multiple words or sentences into one timestamp block (like SRT/VTT do). Adobe Premiere Pro already supports this kind of export. Having it in Vowel would help in two main cases: YouTube chapter/timestamp generation. Feeding an AI the current subtitle export gives it far fewer timestamp anchors, since each block often spans multiple sentences. A word-level JSON gives the AI enough granularity to place chapter markers exactly when a topic starts — instead of chapters that start or end mid-sentence because the underlying block was too coarse. Motion graphics / animation timing. When converting a design into a motion graphic to sync with a video, having every word's exact timestamp means I know precisely when to trigger each animation, instead of estimating from a block-level subtitle. This is achievable today by exporting from Premiere Pro instead, but since I'm already using Vowel's transcription for the whole session, having this JSON export available directly from Vowel would save a full extra step.
Dio 14 days ago
Lowering the sound
Currently, while dictating, we have three options: we can either pause the media, mute the sound completely, or do nothing with it. I think a very useful option would be the ability to lower the sound by a set percentage, for example by 50% during dictation, when we do not want to turn the sounds off completely, but only want them to be quieter.
Miersetnik 16 days ago
Lowering the sound
Currently, while dictating, we have three options: we can either pause the media, mute the sound completely, or do nothing with it. I think a very useful option would be the ability to lower the sound by a set percentage, for example by 50% during dictation, when we do not want to turn the sounds off completely, but only want them to be quieter.
Miersetnik 16 days ago
Raycast Hyper Key compatibility issue on macOS
hen I set a Vowen shortcut to ⌃⌥⇧⌘ + , it works if I press the modifiers physically. However, the same shortcut does not trigger when using Raycast's Hyper Key (Caps Lock → Hyper), even though Vowen records the shortcut correctly and Raycast recognizes it. Could you investigate compatibility with Raycast's Hyper Key?
Rok 17 days ago
Raycast Hyper Key compatibility issue on macOS
hen I set a Vowen shortcut to ⌃⌥⇧⌘ + , it works if I press the modifiers physically. However, the same shortcut does not trigger when using Raycast's Hyper Key (Caps Lock → Hyper), even though Vowen records the shortcut correctly and Raycast recognizes it. Could you investigate compatibility with Raycast's Hyper Key?
Rok 17 days ago
DoubleTap Shortcuts
I have seen similar apps where you can use double-tap shortcuts. So, rather than having a shortcut to hold and a hand free one, you can just hold or double tap for hand free. Ideally, you can also hold, then doubletap to go from hold to handfree. Benefit: on button only, easy, simple, user friendly.
Xavier 18 days ago
DoubleTap Shortcuts
I have seen similar apps where you can use double-tap shortcuts. So, rather than having a shortcut to hold and a hand free one, you can just hold or double tap for hand free. Ideally, you can also hold, then doubletap to go from hold to handfree. Benefit: on button only, easy, simple, user friendly.
Xavier 18 days ago
Bug: Global hotkey recorder captures the wrong key on non-US keyboard layouts (e.g. French AZERTY)
Environment Vowen version: 0.5.1 OS: Windows 11 Keyboard layout: French (France) AZERTY Description When recording a shortcut in the "Enregistrer le raccourci" (Change Shortcut) dialog and pressing the physical key that produces ² on an AZERTY keyboard (top-left key, next to 1), the dialog does not display or capture ². Instead it shows/records something resembling a quote/accent character. Steps to reproduce Switch Windows keyboard layout to French (France). Open Vowen → Settings → any hotkey (e.g. Hands Free) → "Change Shortcut". Press the physical key that types ² (top-left, next to 1). Expected behavior The recorder captures/displays ², and the resulting shortcut reliably triggers when that physical key is pressed later. Actual behavior The recorder shows a different glyph (looks like an isolated accent/quote mark), not ². Root cause (confirmed at the Windows API level) I traced this down to the OS keyboard layout mapping, not app logic at first, so this reproduces on any layout, not just AZERTY. On the French layout, scan code 0x29 (the physical key that types ²) maps to Virtual Key 0xDE, verified via MapVirtualKeyEx(0x29, MAPVK_VSC_TO_VK_EX, hkl) on the active French HKL. 0xDE is VK_OEM_7, which is hardcoded in most keyboard libraries (including the bundled keyspy dependency — see WinGlobalKeyLookup[0xDE]) with the US-centric generic name "QUOTE", because on a US QWERTY layout VK_OEM_7 is the apostrophe key. So the recorder is displaying the generic US name for the virtual-key slot, not the character actually produced by the physical key on the active layout. GetKeyNameTextW for the same scan code correctly resolves to ², confirming the OS itself knows the right label, it's the app's key-naming table that doesn't. Suspected secondary issue (needs dev confirmation, not fully verified on my end) The app appears to use two different keyboard libraries: keyspy (VK-code based, layout-aware) for the shortcut recorder UI. uiohook-napi (scan-code/physical-position based, layout-independent) for the actual background global-hotkey listener, based on strings like "Backquote" found in its keycode table for this same physical key. If the recorder stores the keyspy-derived name (e.g. "OEM_7") but the runtime listener matches against uiohook-napi-derived names (e.g. "Backquote"), the two would never agree for this class of key on non-US layouts, meaning a shortcut recorded this way might silently never fire even after being "saved" successfully. I wasn't able to fully confirm which naming scheme the live matcher uses at trigger time, but it's worth checking given the mismatch is real between the two bundled libraries' naming tables for OEM/punctuation-row keys. Suggested fix Resolve the key's display name and the stored identifier from the same source used by the background listener, so recorder output always matches what the listener will actually see. When storing an OEM/punctuation-row key, prefer the OS-resolved character (², `, etc., via GetKeyNameText or equivalent) over the hardcoded US-centric VK_OEM_* label, since that label is meaningless to a non-US user. This isn't AZERTY-specific: any layout where OEM-row keys don't match the US layout (German QWERTZ, Spanish, etc.) likely hits the same mismatc
Tqt 18 days ago
Bug: Global hotkey recorder captures the wrong key on non-US keyboard layouts (e.g. French AZERTY)
Environment Vowen version: 0.5.1 OS: Windows 11 Keyboard layout: French (France) AZERTY Description When recording a shortcut in the "Enregistrer le raccourci" (Change Shortcut) dialog and pressing the physical key that produces ² on an AZERTY keyboard (top-left key, next to 1), the dialog does not display or capture ². Instead it shows/records something resembling a quote/accent character. Steps to reproduce Switch Windows keyboard layout to French (France). Open Vowen → Settings → any hotkey (e.g. Hands Free) → "Change Shortcut". Press the physical key that types ² (top-left, next to 1). Expected behavior The recorder captures/displays ², and the resulting shortcut reliably triggers when that physical key is pressed later. Actual behavior The recorder shows a different glyph (looks like an isolated accent/quote mark), not ². Root cause (confirmed at the Windows API level) I traced this down to the OS keyboard layout mapping, not app logic at first, so this reproduces on any layout, not just AZERTY. On the French layout, scan code 0x29 (the physical key that types ²) maps to Virtual Key 0xDE, verified via MapVirtualKeyEx(0x29, MAPVK_VSC_TO_VK_EX, hkl) on the active French HKL. 0xDE is VK_OEM_7, which is hardcoded in most keyboard libraries (including the bundled keyspy dependency — see WinGlobalKeyLookup[0xDE]) with the US-centric generic name "QUOTE", because on a US QWERTY layout VK_OEM_7 is the apostrophe key. So the recorder is displaying the generic US name for the virtual-key slot, not the character actually produced by the physical key on the active layout. GetKeyNameTextW for the same scan code correctly resolves to ², confirming the OS itself knows the right label, it's the app's key-naming table that doesn't. Suspected secondary issue (needs dev confirmation, not fully verified on my end) The app appears to use two different keyboard libraries: keyspy (VK-code based, layout-aware) for the shortcut recorder UI. uiohook-napi (scan-code/physical-position based, layout-independent) for the actual background global-hotkey listener, based on strings like "Backquote" found in its keycode table for this same physical key. If the recorder stores the keyspy-derived name (e.g. "OEM_7") but the runtime listener matches against uiohook-napi-derived names (e.g. "Backquote"), the two would never agree for this class of key on non-US layouts, meaning a shortcut recorded this way might silently never fire even after being "saved" successfully. I wasn't able to fully confirm which naming scheme the live matcher uses at trigger time, but it's worth checking given the mismatch is real between the two bundled libraries' naming tables for OEM/punctuation-row keys. Suggested fix Resolve the key's display name and the stored identifier from the same source used by the background listener, so recorder output always matches what the listener will actually see. When storing an OEM/punctuation-row key, prefer the OS-resolved character (², `, etc., via GetKeyNameText or equivalent) over the hardcoded US-centric VK_OEM_* label, since that label is meaningless to a non-US user. This isn't AZERTY-specific: any layout where OEM-row keys don't match the US layout (German QWERTZ, Spanish, etc.) likely hits the same mismatc
Tqt 18 days ago
voice recognition
Recognize my own voice within transcription to always label my own voice/speech as me/you. Alternatively this probably could run based on audio channel or similar.
SH 21 days ago
voice recognition
Recognize my own voice within transcription to always label my own voice/speech as me/you. Alternatively this probably could run based on audio channel or similar.
SH 21 days ago
Selection of the window for recording a note
A very useful feature would be the ability to choose which window should be recorded when creating a note. Currently, as far as I can see, the entire system audio is being recorded, and it would be possible to set it up so that only a specific application or a specific application window is recorded, with the user’s microphone as an optional setting that can be toggled at any time
Miersetnik 26 days ago
Selection of the window for recording a note
A very useful feature would be the ability to choose which window should be recorded when creating a note. Currently, as far as I can see, the entire system audio is being recorded, and it would be possible to set it up so that only a specific application or a specific application window is recorded, with the user’s microphone as an optional setting that can be toggled at any time
Miersetnik 26 days ago
Built-in AI
Built-in AI would allow local model usage without relying on external providers, which would increase privacy, independence, and the predictability of the app’s behavior. A good direction would be the option to download a lightweight model, e.g. the smallest version of Gemma 4 (E2B or E4B), along with a simple choice between local and cloud modes. It would also be worth noting that this feature should be optional, so the user can decide for themselves about resource usage and where the model is stored.
Miersetnik 27 days ago
Built-in AI
Built-in AI would allow local model usage without relying on external providers, which would increase privacy, independence, and the predictability of the app’s behavior. A good direction would be the option to download a lightweight model, e.g. the smallest version of Gemma 4 (E2B or E4B), along with a simple choice between local and cloud modes. It would also be worth noting that this feature should be optional, so the user can decide for themselves about resource usage and where the model is stored.
Miersetnik 27 days ago
Easy tone change
It would be very useful to be able to change the tone in which we speak within the pill, for example by clicking the stars icon and being able to choose the appropriate tone
Miersetnik 27 days ago
Easy tone change
It would be very useful to be able to change the tone in which we speak within the pill, for example by clicking the stars icon and being able to choose the appropriate tone
Miersetnik 27 days ago
Unwanted auto-translation of English input to French
When I dictate in English, the output sometimes gets translated into French without any request to do so. This happens a few times a day and is disruptive to the workflow.
Xavier 27 days ago
Unwanted auto-translation of English input to French
When I dictate in English, the output sometimes gets translated into French without any request to do so. This happens a few times a day and is disruptive to the workflow.
Xavier 27 days ago
Choose between just 2 languages
I speak just two languages and I want to be able to use the app for both of them, but when I go into the language selection section, I can only choose between auto-select of a bunch of languages or choosing one single language. Is there a way to set it up so that the dictation only works for two (the auto-select almost never catches my Hebrew)? Alternatively, and maybe this is an easier fix, can you make a feature so that I can have a different shortcut trigger dictation in a different language? Or, perhaps have it so that whatever language my keyboard is currently set to, the dictation defaults to that language. Thanks!
Yonah Bar-Shain about 1 month ago
Choose between just 2 languages
I speak just two languages and I want to be able to use the app for both of them, but when I go into the language selection section, I can only choose between auto-select of a bunch of languages or choosing one single language. Is there a way to set it up so that the dictation only works for two (the auto-select almost never catches my Hebrew)? Alternatively, and maybe this is an easier fix, can you make a feature so that I can have a different shortcut trigger dictation in a different language? Or, perhaps have it so that whatever language my keyboard is currently set to, the dictation defaults to that language. Thanks!
Yonah Bar-Shain about 1 month ago
Ability to copy Notes transcript
I can copy the summary easily, but often it would be useful for me to be able to copy the whole transcript, but the UI only lets you select one fragment at a time. It would be nice to either be able to use the mouse to select the entire transcript or have separate buttons to copy transcript and copy summary.
Adrian Pauly about 2 months ago
Ability to copy Notes transcript
I can copy the summary easily, but often it would be useful for me to be able to copy the whole transcript, but the UI only lets you select one fragment at a time. It would be nice to either be able to use the mouse to select the entire transcript or have separate buttons to copy transcript and copy summary.
Adrian Pauly about 2 months ago
Completed
Delay in transcription start on Windows
The transcription does not start as soon as I press down the shortcut. I typically have to wait a second or two before the pill changes from the 3 dots to waveform (and makes the start noise). In this time, it catches nothing I say. I have this problem for a while now. It also still has the problem of missing out the last word a lot of the times. I am currently using the Ink 2 model, but I’ve tried with other models both cloud and local and the issue still persists. I even fully reinstalled the app, but the issue still remains. Is this expected or a bug? Windows 11. Vowen version 0.4.9
GoatBro about 2 months ago
Completed
Delay in transcription start on Windows
The transcription does not start as soon as I press down the shortcut. I typically have to wait a second or two before the pill changes from the 3 dots to waveform (and makes the start noise). In this time, it catches nothing I say. I have this problem for a while now. It also still has the problem of missing out the last word a lot of the times. I am currently using the Ink 2 model, but I’ve tried with other models both cloud and local and the issue still persists. I even fully reinstalled the app, but the issue still remains. Is this expected or a bug? Windows 11. Vowen version 0.4.9
GoatBro about 2 months ago
Notch Indicator for meeting notes
I love the notch indicator when i use normal transcription can you do the same with the meetings notes too so we can also like pause or continue directly near the notch if we want to it will look much better
PRK about 2 months ago
Notch Indicator for meeting notes
I love the notch indicator when i use normal transcription can you do the same with the meetings notes too so we can also like pause or continue directly near the notch if we want to it will look much better
PRK about 2 months ago
Post-Transcription Automations (Auto-Copy & Auto-Export)
As a premium user who transcribes multiple videos daily, my current workflow involves a repetitive, manual loop once a video finishes transcribing: Wait for the "transcription ready" status. Open the completed transcript. Click the three-dots menu. Click Copy. Paste the text into a Large Language Model (LLM) to generate video descriptions and metadata. When processing multiple videos back-to-back, these manual steps add unnecessary friction to an otherwise seamless experience. Proposed Solution Introduce an Automation Toggle or an "On Completion" setting within the manual transcription menu. When a transcription finishes, Vowen would automatically trigger a pre-selected action based on the user's preference: Option A: Auto-Copy to Clipboard (with Smart Restore) — The full transcript text is instantly copied to the user's clipboard the second it's ready, mirroring the smooth workflow of the existing voice transcript feature. To make this even more seamless, it could include a "smart clipboard" behavior: the transcript temporarily occupies the clipboard, but once the user pastes it into their LLM or document, the system automatically restores their previous clipboard data so nothing is permanently lost. Option B: Auto-Trigger Export Window — Automatically opens the export menu immediately upon completion. Option C: Preemptive Default Export — Allows users to set a default format preference (e.g., Markdown, Plain Text, or PDF) so the file is generated and saved automatically without extra clicks. Why This Is Relevant For power users, content creators, and marketers who use Vowen as a baseline reference for AI workflows, transcription is rarely the final step—it is just the catalyst for the next task. Automating the copy/export bridge would eliminate tedious micro-tasks, speed up content distribution workflows, and significantly increase daily productivity.
Dio 2 months ago
Post-Transcription Automations (Auto-Copy & Auto-Export)
As a premium user who transcribes multiple videos daily, my current workflow involves a repetitive, manual loop once a video finishes transcribing: Wait for the "transcription ready" status. Open the completed transcript. Click the three-dots menu. Click Copy. Paste the text into a Large Language Model (LLM) to generate video descriptions and metadata. When processing multiple videos back-to-back, these manual steps add unnecessary friction to an otherwise seamless experience. Proposed Solution Introduce an Automation Toggle or an "On Completion" setting within the manual transcription menu. When a transcription finishes, Vowen would automatically trigger a pre-selected action based on the user's preference: Option A: Auto-Copy to Clipboard (with Smart Restore) — The full transcript text is instantly copied to the user's clipboard the second it's ready, mirroring the smooth workflow of the existing voice transcript feature. To make this even more seamless, it could include a "smart clipboard" behavior: the transcript temporarily occupies the clipboard, but once the user pastes it into their LLM or document, the system automatically restores their previous clipboard data so nothing is permanently lost. Option B: Auto-Trigger Export Window — Automatically opens the export menu immediately upon completion. Option C: Preemptive Default Export — Allows users to set a default format preference (e.g., Markdown, Plain Text, or PDF) so the file is generated and saved automatically without extra clicks. Why This Is Relevant For power users, content creators, and marketers who use Vowen as a baseline reference for AI workflows, transcription is rarely the final step—it is just the catalyst for the next task. Automating the copy/export bridge would eliminate tedious micro-tasks, speed up content distribution workflows, and significantly increase daily productivity.
Dio 2 months ago
Hide notification "Transcription cancelled"
When I cancel hands-free mode via ESC, the notification always appears, which is very annoying. It would be great if there was a simple toggle in the settings to stop the notification from appearing at all! Thanks!
Nikita Berger 2 months ago
Hide notification "Transcription cancelled"
When I cancel hands-free mode via ESC, the notification always appears, which is very annoying. It would be great if there was a simple toggle in the settings to stop the notification from appearing at all! Thanks!
Nikita Berger 2 months ago