Skip to content

Atomik Rack v0.2.0-rc.1

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 11 Nov 02:37
· 2166 commits to main since this release
fdb14e1

Fixed

  • Bounce in Place and Unfreeze and Keep Audio make an audible track. The new audio track was
    silent while playing: its devices reached the engine after the routing that connects them, so the
    track and its channel were never cabled to the master. The changes of a compound edit inside
    another one are now reported with every device first, then one routing. The new track also sits
    right after its source track, in the same folder and colour, instead of at the end of the list.
  • Piano roll tools. Only the pencil creates notes now: with Select a press on the empty grid
    starts a rubber band (a click clears the selection, Shift or Ctrl adds to it) instead of drawing
    one. A note can be resized from its left edge as well as its right one, and with several notes
    selected every one of them changes by the same delta (snapped, with a minimum length), in one undo
    step like a group move. The mouse cursor shows what a press will do: a horizontal resize cursor
    over a note edge and during the drag, a move cursor over a note body, a crosshair for the pencil.
  • Sandboxed plugin editors on Wayland. The plugin process now uses the X11 backend (XWayland)
    whenever DISPLAY is set, so a sandboxed CLAP or VST3 editor opens as an X11 window it can embed
    into instead of failing with "Wayland sessions cannot embed a plugin editor". The rack window
    stays native Wayland. In-process editors and sessions without DISPLAY still fall back to the
    parameter pane.

Added

  • Installers, a nightly build and signing in the release pipeline. A release now publishes a
    Windows installer (atomik-rack-<version>-windows-x86_64-setup.exe, built with Inno Setup:
    Program Files or per-user, Start menu shortcut, optional desktop icon, uninstaller, .atomik file
    association), a macOS disk image (atomik-rack-<version>-macos-universal.dmg) and a Debian
    package (atomik-rack_<version>_amd64.deb, with the programs in /opt/atomik-rack and links in
    /usr/bin), next to the zip and tar.gz archives, with a .sha256 for each and one SHA256SUMS.
    The smoke test installs and uninstalls each of them. A daily nightly pre-release (tag
    nightly, replaced each night that main changes) is built by the same reusable workflow.
    Signing is wired and waits for certificates: Authenticode for the Windows programs and installer
    (a certificate file, or Azure Trusted Signing), Developer ID signing with the hardened runtime and
    notarisation for the macOS app and disk image, and a GPG signature of SHA256SUMS. Each step is
    skipped with a notice until its secrets exist in the release-signing environment, so builds are
    unsigned today. See docs/RELEASING.md.
  • Mixer snapshots and comparison. A snapshot is a named copy of the console: every param of
    every channel, output bus and the master (fader, pan, width, mute, solo, input trim and polarity,
    the sends, the dynamics, EQ and parallel compressor, the insert switches, whatever a strip gets
    later), the bypass of the insert and return effects, and the VCA groups' level, mute, solo and
    membership. A snapshot bar under the console toolbar shows a chip per snapshot (up to 16,
    named A, B, 1, 2... or by you), a + that stores the mix, and an A/B toggle. A
    click on a chip recalls it, a double-click renames it in place, and a right-click offers Recall
    (all, or only the levels, the mutes and solos, the sends or the insert bypass), Compare with this,
    Update from current mix, Rename, Move and Delete. The chip of the current snapshot is lit, with a
    dot once the mix has moved. Compare keeps the working mix in a hidden slot, recalls the
    snapshot and flips between the two without losing an edit made on either side; END keeps whichever
    is live. A recall is ordinary param changes (the strips' own 5 ms smoothers apply it, no clicks,
    no rebuild) and one undo step, as are store, update, rename, move, delete and every compare step.
    A snapshot does not hold the arrangement, the cables, the rack's structure or the effects' own
    parameters; a recall skips channels, effects and groups that were deleted since (the bar says
    which) and leaves the ones it never knew. The Mixer menu has Store Snapshot, Update Snapshot,
    Recall Snapshot, Recall Next and Previous Snapshot, Compare A/B, End Compare and Delete Snapshot
    (no default keys). Project format 27 saves them (a project without snapshots differs from its
    version 26 file in the version line alone and bounces bit for bit as before); the MCP inspection
    lists them and session_command stores, recalls (with a scope) and compares by id or name.
  • Channel strip upgrades. A parallel compressor on every channel and bus: a second
    compressor (the one of the strip's dynamics section) after the inserts, the dynamics and the EQ,
    blended with the dry signal by mix (1 is the compressor alone) and followed by a makeup; the
    console has a PARALLEL section after DYNAMICS with an enable button and threshold, ratio and mix
    knobs, and the rack's channel panel has the attack, release and makeup too. It has no lookahead,
    so the dry and compressed paths stay aligned and it adds no latency; off, or at mix 0, the strip
    is bit for bit what it was and costs nothing. The input trim (-24 to +24 dB) and polarity
    were already on the strip; Mixer > Toggle Polarity now flips the selected strips. Insert
    bypass keeps the delay compensation
    : a bypassed plugin effect plays its input delayed by the
    latency it reports (as the built-in effects already did), so the channel does not move against the
    others when you toggle it, with a phase-aligned 5 ms crossfade; each filled insert slot has a
    B that bypasses its effect, and the strip's BYP ALL button (and Mixer > Bypass All
    Inserts
    , on the selected strips) bypasses every effect of the chain in one undo step. No project
    format change: older projects load unchanged and bounce bit for bit. session_status lists the
    strips that use any of it and session_set_param sets a device's param in a headless session.
  • Mixer groups and VCA faders. A VCA group is one fader, one mute and one solo over several
    channels and buses, with no audio and no routing of its own. Mixer > Create VCA from Selection
    (on the console's selection, the arrangement's selected tracks or a selected folder, or the rack's
    selection) makes a group named VCA n; its strip in the console, after the buses, has a plate in
    the group's colour with the name and the member count, M and S, an offset fader from -60 dB (off)
    to +12 dB and a readout. Members keep their own faders and play at their level plus the group's
    offset
    (the sum in dB, smoothed like a fader, no zipper noise); a member's strip shows a marker
    where it plays and its readout shows that level. The group's mute and solo count as the members'
    own: solo beats mute, a soloed group silences the other strips as a solo does, and the members
    stay individually controllable. A strip is in at most one group; drag its name plate onto a VCA
    strip, use the right-click menu of a channel or bus (New VCA..., Add to VCA, Remove from VCA) or
    Mixer > Add to VCA, Remove from VCA and Delete VCA; members show the group's colour as
    a chip on their plate and as a bar on their track header in the arrangement. Every change is one
    undo step, a removed channel leaves its group with it, and a drag of the fader is one step. A
    project without groups sounds and bounces bit for bit as before. Project format 26 saves the
    groups (omitted when there are none, so older projects load unchanged); session_status lists
    them and session_command takes the id of a group. The rack's generated panels no longer show the
    app-only internal.* params (the channel's solo-silence toggle). Not yet: automation of the group
    fader, linked faders, groups of groups and a folder the group follows (see the roadmap).
  • Spectrum and metering. Two new effects that pass the audio through untouched (bit for bit, no
    latency, the bounce is identical with or without them) and show what they see; both are in the
    device browser with the effects and have the usual bypass. Spectrum (atomik.spectrum) draws
    an FFT of 1024 to 8192 points (Hann or Blackman-Harris) of the left, right, mid, side or sum, on a
    log axis from 20 Hz to 20 kHz over a dB range you choose, averaged over a time you choose, with
    peak hold and decay, an optional tilt of 3 or 4.5 dB per octave, a loudest-bin readout, or the 31
    one-third-octave bands instead of the fine trace. Phase Meter (atomik.phase-meter) shows a
    goniometer (mid/side or plain left/right) from the recent samples, the stereo correlation from -1
    to +1 over an averaging time, the balance and a width figure, peak, RMS and hold bars for each
    channel, the sample peak and the true peak, and the momentary, short-term and integrated loudness
    in LUFS (BS.1770-4, the meter of the mastering device) with a reset. The audio thread only copies
    each batch into a lock-free ring (ScopeTap, a new opt-in of the device SDK registered by the
    engine); the FFT, the averaging and the drawing run on the UI side, so the audio path costs 128
    atomic stores a batch. The headless QA server gets session_meters, which renders a project
    offline up to a position and returns the readings (and fills the panels for session_texts and
    screenshots), so a generated -23 dBFS 1 kHz tone can be checked for -23 LUFS, correlation +1 and a
    1 kHz line. Nothing new is saved in a project: the devices are ordinary devices, the project
    format is unchanged and older projects bounce exactly as before.
  • Audio to notes. Audio > Audio to Notes... extracts the notes of the selected audio clip
    into a note clip that starts and ends with it, in one undo step. Pitched follows one voice or
    instrument (a YIN pitch tracker with a voicing decision, written in house) and cuts it into notes
    by pitch stability and by re-attacks, so vibrato and a glide inside the pitch drift stay one note;
    the key is the pitch rounded to a semitone, the length follows the voicing and the decay, the
    velocity the level. Drums finds the hits of a loop and sorts them into kick, snare, closed and
    open hat (and a kick with a hat on top) from the spectrum after each onset, on the General MIDI
    keys 36, 38, 42 and 46. The panel sets the sensitivity, the shortest note, the range, the pitch
    drift, open hats, Beats timing (starts rounded to 1/4 to 1/32, or free) and the target: a new
    poly synth track or the note track selected in the rack. The notes follow the tempo map under the
    clip and the warp time map of a warped clip (a transposed clip adds its transposition; a clip in
    Repitch mode is refused), a reversed clip is read as it plays, and streamed assets are read in
    chunks. The analysis runs on a worker thread (at most ten minutes of a clip) while the song plays.
    session_audio_notes runs it in a headless MCP session. No file format change.
  • Freeze and bounce in place. Track > Freeze Track renders the selected tracks through their
    instrument and every effect of their channel's insert chain and plays the render instead, so none
    of those devices run (the point: CPU). The track's clips, instrument and effects stay untouched;
    Unfreeze Track brings them back exactly (one undo step), Unfreeze Track and Keep Audio
    also leaves the render as a clip on a new audio track. Freeze Track up to Selected Device
    stops at the instrument or the insert effect selected in the rack, and the effects after it stay
    live; the channel's fader, pan, sends and output are never frozen. Freeze with Tail (on by
    default) keeps the decay of reverbs and delays past the end of the clips, cut where it falls below
    -90 dBFS. The render runs through the offline bounce on a worker thread (progress in the status
    line, Cancel Freeze, several tracks queue) and is stored in the project's audio folder; a
    render of a track that changed meanwhile is thrown away. The song keeps its sound: the project
    bounced with a track frozen equals the unfrozen bounce bit for bit when the chain has no tail or
    latency, and a chain with latency stays aligned with the other tracks. A frozen track shows a
    snowflake in its header and its render in ice blue in place of its clips; editing it, its devices
    or the tempo is refused with a message that says to unfreeze. Bounce in Place (and and Mute
    Originals
    ) renders the selected clips through the track's chain into one clip on a new audio
    track and freezes nothing. Plugins render through the plugin sandbox. Project format 25 saves a
    frozen track (version 24 files load unchanged). The QA server runs the commands (session_command
    waits for the render) and lists frozen in the inspection.
  • Time-stretch and pitch-shift (warp). Audio clips can follow the song tempo and be transposed
    without changing their length. Warp (Audio > Warp Audio, or Warp Settings...) plays a clip
    through a time map in beats at the tempo it was recorded at, so the audio stays on the grid when
    the song tempo changes or ramps; three engines are written in house, with no new dependency:
    Beats keeps every transient of drums and percussive loops where the tempo puts it and its
    attack intact and stretches the audio between hits, Tonal is a phase vocoder with phase
    locking for sustained and polyphonic material, and Repitch resamples (speed and pitch
    together, the cheap one). Transpose (Audio > Transpose, up or down a semitone or an octave, or
    the panel with semitones and cents, up to two octaves either way) changes pitch without changing
    length in Beats and Tonal. The source tempo comes from Warp Loop as N Bars (the clip becomes N
    bars long at the tempo its length implies), Warp to Song Tempo (an estimate from the
    transients of the audio, snapped to the exact tempo of the clip when it holds whole beats) or the
    panel's source tempo, DETECT TEMPO, /2 and x2. Quantize Audio (Edit menu and clip context
    menu) finds the transients of the selected clips and moves them to the grid of the quantize
    options by its strength with warp markers, stretching locally between them, with the ends of the
    clip pinned; markers survive trims and splits. The clip shows a W (with the transposition,
    W +3) and its markers as thin lines, and its waveform follows the stretch. A warped clip is
    rendered off the audio thread into a cached buffer (at most two background workers, 512 MiB,
    replaced when a setting, the tempo or the clip changes) and plays unwarped until it is ready; a
    bounce renders every buffer first, so it is never dry and stays bit for bit repeatable. Reverse
    and warp exclude each other; Strip Silence needs the clip unwarped. Project format 24; every
    earlier project plays and bounces as before. The QA server's inspection lists a clip's warp.
  • Audio editing. Audio clips get fades and crossfades, clip gain and gain envelopes, reverse,
    normalise and strip silence, all non-destructive. A clip has a fade in and out whose shape is
    Linear, Equal power, Exponential or S-curve (Audio > Fade Shape, or the clip context menu), the
    fade and gain handles on the clip as before. A clip that starts over the end of an earlier one on
    the same track now crossfades with it: over the overlap the earlier clip fades out and the
    later one fades in, equal power by default (Audio > Crossfade picks Linear, Exponential, S-curve
    or Off, a hard cut), and the zone is drawn on the later clip; a clip inside another still hides
    it. Gain envelopes are drawn on the clip over the waveform: click with the pencil to add a
    point and drag it, drag points with the select tool, right-click or use the eraser to remove one,
    Audio > Clear Gain Envelope; the envelope ramps smoothly between points, sits in clip time and
    follows the audio when the left edge is trimmed. Clip gain also has Audio > Clip Gain (up and down
    1 dB, reset) next to the gain handle, and Audio > Fades sets a 5 ms declick or no fades.
    Reverse (Edit > Reverse Audio) plays the clip's span backwards and works with trims, fades and
    envelopes (an R marks the clip). Normalise (Edit > Normalise Audio) sets the clip gain so
    the peak of what each selected clip plays reaches 0 dBFS. Strip Silence (Edit > Strip
    Silence...) opens a panel (threshold, minimum silence, pad before and after, fade) and cuts the
    selected clips into their sounds, one undo step. Project format 23; files from before load with
    every clip's crossfade off, so old overlaps stay hard cuts and old bounces keep their bytes. The
    QA server's inspection lists audio clips with their gain, fades, reverse, envelope and crossfade.
  • Track organisation. Tracks can be put in folders (Track > Group Tracks, Ctrl+Shift+G, on the
    selected tracks or the tracks of the selected clips; shift-click or ctrl-click on headers selects
    several). A folder is a row above its first track with a chevron that collapses and expands it, a
    name typed in place (double-click, or Track > Rename Folder), M, S and R buttons that mute, solo
    or arm every track of the folder in one undo step, and a summary of the clips of its tracks;
    folders nest up to 8 deep, Track > Ungroup (or Delete on a selected folder) dissolves one and
    keeps its tracks, and Move Track Up and Down (Alt+Up and Alt+Down) move a track one place at a
    time, in and out of folders, or a folder with everything in it. A folder does not touch the audio
    or the routing. A track can have a colour (header and clips; Colour submenu of the track header
    menu) and a comment (Track > Track Comment, typed in the header; a note mark shows it and its
    first line is a tooltip). An automation lane folds to a thin strip with the chevron at the left of
    its header (Track > Fold Automation Lanes folds them all), and the take rows that are open stay
    open with the project. Track > Track Height sets the selected tracks, or all, to Small, Medium,
    Large or Fit (as tall as the view lets them be). Project format 22 saves it all (a project without
    any of it differs from its version 21 file only in the version line; version 21 files open
    unchanged); the MCP inspection lists folders, colours and comments, and the Track menu commands
    are session commands.
  • MIDI file import and export. Standard MIDI Files (type 0 and 1) in and out of the app. File >
    Export MIDI Clip, Track and Song write the selected note clip or track (type 0) or every note
    track (type 1: a conductor track with the song name, tempo map, time signatures and markers, then
    one track per note track, named after its device) with pitch bend, aftertouch and CC lanes as
    controller events; they write what plays (loops, offsets and swing applied, muted notes and clips
    left out) at 15 360 ticks per quarter note, the app's own resolution, so a round trip keeps every
    tick. File > Import MIDI puts a file in one clip on the selected note track at the playhead, or
    makes one new track per MIDI track and channel when no note track is selected; File > Import MIDI
    as Song makes new tracks from the start and also takes the file's tempo map, time signatures and
    markers. A .mid file dropped on the window makes new tracks at the playhead. Every import is one
    undo step. The reader handles running status, SysEx and unknown meta events (skipped), a note-on
    with velocity 0 as a note-off, hanging notes, type 0 files split by channel and other divisions,
    and refuses type 2 files, SMPTE time and corrupt files with a message instead of changing
    anything. Audio and automation lanes, range markers and program changes are not exported; a tempo
    ramp is exported as a staircase. No project format change. The QA server gains session_midi.
  • Quantize, swing, grooves and humanize. Edit > Quantize Options (also in the clip and note
    context menus) opens a panel for the selected clips of the arrangement, or the selected notes of
    the piano roll (every note of the open clip when none is selected): a grid from 1/4 to 1 bar with
    triplets, a strength that moves notes part of the way, swing from 50 % to 75 %, a groove, humanize
    timing and velocity with a seed, and an option to snap the note ends too. A groove is a named
    template of per-step timing offsets and velocity scales: six come built in (Straight, Swing 55, 60
    and 66 %, a shuffled 1/8 and an accented 1/16) and EXTRACT GROOVE FROM CLIP measures one from a
    clip's own feel and keeps it in the song, shared by every track, until DELETE. The grid is the
    song's, so a clip that starts off the grid still lands on the bar lines. Humanize is the same on
    every run (it comes from the seed, the clip and each note's own position), so a bounce is
    reproducible; another seed gives another take. Applying is baked into the note times, one undo
    step over all selected clips, and playback and bounces are unchanged; two notes of one key that
    land on the same tick both stay (the later moves one tick on). Audio clips, controller lane points
    and the takes of a take group are left alone. Ctrl+K (Cmd+K on macOS) quantizes the
    selected notes of the piano roll or the selected clips of the arrangement at once with the panel's
    last settings (Q does the same in the legacy profile), Edit > Quantize does it from the menu
    (enabled with a selection, like Cut and Copy), and the piano roll's toolbar has a QUANT button
    that does it too, with a ... button (or a right click on QUANT) that opens the panel. Project
    format 21 (older files load without grooves); project_inspect lists the song's grooves.
  • Loop recording and takes. Recording over an enabled loop now stacks every pass as a take of
    one take group on the track (note and audio), instead of laying overlapping clips: the last pass
    plays and the others are kept. In the arrangement a thin comp strip under the lane shows which
    take plays where (each take has its own colour) and its chevron opens one row per take. Click the
    name of a take or its row to play that take alone, drag across a take row to comp a range from it
    (snapped, Escape cancels), use the cross to delete a take and FLATTEN to keep what plays as plain
    clips and drop the takes. Every action, and a whole recording, is one undo step. The comp is
    compiled into ordinary clips, so playback and bounces are unchanged, and a cut inside an audio
    take gets a 5 ms fade at the splice so it does not click. Punch and non-loop recording are
    unchanged. Project format 20 (older files load without groups); project_inspect lists the
    groups.
  • MIDI controller data. Pitch bend, aftertouch (channel and per key) and CC lanes in note clips,
    played to devices and plugins, recorded from live MIDI input and edited in the piano roll. A
    CONTROLLERS field in the scale bar opens an area under the velocity lane with chips for Bend,
    Press, Mod 1, Vol 7, Pan 10, Expr 11 and Sust 64, a stepper for any other CC and one for poly
    aftertouch; draw with the pencil or the select tool (one point per grid step), drag points, delete
    them with the eraser or a right click, Ctrl or Cmd click toggles ramp and step, and a whole stroke
    is one undo step. Recording keeps every pitch bend, aftertouch and CC that reaches an armed track,
    per loop pass, next to the notes. Playback sends the events sample-accurately, restores each
    controller's value when you play or locate in the middle of a clip, and zeroes pitch bend,
    aftertouch and the sustain pedal on stop. The poly synth now follows pitch bend (two semitones)
    and the mod wheel (vibrato). Project format 19 (older files load without lanes).
  • Automation recording. Arm an automation lane with the W button on its header, pick how it
    writes with the OVR / TCH / LTC button next to it (Overwrite replaces the whole pass, Touch writes
    only while you hold the control, Latch writes from your first touch until you stop), arm a track
    or just the lane, and press Record: moves of the lane's parameter (a knob drag, a typed value, a
    plugin's own window, a container macro) become automation points. The recorded points are thinned
    (Ramer-Douglas-Peucker, 0.5 % of the parameter's range) so a drag does not leave hundreds of
    points. While a lane is being written the old automation does not fight the control; a loop
    recording writes one clip per pass, and a whole take, whatever the number of lanes and passes, is
    one undo step. The write mode is saved in the project (project format 18; older files load on
    Touch), the arm state is not. MIDI controller input is not recorded yet.
  • Note chase. A note that spans the play position now sounds when you press Play, locate while
    playing, or the loop wraps, instead of staying silent until its next note. Each track has a
    Chase Notes item (checked by default) in its header's context menu; switch it off for a track
    that should play only from its note starts. Live edits never retrigger a note that is already
    sounding. The setting is one undo step and is saved with the project (format 17: a track that does
    not chase has "no_chase": true; versions 1 to 16 load with chase on). The QA server's project
    and session status report chase for each track.
  • Relink missing audio. File > Relink Missing Audio... (enabled while a project's audio files
    are missing) lists them with a LOCATE... button each and SEARCH FOLDER.... LOCATE... takes any
    audio file: it is imported into the project bundle and every clip and sampler, slicer and drum pad
    zone that used the missing asset is switched to it in one undo step (the old, missing state comes
    back with undo); a file with the very same audio only restores the bundle's file, with no document
    change. SEARCH FOLDER... scans a folder (8 levels, 50 000 entries at most, off the UI thread) and
    relinks the missing files it finds by name, in any case, leaving the rest listed; a toast says how
    many were relinked and how many are still missing. A file that does not decode, or that is too
    short for the zones that used the old one, is reported by name and changes nothing. The QA server
    gains session_relink, and session_bounce now renders from the session's bundle, so audio
    projects bounce in a session.
  • QA server (atomik-mcp). A development tool, not part of the release archives: a Model
    Context Protocol server over stdio that lets an MCP client bounce projects and patches, measure
    and compare WAV files (levels, silence, loudness windows, spectrum, bit-exact or within a
    tolerance), and drive a headless app (menu commands, pointer, keys, the texts the UI draws, PNG
    screenshots, undo, save, and a bounce of the open document), with every path confined to the
    working directory and --root folders. docs/MCP.md has the tools and the QA
    recipes that CONTRIBUTING.md now asks for. atomik-ui gains an optional
    cpu-canvas feature (the vello_cpu canvas its preview tests used, now library code).
  • Scales and chords in the piano roll. A clip has a scale (a root and one of fifteen: Major, the
    minors and the modes, the pentatonics, Blues, Whole Tone, Phrygian Dominant and Hungarian Minor;
    no scale is Chromatic), chosen from a new scale bar under the piano roll's toolbar or the notes
    context menu's Scale submenu, or found by Detect from the notes. In-scale rows are tinted,
    out-of-scale rows are dark, the root rows are marked and the keyboard names them. The scale is
    saved with the clip (project format 16; older files load without one). Snap to Scale
    (Shift+S) puts pencil-drawn notes and vertical drags on the nearest in-scale key (a tie goes
    down) and makes Transpose Up and Down move by scale degree, and Conform Selection to Scale
    moves the selected notes onto the scale in one step. Fold (Shift+F, or the Fold field) hides
    the keys outside the scale, or every key the clip does not use, and drawing, dragging, band
    select, the keyboard and the key zoom all work on the folded rows. The chord stamp (twenty-one
    chords, four inversions, and diatonic triads, sevenths and ninths built from the scale) makes the
    pencil drop a whole chord that you can drag to length and that sounds when you click; Chordify
    (Shift+C) turns each selected note into the chord, Arpeggiate turns each chord of the
    selection into an arpeggio over its length (up, down, up-down, down-up, random or as played, at
    the current snap, triplets included, with a gate and one to three octaves), and Strum delays
    the notes of each chord one after the other and keeps their ends. Every edit is one undo step. The
    context menus gain submenus for all of it, and the snap to scale and fold choices are kept between
    sessions.
  • Deep zoom and finer editing. The time zoom goes down to the sample: a tick is up to 16 px wide
    (about 10 px per sample at 120 BPM and 48 kHz), the ruler grid follows with lines at 1/32, 1/64,
    1/128 notes and down to single ticks, and below the bars the ruler names its lines
    bar.beat.sixteenth.tick. Snap gains 1/32, 1/64, the triplets 1/4T, 1/8T, 1/16T and 1/32T and
    Grid, which snaps to the lines the ruler shows at the current zoom (the selector in the
    arrangement and the piano roll cycles through them; sequencer.set_snap takes thirtysecond,
    sixtyfourth, quarter_triplet, eighth_triplet, sixteenth_triplet, thirtysecond_triplet
    and grid, and the piano roll's Quantize uses the same step). Waveforms in the arrangement, the
    sample editor and the slice editor read the samples themselves when you zoom in below 256 frames
    per pixel, and below one frame per pixel draw a line through the sample values with a dot on every
    sample (audio streamed from disk keeps the finest peak level); the editors' wave zoom reaches 32
    px per frame whatever the length of the file. Vertical zoom: drag the bottom edge of a track
    header to set that track's height (24 to 400 px, a double-click resets it), Alt+wheel in the
    arrangement zooms every track (Shift+H and Shift+G, Shift+Z resets the zoom and the heights),
    headers shorter than 52 px keep one line, and the piano roll zooms its keys the same way
    (Alt+wheel, 6 to 48 px, Shift+H, Shift+G and Shift+Z; the white keys are named from 16 px). Track
    heights are saved in the project (format 15, versions 1 to 14 load unchanged: a song may carry
    "track_heights", written only when non-empty); the vertical zooms are saved with the window
    state.
  • Markers and range markers. The arrangement has a marker strip under its ruler (View, Marker
    Strip; on by default and kept between sessions) with named point markers and named ranges (Intro,
    Verse...). Add a marker at the playhead with Shift+M (Transport, Add Marker), by a double-click or
    the pencil on the strip, or from the marker list; drag it to move it (snapped by the current snap,
    the disable-snap keys free it), double-click its label to type a new name in place, and delete it
    with the eraser, Delete or the context menu, which also has a small colour palette. Click a marker
    to locate the playhead there; , and . (and the Transport menu) go to the previous and next
    marker. Ranges are bands in a row above the markers: Transport, Add Range Marker from Loop (or the
    strip's context menu, from the loop or the selected clips) creates one, a drag of the body moves
    it, the edges resize it, and a click sets the loop to its range (Loop This Range and Select Clips
    in Range are in its context menu). View, Marker List docks a list of every marker and range at the
    right edge of the arrangement with its position as bar.beat.tick through the meter map (and the
    end of a range); a click on a row locates (a range row also sets the loop), a double-click on a
    name renames it, x deletes it, and + Marker and + Range add. Every edit is one undo step and
    a drag is one step. Markers follow the bars when the tempo or the meter changes. Project format 14
    (versions 1 to 13 load unchanged): a song may carry "markers" and "ranges", written only when
    there are some. The legacy key profile is unchanged (the commands are in the menus).
  • Tempo and meter changes. The song can change tempo with steps and linear ramps (the tempo
    moves in BPM over ticks) and change time signature on any bar line. A tempo lane in the
    arrangement (View, Tempo Lane; off by default and kept between sessions) plots the tempo curve:
    add a point with the pencil or a double-click, drag it (snapped in time, whole BPMs up and down,
    Shift for tenths, Alt for no snap), delete it with the eraser or Delete, and right-click for Ramp
    to Next, Set Tempo... and Delete. Right-click the ruler to insert a meter change (2/4 to 12/8) at
    that bar; its tag sits next to the bar number and can be dragged to another bar, changed or
    deleted. The ruler, the grid, snapping, the bar keys, new clips, recording and the metronome
    follow the meter map, and notes, audio clips and loop points land on the exact frame of the ramp
    live and in the bounce (one tempo map in atomik-core replaces the four copies of the
    conversion). Tempo-synced devices and Mod Source follow the tempo and the meter at every 64-frame
    batch. The transport shows the tempo and the meter at the playhead, and typing a tempo changes the
    event in effect there. Project format 13 (versions 1 to 12 load unchanged): a tempo event may
    carry "ramp": true, and "meter" is a list of {"bar", "num", "den"} changes. The metronome
    now clicks on the beats of the meter, an eighth in 6/8 rather than a quarter.
  • Plugin sandbox. Every CLAP and VST3 plugin instance runs in its own atomik-plugin-host
    process, so a plugin that crashes or hangs no longer takes the application down. A crashed
    plugin's device shows CRASHED with the reason (dry for an effect, silent otherwise) while audio
    goes on, and RELOAD starts it again from its last saved state. Audio is exchanged through shared
    memory in the same 64-frame blocks, with no added latency; live, a block the plugin answers late
    passes dry. Bounces wait for every block, so a sandboxed bounce is byte-identical to an in-process
    one. Editors open in a window of the plugin's process. Settings > Plugins has "Run plugins in a
    separate process (recommended)", on by default (applies after restarting); atomik-render has
    --plugin-sandbox on|off. Release archives and the macOS bundle include the new
    atomik-plugin-host program.
  • Output buses. The console can hold named output buses (atomik.bus strips with the channel's
    controls): channels and buses route to the master, to another bus (loops are refused) or to a free
    Audio I/O stereo pair, with commands to create, rename, reorder, delete and route to a new bus,
    each one undo step, and a solo that keeps a soloed bus's feeders and a soloed strip's buses
    audible. Project format 12 saves the bus list (omitted when there are none; versions 1 to 11 load
    unchanged). In the console, bus strips sit between the channels and the master with the full
    channel strip, an output selector on every strip (Master, buses, Audio I/O pairs, New bus...;
    pairs in use or beyond the project's outputs are greyed with the reason), rename by double-click,
    a bus context menu (Rename, Delete bus), drag to reorder and meters. Route to New Output Bus
    (Ctrl/Cmd+G, Mixer menu) puts the selected channels on a new bus. In the rack the plate reads
    Output: Bus <name> or Output: Audio I/O 3+4; an Audio I/O pair no longer shows the warning
    colour.
  • Mod Source. A new modulation device with two LFOs (seven shapes with morph, free or
    tempo-synced rate, key sync, rate and amount CV inputs) and an ADSR envelope triggered by notes or
    a gate CV, with CV outputs for the rest of the rack. Its panel has a shape display for each LFO
    and a live scrolling scope of both LFOs and the envelope, and the device browser lists it in a new
    Modulators group.
  • Multi-column rack. The rack can have several columns side by side (saved in the project,
    project format 11; older files load as one column). Add Column and Remove Column are in the rack
    context menu; an empty column stays until it is removed, and removing a column moves its devices
    to the one on its left. Each column scrolls with the rack, which now also scrolls sideways to
    reach all of them.
  • Dragging between columns. A device, or a selected group, can be dragged to any place in any
    column; the drop line shows where it lands, and dropping to the right of the last column makes a
    new column. The whole move is one undo step. The rack scrolls by itself when you drag near its
    edges.
  • Drag devices from the browser. Drag a row of the device browser onto the rack to create the
    device exactly where you drop it, in any column; an effect is routed as if the device above the
    drop point were selected. Release over the browser, or press Esc, to cancel. A double-click still
    adds below the selection.
  • Rack navigator. A strip at the right edge of the rack (View, Rack Navigator; on by default)
    shows every column as small coloured blocks and the part of the rack you are looking at. Click to
    centre the view there, drag to scroll, use the mouse wheel as over the rack; inside a container it
    shows the container's column. The choice is kept between sessions.
  • Paste and plugin drops in columns. Paste from the rack's context menu lands where you
    right-clicked, and a keyboard paste lands below the selected device in its column. A plugin that
    is neither an instrument nor an effect can be dragged from the browser into a column or the
    new-column zone like any other device, and the new-column zone now stays on screen while you drag,
    whatever the window width.
  • CV inputs on the effects, console channels and instruments. One convention: a CV socket
    <target>_cv_in with a bipolar <target>_cv_trim (−1..+1, default +1). The stereo delay (mix,
    feedback), reverb, modulation and distortion (mix, drive), the EQ (gain of the four shelf and peak
    bands) and every console channel (fader, pan, the eight sends) take one; so do the poly synth
    (pitch, resonance, level, pan), the sampler (resonance, level, pan), the drum machine (global
    level and pitch, see below) and the loop slicer (level, and cutoff through a new global low-pass,
    filter.cutoff, which is open by default). Unplugged, nothing changes, and older patches and
    projects load as before.
  • Gates and global CV on the drum machine. Two global CV inputs, level_cv_in (±24 dB) and
    pitch_cv_in (±24 semitones, also bending voices that are already sounding, glided over each
    64-sample batch), each with a bipolar trim. Per pad, a gate in (padN_gate_cv_in: a rise above
    0.5 plays the pad, velocity from the level, the fall releases a gate-mode pad) and a gate out
    (padN_gate_cv_out: high from every hit, from notes, the sequencer or the gate in, until its
    note-off). The back panel shows the 16 gate pairs and the two CV jacks with their trims.
  • CV activity indicators. On the back of the rack, a CV cable that carries signal glows and
    lights both of its jacks, brighter for a stronger signal and fading smoothly when it falls silent.
  • Nudge by beat or tick. In the piano roll, the selected notes can move by one beat or by one
    tick, whatever the snap: Ctrl+Shift+Left/Right (beat) and Ctrl+Alt+Left/Right (tick) in the
    standard profile, Shift+Left/Right and Alt+Left/Right in the legacy one (Cmd for Ctrl on
    macOS).
  • Console keys are commands. The console's arrow, Page Up/Down, Home and End keys are now
    mixer.* commands in the Mixer context (the same keys as before, Shift for fine steps), so they
    show in the cheat sheet and can be rebound in Settings, Keyboard. The console also owns the
    keyboard as a text field while a channel name is being typed, so Space, Delete and the letters
    never run commands then; Enter commits and Esc cancels.
  • Editor keys follow the keymap. Delete and Backspace in the sample editor (remove the selected
    zone) and the slice editor (merge the selected slice into the previous one) are now the
    edit.delete command, so they follow Settings, Keyboard and the active profile. The sample,
    slice, step, sequencer and container editors no longer read Ctrl+Z and Ctrl+Y themselves: undo and
    redo are edit.undo and edit.redo everywhere, and rebinding them takes effect in the editors.
    Esc and typing a name are unchanged.
  • Time signature in the transport bar. Double-click the meter readout and type a signature
    (3/4, or a bare 3 to keep the beat unit, 1 to 32 over 2, 4, 8 or 16): it changes the meter
    change in effect at the playhead, undoable like the tempo. Before, the first signature could not
    be changed at all (a 4/4 start has no ruler tag).
  • Ctrl+Shift+wheel zooms vertically. In the arrangement (track heights) and the piano roll (key
    heights), next to Alt+wheel; Ctrl+wheel stays the time zoom.
  • Multi-select and rubber band in the arrangement. Shift+click adds a clip to the selection,
    Ctrl+click toggles it, across tracks (Ctrl+click is also how a copy drag starts, see below). A
    rubber band selects the clips it touches: drag from empty space below the last track, or Shift or
    Ctrl+drag on an empty lane (a plain drag on a lane still draws a clip); Shift or Ctrl add to the
    selection, a plain band replaces it, and Esc cancels it. Delete, copy, paste, duplicate, split,
    mute and the drag act on every selected clip, as before, and every selected clip is outlined.
  • Drag clips onto other lanes. Dragging clips vertically onto another track moves them there
    (the time follows the horizontal drag), and Ctrl+drag drops copies instead (the clips stay put and
    the copies are selected). Each clip lands on the lane of its own kind: a note clip on the note
    lane, an audio clip on an audio track's lane, an automation clip on the lane of the same
    parameter; a target track without that lane (a note clip onto an audio track) ignores the drop and
    changes nothing. A group keeps its relative tracks and offsets, and the whole gesture, including
    the horizontal moves, is one undo step (a drag of several clips used to leave one step per clip
    and per move). A ghost shows where the drop lands. New WorkflowCommand::MoveClips; no project
    format change, since a clip belongs to its lane in the file.

Fixed

  • Track header click acts like a console strip. Clicking a track header in the arrangement (or
    stepping with Up and Down) now selects its strip in the console, auto-arms the track as a channel
    selection does (disarming the tracks an earlier auto-arm armed), selects the device in the rack so
    the live keyboard plays it, and a plain click hands the keys to the rack.

  • Device search. Typing in the device browser's search kept the scroll of the full list, so the
    few matches (Serum for "ser") sat above the visible panel; the list now returns to the top on
    every edit.

Removed

  • The plugin warning. Turning plugins on in Settings > Plugins, or LOAD on a project that uses
    plugins, no longer shows a warning to confirm: plugins now run in their own processes by default.

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.

Full changelog: v0.2.0-rc.1/CHANGELOG.md