My self-hosted podcast tool writes stiff dialogue with its local 35B. I gave the exact production prompt to Qwen3.8-27B, the 180B Qwen3.8-Flash-Next and Claude Sonnet, three runs each in German and English. The 27B matched Sonnet on form in German, Flash-Next wrote half the script in chopped turns, and with thinking on neither Qwen3.8 model returned a script at all.

Three Local Models and Claude Wrote the Same Podcast Script. Bigger Was Not Better.

Hours earlier, a 180B model had failed my hard-problem test by two tasks out of 28, on a test set that could never have shown it winning. That is an unsatisfying way to learn something. So I asked a question where I already knew what bad looks like.

Vozonda is my open-source tool that turns an article into a two-host podcast episode. The script is written by the local model on my DGX Spark, Qwen3.6-35B-A3B, and its dialogue has had the same faults since September: every turn about the same length, almost no quick reactions, too many questions, and German that reads like a telegram. I work around that in code, with a repair pass and a rhythm layer that reshapes the script after the model wrote it.

The question: does a bigger local model write the dialogue better, so that the workaround has less to do?

The setup

No synthetic task. The harness builds the exact prompt Vozonda sends in production, captures it, and sends the same text to every candidate with Vozonda’s own settings: temperature 0.7, a 16,384-token limit, thinking off. It scores the raw script, before any repair or rhythm layer touches it.

The score measures form, not whether the episode is good:

Results

Means of three runs, range in brackets where it matters.

ModelSourceWord budgetQuick reactionsQuestions / 1,000Contractions / 1,000Rhythm problemsSeconds
Qwen3.6-35B (production)DE89 %1 %20.70123
Qwen3.6-35B (production)EN119 %0 %12.911.9 (0.8 to 31.6)123
Qwen3.8-27BDE93 % (64 to 111)16 % (5 to 29)12.602.389
Qwen3.8-27BEN83 % (55 to 109)7 % (0 to 16)9.80.9259
Qwen3.8-Flash-NextDE54 %40 %12.502.729
Qwen3.8-Flash-NextEN60 %47 %16.24.1326
Claude Sonnet 5.5DE92 % (82 to 99)16 % (12 to 20)13.40090
Claude Sonnet 5.5EN83 % (78 to 91)15 % (10 to 19)10.225.1 (22.7 to 28.1)1.352

With thinking on, Qwen3.8-27B and Flash-Next returned no script in 8 of 8 runs. Each spent all 16,384 tokens reasoning, about five minutes on Flash-Next and ten on the 27B, and never started the JSON.

What the scripts look like

The same moment in the English episode, each from the first run, copied from the output files.

The 35B asks and answers in full sentences of the same weight, every time:

A: And users are identified by public keys, tagged as npub keys. How did this actually start? B: It was first written in 2020 by a Brazilian developer known as fiatjaf. He created it because he had disagreements with other protocols like ActivityPub and Secure Scuttlebutt, and he was frustrated with moderation issues on Twitter.

The 27B lets one host react before the next question:

A: Interesting. How does the data actually work? B: Data is stored in JSON blobs called Events, which are the only objects on the protocol. Users are identified by public keys tagged as npub.

Flash-Next reacts, and often does nothing else:

A: Who built it? B: A Brazilian developer using the pseudonym fiatjaf created it in 2020. He wanted an alternative to Twitter and had technical disagreements with protocols like ActivityPub and Secure Scuttlebutt. A: Interesting.

Sonnet is the only one whose host sounds like a person who wants something:

A: Protocol, not an app? B: Exactly, and that’s the key idea. Nostr can power social media, but also other kinds of applications. A: Okay, but how does the data actually work under the hood? Explain it like I’m new to this.

What I read from it

The 27B fixes the main fault. Quick reactions go from 1 percent to 16 in German and from none to 7 in English, and questions drop from 21 to 13 per 1,000 words in German. On the German source its form numbers are close to Sonnet’s on every column. It is also less steady: its word budget ranged from 55 to 111 percent across six runs, where Sonnet stayed between 78 and 99.

Flash-Next overcorrects. Nearly half its turns are quick reactions, and it delivers a bit more than half the words asked for. An 8-minute episode becomes a 4 to 5 minute one made of short exchanges. It is the fastest of the three new candidates, and that is the only column it wins.

Sonnet’s lead is in English, and in consistency. 25 contractions per 1,000 words against 1 for the 27B. It also broke none of the rhythm rules in German. On the counts in this table, the gap between the best local model and Sonnet is smaller than the gap between my production model and the 27B. Counts do not hear, so I would not stretch that sentence further.

Nobody wrote colloquial German. Zero contractions in every German script, Sonnet included. When the strongest model in the test misses in the same way as the weakest, the fault is in my prompt, not in the models. That is the cheapest fix this test found.

Thinking mode is a trap for this job. Vozonda already switches thinking off for script calls, because the 35B once reasoned its way through the whole token budget. The Qwen3.8 models do the same thing more reliably: both templates default to the highest reasoning effort when thinking is on.

Why the 27B is not simply the new writer

Speed is not the reason. A script is written once per episode, and 60 to 90 seconds disappear next to the minutes the speech synthesis takes.

Memory is the reason. On this box two large models do not fit side by side. The 27B can only run while the production model is stopped, and the production model also serves my coding agents all day. Swapping models for every episode is possible for a batch at night and wrong for an app that should answer when someone presses a button.

Flash-Next has that problem at full size. It needs the entire machine, every other service stopped, for a result that is worse here than the 27B’s.

What follows

Caveats

Was this worth it? Zap the article.

Value for value, no signup. Sats go straight to the writer.

… sats zapped
… zaps
Today 7d 30d All-time
Unique readers — — — —
Page views — — — —
—
All Article Insights →