Granite Speech 5.0 TurboCTC NC vs Lyria 3.5

Benchmark Performance

Available Benchmarks

No Protocol-Matched Benchmark Yet.Results appear here only when both models share the same benchmark version, metric, evaluation protocol, and evidence class.
FieldAt a Glance
IBM · activeGranite Speech 5.0 TurboCTC NCVerified Sep 2, 2026
Google DeepMind · activeLyria 3.5Verified Sep 3, 2026

Technical Differences

Side-by-Side Facts

Indexable
FieldGranite Speech 5.0 TurboCTC NCLyria 3.5
DeveloperIBMGoogle DeepMind
FamilyGranite Speech 5 0Lyria
ModelGranite Speech 5.0 TurboCTC NCLyria 3.5
VersionGranite Speech 5.0 TurboCTC NCLyria 3.5
Lifecycleactiveactive
Released2026-08-252026-07-29
Knowledge cutoffUnknownUnknown
Input modalitiesAudioText, Image
Output modalitiesTextText, Audio
Context windowUnknown1,049K
Total parameters473MUnknown
Active parametersUnknownUnknown
Licensecc-by-nc-sa-4.0Unknown
Open weightsYesNo
API availableNoYes
Self-hostableYesNo
Provider accessUnknownGoogle AI (Standard), Google Gemini (Standard)
Capabilitiesautomatic-speech-recognition, transcriptiongeneration, image-to-music, lyrics, music-generation, synthid, vocals

12 comparable fields · 11 material differences · Pair passes the primary-source comparison gate

Granite Speech 5.0 TurboCTC NC Capabilities

automatic-speech-recognitiontranscription
Input price
Output price
Serving providers0
Canonical IDibm-granite/granite-speech-5.0-470m-turboctc-nc

Lyria 3.5 Capabilities

generationimage-to-musiclyricsmusic-generationsynthidvocals
Input price
Output price
Serving providers2
Canonical IDlyria-3.5

Internal Comparison Graph

Related Comparisons

All audio comparisons →
APairBContext
vscross-developer peerstext

Primary Evidence

Sources and Freshness

Questions

Granite Speech 5.0 TurboCTC NC vs Lyria 3.5 FAQs

Is Granite Speech 5.0 TurboCTC NC or Lyria 3.5 better for coding?+

This comparison does not currently contain a protocol-matched coding benchmark for both Granite Speech 5.0 TurboCTC NC and Lyria 3.5, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.

Which is cheaper, Granite Speech 5.0 TurboCTC NC or Lyria 3.5?+

Neither model has a directly sourced input price in this comparison. Neither model has a directly sourced output price in this comparison.

Which has a larger context window, Granite Speech 5.0 TurboCTC NC or Lyria 3.5?+

Neither model has a larger sourced context window in this comparison. Granite Speech 5.0 TurboCTC NC is — and Lyria 3.5 is 1,049K.

Which performs better in benchmarks, Granite Speech 5.0 TurboCTC NC or Lyria 3.5?+

There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.

Can Granite Speech 5.0 TurboCTC NC or Lyria 3.5 be self-hosted?+

Granite Speech 5.0 TurboCTC NC is the only model in this pair currently marked as self-hostable. Granite Speech 5.0 TurboCTC NC is open weight; Lyria 3.5 is not marked open weight.

Can Granite Speech 5.0 TurboCTC NC and Lyria 3.5 understand images?+

Granite Speech 5.0 TurboCTC NC is not documented with image input; Lyria 3.5 is documented with image input. This reflects supported input modalities, not vision quality.

Which can generate longer answers, Granite Speech 5.0 TurboCTC NC or Lyria 3.5?+

Neither has a larger sourced maximum output. Granite Speech 5.0 TurboCTC NC is — and Lyria 3.5 is 66K.

Do Granite Speech 5.0 TurboCTC NC and Lyria 3.5 support reasoning and tool use?+

Granite Speech 5.0 TurboCTC NC: none of these features are definitively sourced. Lyria 3.5: image input. Feature support does not establish relative quality.

Which is available from more inference providers, Granite Speech 5.0 TurboCTC NC or Lyria 3.5?+

Granite Speech 5.0 TurboCTC NC has 0 sourced provider routes; Lyria 3.5 has 2, so Lyria 3.5 has broader tracked availability.

Which offers better value, Granite Speech 5.0 TurboCTC NC or Lyria 3.5?+

There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.

Send Feedback