How can we help?

Yes. When Analyse 1 launches there is no trial, no licence key and no card. Install it on as many computers as you like.

So the download, and every update after it, lives in one place you can come back to. You can also choose to hear about new releases, but that is up to you.

No. Analyse 1 reads REAPER’s output directly, after the master bus and its effects. There is nothing to insert or arm.

No. Analyse 1 shows momentary (400 ms) and short-term (3 s) LUFS and sample peak, which is what you watch while you mix. For the integrated figure and the true peak of a finished master, use REAPER’s own JS loudness meter, or the loudness statistics from a dry-run render.

REAPER’s JS loudness meter is a plugin you insert, and it measures loudness. Analyse 1 needs nothing inserted: it reads the real output after the master bus and shows loudness, VU, peak, phase, the waveform and the spectrum together, in one strip docked across the top of REAPER.

There is no single right number. Spotify, YouTube, Tidal and Amazon Music play back at about −14 LUFS integrated, and Apple Music at about −16; louder tracks are turned down to match. Many genres are mastered louder than that on purpose. Watch the short-term reading in the loudest section, and keep true peaks below about −1 dBTP so the streaming encoders do not clip.

It depends on what you need. If you work in REAPER and want metering with nothing on the master, Analyse 1. If you need an integrated reading or true peak, in any DAW, a plugin meter does that: Youlean Loudness Meter has a free version, and REAPER has its own JS loudness meter.

No. They change only what you hear, on the monitoring path after everything else. They never touch your project or a render, and an orange bar shows while one is on.

On the audio thread it only copies samples into a buffer, without waiting or locking. Measuring and drawing happen on the interface thread, and stop when the panel is hidden.

Not yet. Analyse 1 launches on Linux first, and the macOS build, for macOS 26 Tahoe and later, follows. Sign up below and we will email you when each one is ready.

Any 64-bit x86 Linux with glibc 2.35 or later: Ubuntu 22.04, Debian 12, Fedora 36 or newer, or any current rolling distribution. Install it with ReaPack, or copy the .so into REAPER’s UserPlugins folder. Neither needs sudo.

No. Kerf is Linux first: we do not make Windows versions of our REAPER extensions or plugins, and we have no plans to. The Windows build of the 0.5.0 beta has been withdrawn and will not be updated or supported.

It works with any plugin REAPER hosts on the track, whatever its format: VST, VST3, CLAP, AU or JSFX. It drives the parameters REAPER exposes. If a plugin does not expose a parameter to REAPER, it cannot be mapped.

REAPER’s built-in parameter modulation is set up one parameter at a time, from each plugin’s own window, with an LFO, an audio signal or a link to another parameter. Modulators puts every plugin on the track in one docked panel, with envelopes, LFOs, drawn waves and followers you can see moving, and keeps it all in the project.

Not always. For one parameter on one plugin, REAPER’s own parameter modulation is free and works well. Modulators is for when you want several moving parts on a track, shapes you draw yourself, and everything visible in one place.

Multi-segment envelope generator: an envelope you draw yourself, point by point, rather than one picked from a list of shapes.

No. Modulation belongs to the track, not the panel. Close it, select another track or switch project tabs, and assigned modulators keep running.

The project opens as normal. The modulation settings stay in the file and come back if you reinstall.

Version 0.5.0 runs on 64-bit Linux, with REAPER 7.8 or later. Kerf is Linux first: the paid release launches on Linux first, with an installer, and a macOS build for macOS 26 Tahoe and later (universal, for Apple silicon and Intel) follows. There will be no Windows version.

£19 while Kerf Modulators is in beta, going up to £29 at version 1.0. It is a perpetual licence, with no subscription: for personal use, run it on every computer you own. If you downloaded the free 0.5.0 beta, you get a licence free.

Yes. When OL-2 is out you can download it without an account and use it for as long as you like. Until you add a licence, a reminder shows for 30 seconds each time it loads.

Your licence lives in your Kerf Audio account, with your invoice and downloads. Activate it online, or offline with a licence file for a computer that never goes online.

Yes. OL-2 launches as an early paid beta, at a lower price than the full release.

OL-2 is CLAP only for now, so it runs in any host that loads CLAP plugins, such as REAPER and Bitwig Studio. VST3 follows for all our plugins once their CLAP versions are fully tested and working without issues.

We test on Linux first. Once OL-2 works well there, it goes through dedicated QA and testing on macOS, so the Mac version follows the Linux one. Sign up below and we will email you when it is out.

Ableton Live 12 Suite beta, version 12.4.5 or later, on macOS or Windows. Extensions are not in Live Standard, Intro or Lite, or in the release version of Live yet.

If you own Live 12 Suite, join Ableton’s beta programme on Centercode. The beta installs as a separate copy of Live. More on the Ableton extensions page.

Warping, Simpler and Utility change how a clip plays back and leave the audio file as it was. Clip Tool writes a new sample with the edit baked in, trimmed, faded, stretched, pitched or folded to mono, so the result is a plain audio file you can see on the waveform, reuse and share.

Yes. Choose left, right, the mid sum or the side signal, audition each one, and Clip Tool writes a mono sample. Utility’s Mono switch does a similar job on the channel, but only while it plays.

No. Clip Tool always writes a new file and leaves the original untouched.

Clip Tool is open source under the MIT licence, and every line of it is on GitHub to read before you install it.

Sign in and open a support ticket from your account. Tell us the product and its version, your DAW and its version, and your operating system, and add screenshots if you can. Every reply shows in your account and comes to you by email. We aim to answer paid products within one working day, and free ones within three.

Use the contact page. You do not need an account, and a person reads every message, usually within two working days.

In your account, under Downloads, for every platform the product supports. They stay there, so you can download again whenever you need to.

For personal use, every computer you own. Devices in your account lists the computers a licence is active on. Studios, schools, labels and companies use our organisation licence instead; see licensing.

Yes. Under Devices in your account, authorise the computer with a licence file, then load that file in the product. It does not need to check in again.

Your licences live in your account, and the full key was in your purchase email. If you cannot find it, open a ticket and we will issue a new one.

Paddle, our reseller and merchant of record. They take payment, add the right VAT or sales tax for your country and send the invoice.

Yes, within 30 days of buying a plugin or piece of software. Open a ticket from your account, or email connect@kerfaudio.com. Our refund policy has the details.

Choose Forgotten your password? on the sign-in page and we will email you a link to set a new one.

Analyse 1 is coming soon. These are the steps for when it launches.

You need REAPER 7.8 or later, 64-bit, on 64-bit Linux with glibc 2.35 or later. A macOS build follows. There is no Windows version.

1. Install ReaPack if you do not have it.
2. In REAPER, open Extensions › ReaPack › Import repositories, paste https://raw.githubusercontent.com/Kerf-Audio/reapack/main/index.xml and click OK.
3. Open Extensions › ReaPack › Browse packages, search for Analyse 1, right-click it, choose Install, then Apply.
4. Restart REAPER, open the Extensions menu and choose Kerf Audio Analyse 1: Show/hide panel.

ReaPack keeps it up to date. Without ReaPack, download the file for your system from your account and copy it into REAPER’s UserPlugins folder. If you installed an earlier build, delete every reaper_analyser file from UserPlugins first, or REAPER may load two copies. More on installing REAPER extensions.

• Check you are running REAPER 7.8 or later, the 64-bit version.
• Check the extension file is in the UserPlugins folder of the REAPER you are starting. Options › Show REAPER resource path in explorer/finder opens it.
• Quit and restart REAPER: extensions only load at startup.
• On Linux, check your system has glibc 2.35 or later (Ubuntu 22.04, Debian 12, Fedora 36 or newer).

You need the Ableton Live 12 Suite beta, version 12.4.5 or later. Extensions are not in Live Standard, Intro or Lite, or in the release version of Live yet.

1. Download clip-tool.ablx from the Clip Tool page.
2. In the Live beta, open Settings › Extensions and drag the file onto the panel.
3. Restart Live if it does not show up straight away.
4. Right-click any audio clip and choose Clip Tool.

Not in the menu? It only appears on audio clips. Check Developer Mode is off in the Extensions settings, and try turning other extensions off for a moment. Bugs and ideas for Clip Tool go on GitHub, where everyone can see the fix.