BUFFR beta · Free until the public beta ends · no end date announcedTry it
BUFFR

BUFFR vs Rewind, Rolling Sampler, and other capture tools

Retrospective recorders do not all preserve the same sources or require the same setup. This source-linked comparison separates plug-in capture, standalone-only features, routing components, history, and export fidelity.

Reviewed July 25, 2026

The short answer

Matari Audio makes BUFFR. This comparison was reviewed on July 25, 2026 against first-party manuals, product pages, and vendor-owned source repositories. It names the documented workflow and its actual boundary instead of filling gaps with ambiguous unknowns.

BUFFR is the only compared recorder that keeps DAW audio, a separate System Audio lane, and DAW or direct-device MIDI in one loaded plug-in. Rewind is the closest broad alternative, but its built-in System mode is explicitly standalone-only. Rolling Sampler and Fine Classics Capture retain audio; MIDI Cap and Mucap retain MIDI; AudioRoute and System Audio Bridge route live system audio rather than keeping a retrospective history.

Capability-by-capability proof

Read each row as a workflow question: what must run, what reaches it, whether sources remain separate, how long history survives, and what the exported file preserves.

BUFFR and retrospective capture tools compared by published capability
CapabilityBUFFRDAW audio + MIDI + System AudioRewindAudio + MIDI; System mode in standaloneRolling SamplerRetrospective audioMIDI CapRetrospective MIDIMucapRetrospective MIDIFine Classics CaptureRetrospective audioSystem Audio BridgeLive Windows system-audio inputAudioRouteLive system-audio routing / recording
One retrospective timelineWhich sources can be retained together inside one recorder while the DAW is running.DAW audio + System + MIDISeparate audio groups plus DAW or direct-device MIDIDAW audio + MIDIBuilt-in System mode is standalone-only, not a source in the normal plug-inAudio onlyThe signal reaching the plug-inMIDI onlyMIDI onlyAudio onlyWaveform retrospective recorderNo historyLive System Audio input for normal DAW recordingNo historyLive route or deliberate WAV recording
DAW audio capacityWhat one loaded recorder can retain from the host.Up to 16 DAW slotsStereo Main plus seven host-routed stereo Aux pairsInsertion-point mixStandalone inputs are merged into one export track; the plug-in records its routed channel/masterOne audio streamAudio reaching the plug-inNoneCLAP audio passes through but is not retrospectively recordedNoneOne audio streamWaveform selection exports to WAVSystem stream onlyNot a DAW-history recorderSystem stream onlyNot a DAW-history recorder
Retrospective MIDIRecover played notes and controller data after the performance.16 channels + MPE/UMPDAW or direct device; rich events retained in the bufferMIDI + CC/MPEVendor warns Ableton drag-in can lose MPE and Bitwig can truncate CCNoneAudio-only recorderMIDI + CCMultichannel; vendor says MPE support is unfinishedBasic MIDIAll channels; MPE is theoretical and untestedNoneThe product and manual describe audio-to-WAV captureNoneNone
Controller without arming BUFFR’s trackOpen a hardware MIDI device from a bus or master rather than routing it to the recorder track.Built inSystem device opens the OS input; matching DAW/device duplicates collapse automaticallyDirect device or DAW inputThe manual makes them mutually exclusive; Windows sharing can require its SharedMIDI extension and a cloned DAW portNoneNo MIDI captureNo direct-device modeVendor’s typical setup is a record-armed, always-monitored MIDI trackNo direct-device plug-in modePlug-in needs a MIDI-receiving track; standalone needs JACK routingNoneNo MIDI captureNoneNone
System Audio inside the retrospective plug-inRetain computer output beside DAW material without leaving the plug-in workflow.Built in · separate stereo laneNo third-party cable or bridge; macOS 13+ grants permission to the bundled helperStandalone onlyExternal/System switch clears current memory; macOS reroutes output, Windows selects an appNot in stable plug-inStable uses loopback/System Audio Bridge; 1.4 beta adds experimental Windows standalone captureNoneMIDI onlyNoneMIDI onlyNoneRecords the audio reaching its DAW trackLive Windows inputWASAPI-loopback CLAP/VST3; no retrospective bufferLive routed inputBackground daemon feeds a DAW plug-in, direct recorder, or macOS virtual input
Source separationWhether different capture sources stay independently recoverable.Main, Aux, System stay separateIndependent groups, lanes, monitoring, and exportOne audio trackStandalone can select many interface inputs but merges them; External/System is a destructive mode switchOne audio streamMIDI channels in one fileAll MIDI channels in one trackOne waveformOne live stereo inputOne live routed stream
Broad safety-net setupWhat must be loaded, wired, or kept running to cover the product’s advertised sources.One DAW plug-inSystem Audio is built in; choose a controller once. Optional Linux MIDI service only for exclusive RawMIDI hostsPlug-in and/or standaloneDAW capture uses an instance; System Audio needs standalone plus installed routing; always-on use needs startup/template setupPlug-in or standaloneStable System Audio needs loopback/virtual cable; 1.4 Bridge needs plug-in + standalone + matching sample ratesArmed/monitored MIDI trackNo helper or serviceMIDI track or JACK routeStandalone needs a JACK-compatible graph connectionOne routed DAW plug-inCaptures the signal reaching its trackOne Windows DAW plug-inPrefer ASIO and avoid feedbackInstaller + background daemonEnable Output to DAW; some hosts must record track output
Maximum published historyHow far the current first-party material says the recorder can look back.120 minutesSelectable 1–120; dense audio remains RAM-resident, with separate recovery checkpointsUp to 90 minutesProduct, Welcome, and settings agree; other manual sentences conflict at 30/60Stable: 10 minutesDefault 45 seconds; 1.4 beta says increased but gives no number60 minutesDefault 60 seconds; adjustable to one hourNo rolling limit in current sourceInstance-memory-bound implementation inference, not a published guaranteeAdjustable, maximum not statedNoneLive input, not retrospectiveNoneLive routing or deliberate recording
MIDI / MPE fidelityWhat is retained and what survives the published export path.Rich buffer; compatible SMFMPE, note expression, UMP, raw events; SMF down-converts richer data and writes a .buffr-midi companionMPE + CC with destination warningsVendor reports lost MPE in Ableton and truncated CC in Bitwig drag-inNo MIDICC + multichannelMPE explicitly unfinished/not guaranteedBasic MIDIMPE theoretical and untestedNo MIDINo MIDINo MIDI
Spectral extractionSelect a sound by both time and frequency before exporting it.Only BUFFR: Spectral GrabAlt-drag, audition, then export with FFT, minimum-phase, or linear-phase reconstructionNo spectral workflowTime/waveform selectionNo spectral workflowTime/waveform selectionNot applicableNot applicableNo spectral workflowTime/waveform selectionNoneLive routing onlyNoneLive routing/recording only
History after a host crashWhat the documented workflow does with unsaved recorder history.Five-second checkpointsSaved instance identity restores audio, MIDI, and markers; an abrupt tail may be lostRAM cache with loss warningsClosing standalone or changing source/length can clear memory; no checkpoint-restore workflow in its manualRAM loop onlyFiles are created on drag; no restore workflow in stable manualNo restore workflowManual describes the live plug-in buffer and drag-outNo restore workflowCurrent source keeps instance-memory event vectorsNo restore workflowManual describes waveform selection and WAV exportNot applicableNo history bufferNot applicableNormal DAW/direct recording owns the file
Current platforms and formatsFirst-party operating systems and deliverables reviewed July 25, 2026.macOS · Windows · LinuxCLAP, VST3 in the current public betamacOS · WindowsVST3, AU, AAX, standalonemacOS · Windows · LinuxCLAP, VST3, AU, standalone; format varies by OSmacOS · WindowsCLAP, VST3, AU; format varies by OSLinuxCLAP, VST3, standalonemacOS · WindowsVST3, AU, AAX; format varies by OSWindowsCLAP, VST3macOS · WindowsVST3/AU path varies; Windows virtual input still pending
Result / export workflowWhere the recovered material can go.Audio + MIDI real-file dragDAW, another BUFFR, accepting app, or file manager; open protocolAudio + MIDI drag/saveSmart Drag placement guidance in the plug-inAudio drag/saveVendor warns some Linux/DAW drag combinations failMIDI-file dragGenerate + clipboard/pasteNot a documented drag gestureWAV dragTo DAW or browserRecord normally in DAWNo retrospective selectionDAW recording or direct WAVNo retrospective selection
Linux Wayland-session drag-outHow retrospective file drag is handled in Linux desktop sessions.Open Wayland/XWayland-aware backendMatari-tested on Hyprland, niri, KDE Plasma, GNOME, and Xfce; Void and NixOS also testedNo Linux buildVendor warns drag can failSome Linux distribution/DAW combinationsNo Linux buildClipboard/pasteNo documented drag sourceNo Linux buildWindows onlyNo Linux build

Linux drag-and-drop on Wayland compositors

BUFFR is the only recorder in this comparison with apublished open-source Linux drag backendthat explicitly handles XDND/XWayland and adds a Hyprland-specific native-Wayland handoff. BUFFR has worked on every Linux desktop Matari has tested:Hyprland, niri,KDE Plasma/KWin, GNOME/Mutter, andXfce.

Void Linux and NixOS are also tested, but they are distributions rather than compositors. BUFFR’s Linux file dialogs normally use the desktop portal/native picker; on Xfce it prefers Zenity and falls back to the native picker. Sway, River, Wayfire, labwc, and COSMIC are additional compositor families covered by the same standard Linux protocol paths, although Matari has not yet listed those combinations as tested.

This distinction matters because Rolling Sampler also publishes Linux drag-out support, while its vendor warns that some Linux distribution and DAW combinations may fail. BUFFR’s unique documented advantage is the open, Wayland/XWayland-aware implementation, not a blanket claim that every other recorder fails on Wayland.

BUFFR vs MonkeyC Rewind

Rewind’s normal plug-in records the audio and MIDI delivered at its DAW insertion point. Its manual labels the External/System control“standalone only.” Switching between External and System mode clears its current memory; on macOS, standalone temporarily routes system output through Rewind, while Windows asks which application to monitor.Read the Rewind 2.2.2 manual.

Rewind also has more setup surfaces: always-on use keeps its standalone app running at login or a plug-in in a DAW template; Windows controller sharing can require its SharedMIDI extension and switching the DAW to a cloned port. Rewind remains the better fit when standalone, AU, or AAX matters more than one in-DAW System Audio + DAW audio + direct-controller timeline.

BUFFR vs Rolling Sampler and MIDI Cap

Stable Rolling Sampler keeps 15 seconds to 10 minutes of the audio reaching its plug-in. Stable System Audio needs loopback/virtual routing or Bird’s separate System Audio Bridge. Its optional 1.4 beta adds experimental Windows System Audio to the standalone app and a Bridge plug-in that streams a DAW master to standalone; that bridge requires both ends and matching sample rates.Read the stable product/FAQ andthe 1.4 beta workflow.

MIDI Cap is a separate MIDI-only plug-in with up to one hour of history. Its typical setup is a record-armed, always-monitored MIDI track, and its manual says MPE support is unfinished. BUFFR covers both audio and MIDI in one instance and can listen to a selected controller from the master or a bus.

BUFFR vs System Audio Bridge and AudioRoute

Bird’s System Audio Bridge is a Windows CLAP/VST3 WASAPI-loopback input. It has no retrospective buffer: record the result normally in the DAW. AudioRoute installs a background capture daemon and exposes live system audio through a DAW plug-in, direct WAV recording, and a macOS virtual input. Choose either when live routing is the whole job. Choose BUFFR when System Audio must already be waiting in a separate look-back lane beside DAW audio and MIDI. See theSystem Audio guide,System Audio Bridge, andAudioRoute’s architecture.

BUFFR vs built-in DAW capture

Built-in capture is the shortest path when it already covers the source you need.Logic Pro Flashback Capturecaptures up to one minute of recent track-input audio during playback plus recent MIDI.FL Studio 2026keeps up to 10 minutes of master audio and 30 minutes of MIDI for the current session.Ableton Live Capture MIDIand Cubase Retrospective Recordingrecover MIDI inside their respective hosts.

Choose BUFFR when you want the same recorder across DAWs. In Bitwig, it complements transport-independent Master Recording; see theBitwig retrospective recording guide.

Primary sources

The table links each product directly. The detailed setup claims also come fromRewind’s manual,Rolling Sampler’s product and FAQ,MIDI Cap’s product/manual,Mucap’s source repository,System Audio Bridge, and AudioRoute’s published architecture. BUFFR claims were checked against version 0.5.81 source; see thecomplete BUFFR manual.