chore(deps): update dependency peteonrails/voxtype to v1.1.0

[renovate]

This PR contains the following updates:

Package	Update	Change
peteonrails/voxtype (source)	minor	1.0.1 → 1.1.0

---

Release Notes

peteonrails/voxtype (peteonrails/voxtype)

v1.1.0: : Whisper on Intel NPUs, Text Rules Everywhere, OSD Theming

Compare Source

voxtype 1.1.0 brings Whisper to Intel NPUs through a new OpenVINO engine, makes your text rules apply everywhere they should have all along, teaches the Quickshell OSD to follow your Omarchy theme and wear entirely different looks, and ships a binary for CPUs without AVX2. Everything in 1.0.1 is included.

Intel OpenVINO engine: Whisper on CPU, iGPU, and NPU (#​547)

A new openvino engine runs Whisper through Intel's OpenVINO GenAI runtime, including the NPU on Core Ultra laptops. 33 models are available through voxtype setup --download, served from models.voxtype.io with sha256-verified manifests.

Why use it: on a Meteor Lake NPU, dictation runs at a fraction of the power the CPU or iGPU would draw. On battery, that is the whole story.

Two things to know. You need Intel's OpenVINO GenAI runtime installed; voxtype loads it only when this engine is selected, so nothing changes for anyone else. And the multi-minute first compile of a large model on NPU happens during voxtype setup, where you expect to wait, instead of silently stalling your first recording (#​698). The compile runs only when your config explicitly says device = "NPU", and a compile failure is a warning, not a broken setup: the runtime falls back NPU to GPU to CPU.

Contributed by Jacob Mink, with testing, the device fallback chain, and a missing-file fix from tslove923.

Your [text] rules now run on every path that produces text (#​669, #​581)

Replacements and spoken punctuation only ever applied to hotkey dictation. Streaming output and voxtype transcribe <file> silently skipped them: the daemon logged your rules as loaded, then never consulted them. Both paths now apply your rules when text is committed.

Why it matters: if you use replacements with a streaming engine, your output will change in this release without any config edit. That is the fix working. Reported by Marc Lavallee.

The Quickshell OSD follows your Omarchy theme live (#​705)

Switch your Omarchy theme and the OSD recolors itself in place, no restart. A small follower process watches the theme directory and rewrites the OSD's runtime palette when it changes; its lifetime is tied to the OSD itself, so it never outlives it and costs nothing when Omarchy is not installed.

Why use it: the OSD stops looking like a sticker from another desktop. It picks up your accent, foreground, and background colors the moment the rest of your desktop does.

OSD style packages and recipes

The OSD's look is now swappable. A style package is a directory of QML dropped into ~/.config/voxtype/osd/ (or shipped system-wide in /usr/share/voxtype/osd/), selected with one config key:

[osd]
style = "aegis-hud"

Recipes are lighter: preset [osd] configurations that restyle the built-in components without any QML. Styles are discoverable everywhere: voxtype info styles lists what is installed, the TUI (voxtype configure) has a style picker with descriptions, the Omarchy settings panel gets a working Style dropdown (#​710), and voxtype config set osd.style round-trips cleanly. A style that ships its own palette keeps it; styles without one follow the Omarchy theme like the default does.

Built on the styling groundwork contributed by OldJobobo.

A binary for CPUs without AVX2 (#​612, #​740)

Every prebuilt x86-64 variant required AVX2, so pre-Haswell machines crashed with SIGILL, and the crash message told them to switch to the binary they were already running. There is now a baseline variant built for x86-64-v2 (Nehalem 2008 and later), shipped in the deb, the rpm, and the AUR packages. The OSD binaries are built to the same floor, so those machines get an OSD too. The SIGILL message on the other variants detects the missing AVX2 with raw CPUID and points at it:

voxtype setup variant --to baseline

Getting this one honest took two tries. The release-candidate baseline builds passed every startup check and then SIGILLed at first inference, because the build flags meant to constrain the bundled whisper.cpp never reached its build system. ironbract diagnosed it on an Ivy Bridge i7-3520M, down to the faulting instruction, and confirmed the fix on the same machine. CI now runs real inference on every baseline artifact under a QEMU-modeled v2 CPU, where the broken build reproducibly crashes and the fixed one transcribes, so this failure class cannot ship silently again.

A panicked transcription no longer poisons the engine (#​643)

1.0.x only recovered Whisper. The cached transcriber is now dropped and re-created after a panic on every engine, including the new OpenVINO one. A hard abort inside a native runtime is still what gpu_isolation is for.

Config that survives one bad value (#​646)

One unreadable value used to stop the daemon and cost you every setting you had. The config now parses section by section: the bad section falls back to defaults and is named in the log, everything else survives. Section names only, never values, because those sections hold API keys.

Bug fixes

• The GTK4 OSD sidesteps a GTK heap corruption in Wayland dmabuf-feedback handling that crashed it every few minutes to hours on AMD iGPUs (#​656)
• voxtype setup --download can now fetch models for every engine, not just Whisper, Parakeet, and SenseVoice (#​687)
• Removed moonshine-tiny-ja and moonshine-tiny-zh: upstream never published a decoder these builds can run, so the entries could never download (#​694)
• --version prints 1.1.0+g<sha> on untagged source builds, so a development binary can no longer pass itself off as the release
• The TUI's test-notification button now goes through the same notification slot real dictation uses
• voxtype setup quickshell fails loudly when the qmldir declares components the install did not ship, instead of the OSD silently dying three times (#​697)
• Feature probes use raw CPUID instead of is_x86_feature_detected!, which statically evaluates to true in binaries compiled with the feature enabled and so never detected its absence where it mattered
• The macOS build of the Quickshell launcher compiles again: the theme follower's lifetime pipe uses portable pipe+fcntl instead of Linux-only pipe2

Known limitations

• Streaming settings ([streaming]) are config-file only; no TUI section yet
• The [osd] recipes still install by hand (copy from /usr/share/voxtype/osd-recipes); a config apply-recipe command is scheduled for 1.1.1

Upgrading

yay -S aur/voxtype-bin      # Arch. The omarchy repo shadows the AUR name, so aur/ is not optional

Restart the daemon after upgrading:

systemctl --user restart voxtype

If you install binaries by hand rather than through a package, also re-sync the Quickshell QML tree, or the OSD keeps rendering the old version's behavior:

voxtype setup quickshell --force

Verifying downloads

Every binary, the .deb, the .rpm, the source tarball and SHA256SUMS.txt are signed in CI by 9CCF7915B750CAE8B095ED1AA3FC9F33FD209279, which dirmngr fetches by fingerprint:

gpg --auto-key-locate keyserver --locate-keys pete+voxtype-ci@peteonrails.com
gpg --verify voxtype-1.1.0-linux-x86_64-avx2.asc voxtype-1.1.0-linux-x86_64-avx2
sha256sum -c SHA256SUMS.txt

Which binary do you want? avx2 runs anywhere from Haswell on. avx512 is faster on Zen 4 and recent Xeon. baseline runs on anything from 2008 on.

For GPUs: vulkan for AMD and Intel, onnx-cuda-12 or onnx-cuda-13 for NVIDIA depending on your driver, onnx-migraphx for AMD on ROCm. On an Intel Core Ultra, try the new openvino engine.

Not sure? Take onnx-avx2 and run voxtype setup gpu --status.

Thanks to everyone who tested the five release candidates. Several of the fixes above exist because someone ran an rc on hardware we don't have.

---

Configuration

📅 Schedule: (in timezone America/Los_Angeles)

• Branch creation
  • Every minute (* * * * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.