Capo
So funktioniert es

Why Capo ships three time-stretch engines instead of one

Elyra-Labs-Team3 Min. Lesezeit
Die kurze Antwort

No time-stretch algorithm is best at everything. Lighter algorithms add less latency and smear sooner at low speeds; heavier ones hold together at a quarter speed and cost CPU. Capo exposes the choice as a setting instead of picking one compromise for every user.

  1. Low: SoundTouch. Lightest, lowest latency.
  2. Medium: Signalsmith. The default.
  3. High: Rubber Band. Required for the vocal reducer.

Time-stretching cuts audio into short grains and re-schedules them, so speed changes while pitch stays fixed. The mechanism is explained here, with a demo.

How cleanly that works depends on where the algorithm cuts and how it joins. Better decisions need more of the signal in hand, which costs latency and processing.

This article covers what each engine trades away, and which setting to use.

Key takeaways

  • Leave the setting on Medium for general use.
  • High is Pro. Low and Med are free; raise to High below about 0.5×, or for the vocal reducer.
  • Changing the engine applies live, mid-playback — no reload needed.
  • Above 0.8× speed the three engines are very hard to tell apart.

SoundTouch, Signalsmith and Rubber Band compared

SettingEngineStrengthCost
LowSoundTouchVery light, minimal added latencySmears earliest below 0.5×
MediumSignalsmithBalanced quality and costThe default
HighRubber BandHolds together at extreme ratiosHeaviest on CPU
Settings · every row
Audio & playback in Settings: Audio quality, Skip interval and Count-in duration
The Audio quality row, with High marked Pro.
1Appearance
1aToolbar badge colour1bLanguage1cVisualizer
2Audio & playback
2aAudio quality2bSkip interval2cCount-in duration

Why the heaviest engine is not the default

Three reasons, in order of how often they matter.

Latency. A heavier engine holds more audio before emitting any. That is acceptable for listening and wrong for playing along.

CPU and battery. Capo runs in a tab beside everything else open on the machine. An inaudibly better engine that runs hotter is a poor default.

Diminishing returns. Above roughly 0.8× the engines are very hard to distinguish. At 0.95× the heaviest one buys nothing.

Why the lightest engine is not the default either

Formant correction is implemented only on Signalsmith and Rubber Band. On the lightest engine the control is disabled.

Shipping only the lightest engine would silently break transposing a vocal, which is one of the most common uses.

What happens when you change it

The change applies live. Capo tears down the old engine’s worklets and re-attaches the new one to every running audio stream, mid-playback — no reload, no lost position.

That makes the setting cheap to test: play the passage you care about, switch tiers, and listen. The difference — or its absence — is audible within a bar.

A note on the name

“Audio quality” is imprecise. At 0.95× speed, Low is not lower quality than High; the output is effectively identical.

The question the setting really asks is how far down you intend to go. Renaming it means 52 translations and a support page, so it remains open.

Which time-stretch engine should you use?

Medium suits almost all material and is free. High is part of Capo Pro; it earns its place below 0.5× and is required for the vocal reducer. Changing tier applies live, so comparing them costs nothing.

This article deliberately contains no benchmark. Which engine sounds best across a given passage depends on the material, and percussive content punishes different weaknesses than sustained content. Test on the track you are working on.

Fragen

Which audio quality setting should I use?
Medium for almost everything, and it is free. High is a Capo Pro tier, worth it below about 0.5× speed, and the vocal reducer requires it.
Do I have to reload the tab after changing it?
No. The change applies live: Capo tears down the old engine and re-attaches to the running audio, so you can compare tiers mid-song.
Why is Formant greyed out on Low?
Formant correction is implemented only on the Signalsmith and Rubber Band engines.

Weiterlesen

Setz einen Capo auf alles, was du hörst.

Zu Chrome hinzufügen – gratisAuch für Firefox & Edge · v2.7.6 · kein Konto