RecallDock Changelog

Notes3 updates

Hotkeys now work every time you press them. Before, a key or button mapped to Recall, Save, or a Recall slot only worked every other press.
RecallDock now double-checks it has the right plug-in before opening or closing its window, so it never touches the wrong one when you recall from another track.
Tip: using letter keys as hotkeys? Turn off Live's Computer MIDI Keyboard (the little piano button at the top right), or those letters will play notes instead.

Notes6 updates

Recall now takes you back to where you were. Press your Recall hotkey while you're working on any track, and when RecallDock is done, Live returns to that same track with the same device or clip showing. Save and Recall On Load do the same.
Want to land on one particular track every time instead? Open Settings on the RecallDock device and pick it. Your pick always wins. If you don't pick one, the setting is Track I Was On.
The Settings panel now explains in plain words where you'll land, and what happens if your picked track is deleted or tucked inside a closed group.
Groups and racks that RecallDock opens to reach a plug-in are now put back the way you had them when it finishes.
Plug-ins on tracks inside a closed group now reopen when you recall. RecallDock opens the group to reach them, then closes it again.
If the track you picked in Settings is inside a closed group, Live now lands on that group instead of the RecallDock track.

Notes7 updates

Choose where you land after a recall: open Settings on the RecallDock device and pick the track Live selects after Save, Recall, and Recall On Load. Pick any track, return track, or Main, or keep the default, the RecallDock track.
Max for Live windows now come back in the same front-to-back order you saved them in.
Fixed Save and Recall failing when you use the same Max for Live device more than once and its windows open in exactly the same spot.
Recall On Load no longer fails if Live shows a message while your Set opens (such as Save changes? or a missing audio device). RecallDock waits until you close it, then restores your layout.
If a plug-in window can't be reopened, RecallDock now clearly shows Recall Failed instead of pointing you to Live's plug-in settings.
If RecallDock restarts in the middle of a recall, your next recall now runs right away instead of being skipped.
RecallDock writes much less to disk during long sessions, and Export Debug Logs... now includes more detail to help us fix problems faster.

Notes5 updates

Windows: plug-in editors now reopen even when a floating Max for Live window or another editor is in front; the helper locates Live's main window instead of the first Live-owned window.
Recall now reopens every closed Max for Live window in a snapshot, not just the first one, by addressing each device through its native runtime key.
Plug-in editors that were closed when a layout was saved are closed again on recall, including plug-ins whose window title is unique in the Set.
A recall that cannot reopen a saved plug-in window now reports Recall Failed instead of Complete.
Windows: added Export Debug Logs... to the notification-area menu, fixed blank dialog title bars, and the installer now stops a running helper so the new executable is always installed.

Notes3 updates

New Settings panel: choose which track Live selects after Save, Recall, and Recall On Load — the RecallDock track by default, or any regular, grouped, return, or Main track. The choice is stored by Max's persistent Live object mapping, so it survives renaming, reordering, and reopening the Set.
Finishing on your chosen track is best effort and can no longer fail a Save or Recall: if Live cannot select it (for example inside a folded group, or after it was deleted), RecallDock lands on its own track instead and the operation still completes.
Return tracks are labelled (Return) and the master track appears as Main; two tracks with the same name stay separate entries in Set order.

Notes3 updates

RecallDock now spots older devices saved inside Live Sets and templates before they can cause Save or Recall failures, then shows clear steps for replacing them safely.
When you replace an outdated device, RecallDock can safely restore your saved layouts and Recall On Load preference after verifying that the replacement belongs to the same Set and device location.
Save and Recall requests now survive audio-engine pauses and busy Max sessions, resuming once without being lost, duplicated, or applied to the wrong device.

Notes3 updates

Verify the hardcoded identity of the RecallDock patcher actually loaded in each Live Set against the current Node and JavaScript bridge before enabling Save or Recall.
Detect stale, missing, and mixed runtime components with precise status codes, clear in-device replacement guidance, template-specific warnings, and complete compatibility details in debug exports.
Preserve layouts and RecallDock preferences across deliberate device replacement through a guarded recovery record, while rejecting corrupt, expired, mismatched, non-empty, or ambiguous migration state.

Notes3 updates

Keep every Max-to-Node bridge command in a persistent correlated queue until the exact patcher acknowledgement arrives or the operation is explicitly cancelled, so scheduler suspension cannot discard Save or Recall work.
Recover the same queued request automatically and exactly once after Ableton's audio engine or Max scheduler resumes, while treating qmetro as a wake-up hint and maxApi.outlet fulfillment as submission evidence only.
Preserve the validated chunked large-device transport and add hard suspension, duplicate-wakeup, cancellation, queue-pressure, and exact 111-device regression gates.

Notes3 updates

Deliver production bridge commands through a Max-driven correlated request pump so Save and Recall no longer depend on unsolicited Node-to-Max messages waking the patcher.
Require patcher acknowledgement before starting bridge response deadlines, keep diagnostics observational, and report the exact inactive-pump, missing-route, unavailable-JavaScript, or missing-response boundary.
Preserve the validated chunked deep-result transport for large Ableton Sets, including complete device metadata, byte-count, ordering, request-identity, and checksum verification.

Notes3 updates

Transport large Ableton device inventories as correlated bounded chunks below Max's 32,767-byte message limit, preserving every device row and metadata field during Save and Recall.
Validate chunk order, serialized byte count, CRC32 checksum, UTF-8, request identity, and terminal device count before accepting an inventory, with exact transfer measurements included in exported diagnostics.
Keep independently bounded duplicate-device window-state probes from consuming the unrelated Save transaction budget, and recompute the final restore deadline after enrichment so large duplicate-heavy Sets complete deterministically.

Notes3 updates

Detach every long-running Node-for-Max command handler so Save and initialization work return control immediately and correlated Max callbacks cannot be starved behind an operation Promise.
Treat maxApi.outlet Promise fulfillment as confirmed bridge dispatch, starting response and cancellation deadlines only afterward and reporting delayed or rejected dispatch precisely.
Route production bridge requests and responses independently from deferred diagnostic sidebands, preserving boundary evidence while missing diagnostics emit warnings without failing Save or Recall.

Notes3 updates

Require a fresh, identity-verified Max bridge handshake through the exact production patcher route before every Save, Recall, or deep-enumeration operation.
Record each Node, patcher, JavaScript handler, response-outlet, unload, cancellation, dispatch-failure, and terminal boundary in exported debug logs so one customer ZIP identifies the first unobserved component.
Fail at the precise missing or mismatched bridge boundary instead of entering the deep-enumeration timeout, while preserving the 3.4 Task-driven traversal and Save/Recall behavior.

Notes3 updates

Fix Save failures in complex Ableton templates by yielding during deep device enumeration and reporting an explicit accepted/start acknowledgement plus continuous correlated progress.
Add deterministic cancellation and terminal cleanup so a timed-out deep scan releases its quarantined request instead of causing every subsequent Save to fail as busy.
Separate acknowledgement and progress-idle deadlines, remove the arbitrary hard completion cutoff while traversal continues making progress, and preserve phase-specific diagnostics for future failures.

Notes2 updates

Prevent Live's automatic RecallDock numeric device-name suffix from being misclassified as a Max for Live topology change when the structural device identity is unchanged.
Add persistent per-Save and per-Recall diagnostic flight records with stage timings, correlated helper requests, terminal errors, and bounded beginning/end evidence so one debug export preserves the exact failed transaction.

Notes6 updates

Add 16 stable RecallDock snapshot slots that can be assigned in Ableton Live Key Map or MIDI Map, along with all RecallDock action controls.
Add a stored Show Mappings toggle that expands the device to reveal the slot grid and collapses it back to its compact width.
Restore real Live 12.4.3 Key/MIDI Map visibility for the slot and action controls after no-undo parameter modes made them unassignable.
Make mapped slot and momentary action controls accept one Max bang or mapped value 1 per press, reject note-off value 0, reset silently, and ignore stale saved trigger values during Set startup.
Recover plug-in editors when Live reports their wrench as open but the actual floating window is missing.
Recover Max for Live windows after their real outer window closes but Max leaves a stale internal visibility flag set.

Notes3 updates

Fix macOS capture and recall for valid floating plug-in editors hosted above WindowServer layer zero.
Require one-to-one Accessibility identity for nonstandard window layers while rejecting incomplete or ambiguous window inventories before capture or mutation.
Stabilize first-open plug-in restoration by reacquiring fresh window identity and geometry during Live's bounded editor-settle period.

Notes3 updates

Fix macOS layout saves that could stall for two minutes in particular Ableton sets by replacing the unbounded all-application Accessibility scan with bounded, Live-only window discovery.
Make each save use one idempotent native window capture, while reusing that capture for set scope and Max for Live window correlation instead of rescanning.
Add stable WindowServer identities, finite Accessibility and transaction deadlines, single-flight enumeration, request-ID replay protection, and fail-closed partial-capture diagnostics.

Notes3 updates

Fix layout saving in large or deeply nested Ableton templates by replacing the fixed 2.2-second whole-project device scan deadline with a progress-aware watchdog.
Add request-correlated track and device diagnostics so stalled or failed LiveAPI enumeration identifies the exact scan location without accepting incomplete plug-in topology.
Remove temporary helper snapshots when device-metadata enrichment fails, preventing failed saves from leaving ghost layouts in helper memory.

Notes4 updates

RecallDock now captures and restores floating Max for Live device windows on macOS and Windows, including their open/closed state and screen position.
Added a Start At Login menu option on macOS.
Added in-app Release Notes and cumulative changelogs in update prompts.
Various fixes and enhancements for startup, installation, packaging, and overall reliability.

Notes3 updates

Harden Windows startup and activation dialog message-loop handling.
Fix Windows installer builds for both x64 and ARM64 systems by selecting the correct Visual Studio toolchain automatically.
Make Windows ZIP packaging and frozen Max for Live device verification reliable across fresh repository checkouts.

Notes4 updates

Capture and recall standard floating Max for Live patcher windows on macOS and Windows, including open/closed state and screen position.
Restore Max for Live windows through their real device patchers without duplicating device controls.
Ship one frozen Max for Live device containing both the universal macOS external and the x86-64 Windows external.
Prevent duplicate RecallDock helper processes and extra menu-bar icons.

Fixed1 update

Bug fixes

RecallDock changelog

v4.7

v4.6

v4.5

v4.4

v4.3

v4.2

v4.1

v4.0

v3.9

v3.8

v3.7

v3.6

v3.4

v3.3

v3.2

v3.0

v2.9

v2.8

v2.7

v2.6

v2.5

v2.2