Lyria 3.5 vs SOMA X v0.3.0

At a Glance

Compare
Lyria 3.5Google DeepMind
Pricing and Limits
Context windowMaximum documented tokens1,049KNot reported
Model facts checkedSep 23, 2026View model evidence →Sep 2, 2026View model evidence →

Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →

Different Model RolesThese models do not share a sourced market category. Their primary-source facts remain comparable below, while performance claims require matched evidence.

Available Benchmarks

All benchmark results →
No Protocol-Matched Benchmark Yet.Results appear here only when both models share the same benchmark version, metric, evaluation protocol, and evidence class.

Side-by-Side Facts

FieldLyria 3.5SOMA-X v0.3.0
DeveloperGoogle DeepMindNVIDIA
FamilyLyriaSoma X
ModelLyria 3.5SOMA-X v0.3.0
VersionLyria 3.5SOMA-X v0.3.0
Lifecycleactiveactive
Released2026-07-292026-09-02
Knowledge cutoffUnknownUnknown
Input modalitiesText, ImageModel-specific input
Output modalitiesText, Audio3D
Context window1,049KUnknown
Total parametersUnknownUnknown
Active parametersUnknownUnknown
LicenseUnknownapache-2.0
Open weightsNoYes
API availableYesNo
Self-hostableNoYes
Provider accessGoogle AI (Standard), Google Gemini (Standard)Unknown
Capabilitiesgeneration, image-to-music, lyrics, music-generation, synthid, vocalsanimation, hand-modeling, human-body-modeling, motion-retargeting, pose-inversion, simulation

Lyria 3.5 Capabilities

generationimage-to-musiclyricsmusic-generationsynthidvocals
Serving providers2
Canonical IDlyria-3.5

SOMA X v0.3.0 Capabilities

animationhand-modelinghuman-body-modelingmotion-retargetingpose-inversionsimulation
Serving providers0
Canonical IDnvidia/SOMA-X-v0.3.0

Primary Evidence

Sources and Freshness

Questions

Lyria 3.5 vs SOMA X v0.3.0 FAQs

Is Lyria 3.5 or SOMA X v0.3.0 better for coding?+

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

Which is cheaper, Lyria 3.5 or SOMA X v0.3.0?+

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 SOMA X v0.3.0?+

Neither model has a larger sourced context window in this comparison. Lyria 3.5 is 1,049K and SOMA X v0.3.0 is —.

Which performs better in benchmarks, Lyria 3.5 or SOMA X v0.3.0?+

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 SOMA X v0.3.0 be self-hosted?+

SOMA X v0.3.0 is the only model in this pair currently marked as self-hostable. Lyria 3.5 is not marked open weight; SOMA X v0.3.0 is open weight.

Can Lyria 3.5 and SOMA X v0.3.0 understand images?+

Lyria 3.5 is documented with image input; SOMA X v0.3.0 is not documented with image input. This reflects supported input modalities, not vision quality.

Which can generate longer answers, Lyria 3.5 or SOMA X v0.3.0?+

Neither has a larger sourced maximum output. Lyria 3.5 is 66K and SOMA X v0.3.0 is —.

Do Lyria 3.5 and SOMA X v0.3.0 support reasoning and tool use?+

Lyria 3.5: image input. SOMA X v0.3.0: 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 SOMA X v0.3.0?+

Lyria 3.5 has 2 sourced provider routes; SOMA X v0.3.0 has 0, so Lyria 3.5 has broader tracked availability.

Which offers better value, Lyria 3.5 or SOMA X v0.3.0?+

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