Threadsmith Sequence Optimizer

What it is for

Many embroidery files are sewn in an order that wastes time: the machine trims, jumps across the hoop, sews a small piece, trims again and comes back. Every trim costs a few seconds and leaves two thread tails; every colour stop waits for you. On a 200-piece order that adds up to hours.

This tool reads a Tajima DST, Brother PES, Janome JEF or Melco EXP file (or a stitch list), cuts it into the segments that are sewn without a jump or trim, and looks for a better order. A segment may be sewn backwards when that brings its start closer, and colour blocks that use the same thread can be merged into one stop. Segments whose stitches overlap keep their original order, so nothing that was on top ends up underneath. Every stitch is kept: the tool checks that the output has exactly the same penetrations, then writes the file and decodes it again.

It does not redigitize anything. Stitch lengths, density, underlay and tie-offs stay as they are.

Worked example

The first example uses the monogram badge template as a DST file. The tool found 26 sewn segments and reversed 11 of them:

Trims: 15 → 10 · Jumps: 26 → 26 · Colour changes: 2 → 2 · Sewing time: 8 min 46 s → 8 min 26 s. All 4,925 stitches kept.

Five trims disappear because several gaps became shorter than the 5 mm trim distance, so the machine just jumps. That is 20 s per piece, or more than an hour on a 200-piece run.

The second example takes the name tag as a Melco EXP file and writes an optimised DST at 800 stitches per minute: trims drop from 19 to 12 and the time from 3 min 34 s to 3 min 6 s, with all 1,503 stitches kept.

The third example is a stitch list with a red square, a blue square and another red square that don't touch. The two red blocks are merged: colour changes go from 2 to 1 and the time from 50 s to 30 s.

How to read the result

• Trims, jumps, colour changes: before → after. The new order is only used when none of them goes up and at least one goes down; otherwise the file is written unchanged and the result says so.
• Sewing time: stitches at your speed plus 4 s per trim, 20 s per colour change and 0.15 s per jump.
• Segments / reversed segments: how the file was cut up and how many pieces now run backwards.
• Stitches preserved and verified: the input and output have the same penetrations, and the written file decodes back to them.
• Colour order for the machine: thread the needles in this order.

Tips and common mistakes

• DST and EXP files store no colours. Enter the thread colours in sewing order, otherwise colour blocks are never merged.
• Jumps count as moves: one long move that a format splits into several records counts once.
• Lower the trim distance if your machine trims short jumps anyway, or raise it to keep more jumps untrimmed.
• Turn off Allow sewing segments backwards for designs where the sewing direction matters, such as directional satin effects.
• Open the result in a viewer or the Threadsmith app and test-stitch before a production run.

FAQ

Can it change how the design looks?

Overlapping segments keep their order, so layering doesn't change. Segments sewn backwards land on the same needle holes, but the thread lies slightly differently at their ends.

Why did it find nothing better?

Designs that are already sewn colour by colour, nearest piece next, often can't be improved without adding trims or jumps somewhere else.

Does it keep tie-in and tie-off stitches?

Yes, they are part of the segments. Where a trim disappears, the tie-off before it stays in the file.