Lyria 3.5 vs MAI-Transcribe 2

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
Google Deepmind · activeLyria 3.5Verified Sep 3, 2026
Microsoft · previewMAI-Transcribe 2Verified Sep 3, 2026

Technical Differences

Side-by-Side Facts

Indexable
FieldLyria 3.5MAI-Transcribe 2
DeveloperGoogle DeepmindMicrosoft
FamilyLyriaMai Transcribe
ModelLyria 3.5MAI-Transcribe 2
VersionLyria 3.5MAI-Transcribe 2
Lifecycleactivepreview
Released2026-07-292026-09-03
Knowledge cutoffUnknownUnknown
Input modalitiesTextAudio
Output modalitiesText, AudioText
Context window1,048,576Unknown
Total parametersUnknownUnknown
Active parametersUnknownUnknown
LicenseUnknownUnknown
Open weightsNoNo
API availableYesYes
Self-hostableNoUnknown
Provider accessGoogle AI (Standard), Google Gemini (Standard)Microsoft Foundry (Public preview)
Capabilitiesgeneration, image-to-music, lyrics, music-generation, synthid, vocalsdiarization, multilingual, speaker-attribution, transcription, word-level-timestamps

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

Lyria 3.5 Capabilities

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

MAI-Transcribe 2 Capabilities

diarizationmultilingualspeaker-attributiontranscriptionword-level-timestamps
Input price
Output price
Serving providers1
Canonical IDmicrosoft/mai-transcribe

Internal Comparison Graph

Related Comparisons

All audio comparisons →
APairBContext
vscross-developer peersaudio
vscross-developer peersaudio
vsdeveloper peersaudio, text
vsdeveloper peersaudio, text
vscross-developer peersaudio, text
vscross-developer peersaudio, text
vscross-developer peersaudio, text
vscross-developer peersaudio, text
vscross-developer peersaudio
vscross-developer peersaudio
vscross-developer peersaudio
vscross-developer peersaudio

Primary Evidence

Sources and Freshness

Questions

Lyria 3.5 vs MAI-Transcribe 2 FAQs

Is Lyria 3.5 or MAI-Transcribe 2 better for coding?+

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

Which is cheaper, Lyria 3.5 or MAI-Transcribe 2?+

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, Lyria 3.5 or MAI-Transcribe 2?+

Neither model has a larger sourced context window in this comparison. Lyria 3.5 is 1,048,576 and MAI-Transcribe 2 is —.

Which performs better in benchmarks, Lyria 3.5 or MAI-Transcribe 2?+

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

Can Lyria 3.5 or MAI-Transcribe 2 be self-hosted?+

Neither model is the only model in this pair currently marked as self-hostable. Lyria 3.5 is not marked open weight; MAI-Transcribe 2 is not marked open weight.

Can Lyria 3.5 and MAI-Transcribe 2 understand images?+

Lyria 3.5 is not documented with image input; MAI-Transcribe 2 is not documented with image input. This reflects supported input modalities, not vision quality.

Which can generate longer answers, Lyria 3.5 or MAI-Transcribe 2?+

Neither has a larger sourced maximum output. Lyria 3.5 is 65,536 and MAI-Transcribe 2 is —.

Do Lyria 3.5 and MAI-Transcribe 2 support reasoning and tool use?+

Lyria 3.5: none of these features are definitively sourced. MAI-Transcribe 2: none of these features are definitively sourced. Feature support does not establish relative quality.

Which is available from more inference providers, Lyria 3.5 or MAI-Transcribe 2?+

Lyria 3.5 has 2 sourced provider routes; MAI-Transcribe 2 has 1, so Lyria 3.5 has broader tracked availability.

Which offers better value, Lyria 3.5 or MAI-Transcribe 2?+

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