Skip to content

Atomik Rack v0.2.0-rc.2

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 28 Oct 19:42
· 1890 commits to main since this release

Release candidate 2 of Atomik Rack 0.2.0.

Signing: Windows not signed, macOS ad-hoc signed only, SHA256SUMS is not signed. A build that is not signed makes the system warn on first launch; see the README for the first-run steps. Verify the downloads against SHA256SUMS.

Added

  • Automate a mixer channel, the master or an effect. Any parameter that can have a lane now can: right-click a knob or fader of a console strip, the master, an insert or send effect or any effect in the rack, in the mixer or in the rack, choose Edit Automation, and the lane is added on an automation track, in one undo step, and shown in the arrangement (the old "automate it through a macro" workaround is not needed; the macro route still works). An automation track is the usual DAW track of a device that plays no notes: it belongs to the channel or effect, shows its name and colour, and holds automation lanes alone (no note lane, no audio lane). The first lane shares the track's header row, which carries the name, the expand chevron, a mute button and that lane's write-mode and arm buttons; the other lanes fold and collapse as on any track. It can be renamed, coloured, moved, put in a folder, copied with its device and deleted like any track. Mute stops its automation (the param keeps its own value); solo has no meaning for it: it has no solo or arm button, a folder's solo and arm leave it alone, and soloing another track does not silence it. It cannot be frozen. Automation recording (the W button, Touch, Latch, Overwrite) writes into these lanes like any lane, the strips, the master and the rack controls follow them while the song plays, and a bounce plays them exactly as it plays an instrument's lanes (bit-identical across block sizes). The master section now draws the automation mark on its controls, as the channel strips do. A device inside a container, an audio track and the internal parameters still have no lane. Project format 34: a track may sit on a device without a Notes input and then holds "automation" lanes only; every older file loads unchanged, and a project without such a track differs from its version 33 file in the version line alone.

  • The loop is between a left and a right locator flag. The loop bar in the arrangement ruler is gone: an L flag marks where the loop starts and an R flag where it ends, drawn like the song's E flag, with a tint between them in the ruler (faint while the loop is off, clearly stronger while it is on; the lanes keep their loop shading). Drag a flag to move it (it snaps, the disable-snap keys free it, Escape cancels, and one drag is one undo step; the left flag cannot pass the right one), choose Transport > Set Left Locator at Playhead or Set Right Locator at Playhead, or right-click the ruler and choose Set Left Locator Here or Set Right Locator Here. The commands have no default key and can be mapped in Settings > Keyboard. Flags that meet stay readable: R hangs to the left of its line, L and E to the right, and a flag that would cover another moves down one row; where R and E share a tick, a press on the shared line takes R. A press in the lower band of the ruler now locates the playhead like the bar numbers (it no longer toggles the loop or draws a new loop; the loop button, Loop to Selection, a click on a range marker and the flags set it). Alt+click and Ctrl+click (Cmd) in the ruler still set the left and right locator.

  • Edit Automation on a control. A right click on a knob, fader or switch of an instrument in the rack (or of the console or the parameter pane) now offers Edit Automation at the top of its menu: it adds the automation lane of that parameter to the device's track (the track too, when the device has none), unfolds the track's lanes and the folders that hide it, brings the arrangement into view and outlines the lane, ready to draw in. When the lane is already there it only shows it. Adding is one undo step, and an empty lane holds no automation until you draw. A parameter a macro drives opens the macro's lane on the bank's track. Channel strips, the master and effects get an automation track of their own (see the entry above). View > Show Automation Lane now also brings the arrangement into view. New command automation.edit_control (menu only, no default key).

  • A dragged note ends where you let go. Drawing a note in the piano roll (the Pencil, or a double-click with Select) and dragging now ends the note at the pointer, snapped to the current snap (the disable-snap key frees it), and the note follows the pointer while you drag; before, the drag was added to the default length. Dragging left of the start keeps the minimum length (one snap step), and a click without a drag still draws a note of the default length. A chord stamp is stretched the same way.

  • Stepping through notes plays them. In the piano roll, Left and Right (and Shift+Left and Shift+Right) now sound the note they select, on the track's instrument, for a quarter of a second; the next step, a click, closing the roll or opening another clip ends it at once, so nothing hangs. Shift+Right and Shift+Left now move the end of the selection like a text selection: with the selection extended to the right, Shift+Left gives the last note back (and once only the starting note is left, extends to the left past it), and the other way round. A selection made another way (a rubber band) starts from its earliest note, so Shift+Left first drops its latest one. A shrink sounds the note the selection now ends on.

  • Guitar Amp. A new effect, atomik.guitar-amp ("Guitar Amp" in the browser): a guitar amplifier with a cabinet, chorus, delay and reverb, and five setups. The signal runs through a noise gate (gate), a tight high-pass and a mid boost (tight, boost), a three-stage preamp (gain) with a passive-style tone stack (bass, mid, treble, which affect each other) and a power amp (master, sag, presence, depth), then a cabinet synthesised from designed filters (1x12 open, 2x12, 4x12 closed or none, with a mic position from the centre of the cone to its edge; no recorded impulse response), a chorus, a ping-pong delay (in ms or as a note value at the project tempo) and a reverb, each with an on switch and a mix, and a level. The preamp and the power amp run at four times the sample rate and every clip is antiderivative anti-aliased, so a high note at full gain keeps everything that is not a harmonic below -53 dB; the 35 samples of latency are reported, so plugin delay compensation and the bypass switch keep the amp in time with the rest of a project. The amp plays the mono sum of its two inputs (the cabled one when only one is) and makes the stereo image with its effects. The setup selector loads Clean, Crunch, Industrial Rhythm (very high gain, tight and percussive for drop-tuned guitars: a pre-gain high-pass and mid boost, a scooped but present mid, strong presence, a closed 4x12 and a noise gate), 80s Lead (hot, singing sustain, mid-forward and compressed, with a 380 ms ping-pong delay and a plate-like reverb) or Synthwave (clean to light crunch, bright, a wide chorus, a dotted-eighth delay and a big reverb): it sets every control in one undo step, and you tweak from there. The rack panel shows the speakers of the chosen cabinet with the microphone, in and out meters, a gate meter, and a one-line tooltip on every control. The five setups are level-matched. The amp is an original design and the setups are named for the sound, not for any product or player. See docs/DEVICES.md.

  • Export the song or the loop as an audio file. File > Export Song as Audio File... renders from the start of the song to the End marker and keeps the tail that is still audible (reverb and delay ring out, up to 10 s, cut where the output stays below -90 dBFS; never shorter than the End); File > Export Loop as Audio File... writes exactly the audio between the left and the right locator with no tail, so the file loops on the grid. Both ask for a WAV file, then for the options: 16-bit with dither (triangular, the default for 16-bit; none; or triangular with the noise shaped towards the high frequencies), 24-bit or 32-bit float, the sample rate (the project's, or 44.1, 48, 88.2 or 96 kHz: the render is converted before it is quantised), and whether a song keeps its tail. The render runs faster than real time on a worker thread through the same path as a bounce (mute and solo, the master section, automation, tempo ramps and plugins, the latter needing the plugin sandbox as a freeze does), on a copy of the project, so playback and editing go on; a progress bar with Cancel replaces the options, and a cancelled or failed export leaves no file (it is written under a temporary name and renamed when complete, and an existing file is replaced only by a complete one). The dither is seeded, so the same project exports the same bytes; 24-bit and float are not dithered. The choices are remembered in export.json next to settings.json. Both are commands (file.export_song_audio, file.export_loop_audio, no default keys) that can be remapped in Settings, Keyboard. The renderer gains 16-bit PCM output (atomik-render --format pcm16, dithered) and the QA server gains session_export. A bounce (atomik-render, session_bounce) still ends two beats after the End. No project format change. See docs/ARCHITECTURE.md.

  • A song End marker. The arrangement ruler shows an E flag where the song ends: drag it (it snaps like the loop locators, and one drag is one undo step), choose Transport > Set End Marker at Playhead, or right-click the ruler and choose Set End Marker Here. The lanes past it are shaded and the scroll bar covers it. The End is the length of the song for a render; playback still runs past it. Drawing, moving or stretching a clip past the End now moves the End out to the next bar line in the same undo step (it never moves back by itself). Projects need no migration: the End was already saved.

  • A tuner for the audio track input. The name plate of an audio track in the rack has a TUNER switch, on the left under the name, off by default: it opens a display with the note and octave of what is plugged into the track (a guitar or bass, 28 Hz to 1.6 kHz), a needle from -50 to +50 cents that turns green within 3 cents and lights an IN TUNE lamp, the frequency in Hz and the deviation in cents. It reads the input after the track's input gain whether or not the track is armed, smooths the needle, and holds the last note for 0.8 s when the string decays; a signal below about -56 dBFS shows PLAY A NOTE (raise the input gain for a weak pickup). Mute while tuning (on by default, a param of the track) silences the track while the tuner shows; the A4 reference (415 to 466 Hz, default 440) is a param too. Both are additive: older projects load with 440 Hz and mute on, and the tuner is hidden whenever a project opens. While it is hidden the panel has no display and no tuner settings and is one rack unit shorter. The analysis runs off the audio thread, so tuning costs the audio thread two small copies per batch.

  • A level meter in every audio track header in the sequencer. Each audio track shows a small stereo meter with a peak hold, a dB readout of the held peak (-6.2, +1.4, -inf) and a clip lamp that lights when a peak reaches 0 dBFS and stays lit until you click the meter. An armed track reads its input after the input gain, per channel (the level the transport bar's recording meter shows, and the lamp is shared with it: clicking either clears both); an unarmed track reads its playback, the output of its console channel after the fader and the mute, so the number is what you hear from the track. At the Small track height the header keeps the bars and the lamp and drops the readout; at every other height the meter sits on the first line, after the track name (an audio track's name has less room). The meters update even with the mixer hidden, and the sequencer repaints only when a visible meter changes. Note tracks have no meter (use the mixer).

  • Left and Right select the previous and next note in the piano roll. With the piano roll focused, Left and Right select the note before or after the selection in time order (notes that start together go from low to high pitch); with nothing selected, Right takes the first note at or after the playhead and Left the last one before it. Shift+Left and Shift+Right add the neighbour to the selection. The view scrolls to keep the note in sight. They are the commands Select Next Note, Select Previous Note, Extend Selection to Next Note and Extend Selection to Previous Note, remappable in Settings, Keyboard. In the standard keys the nudge already sits on Ctrl/Cmd+Left and Right (with Shift for a beat, Alt for a tick), so nothing moves; the legacy keys keep Left and Right as the nudge and leave the new commands unbound.

  • Notes are coloured by velocity. In the piano roll a note's fill (and its bar in the velocity lane) runs from a dim steel blue for a soft note, through blue and green, to a bright warm yellow for a loud one. A selected note is lifted toward white with a light outline, and a muted note stays a faint hollow fill in its velocity colour. The note clips in the arrangement keep the clip's colour.

  • Draw notes with the Select tool. In the piano roll, a double-click on the empty grid draws a note (at the snapped start, the length of the snap step or of the last drawn note, as the Pencil does) and selects it; keep the button down after the second press and drag to set where it ends. It is one undo step. A single click or drag on the empty grid still clears the selection and rubber-bands, and a double-click on a note does what it did.

  • A mouse cursor per edit tool, and resize arrows on a clip's edge. Over the arrangement's lanes and clips and the piano roll's grid the pointer shows the tool in use: a pencil for Pencil (its tip is the pointer), an eraser for Eraser, a pair of scissors for Razor, the arrow for Select; the alternate-tool key swaps it while held. The cursors are drawn in code, outlined for dark and light content, and sharp at 1x and 2x. A clip's right edge in the arrangement (and the start edge of an audio clip) now shows the horizontal resize arrows with Select, and keeps them during the drag; a note's ends in the piano roll already did, and the other tools show their own cursor there since they do not resize. Headers, the ruler and the buttons keep the arrow. No project format change.

  • Rename a device in the rack. Double-click the name on the plate of any rack device (instrument, effect, player, utility or container, inside a container too, in the docked and in the detached Rack window) and type a new name in place: Enter commits, Escape cancels, a click elsewhere commits, and an empty name gives the device back the default name of its type. It is the same name the track and the mixer channel show, so all three change together, as one undo step. No project format change.

  • Grain sampler. A new instrument, atomik.granular ("Grain Sampler" in the browser): one sample played as a cloud of grains, up to 64 at once per voice. Density, size, three window shapes (Hann, Tukey, percussive), a position through the sample with a scan (0 freezes, negative runs back) and a random spray, a pitch from the key, transpose and a per-grain scatter, a share of reversed grains, a random stereo spread and a grain cap that replaces the grain nearest its end. Eight voices by default with an amp and a mod envelope, a filter, an LFO, the mod wheel (spray by default), pitch bend and pitch, position, density, cutoff and level CVs. Drop a sample on the panel or load it from the browser (one sample; a drop replaces it in one undo step, relink works as for the sampler); with none the device plays a built-in vowel pad made in code. A high transposition is low-passed against aliasing. The panel shows the waveform of the sample window with the position, the spray band and the live grains, a sample strip and a tooltip on every control. Five sounds (Init, Frozen Pad, Shimmer, Stutter, Texture) load through the same one-undo-step batch as the FM synth's. examples/patches/granular-demo.json is a demo.

  • FM synth. A new instrument, atomik.fm-synth ("FM Synth" in the browser): four sine operators that phase-modulate each other through one of twelve routings (stacks, forks, pairs, additive), each with a frequency ratio (coarse step plus a fraction, or a fixed frequency in Hz), detune, level, velocity sensitivity, key level scaling and its own envelope with a delay; a damped feedback path on operator 4 that turns a sine saw-like without going to noise; a pitch envelope, an LFO (pitch, amplitude, index), the mod wheel and an index CV on the modulation index; poly with up to 16 voices and stealing, mono and legato with glide; stereo spread by key and the usual pitch, level and pan CVs. A bandwidth limiter eases the index and the feedback back on high keys so bright patches do not alias. The panel draws the algorithm as a diagram and each operator's envelope as a shape, with a row of controls per operator and a tooltip on every control. Six sounds (Init, E. Piano, Bell, Bass, Brass, Pad) load through the same one-undo-step batch as the guitar amp's setups. examples/patches/fm-demo.json is a demo.

  • Wavetable synth. A new instrument, atomik.wavetable-synth ("Wavetable Synth" in the browser): two wavetable oscillators, each with a table (twelve factory tables generated in code: saw to square, pulse width, sine to saw, sine to hollow, triangle to saw, vowels, a harmonic sweep, a hard-sync sweep, two FM families, seeded digital spectra and a drawbar organ), a frame position (0 to 100 %, the two neighbouring frames blended, so a sweep is smooth), octave, semitone, cents and level; up to seven unison copies of each with detune and stereo spread; a sub sine and noise; a stereo pair of state-variable filters (LP, BP, HP); an amp and a mod envelope and an LFO, any of which can move the frame positions, and the mod envelope or the LFO the pitch and the cutoff; velocity, pitch bend and the mod wheel as in the poly synth; CV inputs for the cutoff, pitch, position, resonance, level and pan. The tables are band-limited by octave (the oscillator reads the richest level whose harmonics stay below Nyquist, detune and pitch modulation included), so high notes do not alias; they are built once per process and shared by every instance, and process allocates nothing. The panel shows each oscillator's current frame. No project format change (the device is new; examples/patches/wavetable-demo.json is a unison pad). See docs/DEVICES.md.

  • Input gain, level meter and clip-safe for audio recording. Arm an audio track and the right end of the transport bar shows its input: INPUT GAIN (-60 dB, which is off, to +24 dB; drag or scroll, Shift for tenths of a dB, double-click for 0 dB; a drag is one undo step), SAFE and an input level meter in dBFS with a peak hold and a clip lamp that lights when the level after the gain reaches 0 dBFS and stays lit until you click the meter. It shows the selected armed track, else the first armed one, works before a take starts, and gives way to the clip inspector on a narrow bar. The gain is applied to the recording and to the input monitor alike, so what you hear is what is written, and a gain turned during a take glides without a zipper. SAFE puts a limiter on the take only (instant attack, about 43 ms release, the channels of a stereo track limited together, never above 0 dBFS, a take that stays below it untouched to the bit; the monitor is not limited); without it a hot input is kept as it was played in the 32-bit float file. Two tracks recording one input each keep their own gain. The settings are the track device's new rec_gain and rec_clip_safe params: stored, undoable and listed with the device, and a project written before them records at 0 dB with SAFE off, as it did. The engine gains EngineHandle::record_tap_gained (a gain and a limiter per recorded track, wait-free controls); the plain record tap is unchanged. See ARCHITECTURE.md 2.6.

  • Clip inspector. Select audio clips in the arrangement and the transport bar shows their properties to the right of the tempo and signature: FADE IN and FADE OUT in milliseconds, TRANSPOSE in semitones (the two decimals are cents), GAIN in dB and a REV button, with the clip's file name (or "N audio clips") in front. Values take the same drag, wheel (Shift: fine) and double-click-to-type as the tempo. With several clips a field shows a dash when they differ, and an edit sets all of them in one undo step. A fade never grows past the clip less the other fade. A reversed clip cannot be transposed and the Repitch warp mode does not transpose: when no selected clip can, the TRANSPOSE field is dimmed and its tooltip says why; in a mixed selection those clips keep their settings. REV switches a warped clip's warp and transposition off, as Reverse Audio does. With only an audio track selected the bar shows its name and the fields dimmed, with a tooltip saying to select a clip; with nothing audio selected the inspector is not drawn. On a narrow bar the clip name goes first, then the fields from the right (gain, reverse, transpose, fade out). Every field has a help tooltip.

  • Tooltips on the buttons. Resting the pointer on a button for 0.6 s shows a one-line tooltip under it that says what the button does and, when it runs a command that has a key, that key as the menus print it (the first chord of the active keymap, so a key you rebind shows at once, and an unbound command shows none). It hides on a press, a key, the wheel or when the pointer leaves the button, stays inside the window, and costs no repaint while it waits or when it does not change. Everything that is a button has one: the transport buttons and the tempo and signature readouts; the arrangement's tools, snap selector, track, lane, folder and take buttons and the marker list buttons; the piano roll's toolbar, scale bar and controller chips; the mixer's toolbar, snapshot bar, strip buttons and choices, inserts, output selectors and VCA strips; the rack's fold, edit, slice, TO CH, container, plugin, step sequencer, arpeggiator and drum generator buttons, its switches and choices and the breadcrumb; the sample, slice, step, sequencer and container editors and the parameter pane; the file browser's toggles, sort headers and path; the plugin banner; and the quantize, Strip Silence, Audio to Notes, Warp, MIDI Mappings, Macros, Find Parameter, Relink and Plugins panels. Settings > Workflow > Show tooltips (on by default, saved in workflow.json) switches them off, together with the rack's own hover texts of BYPASS and a return's EDIT button; the value readout shown while a knob or fader is dragged, the names of jacks and presets and the note mark of a track comment are information, not help, and stay. In the QA server session_pointer takes wait (seconds the pointer rests) and answers with the tooltip text; session_texts and session_screenshot show it. See docs/KEYBOARD.md.

  • Drag and wheel on values. The tempo and the time signature of the transport bar, the snap selector of the arrangement and the piano roll, and the values of the quantize, Audio to Notes, Strip Silence and Warp panels take a vertical drag (up increases, down decreases, 5 pixels per step) and the mouse wheel (one notch, one step). The BPM readout acts on the part under the pointer: whole BPM (tenths with Shift) or the two decimals; the signature steps the beats per bar on the left of the slash and the beat unit (2, 4, 8, 16) on the right; the snap selector and the quantize grid step through their lists in order and stop at the ends. A tempo or signature drag applies live and is one undo step. A click without movement does what it did (the snap selector now cycles on release instead of on press), and double-click still types the tempo or the signature. The gestures are in docs/KEYBOARD.md.

  • Drum Generator. A note player (atomik.drum-generator, "Players" in the browser) that plays 8 patterns of 16 lanes (one key each, by default the drum machine's 16 pads) and varies them with a pure function of the position: density adds hits on empty steps or removes hits, weighted by what the lane is (an original table: kick on the beats, snare and clap on the backbeats, hats on every eighth, toms late in the bar), variation moves hits a step and adds ghost notes in some bars, fill.every and fill.amount turn the end of every 2nd, 4th or 8th bar of the time signature into a fill, and accent boosts each role's strong positions. A bounce is bit-identical at any block size and worker count. The 4-unit panel has the pattern slots, a grid of 16 lanes by 16 steps with a page selector (a click toggles a step, a vertical drag sets its velocity, a square mutes a lane), COPY, PASTE and CLEAR, and the knobs; the lane labels show the pad names of the drum machine it is cabled to, directly or through other players. GENERATE writes the edited pattern from a style (four on the floor, broken beat, half time or straight), density and random.seed, RANDOMISE does the same with the next seed, each one undo step and the same pattern for the same seed. Project format 33 saves the patterns ("drums" on the device; older projects load unchanged and render the same). See docs/DEVICES.md.

  • CV Sequencer. A note player (atomik.cv-sequencer, "Players" in the browser): the step sequencer's patterns and note rules plus two rows of control voltage per pattern on curve_a_cv_out and curve_b_cv_out, held per step or sliding linearly into the next step, bipolar or unipolar with an amount, and a chain of 1 to 8 patterns that play in order, each in its own resolution and swing. The position is computed from the tick, so a locate, a loop wrap and a bounce land on the same step and curve value at any block size. The curves hold their last value on stop and while bypassed. The panel is the step sequencer's with a strip per curve; the grid editor shows two curve lanes for it (press or drag to set a value, Alt-click for a slide). Project format 32 saves the curves ("curves" on the device; older projects load unchanged and render the same). The player-demo project gains a Filter Sweep cabled to a synth's cutoff. See docs/DEVICES.md.

  • Player stacks. A note player can sit above an instrument and play through it for the instrument's track. Select an instrument (or a player of its stack) and add a player from the device browser, or the library's device rows: the player goes above the top of the stack in the rack, its notes are cabled into it, the track's notes now enter the new player (project format 31, "notes_to" on the track), and the whole step is one undo. A second player goes above the first. Shift adds the player unrouted, and a player dropped at a rack slot or created inside a container is a plain add. Deleting a player cables its note source to what it fed, and the track's entry moves to the next device down. The live keyboard on an armed track, the audition, a bounce and a freeze all play through the stack, bit for bit the same at any block size; a take records the notes you played, before the players; a project whose entry names a device that is gone plays the instrument as before. project_inspect and session_status list a track's notes_to. See docs/DEVICES.md, "Stacking players".

  • Note Repeater and Note Delay. Two note players (atomik.note-repeater and atomik.note-delay, "Players" in the browser). The repeater is an echo: every note keeps playing and adds repeats at a note value or a time in milliseconds, with a velocity decay per repeat, a pitch step in semitones or scale degrees, a gate and an optional dry note; repeats ring out after the key is released, across a loop wrap and while stopped. The delay moves every note event later (note value or milliseconds), with swing on the off-beats of a 1/8 or 1/16 grid while the transport plays and seeded humanize of time and velocity, keeping note lengths and never adding a note. Both keep their notes in a fixed queue of 512 scheduled events that drops notes, never note ends, when full, and have the BYPASS switch. See docs/DEVICES.md.

  • Key & Chord. A note player (atomik.key-chord, "Players" in the browser) that locks notes to a scale and plays chords from single notes: the scale (root and any of the piano roll's 16 kinds) snaps notes to the nearest, next higher or next lower scale note, or filters out the notes outside it; a chord (a diatonic triad, seventh or ninth on the scale, or any of the 21 chord kinds) with inversion, an open, drop-2 or bass voicing, an octave shift and a velocity for the added notes. Changing the scale or chord while keys are held releases the old chord exactly, so nothing sticks or doubles. A FROM CLIP button on its panel copies the scale of the clip open in the piano roll into the device in one undo step. It has the BYPASS switch of the other players. See docs/DEVICES.md.

  • Note Filter. A note player (atomik.note-filter, "Players" in the browser) that transposes and filters the notes cabled through it: transpose and octave, a key range (pass inside, pass outside or fold into the range), a velocity range, and velocity curve, scale, offset or a fixed value, with switches for pitch bend, controllers and pressure. A note shifted outside 0..127 is dropped, never clamped. Changing a param while keys are held releases the pitch each key actually sent, so nothing sticks or doubles. It has the BYPASS switch of the other players. See docs/DEVICES.md.

  • Bypass on the step sequencer and the arpeggiator. Both note players get a bypass param (appended last; older projects load with it off) and the BYPASS LED button of the effects in their name strip. Bypassed, a player passes its input notes straight through and plays nothing; the switch closes what it sent, and a key held at the switch is ignored until its own Off, so nothing hangs. See docs/DEVICES.md.

  • Tracks in a folder are indented. The content of a track header (chevron, name, M, S and R, the other buttons, and the labels of its lanes) moves right by 10 px per level of folder, up to three levels, so nested folders read as a tree. The clips and the folder rows do not move.

  • Rename a track in the sequencer. Double-click the name in a track header (an instrument, audio or bus track) to type a new one in place, or use Track > Rename Track... (also in the track header menu). Enter or a click elsewhere commits, Esc cancels. It is the mixer's rename (Command::Rename, a bus is renamed in the console too): one undo step, the name changes everywhere, and a blank name is ignored. A double-click on a note lane's label still renames the lane.

  • Detachable windows. View > Detach Rack (Ctrl/Cmd+Shift+F6) and Detach Mixer (Ctrl/Cmd+Shift+F5) put the rack or the console in a window of their own, on a second monitor for instance; closing the window, or the same command, puts it back. One document and one set of shortcuts serve all the windows, the meters run at full rate in the mixer window, files and library items can be dragged from the file browser into the detached rack, and the windows come back where they were at the next start (the main window too, maximised or not; a window that was on a monitor you removed opens on a visible one). --detach rack,console opens them at start. Drag between windows is not available on Wayland (it cancels with a note). The platform side is in docs/ARCHITECTURE.md.

  • Library. The file browser gets a Library section: Devices (the built-in devices), Patches, Containers, Clips and Projects, kept in a library folder (Documents/Atomik Rack/Library by default; Settings > Workflow > Library folder, or --library <dir>). Save to Library (the device and clip context menus; commands rack.save_to_library and sequencer.save_clip_to_library, unbound) writes the selected devices as a patch, one container as a container item, or the selected note clip as a clip, with the samples they use beside them; saving changes nothing in the project and the new row opens its rename entry. Double click or Enter loads an item (a device row is added like in the device browser, a patch or container is pasted, a clip goes on the selected note track at the playhead), and so does dragging it onto the rack (at the slot under the pointer, inside a container too) or a clip onto a note lane; each load is one undo step and brings its audio, and audio the item lacks stays missing and relinkable. A project opens after the question about unsaved changes, also when dropped on the window. Rename (F2, the context menu) renames an item with its audio folder and keeps its tags and favourite. New file types: .atomikpatch and .atomikcontainer (ordinary project texts with only devices, cables and sample entries) and .atomikclip (atomik-clip version 1: one note clip with its tempo and meter). Templates, a start screen and collect and relocate are not part of this. See docs/ARCHITECTURE.md.

  • The library in the MCP server. validate and project_inspect read the item files, library_list lists a library folder, session_open takes a library folder and session_library saves the selection or a clip into it and loads items back (recipe in docs/MCP.md).

  • MIDI learn. Map any parameter to a MIDI control by moving it. Mixer > MIDI Learn switches the mode on (the status bar says so, and every mapped control is outlined): change a control in the rack or the console and it is armed instead of moving, then move a knob, fader, pad or key on the hardware and the mapping exists. A right click on a knob, fader or switch offers Learn MIDI and Forget MIDI without the mode. The sources are 7 bit controllers, 14 bit controller pairs (MSB and LSB are recognised as one source), pitch bend and notes, on one channel or any, from one input or any; the targets are any device parameter (rack panels, console strips, the plugin parameter pane), a VCA group's level, the tempo, a transport key (play, stop, play/stop, record, loop, return to zero) and the selected strip (one fader that follows the console's selection). Each mapping has a range (a fraction of the target's own range), invert, a mode (absolute, three relative-encoder encodings, toggle and momentary buttons), soft takeover (an absolute control waits until it reaches the value, so nothing jumps; on by default) and whether it is consumed. A consumed control plays no notes into the armed track (on by default; a keyboard key you did not map still plays, and everything is consumed while learning). A move is an ordinary edit: the engine's smoothers apply it, a sweep is one undo step, and automation recording captures it as a touch that lets go half a second after the control stops. Controls with a mapping carry a small dot; Mixer > MIDI Mappings... lists them with their source, target, range, mode and switches to edit, re-learn or delete. Mappings are saved with the project (project format 28; older projects load unchanged and bounce bit for bit the same, and so does a project with mappings, which never change a render) and as presets: Export and Import MIDI Mapping Preset write and read a file that addresses devices by type and position (the first poly synth, channel strip 3) instead of by key, so a preset made for one project applies to the matching devices of another. Creating, editing and deleting a mapping is undoable.

  • Control surfaces. The Surfaces tab of Settings picks a control surface driver and the MIDI input and output ports it talks through (saved in settings.json, not in the project). The first driver is the common eight-fader motor surface protocol (MCU-compatible): 14 bit motor faders both ways (a touched fader is left alone; the touch sensors start and end an automation touch and hold one undo step), the master fader, V-pots with LED rings for the pan, mute, solo, record-ready and select keys with their LEDs, bank and channel keys (the strips are in console order: channels, then buses, then VCA groups), the transport keys and lamps, the jog wheel, the beats and timecode display, and the scribble strips (strip names, the pan and, while touched, the fader level). Feedback is sent only for what changed, at most thirty times a second, from the UI thread. The driver is plain Rust behind a small trait and tested byte for byte without hardware. A second protocol, level meters and OSC are on the roadmap.

  • MIDI control in the MCP server. project_inspect and session_status list the mappings; session_midi_input sends note, controller and pitch bend messages to the mappings as a live input would, session_midi_learn learns, edits and exports mappings, and session_surface plays a control surface on an in-memory port, so learn, mappings and the surface driver can be tested headlessly (recipe in docs/MCP.md).

  • Macro banks. A macro bank is a new device (atomik.macro-bank, in the device browser with the utilities) with eight macro knobs. Right-click any knob, fader or switch of a rack panel, a console strip or a row of the parameter pane and choose Assign to Macro > Macro 1 to 8 (or Assign to New Macro Bank): the param is driven by the macro between a minimum and a maximum, optionally inverted, and several params can follow one macro. A driven control shows the macro's value, wears an M1 tag, refuses a drag and keeps its right-click menu (Remove from Macro leaves the param at the value it had). A first assignment moves the macro so nothing jumps. Mixer > Macros... is the panel of the banks: a bar for each macro, a name edited in place, LEARN for a controller, and every assignment's range, invert and removal. The macros are automatable (the bank has its own track in the arrangement, which is also how an effect or a channel strip is automated, since only a device that takes notes has a track) and a lane on a macro plays as lanes on its targets, live and in a bounce, bit for bit like hand-made lanes. Project format 29 saves them; older projects load unchanged and a project without macros renders as before.

  • Find Parameter. View > Find Parameter... (Ctrl/Cmd+Shift+P) searches every parameter of the project, containers' insides, channel strips, buses, the master, plugin params, macros and VCA levels included, by track, device, param name and unit as you type (lead > filter > cut works, a prefix ranks above a substring above a fuzzy match). Each row reads track > device > param with its value, a macro tag and MIDI and lane marks; the arrows move, Enter reveals it in the rack or the console, Ctrl/Cmd+L shows its automation lane, M assigns it to a macro, E arms it for MIDI learn and Ctrl/Cmd+Left and Right adjust the value in place.

  • Automation follows the selection. View > Automation Follows Selection (also in Settings, Workflow; off by default) shows the lane of the parameter you touch: pressing a knob in the rack, a fader in the console or a row of the parameter pane adds the empty lane to the track when it is missing (no automation data is written), opens the folder that hides the track, shows a folded lane open without changing the project, scrolls it into view and outlines it; a param a macro drives shows the macro's lane, and selecting a device shows the last lane touched on it. View > Show Automation Lane does it on demand. Nothing is added while an automation take records.

  • Macros and the parameter search in the MCP server. project_inspect and session_status list the macro banks; session_macros makes banks and assignments, session_param_search and param_search search the session's project or a file (recipe in docs/MCP.md).

  • Note lanes. A track can have several note lanes that feed its device together. Add Note Lane, Rename Note Lane..., Delete Note Lane and Mute Lane are in the Track menu and the track header's context menu; a lane from the second on has a header with its name and an M button, and the first lane gets a small chip when there are several. A click on a lane's header, on its empty part or on one of its clips picks it: recording, Paste and MIDI import go to the picked lane. Clips drag between lanes, a double-click on a lane's name renames it, and a muted lane plays nothing (in playback, bounce and freeze) and exports no MIDI. Unmuted lanes merge: where two lanes start the same key or set the same controller at the same tick, the later lane wins. project_inspect and session_status list each note lane's index, label, name and mute.

Changed

  • The project format is version 31 (a track may have a notes_to, the top of its player stack). Version 30 files load unchanged.
  • The project format is version 30 (a notes lane may have a name and muted, and a track may have several notes lanes). Version 29 files load unchanged.
  • The project format is version 29 (an optional macros object after midi_maps). Version 28 files load unchanged. A MIDI mapping cannot be armed for a param a macro drives (map the macro), and the device browser lists the macro bank among the utilities.

Fixed

  • Controls follow their automation lane. A knob, fader, switch or selector of a parameter that has an automation lane now moves with the lane while the song plays, in the rack, in the console strips, in the parameter list of a plugin and in the detached windows, and shows the lane's value at the playhead when the song is stopped (a locate moves the controls too). Before, the sound followed the lane but the controls kept the value stored in the project. The stored value is not changed by playback: no undo step, and the project does not become modified. A control whose parameter has a lane carries a thin cyan ring and a dot at its corner, and its tooltip says it is automated. While you record a lane, the control shows the value you are moving (in Touch it follows the lane again when you let go); with the song stopped, a value you set by hand stays on show until you move the playhead or play. A lane on a muted track, or on a track another one's solo silences, plays nothing, so its control shows the stored value.
  • A project with comped takes opens after one of its comp clips was removed. A take group remembers the clips it compiled onto the lane; removing or moving one of them with an ordinary clip edit left its id in the group, the save wrote it, and opening the project failed with "clip N is not on this lane". The save now writes only the ids still on the lane, and opening drops an id that is not there, so a project saved that way opens as it was. No format change.
  • Every detached window animates. With the rack, the mixer and the sequencer in separate windows, only the focused one kept moving: the others froze until they were focused, because the OS's redraw requests were served window by window and the window it served first starved the rest. The app now paints every window that has something new each tick, asks again for a frame the GPU did not show, and, with more than one window open, presents without waiting for each monitor's vertical blank, so windows on monitors with different refresh rates no longer slow each other down (a single window keeps vsync). An idle app still paints nothing.
  • A reversed audio clip shows its waveform. The arrangement painted nothing for a clip with Reverse on, although it played: the waveform reads the source frames under each pixel column, and a reversed clip reads them downwards, so every column asked for a range that ended before it began and found no audio. Columns now take the range in either order, and the silent stretch at the left of a reversed clip that starts above the end of its file is skipped instead of ending the drawing. The waveform is the mirror of the forward one, right after toggling, when toggled back and after a save and reload (the picture depends only on the clip). No format change.
  • Context menus no longer repaint the window for every pointer move. An open context menu (the piano roll Notes menu with a big clip behind it was the worst case) marked the whole window dirty on every event, so each pointer move re-encoded and re-rendered the roll, thousands of notes included, even inside one row. It now repaints only when the highlighted row or the open submenu changes.
  • Reverse Audio works on a warped clip. Reversing a clip whose warp or transpose was on was refused by the model (a reversed clip cannot be warped), so the command did nothing and the clip kept playing forwards. Reverse now switches the warp and the transposition off and reverses in one undo step; the warp mode, tempo and markers are kept.
  • Tracks enter at the top of a player stack. A track made for an instrument that already has note players cabled into it, and a player cabled by hand into the device a track enters at, now make the track play through the stack (clips and the live keyboard reach the top player); cutting a note cable moves the entry back down to what still feeds the instrument. Before, such a track played the instrument directly and the players did nothing.
  • Submenus no longer vanish on the way to them. Moving the pointer from a menu row that opens a submenu (the arpeggio options of the piano roll notes menu, for instance) toward the submenu crossed other rows of the parent panel and closed it. Now a move inside the triangle between the pointer and the submenu's near edge keeps it open, and the pointer must rest on another row for about a quarter of a second to replace it, on the left side of a menu near the screen edge too. This is the one menu code of the context menus (piano roll, sequencer, rack, console); the macOS native menus are the system's.
  • Keys work in menus. In an open menu, Up and Down move the highlight (it wraps around and skips separators and disabled items, and it is the hover highlight too), Home and End jump to the first and last item, Right or Enter opens a submenu on its first item, Left or Esc closes it and returns to its row (Esc on the first panel closes the menu), and Enter or Space chooses the item. In the in-window menu bar (Windows and Linux) Left and Right move to the neighbouring menu, and Right on an item does too. An open menu keeps every key, so Space no longer starts playback behind it.
  • Right click on a note in the piano roll. With the Select tool it no longer deletes the note: it selects the note (a note already in a multi-selection keeps the selection) and opens the notes menu, so Delete, Quantize and the rest act on it. The pencil, eraser and razor still delete on a right click.