model family

Moonshine

Published by UsefulSensors. 1 member has been measured on real machines. Every number below was signed by the machine that produced it — none of it is from a model card.

what it takes, what it returns
audio → text

Declared by the network’s catalog, not measured — a signature says what this family would be asked. Whether it answered is the signed capability flags on each member.

1 of 2 builds measured · 1 still open

Builds this network knows of

Declared, not measured — this is what the catalog says exists and what it would cost a machine to hold. Nothing here is signed, and none of it claims the build works.

how much memory does your machine have

2 of 2 builds fit a 16 GB machine — budgeting 70% of it, or 11.2 GiB, because the cache and the runtime want the rest.

  • UsefulSensors/moonshine-tinyspeech-podmeasured herepublished by UsefulSensors
    0.1 GiB
  • UsefulSensors/moonshine-basespeech-podpublished by UsefulSensors
    0.2 GiB

Sizes are what the catalog declares, not what a machine measured — fitting on disk is necessary and not sufficient. Nobody here has run these on your machine, and this narrows the candidates rather than certifying one.

the same builds, by member
moonshine base
UsefulSensors/moonshine-basespeech-pod234 MiB on diskpublished by UsefulSensors
moonshine tiny
UsefulSensors/moonshine-tinyspeech-pod103 MiB on diskpublished by UsefulSensors
ask your own gram

Your concierge can answer this from the network rather than from this page. The ask carries the operator id, so it resolves to a capability and an engine — not to a name somebody has to recognise.

What has this network measured about the Moonshine family (epn.family.moonshine), and can my gram run any of it? See /inferences/moonshine

open a gramx with this ask →epn.family.moonshine