A .wt is a Bitwig wavetable: a fixed 12-byte vawt header, then raw signed 16-bit samples. The header names the length of one single-cycle wave and how many waves are stacked; the data is those waves laid end to end, frame-major, no interleave. Bitwig writes one whenever you drop a WAV onto Polymer or another wavetable device. Hover any field or byte to light its exact span and read the decode. Color marks kind, the way syntax highlighting does (see the key). Example: vawt + 2048 samples/wave + 256 waves, a real 1 MB table.
Top to bottom, what a reader walks. There is no footer: the file is exactly 12 + frame_count * frame_samples * 2 bytes.
The whole header, drawn below as a byte map. Four fields, all little-endian: the magic, the wave length, the wave count, and the offset where samples begin.
Immediately after the header: frame_count * frame_samples signed 16-bit little-endian samples, laid out frame-major. Wave 0's complete cycle comes first, then wave 1's, and so on. No per-wave header, no interleave. Full-scale (observed range spans the whole -32768..+32767).
frame_samples is not fixed. Across a 5636-file corpus, three values appear; 2048 dominates.