Autoregressive image generation has always lost on speed, which is why models like it mostly went unused. BitDance's claim is that it fixes exactly that, and the author's test puts a number on it: about 25 seconds per image on a 48GB 4090, with generation quality that is genuinely different from the diffusion models he compares it against.

Evidence note: this episode ships no workflow JSON - the model runs behind a WebUI, not a ComfyUI graph. All numbers below are the author's on-camera observations, not graph values.

When this is useful

  • You want to try an autoregressive image model without installing anything locally.
  • You care about prompt adherence and final-image convergence more than fine texture detail.
  • You need direct English or Chinese text rendering inside the generated image.

What BitDance is

A 14-billion-parameter autoregressive image generator. Autoregressive means next-token prediction, applied here to image tokens, which historically makes generation slow: the author's reference point is that autoregressive models like the GLM-Image family are simply slower. BitDance's contribution is speed, not a new architecture.

Two weight variants ship:

  • 64X, the distilled fast one, used by default after auto-start. Roughly 25 seconds per image in the author's test.
  • 16X, slower, but able to generate smaller images such as 512-class and 1024-class sizes.

What the author found, task by task

Aspect Reported result
Portraits Reasonable; one sample had a broken hand
Detail rendering (64X) Not especially good
English text in image Works directly; no clear lead over the comparison models
Chinese text Works
Stylisation Good
Prompt adherence Top tier, per the author
Complex scene Handled a multi-subject prompt (elderly man on a plaza bench, pink-haired woman to one side, dog with a blue scarf to the other, clown juggling three specified colours behind, broken paper cup in a corner) with acceptable aesthetics
Aesthetics vs Qwen-Image Slightly ahead
Very long prompts Behind Qwen-Image
Convergence Strong, which the author attributes to the autoregressive path
Identity vs other models Clearly a different look; an RPG-style illustration separated it from the comparison set immediately

Step by step

  1. Open the mirror and deploy an instance. The author follows the official recommendation and rents a 48GB 4090; overnight rates on 4090 and 5090 are cheaper.
  2. Register through the link first if you are new; identity verification adds platform credit.
  3. Wait while the model loads and the service auto-starts.
  4. Click the BitDance button to open the WebUI.
  5. Enter a prompt, pick a width and height from the presets, set step count, CFG and whether to randomise the seed.
  6. The author keeps steps and CFG at their defaults and considers that sufficient.
  7. Switch to the 1.0 variant if you want to compare the non-distilled behaviour.

Parameter basis

No JSON exists for this episode. What the material actually establishes:

Item Value Basis
Parameters 14B, autoregressive spoken
Speed, 64X ~25 s per image author's observation
Speed, 16X slower spoken, no figure
GPU 48GB 4090 platform recommendation quoted by the author
Startup model auto-loads, service auto-starts spoken
Controls exposed prompt, width/height presets, steps, CFG, seed toggle on screen

Nothing beyond that is claimed, because there is no graph file to read.

Limits

  • Hands break. The author shows one portrait with a collapsed hand, and calls the results "acceptable" rather than good.
  • Detail at 64X is soft. This is an explicit negative finding, not an oversight.
  • Long prompts lose. Against Qwen-Image on very long text, BitDance is behind.
  • The timing is one observation. 25 seconds on one card, one session, is not a throughput benchmark.
  • No ComfyUI graph yet. The author expects ComfyUI support soon; at the time of recording this is a WebUI-only route.
  • Transcript variance. The load-time figure is quoted as about five minutes in this episode's subtitle; a duplicate transcript of the same talk elsewhere in the source tree says 15. Treat startup time as "several minutes" rather than a precise number.

Episode resources