MAJORFailure Reference

Luma Dream Machine Text Rendering Failure — Pre-Generation Risk Reference

Technical Classification

Glyph Synthesis & Typographic Coherence Failure

Luma Dream Machine shares the typographic limitation common to diffusion video models: no character-level encoder. Letters are synthesized as visual texture rather than reconstructed from characters. Any prompt requesting readable signage, packaging copy, screen UI, or printed text produces marks that look text-shaped but spell nothing. Failure is reliably reproducible on any prompt with explicit text.

How to identify this failure

  • Storefront signs rendered as glyph-shaped smudges
  • Letters mirroring or inverting between frames
  • Brand names substituted with letter-shaped nonsense
  • Screen UI showing illegible mock-text
  • Numbers shuffling between frames on the same surface

Real generation examples

Prompt used

"Cafe storefront with sign reading 'COFFEE', morning light"

Failure observed @ 0:00

Sign rendered as glyph-shaped smudge with no readable characters at 0:00–0:05

Prompt used

"Open book showing the words 'Chapter One'"

Failure observed @ 0:02

Page rendered with letter-shaped marks that do not spell any word at 0:02

Documentation strength

If you need to escalate

HIGH — Luma support recognises text-rendering as a current model limitation; refunds are routinely granted with a documented Generation ID.

AVA is a pre-purchase prevention tool, not a post-purchase recovery tool. Platforms generally do not guarantee credit refunds for output-quality failures; goodwill credits are at each platform's discretion. The strength rating reflects how well-formed your support ticket can be, not a promised outcome.

Prevention + documentation steps

  1. 01

    Score your prompt before you generate

    Run your prompt through AVA's pre-flight scoring against the Glyph Synthesis & Typographic Coherence Failure pattern. Green light = generate. Yellow/red = rewrite using the suggested fix before you commit credits.

  2. 02

    Capture Generation ID + timestamp if it failed anyway

    Find the Generation ID in the URL or share link. Note the exact time when the Glyph Synthesis & Typographic Coherence Failure first appears (e.g. "failure first visible at 1.2s"). Timestamped evidence is significantly stronger than a general complaint.

  3. 03

    Use the correct technical term in your support ticket

    Describe this failure as "Glyph Synthesis & Typographic Coherence Failure". This term maps to a recognised internal workflow in the support system and routes the ticket to the right team.

  4. 04

    Submit via the correct support channel

    Runway has no direct email intake. Pro+ plan: open the in-app AI Assistant (help widget bottom-right of app.runwayml.com), describe the failure with the technical term, attach evidence. Free/Standard plan: human support isn't available — your channel is Discord #community-help with @On Call - Moderators.

Frequently asked questions

Does Luma support response credits for text rendering failures?

Yes. Submit the generation ID, prompt text, and a screenshot of the unreadable text region. Luma support recognises Glyph Synthesis Failure as a known mode.

Why can't Luma render readable text?

Luma synthesizes text as visual patterns through diffusion rather than reconstructing glyphs from a character-level tokenizer. Without a text-conditioned encoder in the pipeline, legible typography is statistically unlikely.

What's the workaround for Luma text rendering?

Avoid prompts that require readable signage, packaging text, or book pages. Add text in post via After Effects or Premiere. AVA flags text-rendering risk in your prompt before submission.

Catch it before you generate

AVA scores this failure mode against your prompt in real time

Free Chrome extension. Analyzes your prompt as you type, flags failure-prone patterns specific to this model, and tells you what to rewrite — before you commit credits to a generation that will fail.

AVA Pro · founders' round

$50 for 6 months of unlimited scoring across all failure modes + personal failure-history dashboard. Locks in $13/mo grandfathered after.

Claim $50 founders

Related failures across models

If you’re seeing this failure, you may also encounter these on other models:

Pick a different tool for Luma failures

Some prompt shapes will keep failing on Luma. Routing those shots to a different vendor is the cheapest fix.