Skip to content

Atomik Rack v0.4.0-rc.2

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 11 Nov 03:28
· 306 commits to main since this release
04ceaff

Added

  • Themes, with a built-in Synthwave theme. The colours of the interface are now data: one JSON file per theme with
    a version, a name, the built-in theme it is based on (a colour it leaves out comes from there) and about sixty colour
    tokens. Light and Dark are files compiled into the program that give back the old palettes exactly, so nothing looks
    different; Synthwave is new, a neon night with an indigo background, magenta and cyan accents, a magenta grid in
    the arrangement and meters that run cyan, magenta and orange, with its body text kept above a 4.5 to 1 contrast
    (a test checks it for every built-in theme). Settings > Themes lists the themes with a sample of each and uses
    one at once; Duplicate, Rename, Delete (after a question), Import, Export and Open Themes Folder manage your own,
    which are files in a themes folder next to settings.json. A theme editor opens on a theme of your own: the colours
    in groups (Backgrounds, Text, Accents, Meters, Arrangement, Rack, Console), each with a swatch that opens the colour
    picker and a hex text field, a live preview in the whole program, RESET to the base theme, and an undo for the
    session (Ctrl+Z); it writes the file when it closes. A file that is not a theme is skipped with one message that
    names it. View > Theme gains Next Theme (view.next_theme) and Theme Manager (view.theme_manager), neither with a
    key. The grid lines and level meters are theme colours now (grid_bar, grid_beat, grid_sub, meter_low,
    meter_mid, meter_high). A glow on the meters and the playhead is not done. The theme is a preference
    (theme_id in workflow.json, an old "theme": "dark" still gives Dark); the project format is unchanged (45).
  • A French interface and a way to add languages. Settings > Video has a Language row, System (default), English
    or Français, and a change applies at once with no restart. System reads the language of the operating system once
    at start (the sys-locale crate, decision W) and falls back to English. The menus and every command of the
    registry, the Settings tabs, the start screen, the export panel, the rack, arrangement, console, launcher and
    palette labels, the status messages and the tooltips are in French (Piste, Clip, Boucle, Calque, Table de mixage,
    Envois, Retours, Réglages, Annuler, Rétablir; the glossary heads crates/ui/locales/fr.txt), the shortcuts use
    the French key names (Maj, Entrée, Échap, Suppr, Espace, Retour arrière), and dB, Hz, BPM, LUFS, MIDI and CC stay
    as they are. A text with no French line shows in English, and the names of songs, tracks, clips and files that
    the views draw are left as typed. Another language is one file of English text => text lines (docs/EXTENDING.md, "Adding a
    language"); a line may name values (Added {name}) and then matches any message of that shape. The manual, the
    texts of Help Mode and the parameter names of most device panels are still English. The language is saved in
    workflow.json; the project format is unchanged.
  • A built-in manual. Help > Manual (help.manual, Ctrl+F1, Cmd+Alt+F1 on macOS) opens the user documentation in a
    large panel that works offline: a table of contents built from the headings on the left, the page on the right with
    headings, paragraphs, bold and italic text, code, lists, tables and links between sections (a picture shows its
    description), a search field with ranked results (a heading match above a body match) and a line around each match
    with the matched words in bold, and Back and Forward buttons (Alt+Left and Alt+Right). The text is docs/README.md
    and docs/KEYBOARD.md compiled in, so the manual and the documentation are one source; a new Manual section and a
    Devices section in README.md describe it. The More link of Help Mode now opens the manual at its section instead of
    the browser, the command palette lists "Manual: " for every section, and a link to a page the manual does not
    hold (the device reference, the other documents) opens that page on the project site, one request to a fixed address.
    Help > Documentation still opens the project page. The Markdown reader is written in the project (decision V).
    The project format is unchanged.
  • Backup copies in a second folder. Settings > Backup has a Backup folder (None by default, with Choose... and
    None), Keep (the copies of each project that stay, 1 to 50, default 10) and Include audio (default on). Every
    successful save also copies the project to <backup folder>/<name>/<name> <YYYY-MM-DD HHMMSS>.atomik (UTC) and, with
    audio, the audio files it uses to <backup folder>/<name>/Audio/, once each by content hash. The copy runs on its own
    worker after the save is confirmed, never delays or fails a save, and a failure shows Backup failed: <reason> once
    per session (later ones go to the log). Autosave snapshots make no backup. Only the newest Keep copies stay; an audio
    file goes only when no kept copy names it (every project file of the folder is read first, and an unreadable one keeps
    all the audio), and files that are not copies are never touched. File > Restore from Backup lists the copies of the
    open project with their date and size and opens the chosen one as a new unsaved song, after the question about
    unsaved changes. The command is file.restore_backup (no default key); the settings are backup_folder,
    backup_keep and backup_audio in workflow.json. The project format is unchanged.
  • Share a project as one file. File > Share Project opens a small panel with the title, the author and a note (they
    go into the song information as one undo step when you changed them) and three check boxes: Include a preview (an
    MP3 of the whole song at -14 LUFS, or a 16-bit WAV file when FFmpeg is not set up), Include stems (one 24-bit WAV
    file per mixer strip) and Include plugin list. A line says what the share will weigh and turns to the warning
    colour over 500 MB. SHARE asks for a file name (<title>.atomikz, the project archive extension) and writes, on a
    worker with progress and cancel, one file with the project, every audio file it uses, credits.txt (title, author,
    note, the date, the version of the program and the plugins with vendor and format), the preview and the stems.
    A cancel or a failure leaves no file. File > Open and a drop on the window take an .atomikz file: a folder
    dialog asks where to unpack it (it starts in Shared beside the library folder), the project opens and the Song
    Information shows what the sender wrote. The archive reader accepts only the project, its audio, the credits, one
    preview and the stems, and still refuses entries that leave the folder, duplicates and anything over its limits
    before it writes a byte. The command is file.share_project (no default key). The project format is unchanged.
  • A plugin manager. Options > Plugin Manager opens a table of every plugin the scan found: its name, vendor,
    format (VST3 or CLAP), category (instrument, effect or note effect), status (OK, Failed with the reason,
    Quarantined, Disabled, Unsupported), file and when it was last scanned, with the files that failed to scan as rows
    of their own. Click a column head to sort (again to reverse it); the search field matches the name, vendor, path and
    tags, and four buttons filter by format, status, category and tag. The star of a row marks a favourite: the device
    browser lists favourites first, in a Favourites group of their own and at the top of their kind. Tag the chosen
    plugins from the small field (the same tags as the file browser: no #, no comma, 32 characters at most) and find
    them in the browser by typing # and the tag in its search field. Disable hides the chosen plugins from the
    browser and the menus; a project that uses one still loads it. A plugin whose process ends, or that fails to
    load, three times in a row is quarantined (hidden like a disabled one, with a message once); a working instance, or
    a load that works after a failed one, starts the count again, and Try Again clears the quarantine. Rescan All and
    Rescan Selected run on the scan worker with a progress line and a Cancel button, and Show in Folder opens the file
    manager at the file. Favourites, tags, disabled plugins and the quarantine are kept by the plugin's id (so a plugin
    that moved keeps them) in plugins_user.json in the settings folder; a missing or damaged file reads as empty.
    The scan cache now also keeps when each file was scanned. The command is options.plugin_manager (no default key).
  • Soft takeover and knob pages for controllers. An absolute knob or fader of a controller set up with the wizard
    no longer makes a parameter jump: when it is not where its parameter is (after another device is selected, a page
    or bank change, or an edit with the mouse), moving it does nothing until it comes within 2 percent of the value or
    sweeps through it, using the same rule as MIDI learn, and the status line says which way to turn it ("Turn knob 3
    up to pick up Cutoff"). Relative encoders, stepped parameters and faders that receive their value as feedback do
    not wait. The eight knobs now have pages: Page Down and Page Up (two optional keys the wizard asks for last), or
    the commands Controller Knobs: Next Page and Previous Page (controller.knob_page_next and
    controller.knob_page_prev, no default keys), move over the parameters of the followed device eight at a time and
    wrap round; the status line names the page ("Knobs: Filter 9-16") and motorised or LED controls receive the new
    values. The page goes back to 1 when another device is followed, unless the profile keeps the page for each device.
    Pick up values (on by default) and Keep the knob page for each device (off by default) are check boxes on the last
    page of the wizard and chips in Settings > Controllers; they are saved in the profile file, and older profiles
    read as the defaults.
  • Editing note expression by hand, and MPE out. The strip beside the selected note in the piano roll is now an
    editor for its pitch, pressure and timbre curves. A tab picks the curve; a click on empty space adds a point, a
    drag moves it (Shift moves finely, Ctrl snaps a pitch to a semitone; time stays inside the note and the value
    inside the range), Alt-click or a double click deletes it, a drag from empty space is a rubber band that selects
    points to move or delete together, and with the Pencil tool a drag draws the curve freehand, thinned like Cleanup
    Automation. A scale chip steps the pitch plot through 48, 24, 12 and 2 semitones. Apply copies the curve to the
    other selected notes, stretched to each note's length. Every gesture is one undo step and a curve keeps its limit
    of 1024 points. The command Edit Note Expression (editor.edit_expression, found in the command palette) shows
    the strip for a note without curves and with several notes selected; Apply Curve to Selected Notes
    (editor.apply_expression_curve) copies a curve. The MIDI Out device
    has an MPE zone (off, lower or upper) and a member channel count: with it on, every note goes out on a member
    channel (taken in turn, the one released longest ago first), its curves as that channel's pitch bend, pressure and
    CC 74, the first values before the note on, and the MPE Configuration Message when the zone is set and at each
    playback start; with it off the output is as before. A plugin device has a Send MPE option (the MPE button on its
    panel) that sends a lower zone as raw MIDI on channels 2 to 16 to a plugin that takes plain MIDI; plugins that take
    note expressions still get them as note expression events without it.
  • Help Mode. Help > Help Mode (Shift+F1; F1 is still the shortcut list) docks a Help panel above the status line
    that explains the control under the pointer: its title, one to four sentences, the shortcut of the command it runs
    (read from your keymap, so a rebound key shows) and a "More:
    " link that opens the matching section of the
    documentation in the browser. Clicks still reach the controls, the ordinary tooltips stay quiet while the mode is on,
    and the panel keeps the last control it explained while the pointer is over empty space or over the panel, so the
    link can be reached. Help text is written for the transport bar, the arrangement tools and lane buttons, the mixer
    buttons and sections, the file browser, the piano roll tools, the launcher and the buttons of the rack panels. Every
    knob, switch and choice of every device explains itself from its descriptor (its name, its range and unit) plus a
    line about its device, and every device type has such a line. A control with no entry yet falls back to its tooltip
    text. The text lives in two data files (crates/app/src/help/), and a test lists the controls that still lack an
    entry.
  • Genre templates. Six songs to start from ship with the program and come first in File > New from Template and on
    the start screen: Ambient, Hip-Hop Boom Bap, House, Lo-fi, Synthwave and Techno. Each has a tempo, a song key, eight
    sections over 64 bars as ranges, six named and coloured tracks (kick, drums, bass, chords, lead and a texture) of
    factory patches, kit pads and clips, a filled launcher, two sends (a space reverb and an echo), the strip EQ on the
    bass, a duck from the kick, a glue compressor and a -1 dBTP limiter on the master aimed at -14 LUFS, and song
    information. Your own templates follow them in the list.
  • Export presets. One choice exports for a purpose. The export panel has a Preset row (a drop-down, Save Preset
    and Delete Preset) and File > Export for runs a preset at once: Streaming (a 24-bit WAV and an MP3 at 320 kbps at
    -14 LUFS, true peaks under -1 dBTP), Podcast (a mono MP3 at 128 kbps at -16 LUFS), Video (AAC at 256 kbps and
    48 kHz at -14 LUFS, or the film with that mix when the song has one), Stems for mixing (a 24-bit WAV per strip,
    no loudness change, no dither) and Club (a 24-bit WAV with -9 LUFS as a guide only, no limiter added, and a
    warning in the report if the peaks clip). Choosing a preset fills the panel's fields, which stay editable (the
    name shows "(changed)"); Save Preset keeps them under a name of your own in export_presets.json. The panel has
    new rows for the mono mix-down, the loudness (off, -16 or -14 LUFS, or a -9 guide) and an extra MP3 next to a
    lossless file. A loudness target measures the render, turns it up or down and, when the peaks would pass the
    ceiling, holds them with the true-peak limiter of the Mastering device; the toast says the level before, what
    was done and any limiting. The presets that write MP3, AAC or Opus are greyed with "Needs FFmpeg" without it.
    A mono MP3 is now written as one channel.
  • Quick sidechain: Duck from. One step makes a track duck under another, such as a bass under a kick or a pad
    under a vocal. The right-click menu of a track header, the rack menu of a track's device and the mixer's strip menu
    have a Duck from submenu (and Track > Quick Sidechain has Duck from...) that lists the other tracks by name and in
    their colour, at most thirty and then More... for a pop-up with all of them. Choosing a track puts a Compressor
    named "Duck from " at the end of the ducked track's insert chain, with its key cabled from the source's
    post-fader output (Duck from (pre-fader) takes it before the fader) and set to 4:1, 5 ms attack, 120 ms release
    and -24 dB threshold, in one undo step; the toast says "Bass ducks under Kick. Adjust: Threshold on the
    Compressor." Choosing the same pair again selects the device ("Already ducking from Kick"), a source that the
    track feeds is refused as a loop, Remove Ducking takes every ducker off in one step, and Gentle Pump puts a
    quarter-note pump with no key on the track. Nothing is added to the project file: the device name marks the ducker.
  • AppImage and Flatpak for Linux. The release and nightly builds now also produce
    atomik-rack-<version>-x86_64.AppImage and atomik-rack-<version>.flatpak (a single-file bundle), each with a
    checksum in SHA256SUMS, beside the .tar.gz and the .deb. All four hold the same programs. One desktop entry,
    one AppStream file (with a releases list made from the version) and the icons are installed under the app id
    io.github.atomikfactory.AtomikRack by the .deb, the AppImage and the Flatpak, and the program uses that id as
    its window class so the desktop shows the right name and icon. The AppImage takes the sound, font and graphics
    libraries from the host; the Flatpak runs on org.freedesktop.Platform with Wayland and X11, GPU, sound, MIDI
    and read-only access to the home folder, with ~/.vst3 and ~/.clap named (plugin folders under /usr are not
    visible in it). In a Flatpak the update notice says to update with your software centre. Pull requests check the
    scripts, the manifest, the desktop entry and the metainfo; the packages are built only by the release workflows.
  • CPU use per device. The engine now times every device all the time (about half a percent of a 64-frame callback
    for a hundred devices, never part of the sound), and the figures are averaged over about a second with a peak held for
    two seconds. View > Show Device CPU (the old CPU Meters switch, off at the start) shows a figure such as 3.2% on the
    name plate of each device, in the warning colour above 25 % of the audio time, and the total of its track (instrument,
    channel and insert effects) on each channel strip of the mixer. The tooltip of the status line gives the engine load
    and lists the five heaviest devices with their tracks. When the engine load stays above 70 % for five seconds while
    playing, a card says which track uses the most CPU and offers to freeze it with one click, once per track per song.
  • Chord track and song key. The song can have a key and a chord lane that the rest of the app follows. A key is a
    root and a scale kind (every kind of the piano roll but chromatic); key changes along the song work like meter
    changes, and the key at a tick is the last change at or before it, else the song key. A chord has a root, a quality
    (the 21 qualities of the chord stamp), an optional bass note and a span; chords never overlap. View > Lanes and
    Markers > Key Lane and Chord Lane show two rows above the track lanes, under the tempo and energy lanes. A click on
    the empty lane adds a key change (the key already in effect) or the tonic chord of the key there, a bar long, and a
    drag from the press sets its length; a drag moves a tag or a chord, the right end of a chord resizes it and neither
    runs into the next chord; a double click opens a picker with the root, the quality (or the scale) and the bass note
    and a text field for a chord symbol such as Am7, F#m7b5, C/G, Bbmaj7 or Dsus4/A, read by a small parser
    that takes the common spellings (m, min, -, maj7, M7, dim, sus, add9, flats and sharps in letters or
    signs) and says what it cannot read; the right button lists Delete and Copy, and Paste on the empty lane. Every
    gesture is one undo step and Escape puts a drag back. The transport bar has a Key field with the key at the playhead
    (a click sets the song key; it moves into the overflow list on a narrow bar, where Song Key... is a row) and
    Transport > Song Key... and Detect Song Key do the same from the menu. A clip without a scale of its own follows the
    song key at its start in the piano roll (highlighting, snap to scale and the fold), and a scale on the clip still
    wins. The chord stamp has a Song Chord entry that drops the chord of the lane at the place drawn (with its bass note
    below), and Fit Notes to Chords moves the selected notes that fall outside the chord at their position to the
    nearest chord tone, a tie going down and never onto a note that is there already, in one undo step. Detect Song Key
    reads a pitch-class histogram of every note clip (a note counts as much as it is long) against the standard major
    and minor key profiles, sets the best of the 24 keys as one undo step and says in the status line how clear it was;
    a toast holds no buttons, so Undo is the way back. In the browser, key:song in the search finds the loops tagged
    with the song key (A minor, D dorian; flats match too, and a song without a key filters nothing), and
    key:minor finds a part of a tag. Format 45, the song fields key, key_changes and chords are written only
    when set and are ignorable, so the version and the compat stay; every saved file lists them in its ignorable
    header, so the example projects, the factory files and the format fixtures were saved again. Command count 538.
  • Audio and MIDI setup. The first time Atomik Rack starts (no settings.json yet) a short panel opens before the
    start screen and gets sound working in three steps. Sound output lists the audio hosts, the output devices and the
    buffer sizes (the same lists as Audio Settings, with the hint "smaller = less delay, more CPU"), a Test button plays
    a soft sine chord for one second at -18 dBFS through the engine, and the output meter beside it moves when the sound
    reaches the device; the output latency is shown in milliseconds, as the stream reports it or as an estimate from
    the buffer when the host does not say. If the device does not open, a plain message says why and points to another
    one. Input is optional: an input device list, a live input meter and a Turn On Input button for a project with no
    input channels. MIDI keyboard lists the MIDI inputs with a check box each, lights a "note received" lamp and plays a
    soft tone for every key, and Set Up Controller... opens the controller wizard. Next, Back, Skip and Done move
    through it; Skip and Done both write settings.json, so it never opens by itself again, and each choice is applied
    at once through the same path as Audio Settings, which writes the same file. The question about checking for new
    versions waits until the setup is closed. Options > Audio and MIDI Setup... (options.audio_setup) opens it again
    at any time. The engine now publishes the loudest output and input sample of each batch (the preview voice and
    the click included). Format unchanged (45), command count 533.
  • Clip launcher. View > Launcher (F10) puts a grid where the rack was, the arrangement below it: one column per
    note track, one row per scene, a launch triangle in each slot, a scene column with a launch button and the scene's
    name, a stop square under each track and STOP ALL. A slot holds a note clip with its own loop length, name, colour and
    launch quantize; a double click opens it in the piano roll (an empty slot gets a one-bar clip), a drag moves it and
    Ctrl-drag copies it, and the right-click list renames, colours, sets the loop length and the quantize, duplicates and
    deletes. A launch waits for the next boundary of the quantize (None, 1/16, 1/8, 1/4, 1/2, 1, 2 or 4 bars, 1 bar by
    default, set for the song or per slot), exact through tempo ramps and meter changes, and then the clip loops from its
    own start while its track's arrangement stays silent, until the slot stops or Back to Arrangement (at once) gives the
    track back. Launching with the transport stopped plays; notes that are on when a slot stops or switches get their
    note-offs. A scene launches every slot of its row and, with Scene Stops Empty Tracks on (the default), stops the
    tracks that have nothing in it. Record Launches (a switch in the view and a command) makes the Record button write
    what was launched into the arrangement, at the song ticks it played, as looped clips, and the whole pass is one undo
    step; it needs no armed track. The Launcher menu under View has the commands, Clip to Launcher and Launcher Clip to
    Arrangement move a clip between the two by command, and Enter and Shift+Enter launch the slot and the scene under the
    cursor. Audio tracks have slots too: an audio clip (its file, gain and fades) plays unwarped, looped over the length
    of the slot, with a small waveform in the slot; an audio file dropped on an audio slot (a MIDI file on a note slot)
    makes its clip. A clip dragged from the arrangement into a slot copies it, and a slot dragged onto an arrangement lane
    writes a clip there at the snapped tick (each one undo step). Not done yet: warped audio in slots (it plays at the
    file's own tempo), launching from a controller, follow actions and scene tempos that change the song tempo. Command
    count 532.
  • Project format 45. A reader of format 44 refuses a file of 44 that holds a field it does not know, so the
    launcher and the per-note expression, added after 0.4.0-rc.1, could not be skipped by it. Files now say version 45
    with "compat": 44 and list those fields as ignorable: a 44 reader opens them, drops the launcher and the note
    expression with a warning each, and plays the rest. The version-45 corpus file and demo fixture are added.
  • Undo History panel. Edit > Undo History (the command edit.history, no default key) docks a list of the edits
    made to the song on the right of the window, left of the Track Panel when both show. The first row is the state the
    song started in ("Opened", or "New song"), each row after it is one undo step with its name and how long ago it was
    made ("2 min ago"), oldest at the top. The row the song stands on is highlighted and the steps after it, the ones
    Redo would bring back, are dimmed. A click on a row undoes or redoes as many steps as it takes to reach the state
    right after that step, through the same Undo and Redo the keys run; a click on the first row undoes everything. With
    the list focused, Up and Down step one undo or redo, and Home and End go to the first and the last row. The list
    scrolls and keeps the current row in view, follows every edit, undo and redo (also the ones made with the keys while
    it is open) and starts again with a new or opened song; each song window has its own. Whether it shows is kept for
    the session. The times are not saved. Format unchanged (44), command count 521.
  • Command palette. Help > Command Palette (Ctrl+Shift+K, Cmd+Shift+K on macOS) opens a floating panel with a search
    field and a list of every command: the menu items as the menus show them now, with their menu path, and the other
    commands the keys reach, under their group. The search takes several words and matches the name, the menu path and
    the id, by whole words first and by scattered letters after that, and the matched letters are bold. Each row shows
    the key the live keymap gives the command, so remapped keys show; a command that cannot run now is dimmed and still
    says why when run. Up, Down, Page Up and Page Down move, Enter or a click runs the command after the palette has
    closed (on the pane that had the focus), Escape or a click outside closes it, and typing never reaches a shortcut.
    The last eight commands run from the palette come first, and are kept in palette.json next to the settings.
    Format unchanged (44), command count 520.
  • More factory content. The Factory root grows from 49 to 79 patches, from 12 to 36 note clips and gains 12
    audio loops (the addition is about 8 MB in git; a test keeps the whole folder under 25 MB). Four new drum kits
    (Timber Kit, acoustic-like; Circuit Kit, electronic; Cassette Kit, lo-fi; Bazaar Kit, hand percussion) have 14 or
    15 pads each on keys 36 to 50, rendered by the writer from the drum machine's pad modules. Thirty patches are
    new: more for the FM synth, dual layer, organ, semi-modular synth, grain sampler, mono bass and wavetable synth
    (at least five each now), and the first for two reverbs, an echo, modulation, distortion, the auto-filter and the
    rotary speaker. The 24 new clips are eight drum grooves (from 70 to 174 BPM, in straight and triplet time), six
    bass lines, five chord progressions and five arpeggios. The 12 loops are 24-bit stereo FLAC files rendered from
    clips by a factory kit or patch; each plays its clip twice and keeps the second pass so it repeats without a
    gap, and carries a tempo tag (88 bpm) and, when pitched, a key tag, so the browser's tag filter finds them.
    The Clips section of a library, and of the factory, now lists audio files next to note clips. Everything is
    original and rendered by the application's own devices; the writer is still test code
    (ATOMIK_WRITE_FACTORY=1 cargo test -p atomik-app --lib write_the_factory_library -- --ignored), and tests check
    that every file is what the tables describe, that each patch and kit makes sound and that each loop decodes at its
    tagged tempo. Format unchanged (44), command count unchanged.
  • MPE: per-note expression. A MIDI input can be switched to MPE in Settings > Audio > MIDI inputs with MPE
    (a click steps through off and a lower or upper zone of 15, 7 or 4 member channels). The zone is the one set
    there until the controller sends an MPE Configuration Message, which then replaces it (a zone of 0 members
    removes it). On a member channel the note on and off are ordinary notes, and the pitch bend (48 semitones until
    RPN 0 says otherwise), the channel pressure and CC 74 of that channel are the expression of the note sounding
    there, not of every note: what a channel holds before the note on starts the next note. Recording keeps them
    with the note as three curves, pitch in semitones, pressure and timbre, a burst closer than about 5 ms folded
    into one point and at most 1024 points per curve; Layer mode, loop passes, input quantize, splits, joins and
    loop conversion carry them with the notes. The poly synth (and so the mono bass and the dual layer), the
    wavetable synth and the FM synth play them: the tuning moves that voice's pitch, the pressure raises its gain by
    up to 6 dB (it is the pressure source of the poly synth's modulation slots), and the timbre opens the cutoff of
    the poly synth by up to three octaves, moves the frame position of the wavetable synth and adds up to one to
    the modulation index of the FM synth (the other instruments take a note's pressure as their pressure source and
    ignore the rest). A note with no expression sounds exactly as before. Seeks and loop wraps inside a note send
    the value in force, and a bounce is the same at every block size. MIDI files keep it: a clip or track with
    expression is written as an MPE track (the zone announced on channel 1, the notes on member channels, each
    note's bend, pressure and CC 74 on its own channel) and a file that announces a zone is read back into notes
    with their expression. In the piano roll the selected note shows its curves in a small strip under it with a
    button that clears them (one undo step). No project format change: a note clip may carry an optional,
    ignorable "expression" field (under format 44), written only while a note has curves. Not done yet: editing
    the curves by hand, expression for the other instruments, MPE member channels to plugins that take MPE MIDI and
    to the MIDI Out device (CLAP and VST3 plugins already get note expression events), and an expression that
    follows a note when the note is moved or retuned (it is kept by the note's start and key).
  • Controllers that just work. Settings > Controllers > Set Up Controller... walks through a controller:
    pick its MIDI input port, then move knob 1 to 8, fader 1 to 8, the master fader and press Play, Stop,
    Record, Loop and the two bank keys, with Skip, Skip Group, Back and Finish for what the keyboard lacks. It
    tells 7 bit and 14 bit controllers, NRPN, notes and pitch bend apart and whether a knob reports its position
    or is an encoder (three codings), asks to be turned both ways when it cannot tell, and ignores a control it
    already has. The result is a controller profile, a small JSON file in the controllers folder next to
    settings.json (the format is in the architecture notes), remembered by the MIDI port name, and set up as a
    surface of its own. The first eight knobs drive the first eight parameters of the selected device (or the
    device the surface is locked to) and follow the selection, the faders are the levels of the eight visible
    mixer strips and bank left and right move eight at a time, the keys are play, stop, record and loop. When the
    controller has an output port the wizard asks whether its knobs, faders and keys show values, and the
    profile then sends them back (LED rings, motorised faders, lit keys), only what changed and never against a
    hand on the control. Profiles are exported and imported from the same tab to share them, and several
    controllers work at once, each with its own profile, bank and lock. No project format change (profiles
    live with the settings, not the project).
  • An optional check for a newer version. The first time the program starts it asks "Check for new versions once a
    day?" in a small notice in the lower left corner (over the start screen too); until you answer Yes nothing is sent.
    A Yes asks the project page once a day, at the start, for its list of releases; Help > Check for Updates asks at once
    (and shows the question first while it is open). The request is one HTTPS GET of a fixed address with the User-Agent
    atomik-rack/<version> and nothing else: no identifier, no cookie, no query, no redirect, a short timeout. It runs
    on a worker, and a failure is silent unless you asked. A newer version (release candidates in the right order; a
    pre-release only for a pre-release build; never a draft) shows a notice with What's new (its release page in the
    browser), Skip this version (a later version still shows) and Later. Nothing is downloaded or installed. The answer
    is in Settings > Video & updates (update_check in workflow.json), the time of the last request and the skipped
    version are in updates.json. The README and SECURITY.md say what is sent; the client is the new crate
    atomik-update (ureq on rustls with the bundled root certificates; CDLA-Permissive-2.0 joins the allowed
    licences). The project format stays 44.
  • Film with Mix. File > Export > Film with Mix... writes a new film made of the song's film and the song's mix,
    through the FFmpeg you installed. The film's span is exactly the part of the song under the film after its trim and
    start (a film that begins before the song gets silence in front of the mix); the whole song renders from the start
    to the End with black pictures before and after the film. The mix's first sample sits at the first exported frame.
    The picture is copied without re-encoding when the cut is at the film's start (AUTO), always (COPY, which cuts at
    keyframes: the dialog says so, and RE-ENCODE cuts exactly) or re-encoded to H.264 at a high, standard or small
    quality; black before or after the film needs a re-encode. The mix goes in as AAC at 128 to 320 kbit/s in an MP4
    file or as 24-bit PCM in a MOV file, and the film's own sound can stay as a second track. It runs on the export
    worker with progress and a cancel that leaves no partial file (an existing film is replaced only by a complete
    one), and the menu item is greyed with the reason in the toast when the song has no video, the film's file is
    missing or FFmpeg cannot be used. The choices are remembered in export.json. The project format stays 44.
  • MP3, AAC and Opus export. The export panel has MP3, AAC (.m4a) and Opus buttons next to WAV, AIFF and FLAC
    and a QUALITY row: MP3 at 128, 192, 256 or 320 kbit/s or variable quality V0, V2 or V4, AAC at 128 to 320 and Opus
    at 64 to 192 kbit/s. They encode through the FFmpeg you installed, so no codec ships: the song, the loop and the
    selection are rendered to a temporary WAV file and FFmpeg encodes it on the export worker, with progress and a
    cancel that removes the temporary and partial files (an existing file is replaced only by a complete one). The
    song's title and author go into the file's tags as arguments, never through a shell. Without FFmpeg the three
    buttons are greyed with a line that says to set its folder in Settings > Video or put it on your PATH; stems stay
    WAV, AIFF or FLAC. The loudness in the toast is measured before encoding, so leave about 1 dB of true-peak
    headroom. The last format and quality are remembered in export.json. The project format stays 44.
  • A start screen that teaches. A strip of cards sits above the lists of the start screen: the three factory
    example songs, each with a line about what it is for (a click opens one as a new unsaved song, like a template),
    and a Make your first song card. A check box at the foot of the box turns that card off; Help > Guided Tour starts
    the same guide whenever you like.
  • A guided first song. Make your first song (the start screen card or Help > Guided Tour) opens a new song and
    shows a small floating panel with seven steps: add an instrument, play or draw some notes, loop them, add a drum
    pattern, mix (a level and an effect), save and export. Each step says what to do, watches the song and moves on
    when it is done (or waits for Next when you had done it already), and outlines the menu, button or area it talks
    about. Back, Skip, Move (to the other side of the window) and Close are always there. The panel never takes the
    keyboard, only the pointer inside its own rectangle, and what it shows is not saved in the song.
  • Drum pads light when they play. A pad of the drum machine panel flashes when the engine plays it, whatever
    sent the note: a note generator, the sequencer, a MIDI input, a click on the pad or a gate on its jack. A harder
    hit lights it brighter and the light fades out in a quarter of a second. The drum machine counts the hits that
    sound and publishes the counters like any other device's display values; nothing on the audio thread waits for
    the panel, and a hit on a pad that makes no sound lights nothing.
  • A level for the browser's previews. A small control in the browser's header sets the level audio files,
    patches, containers and clips play at when you preview them, from -60 dB to +6 dB (drag it, double-click to go
    back to 0 dB). It is saved with the Settings and applies to the next preview of every kind.

Changed

  • The menu bar in every window. The detached rack window and the detached mixer window now show the same menu bar
    as the main window (File, Edit, View and the rest), so every command is reachable from the window you work in. It
    is one menu model: the same items, check marks and enabled states in all three windows, and a toggle chosen in one
    shows its mark in the others. A command acts on the pane of the window whose bar you used: Edit > Select All, Copy
    and the others work on the rack devices in the rack window and on the strips in the mixer window. Only one menu is
    open at a time across the windows; it closes when another window takes the focus, when you press in another window
    or when the app loses the focus. The pane starts below the bar, a window is never narrower than the bar, and
    pointer positions, drags between windows and the saved window size are unchanged. The small windows (Spectrum EQ,
    Piano Keys, Video and the detached browser) keep no bar, and on macOS the system's menu bar stays the only one.
    Format unchanged, command count unchanged.
  • One text field everywhere. Every place where you type text (names of markers, folders, tracks, clips, lanes,
    buses, groups, snapshots, devices, patterns, macros and assets, the search boxes, comments, the tempo, signature,
    position, time, locator and clip inspector entries, the note and point fields, the macro range values and the
    buffer size) is now the same field, with a caret, a selection by Shift and the arrows or the mouse, a double click
    on a word, Ctrl/Cmd+A, C, X and V, Home, End, word moves with Ctrl, input methods and an undo of its own:
    Ctrl/Cmd+Z undoes, Ctrl/Cmd+Shift+Z or Ctrl+Y redoes, a run of letters is one step and 50 steps are kept. While a
    field has the keyboard these chords edit the field and never run the song's Undo; with no field, Ctrl+Z is the
    song's Undo as before. Number fields refuse other characters. In the plugin parameter pane, whose search field
    always has the keys, Undo is the field's only while it has typing to take back. A right-click on a name, search,
    comment or macro field opens a small menu (Undo, Redo, Cut, Copy, Paste, Delete, Select All, dimmed when they have
    nothing to do) that edits that field only. Format unchanged (44), command count unchanged.
  • Bigger drum pads. The pad grid of the drum machine panel uses the room between the pads and the knob
    columns, and the sample name and the pad number are drawn larger.
  • A click on an empty automation lane selects the lane. With the Select tool a click on empty lane space picks
    the lane and its track, and a drag draws a selection band, instead of adding a clip and a point. A double-click
    on empty lane space still adds a point (a clip over the bar clicked, with a point at the pointer), and the Pencil
    tool still draws.

Fixed

  • A plugin that answers a busy result no longer shows FAILED. A VST3 plugin that returned something other than OK
    from its audio call (many do while they load content, sign in or change their buses) failed its device for good with
    "the plugin returned an error status", and the instrument made no sound. That block is now silent (dry for an
    effect), counted and reported once in the plugin log, and the device keeps playing; only a crash, a panic or a lost
    plugin process fails a device. A plugin whose buses moved without a restart request is given matching buses when it
    is activated, and a bounce waits for a restart to finish so its pre-roll is the same everywhere.
  • The notes input follows the rack selection. Selecting an instrument in the rack (built-in or plugin) now arms its
    track and sends the keyboard to it, as clicking its channel strip in the mixer does, instead of leaving the input on
    the instrument that was armed before.
  • Plugins that take long to restart, change their buses or replace a built-in device. A plugin that was busy
    while the host deactivated it for a restart (just after a sign-in in its own window, for example) was stopped after
    2 seconds; deactivation is now waited for as long as an activation, and a restart polls it instead of holding the
    window, so a busy plugin that is alive is no longer stopped (a plugin that never answers still is). A plugin that
    gains or loses buses at run time (aux outputs, a sidechain) now updates the scan cache (plugins.json), the device
    browser and the registry together, so adding it again, opening a project saved after the change and dragging its
    row from a browser that predates it all work; the cables on ports that remain are kept, and only those on ports
    that vanished are removed, with a message. Dropping a plugin on a built-in instrument or effect to replace it now
    creates the plugin like a normal add instead of leaving a MISSING stand-in with audio off; undo brings the
    built-in device back.
  • Select All in the search boxes. Ctrl+A (Cmd+A on a Mac) in the device browser's search, the parameter
    search and the plugin parameter search now selects the text you typed, instead of the devices in the rack. These
    boxes now have a caret you can move or click into place, and Ctrl+C, X and V copy, cut and paste their text.
  • A dropped sample names its drum pad at once. The panel kept saying "empty" for a pad that had just received
    a sample until something else rebuilt it; the pad names now follow the zones the moment they change.
  • Undo in the middle of a band selection. Undoing while a rubber band was open in the arrangement left clips
    in the selection that the undo had removed; the band now keeps only the clips that still exist, on release and
    on cancel.
  • Undo of an effect created inside a channel's insert chain. Creating an effect at a rack slot above the
    chain's end joins it to the chain and rearranges the rack in the same step; the step recorded the old order
    from before the new effect moved, so undo could fail and leave the effect behind. The recorded order now
    matches the rack as it really was.
  • Sandbox crash tests on slow machines. The tests that wait for a crashed plugin child to turn its device
    to Crashed now wait on that state against a generous deadline instead of a fixed number of batches.
  • Cables that would close a loop through the console. Dropping a cable from a console output onto a channel
    input (or its stereo pair) used to send a cable the project refuses; the drop is now ignored up front.

Fixed

  • A compressed or renamed export no longer replaces a file unasked. The save dialog picks a name before the
    format is chosen in the export panel, and the file gets the extension of the format, so an existing .mp3, .m4a,
    .opus, .aiff or .flac (or the .mov of a film) at that name was overwritten without a question. The dialog now
    proposes the extension of the format used last, and an export whose format changes the name to a file that exists
    says so under the options and starts only when EXPORT is pressed again.

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.4.0-rc.2/CHANGELOG.md