TAP
Status
| Field | Value |
|---|---|
| Extension(s) | .tap |
| Common ecosystem | Happy embroidery workflows |
| Format family | Headerless expanded stitch stream |
| Satin Studio status | Researching |
| Open / import | No |
| Export | No |
| Confidence | Medium. |
What it is
TAP is associated with some Happy embroidery machine workflows and conversion tools.
Satin Studio direction
Possible import after DST/EXP if files appear.
Versions and variants
TAP may be closely related to DST stitch data without the 512-byte DST header. If that relationship holds for user files, Satin Studio could reuse a DST stitch decoder while handling missing header metadata explicitly.
File identification notes
Reported structure is DST-encoded stitches with no DST header. That means labels, extents, and counts may need to be recalculated instead of read.
Observed structure notes
- Observed TAP readers parse the file directly as DST three-byte stitch records with no 512-byte header.
- Because the header is absent, label, extents, stitch counts, and color-change counts must be recalculated or supplied externally.
Structure sketch
TAP is reported as DST-compatible stitch data without the 512-byte DST header.
struct TapCandidate<'a> {
records: &'a [DstRecord], // reported headerless DST body
}
struct DstRecord {
b0: u8,
b1: u8,
b2: u8,
// decode with DST weighted movement and command bits if compatibility is proven
}
What we still need
Happy-machine files, confirmation of DST-compatible body encoding, and reader validation.