INB
Status
| Field | Value |
|---|---|
| Extension(s) | .inb |
| Common ecosystem | Inbro-related lead |
| Format family | Machine-specific lead |
| Satin Studio status | Researching |
| Open / import | No |
| Export | No |
| Confidence | Low-medium. |
What it is
INB is reported for Inbro-related embroidery workflows in converter ecosystems.
Satin Studio direction
Research lead only.
Versions and variants
Tracked as a format lead until files confirm machine family, header layout, and command mapping.
File identification notes
Reported structure includes a large 8192-byte header followed by unsigned x, y, control-style records.
Observed structure notes
- Observed INB readers skip an 8192-byte (
0x2000) header before the stitch stream. - Observed records are three bytes: X, Y, control. Control bit
0x40negates X and bit0x20negates Y after Y inversion. - Observed low-nibble controls include
0x0stitch,0x1color change with movement,0x2jump, and full control0x04end.
Structure sketch
Observed INB files use a large header and three-byte records:
struct InbCandidate<'a> {
header: [u8; 0x2000],
records: &'a [InbRecord],
}
struct InbRecord {
x: u8,
y: u8,
control: u8, // 0x40 negates x; 0x20 negates y
}
enum InbCommand {
Stitch, // control & 0x0F == 0x00
ColorChange, // control & 0x0F == 0x01
Jump, // control & 0x0F == 0x02
End, // control == 0x04
}
What we still need
Known-source files, header samples, command mapping, and reader validation.