T01 / T09
Status
| Field | Value |
|---|---|
| Extension(s) | .t01, .t09 |
| Common ecosystem | Wilcom conversion leads |
| Format family | Headerless stitch streams |
| Satin Studio status | Researching |
| Open / import | No |
| Export | No |
| Confidence | Low-medium. |
What it is
T01 and T09 are tracked as Wilcom-related stitch-stream leads.
Satin Studio direction
Research after DST/VP3-family import foundations.
Versions and variants
Treat each numbered extension separately. The number may identify the underlying stitch encoding.
File identification notes
Reported details:
.t01: DST-encoded stitch data without the 512-byte DST header..t09: Pfaff-family data lead.
Observed structure notes
- Observed T01 support treats the body as DST three-byte records without the 512-byte DST header.
- T09 remains a Pfaff-family lead with insufficient structure detail here. Treat each numbered extension as its own dialect.
Structure sketch
Treat numbered T files as different leads. T01 is reported as DST body data without the DST header.
struct T01Candidate<'a> {
dst_records_without_header: &'a [DstRecord], // no 512-byte DST header
}
struct DstRecord {
b0: u8,
b1: u8,
b2: u8,
}
struct T09Candidate<'a> {
header_or_metadata: &'a [u8], // Pfaff-family lead, unverified
payload: &'a [u8],
}
What we still need
Known files, safe signatures, and confirmation of underlying encodings.