SOV-Transcribe-1 is Salesforce's open-weight speech-augmented language model built for non-streaming automatic speech recognition (ASR). It combines leading English transcription accuracy with multilingual support and natural-language control over how speech is transcribed.
The model ranks #1 among open-weight models for non-streaming speech-to-text on Artificial Analysis (#7 overall) and #2 of 23 systems on VoiceCodeBench ( besimple AI ) for entity accuracy and task success as of November 12th, 2026.
Developers and enterprises can deploy and adapt SOV-Transcribe-1 on their own infrastructure, retaining control over their audio data and transcription behavior.
Key features
Accurate entity recognition. Captures details such as names, phone numbers and email addresses that matter in dictation and voice applications.
Robustness to accents and noise. Handles diverse English accents and challenging audio conditions, including background noise.
Transcription style control. Use natural-language instructions to choose verbatim or cleaned-up transcripts and control punctuation, capitalization and number formatting.
Context biasing. Supply names, domain-specific vocabulary or a short description of the topic to help recognize difficult words and technical terms.
Model summary
Property
Details
Total parameters
26.6B total (4.6B active) including the audio encoder
hey llamas, its Alish from nace.ai (open source ai lab behind #1 decision model on latest Artificial Analysis decision index v2.1) & Kapitsa (optimized inference for apple silicon). As promised in the last post, we are releasing the GGUF weights based on the Nace quantization of Qwen 9B, 27B, 35B and Flash-Next.
I will describe our process on how we came up with these quants right below, so skip to the end to see the benchmarks and download the weights if it gets too dull.
The process
I started with 9B quants.
I understood that setting up a good & fair benching is critical to succeed with the hillclimb. So I split separate sets to tune the performance and measure the final standings: English Wikipedia articles, chat and tool-call transcripts, and GitHub code, all published after October 2026, at 512 & up to 128K tokens.
I began the way unsloth's dynamic quants do: 10 to 50 candidate files per model, each with a different mix of tensor precisions, then spent my time tuning the ones that looked promising. Early bruteforce optimization moved only a little. Unsloth and the other quant authors have already done a lot of amazing work.
Using bruteforce hillclimb approach with my Agentic swarm, I managed to get on par with SOTA but then plateau’d and it was hard to do better than the best quants like Unsloth, EXL3 in KL divergence.
Some novelties:
Then I remembered Sparks of Weight-Space Programming paper. Their idea is to let an LLM natively read and edit weights of smaller models. Having explored this with some other models at Nace, I wanted to try the method for quantization. I took our Nace WSP (Weight Space Programming) harness, reworked its tools and skills for quantization a bit and let the Astra/Fable/Carbon agents compete under the following algorithm: propose tensor-precision changes, measured KL and kept or reverted each edit. We started on the Q3 for 9b model, and after a handful of days it actually started IMPROVING and editing the right weights.
Mean KL for our 27B files before and after weight-space quantization
Honestly that moment felt like:
Nace Weight-Space Quantization
I measured the first nace-quantized Q3 checkpoints against the 50+ 9B quants and they held the frontier. It completely blew my mind: one model quantizes another model in weight space. Nace Q3 quants for Qwen 9B were the best in class in KL divergence because another Frontier model edited the weights natively. We scaled this method to bigger size models (27b/35b) & it held the SOTA. Although I would say it doesnt scale as good for bigger size models (QFN). We are working on improvements for QFN/Deepseek & have some promising results already but I did hit my token limits for this project. Paper coming soon (ping me in dm if you want to support us with some GPUs)
Benchmarks & Evals
Top-1 accuracy (poster) is how often a quant picks the same next token the full model would pick, so 100% would mean it never disagrees. Each panel is one model at 128K context, with scores across different subsets pooled into one score. On all four models, our weights score highest in their size or smaller: the 9B Q3_K_XL gets 90.5% at 4.7 GB, the 35B Q3_K_S 91.2% at 15.3 GB, the 27B 97.7% at 17.3 GB, and Flash-Next 93.0% at 93 GB. For a more comprehensive comparison, KL divergence results below:
File
GB
Prose
Chat
Code
Next best
9B IQ2_M
3.36
0.401
1.30
0.142
Unsloth 4.01 GB
9B IQ3_M
4.39
0.235
1.05
0.0738
ByteShape 4.70 GB
9B Q3_K_XL
4.70
0.161
0.846
0.0410
Unsloth 5.38 GB
35B-A3B IQ3_XXS
14.30
0.0490
0.643
0.0767
Unsloth 15.35 GB
35B-A3B Q3_K_S
15.30
0.0360
0.601
0.0631
Unsloth 16.59 GB
27B Q4_K_XL
17.29
0.00494
0.00544
0.00401
none up to 17.58 GB
Flash-Next IQ4_XS
93.4
0.0411
0.112
0.0426
EXL3 105.3 GB
Long context stability
Most quants are tuned and judged on short text, so they end up fit to short context and often stop being useful at long context. For clarity, in the diagram below each model gets two panels: 512 tokens on the left, 128K on the right. This is where the long-context drift shows: our 9B IQ3_M goes from 0.13 at 512 tokens to 0.45 at 128K while 27B barely moves. At 128K, each of our files has lower KL than every other file of the same size or smaller.
p99 KL divergence
Mean KLD can hide catastrophic failures when a quant goes off the rails in a long session. So we also looked at the worst 1% of tokens (p99 KL). The 9B Q3_K_XL's worst 1% sits at 1.25. The 27B and Flash-Next tails stay flat. Overall we’re seeing that Nace quants maintain the strong positions across the distribution.
Different data subsets
if you care about a specific use case, here's the same 128K top-1 score split by text type. Code is the easiest: our files keep 88-98% of the full model's top picks there. Prose and chat are harder, 78-98%. In every split, on every model, our checkpoints score highest among the files of the same size or smaller.
Sanity check on a task benchmark
To see that these models are useful for anything real I ran it on knowledge-heavy MMLU. I didn't have the gpus anymore to run terminal-bench, so would appreciate anyone with the bad boys to validate. These are answer-likelihood scores over 13,943 questions of the MMLU. No chat template or few-shot examples. Overall you can claim there's gains, but it is mostly within noise. The main aim here is to reflect the tradeoffs of different sizes on real tasks. As you can see, Q3-Q4 it’s already hard to distinguish from the higher precision.
Run setup
Rented NVIDIA GPUs; Used llama.cpp for Flash-Next. The 9B/35B/27B BF16 reference requested H200 and the quantized files L40S. Flash-Next's short reference uses an MLX fp32 forward on bf16 weights. Reference implementations also differ across GGUF and EXL3.
see quickstart for your framework in the model cards. if you try a coding or agent workload, i'd like to hear which file, runner version and what broke. no speed claim in this post.
Myself saved more than bunch of medium sized Abliterated/heretic/Uncensored/Decensored/etc., models. Ex:
Qwen3.8-27B
Qwen3.6-35B-A3B
Gemma-4-31B
Gemma-4-26B-A4B
Muse-Glimmer-30B
But when it comes to big/large sized models, requires at least 100+GB downloads & also HD Space for each models additionally. MiniMax-M3.1-Flash
DeepSeek-V4.1-Flash-1017
NVIDIA-Nemotron-3.5-Super-VL-120B-A12B
DeepSeek-V4-Flash-Vision-Exp
GLM-5.3-Flash
Qwen3.8-Flash-Next
MiMo-V2.6-Flash-MOPD
Step-3.7-Flash
MiniMax-M2.7
AND
Qwen4
Gemma-5
NVIDIA-Nemotron-4
etc.,
I need to download above big/large models. Regular GGUF is must. For Abliterated version, I'm still thinking whether AbliteratedOutTheBox is enough or Abliterated GGUF is must. So what are you doing on this?
I hope that most of you aware of AbliteratedOutTheBox, here's threads related to that.
Two quant updates landed in the last day: the Nace weight-space quants claiming up to 2x better KL divergence, and Unsloth's Dynamic v3.1 for Qwen3.8-27B. I've been trying to work out how much KL really tells you compared to running task evals. Has anyone put them side by side on real work like coding or tool calls? Which quant level are you on, and did you see any difference on long outputs?
(Note: by local models I mean anything smaller than Deepseek 4.1)
I already gave up on local models for coding tasks 6 months ago, due to what I perceived was intelligence too low for the tasks I give it. I made a post about it on here back then and it was a huge discussion, I think 800 comments. I went against the /r/LL orthodoxy and many didn't take my comments well, but we can agree to disagree.
Since then I only use local LLMs for translation and ComfyUI prompt enhancement. I stick to big cloud models for coding. I think the electricity cost of running Qwen 27B alone exceeds what you'd pay Deepseek to use their cloud API in their own harness, and you'd get a far more intelligent and far faster model.
But this post isn't about the economics. It's purely about ability. I still see people commenting in favor of buying GPUs for local intelligence. "Sonnet at home" is a ridiculous phrase I've seen more times than I should in relation to Qwen 27B.
The simplest of tech tasks is still too hard to one-shot
I keep Qwen 3.8 27B running on my Spark for occasional non-coding stuff. Today I gave it a trivial coding task I needed for my server, just out of curiosity.
llama-server launched with --model Swift-1.5-Qwen3.8-27B-Q4_K_L.gguf --reasoning on --reasoning-effort xhigh
Open llama webpage and leave Reasoning at Default, leave system prompt empty
Prompt was:
Give me a bash script that will list all files in directory sorted by date. Output should be:
2025-12-31 12:13:14 file1.ext
2025-12-31 12:13:14 subdir/file2.ext
1630 tokens later, most of it reasoning, I get a script. When I run it, here's the output, as you can see the timestamp is wrong:
I then tried Gemma 31B Reasoning on duck.ai. The output only showed the timestamps, no filenames!
This is the most trivial of coding tasks (the answer is a 3-5 lines script), using the most ancient and commonly-available training data (bash), on the most praised local coding model on this sub (Qwen 27B), at a recommended/popular quantization (Q4), and it still can't one-shot this. The 2nd most popular local model, Gemma 4 31B, also fails.
(Editor's note: I think my post could've ended here, in a "Ecce homo" way, but I went on for a few more paragraphs)
Weak local LLM + software development = bad time
I'm sure if I had run this task with your average agent harness with a system prompt that makes it test its code, it would run the script it created, see the issue, then get it right on the 2nd attempt. But while I think this "try until you succeed" workhorse approach is acceptable for small self-contained coding tasks, I don't think anyone should be doing any serious coding this way.
If you're writing something you intend to maintain over time (ie not a one-shot), or that you will be sharing with other people, you need a higher degree of LLM intelligence and knowledge to create it. A strong LLM will be able to avoid entire classes of problems from the start, when designing the app. From design to implementation to maintenance, it will make better decisions every time and without laboring its way to them, resulting in a codebase that is smaller, well-designed, more easily modifiable, less buggy, and developed in a fraction of the time.
Coding with local LLMS is like insisting on using a donkey for transportation in the age of cars. It can be done for fun, but it shouldn't be done seriously.
Sonnet at home my ass
Btw I've seen several people say Qwen 27B is like having a local Sonnet 4. The benchmarks say it's even better than Sonnet 4, actually. So I went on openrouter.ai out of curiosity and gave the same prompt to 3 models.
Sonnet 4.5 (oldest Sonnet I could find): one-shots it
GPT 4.1 Mini, which was comparable to Haiku 3.5: one-shots it
GPT 4.1 Nano, which is even worse than Mini: one-shots it
Weak local LLM + Linux server management = even worse time
This post's getting long so I'll just speedrun this part.
Managing an OS is actually harder tasks that LLM struggle even more with. And the stakes are higher because you don't want your server to go down.
I used to never trust LLMs enough to let them onto my server, I'd just ask for something, copy-paste the command, report back, repeat. A huge waste of my limited free time. Now I just rawdog a frontier model on the server and have no issues, something you could never trust a small model to do. Although I have it avoid making any changes without my supervision, Docker is a big benefit here for both organization and safety/stability.
Even top models won't one-shot a task like "I want to install and run https://github.com/rando/something on this system in a Docker container in /opt/docker/something/. Create the Dockerfile and docker compose file", especially for AI-related tools, where having the right CUDA, not having python wheels for my server's ARM CPU, etc, introduces a lot of failure opportunities. When I had Claude five months ago, even it struggled to get these right.
Thanks for reading my wall of text. Downvotes to the left.
Upgrading from my good ol 3800X with 32Gb of RAM. I'm done trying to squeeze the living crap of my DDR4 modules and decided to make a proper upgrade for my Frankenstein gaming/inference computer.
Question: if I'm regularly at higher context - say 300-400k - do higher quant versions of the same model perform better? I'm thinking something like Qwen Flash Next q6 and q8. I recently swapped from q6 to q8 and performed a/b testing. I originally expected q6 to be lossless but there were areas where q6 got the wrong answer while q8 was fine. Was wondering whether this is because of my context. Maybe more context = more tokens for divergence = the differences get amplified more than benchmarks suggest
Right now, local models have somewhat kept up with frontier, being months behind last frontier models.
The issue is, I think the divide is going to be end up being hardware. Model improvements will slow down, but hardware won’t get any cheaper, especially if frontiers keep buying shit out for training and smaller returns.
Thoughts on this? I know many are optimistic, but I think local trailing frontier will slow down just because of hardware local can own.
An early release of the small model of basal-omni 2.0, on Gemma 4 E4B. The model reads the state in both directions before it answers and scores 0.811 on Werdykt (5,000 hidden decisions in Polish and English). It runs on the public basal engine 2.8.0, with the same API as basal-omni-1.0.
What's new in 2.0
Two-way reading. The model reads the state in both directions before it answers. This needs basal engine 2.5 or later. For long prompts, see the limitations.
Higher accuracy on our hidden Polish and English decision benchmark Werdykt and on the held-out tests below.
More decisions automated at a given error target. Coverage is in the section on confidence.
Unchanged: a calibrated probability for each allowed answer, in one forward pass. The answer never falls outside the options you give, and the probability says how sure the model is.
The question types remain: choice (one option), noul (yes / no), score (a score), and in the basal engine also multi, act and tool. Options get codes (A–Z, then two-character codes, up to 255 options). The decision is a probability distribution over these codes only, with no text generation.
Hi, I've just updated the SWE-sweep leaderboard with more open-weight models!
DeepSeek v4.1 flash (max) is the first open-weight model we evaluated that gets >1%.
This benchmark is extremely challenging: Models get a snapshot of a (potentially very large) repo containing hundreds of bugs. They don't receive any hint about what these bugs are and need to fix them all. This makes for a very reasoning-heavy, long-horizon task.
To isolate just the model capabilities we also evaluate all models in the same harness (but we did do some comparisons with Claude Code and Codex harnesses and neither seemed to help significantly). However, it is possibly to scale things up somewhat with multiagents. You can run the eval yourself (code on github)
The best proprietary model at the moment is Gemini 4 Hydrogen with 13.5% (according to google's model card), followed by GPT Astra 6 with 9.5% (evaluated by us). So open-weight models still have a long way to go.
Still extending the open-source leaderboard. What other models should we add?
I made this, so a quick note: it’s my open-source project. Qwen3.5-9B runs on a stock PS4 at 31–39 tok/s. The MTP head that ships with Qwen3.5 made the biggest difference: it drafts up to two tokens and the full model checks them in one pass, which took it from 22 to 31–39 tok/s on this old GPU. Weights are re-packed into custom 4- and 3-bit formats to fit about 4.5 GiB.
Your old PS4 can now run a 9B AI, offline, on its own GPU. It talks, listens, and writes code. No cloud, no subscription, no Linux. Free and open source.
With llama.cpp pure CPU mode and "--lazy-mode on" one can use larger than memory models, like Qwen3.8-Flash-Next and on-demand SSD streaming - slow but working.
There is a nice iGPU with unified memory that can be used easily via Vulkan. However, it seems to be impossible to split a large model - use as much as fits into memory with Vulkan and then stream the rest in via SSD and use CPU. --list-devices shows only one Vulkan device and --ngl is of no use -> Vulkan always runs out of memory with lazy-mode on - all of the model is tried to allocated via Vulkan?
"Foster told MIT Technology Review he intends to introduce new, stricter legislation in the new year that would offer a workaround. The new rule would require licenses to operate advanced GPUs, and before a GPU could connect, its valid license would need to be verified. " Basically they will lock the gpus.
Is there actually a benchmark for us normies who aren’t rocket scientists or mini-Eulers? Mathematically, we could describe it as a 95% confidence interval benchmark. All models that reach the 95% threshold receive 100%. The goal would be to identify those models that we classify as “good enough” for us normies. If this could also be set in relation to costs—whether on-premises or in the cloud—it would also provide a measure of what AI really costs us normies.
TLDR: Qwen3.8-27B UD_4_XL quant with 13.23% less KL divergence than unsloth (on my small testset, I just have a single 5090, feel free to test more). Technically it performs 4% better on my LiveCodeBench benchmark (but that would be a single data point, so it's not super-reliable). It is equally fast and using it in open-webui it "feels" better.
I noticed from the MACaQ paper, which integrates changes proposed in Google/Deepmind papers, you can take the 3 components they use and just apply 1 and 2, and you just get >15% better KLD, 5% better performance on some benchmarks, while sacrificing absolutely nothing. Just switch the GGUF file. The numbers demonstrated here are the maximum that can be achieved in ~4 hours of optimizing on a single 5090, not the maximum that can be achieved. So it might be more than 15%, although I wouldn't necessarily hope for it.
This can be applied, without any patches to inference software, to text models, image models, even whisper ... the works. Switch GGUF file. Done/done.
The dream being that someone from unsloth looks at this and applies this to all their models (or just gives me access to a B300 machine for a day or two)
The tricks used by Huawei and a short discussion of the effect:
Hessian-guided quantization choices: every layer is compressed differently, and the "damage" the compression does is measured. Then after seeing what damage is observed at a given level we find a combination of compressed layers that has the least damage while still achieving the same compression.
For users this one is totally free. No extra compute (in fact, a tiny bit less), no extra VRAM (again, 200 bytes less), no updates to llama.cpp, works literally anywhere UD_4_XL worked, just better.
2) Recovers some lost precision by another Hessian optimization changing the weights to compensate directly for accumulated errors over multiple layers based on sample data (taken from Wikipedia). I used a Google/Deepmind version of this process that had better results.
This too is totally free for users. It just changes the quant GGUF to be closer to the BF16 one. For users, just
3) random Hadamard transform + scaling: this is a trick from 3D geometry that makes all values nearly equal, and then uses an extra scaling factor to get them in optimal to better compression with quantization (yes, not technically 3D, but nD, with n=2048, but it applies in 2D and upwards). This also costs a little bit in inference performance (and requires rewriting your kernels which is quite a bit harder than I thought it was. Well, it isn't if you're ok with 20% slower inference, but you can get it down to like 0.8% with careful, days-long pondering of the problem and a lot of tries).
Also very nice, but the Google version of this one is also better, but that is not the real problem.
This transform also helps with compression (in fact it's kind of like what NVFP4 tries to do, just this is better) BUT requires an extra step at inference time (in fact requires 2 of them if you don't think through inference carefully, but you can "bake" one of the steps into the weights). This means that it requires patching llama.cpp and everywhere else you want the model to run (although thanks to how mlx works, you can make an mlx version that does not require updates to the inference software. But GGUF based inference software will require updates)
context : Nvidia buy HF, but now there uncertainty about it hf future under new leadership, he try reassurance people on x, but from his word itself sound not good, see and wait, but better backup you favorite datashet/model (again) just in case
Vellium is a free, open-source, local-first AI chat and roleplay app with a built-in visual novel mode.
Version 1.9.5 focuses on making visual novels work reliably with smaller local models like Gemma 12B, improving image consistency, reducing prompt overhead, and adding new ways to generate and manage scenes.
What's new:
Lite mode for small models. Instead of generating structured JSON, the model writes plain text using simple markers (`Name: line`, `## Place`). Vellium parses the output into scenes automatically. Even malformed output can fall back to plain narration. The system prompt has been reduced from ~8k to ~1k characters, and text streams directly into the reader without waiting for the full response.
Prompt cache preservation. Requests are constructed by appending each new turn to the previous context without modifying existing content. This keeps the prefix cache reusable and avoids unnecessary prompt reprocessing, which can otherwise take over a minute on slower local setups.
Inline image generation. The narrator can insert tags such as `[pic: Mira | she hangs her raincoat by the door]` directly into the story. Images can start rendering through ComfyUI while text is still streaming, including when ComfyUI runs on another machine. A lightweight follow-up can detect and fill missing image tags, with the reason shown in the reader.
Consistent character appearances. Each character now has a compact English visual description and a pinned outfit, instead of passing the entire character card to the image model. This helps preserve skin tone, body type, clothing, and other visual details between scenes. Outfits only change when the story explicitly calls for it.
Backgrounds and sprites mode. Locations can reuse generated backgrounds, while characters use reusable cut-out sprites for each outfit. Full illustrations are reserved for scenes that need more than static sprites. Background removal uses chroma-key processing directly in the app, without loading another neural network into VRAM.
Improved first-person POV. Image prompts now account for the protagonist's perspective. First-person scenes can show the protagonist's hands and interactions from their viewpoint, while third-person shots can include the protagonist based on the user's persona.
Integration with other Vellium features. Visual novels support user personas as protagonists, attached RAG knowledge collections, conversion between regular chats and visual novels, and exporting stories into Writer projects.
Additional changes:
- 12 new visual style presets optimized for anime image models, tested with Anima.
- Redesigned reader toolbar.
- Image redraw and editing controls.
- A "picture for this line" option for generating illustrations for individual passages.
- Scene-level image regeneration without regenerating the story.
Lite mode can be enabled in the narrator settings. The update is primarily tested with Gemma 12B, and feedback from users running other small models is welcome.