NOKTA user guide Manual preview · interface reference 0.9
User guidev0.9

Learn the machine. Then stop looking.

NOKTA is built around one idea: each track follows the same clock while owning its own loop. This guide takes you from a blank 4/4 pattern to a playable, polymetric system without turning the instrument into a menu.

Tracks
16
Range
1–64 steps
Views
Orbital · Grid
NOKTA instrument in three-quarter view
01
Five-minute start

From one trackto a moving system.

A new pattern opens deliberately plain: all sixteen tracks are 16 steps long, and only Track 1 is active. Build the relationship yourself so every change is audible.

  1. 01
    Start the host.

    Press play in your DAW. In Standalone, use NOKTA’s transport and tempo field.

  2. 02
    Listen to T1.

    The opening loop is a regular four-on-the-floor reference at 16 steps.

  3. 03
    Enable T2.

    Use the second rail row or press 2 while Bank A is visible.

  4. 04
    Turn LEN from 16 to 15.

    LEN moves in exact one-step detents. The request waits for T2’s next loop.

  5. 05
    Shape, then protect.

    Edit trigs, press CAPTURE, perform, and use RELOAD to return to the marked pattern.

Core rule

Change one length first. Add complexity only when you can hear what the previous difference created.

02
Machine anatomy

Five zones.One causal path.

NOKTA interface with Orbital view active 12 34 5
PLAY surface · hardware theme · Orbital view
1Track rail

Select, mute or solo the visible bank of eight tracks.

2Main screen

See relationships in Orbital or edit detail in Grid.

3Control cluster

Nine direct controls follow the selected track or held step.

4Performance strip

Fill, seed, apply boundary, capture and reload.

5Trig row

Sixteen physical steps; pages appear for longer tracks.

03
Core concept

Same pulse.Different returns.

Polymetry does not require different tempos. Every track advances on the shared clock; its LEN decides when that track returns to step 1.

T116
T215

The downbeats separate by one step per cycle, then meet again after 240 shared steps.

LEN

Every integer is valid

Use any value from 1 to 64. Prime and odd lengths are not hidden behind a “musical” ladder.

LANDING

Changes are boundary-safe

A structural request becomes active at the selected musical boundary, never halfway through the old loop.

DIV

Slow a track independently

DIV advances a track once every 1–8 shared steps, creating slower relationships without changing the host clock.

04
Track controls

Nine controls.No hidden page.

Turn a knob with no step held to edit the selected track. The screen names the target and shows the value while you move.

ControlRangeWhat it changes
LEN1–64

Track loop length, in exact ±1 detents. Structural and boundary-applied.

NOTESOff–LEN

Euclidean pulse count. Off preserves the hand-programmed pattern.

ROT0–63

Rotates the generated pattern; the value wraps inside the current length.

DIV1–8

Advances the track once every N shared steps.

SWING0–100%

Delays off-beat positions on this track.

GATE2–100%

Default note duration for the track.

VEL0–127

Default MIDI velocity and accent level.

PROB0–100%

Default note probability, resolved deterministically from the current seed.

COND11 states

Always, cycle positions, previous-step states, Fill and Not Fill.

05
One sequence, two views

See the relationship.Edit the evidence.

Orbital relationship view
Orbital · radius identifies tracks; phase and active steps reveal how loops relate.
Grid step editor
Grid · nine parameter rows expose the same pattern one step at a time.
Same state

GRID and EUCLID never copy or translate a pattern. Switching views changes only the representation.

06
Step workflow

Hold a trig.Turn the same knobs.

A held step temporarily re-targets the controls. Track defaults remain intact; only that step receives the locked value.

1Choose a step

Press and hold a trig until the screen names Tn · STEP n.

2Turn a control

The animation previews the exact parameter and value being written.

3Release or Esc

The cluster returns to track scope automatically.

NOKTA length feedback showing a pending 15-step loop
Track LEN feedback · requested value 15 · lands at the next track loop
NOTES → NOTEPer-step MIDI note
ROT → MICROEarly/late placement
DIV → RATCHET1–8 retriggers
SWING → TIEConnect to next note
VEL · PROB · GATE · CONDKeep their meaning at step scope
LENUnavailable: a single step has no loop length

Grid pages and rows

Pages 1–4 address steps 1–64. Clicking beyond the current lane end extends LEN so the edited step becomes part of the sequence.

TRIGNOTEVELGATEPROB MICRORATCHTIECOND
07
Performance strip

Make a move.Keep a way back.

FILL

Hold for variation

Momentary. Conditions listening for Fill respond only while the key is held.

SEED

Re-roll deterministically

Changes probability outcomes. The visible hex seed makes the result recognisable and undoable.

APPLY

Choose the landing

Cycle through next Step, Beat, Bar or Cycle. PLAY never selects Instant.

CAPTURE

Mark this pattern

Stores the current resolved sequence as a performance return point.

RELOAD

Return to the mark

Restores the captured state. The key remains dim until a capture exists.

Safety

UNDO is always in the header. PANIC sends the emergency note release path if a receiver keeps sounding.

08
MIDI and export

Route per track.Export the performance.

Per-track routing

SET exposes channel, fixed note, transpose and gate mode for all sixteen tracks at once.

  • Use one channel per instrument for independent parts.
  • Route several tracks to one channel with different fixed notes for a drum rack.
  • Set NOTE to PATTERN when the programmed pitch should pass through.
DRAG OUTNOKTA-pattern.mid

In Orbital view, drag from the cycle hub to the DAW or desktop. Export is capped at 64 bars so very long full cycles remain usable.

MIDI-effect routing depends on the host. Confirm the destination receives NOKTA before relying on a live set.

09
SET

Configure all sixteen.Perform eight at a time.

SET is global configuration, so Bank A and Bank B remain visible together. The live rail stays banked to preserve large, reliable targets.

NOKTA SET view showing Bank A tracks 1 to 8 and Bank B tracks 9 to 16
SET · Bank A and Bank B remain visible together
BANK ATracks 1–8

Channel, note source, transpose and gated/one-shot mode.

BANK BTracks 9–16

The same controls, shown beside Bank A instead of hidden behind it.

VISUALHardware / Normal

Switch material presentation without changing the sequence or control layout.

3D MODELPresentation view

A separate full-instrument visualization. It is not embedded inside the sequencer screen.

10
Keyboard reference

Fast routes.No secret modes.

TabSwitch Bank A / B while keeping the same visible track slot.
1–8Enable or disable the corresponding track in the visible bank.
← / →Select the previous or next track.
↑ / ↓Nudge selected-track LEN by exactly +1 / -1.
EscClear an armed step lock and return the knobs to track scope.
⌘ ZUndo the last gesture.
⇧ ⌘ ZRedo.
11
Troubleshooting

Read the state.Then fix the route.

I see motion but hear nothing.

NOKTA generates MIDI, not audio. Route its MIDI output to an instrument track and confirm that track is armed or monitoring.

LEN shows a new value but the ring has not changed.

The value is pending. Structural edits wait for the selected APPLY boundary; the screen confirms when the new loop lands.

A note keeps sounding.

Press PANIC in the top strip. Then check the receiving instrument and avoid switching routes while tied notes are active.

The knobs are editing one step instead of the track.

Press Esc or click empty panel space. The screen header should return from Tn · STEP n to TRACK n.

I cannot see tracks 9–16.

Press BANK or Tab. SET shows both banks together; the performance rail shows one bank of eight at a time.

RELOAD does nothing.

RELOAD is intentionally inert until CAPTURE has marked a return point.

Still blocked?

Capture the state before changing it.

Note the host, plugin format, selected track, visible bank, APPLY boundary and exact gesture. That is enough context to reproduce most sequencing issues.

Return to product page