Troubleshooting

A few sites skip real audio elements entirely, so Capo falls back to a reduced mode.

Capo normally finds audio by detecting elements once they play. Sites like QQ Music and Pandora decode straight to Web Audio with no element — Capo then falls back on the tab’s audible signal instead.

• Pitch and Volume stay live.
• Speed, the loop and the transport are greyed out.

Muting the tab doesn’t turn Capo off — it keeps working, you just can’t hear it.

Capo keeps detecting the track and applying your settings while muted. One nuance: when Capo’s own volume sits at 0, Capo still treats the tab as audible, so muting from inside Capo never makes your controls vanish.

Unmute and your pitch and speed are already waiting.

A few things genuinely differ per site — it isn’t one single cause.

• Some pages block every extension — you’ll see Capo can’t run on this page.
• Some have a strict security policy that blocks Capo’s WebAssembly engines, so it quietly drops to the lightweight one.
• Some hand their audio to another extension first — that’s Another extension has this tab.

Chrome blocks extensions in incognito until you allow each one.

1. Open Extensions → Manage extensions.
2. Select Details on Capo.
3. Turn on Allow in incognito.

That's the whole fix in almost every case. Capo adds no incognito rules of its own, so once Chrome lets it run there it behaves exactly as it does in a normal window — including your saved settings, which are shared between the two.

Another extension claimed this tab’s audio first — only one extension can control a given element.

A page can hand each audio element to one extension’s audio engine — first come, first served, and the browser refuses everyone after. The screen says so: Capo can’t change this tab’s pitch or volume while another audio extension controls it. Turn that extension off and reload.

• Volume boosters, equalizers, pitch shifters, and some media controllers all qualify.
• Whoever claims the audio element first keeps it — there’s no sharing.

Capo spots the refusal and shows Another extension has this tab rather than pretending your sliders still work.

Use the conflict screen’s two buttons — disabling alone isn’t enough, you also need to reload.

1. Tap Manage to open chrome://extensions in a new tab and switch the other extension off.
2. Tap Reload to reload the tab so Capo can retry its connection.

The reload really is required — once Capo has been refused, that verdict sticks for the rest of the page’s life.

Bisect it — disable other audio extensions one at a time and reload between each.

If the conflict screen is gone and your sliders bite, you’ve found the culprit.

The further you push pitch, the more the engine has to invent — that’s expected at extremes.

Capo’s dial reaches ±12 semitones by default; Pitch range in Settings widens it to ±36 or ±48, where artefacts get obvious fast.

1. Try a smaller shift first.
2. Raise Audio quality — Med is the strongest free tier; on Pro, High is the richest engine.

Sounds like a chipmunk? That’s pitch shifted well up — check the Pitch dial, not Speed.

• Check the Pitch dial and the Fine control.
• Use the pitch reset — it zeroes both in one click, since they’re one knob conceptually.

Speed alone won’t cause this: Capo keeps tempo and pitch apart, unless you’ve switched varispeed on, which couples them like tape.

That’s the browser’s own playback-rate stretching, not Capo’s engine — it gets rough at extremes.

• The slider runs 0.25×–3× by default.
• Speed range in Settings pushes the ceiling to 8×, which sounds rougher still.
• Some sites also fight the rate change, so Capo re-applies it.

Boosting past 100% adds real gain on an already-mastered mix, so loud peaks clip.

1. Back the boost off until it cleans up.
2. Raise your system volume instead of Capo’s.

Capo’s slider tops out at 300% by default; Volume range in Settings lifts the ceiling to 600% — plenty of rope.

Audio still too quiet even at 300%? That isn’t actually Capo’s limit — the ceiling goes higher in Settings.

• In Settings, raise Volume range from 300% to 600%.
• Past that, raise your device and OS volume instead of Capo’s.

Work down this list.

• Is Capo's main switch on, and is something actually playing?
• Greyed-out Loop card? The site plays through Web Audio with no media element (QQ Music, Pandora) — there's no timeline to loop against.
• Only one button greyed? The playhead's within a quarter-second of the other point. Move it and retap.

On a live stream, the loop still works — only the seek bar is missing.

Tap A and B and Capo wraps you back as usual. What's missing is the seek bar: a live stream has no fixed timeline, so Capo shows a static LIVE bar instead, with no scrubbing and no drag handles. Rewind and fast-forward keep working.

Use the A/B buttons and the steppers, and keep the loop inside the part the stream still holds.

That's count-in — it's switched on, and it's deliberate.

At the top of every repeat Capo pauses for a beat so you can reset your hands, then resumes on its own.

Tap the timer button in the loop pill to turn count-in off — the loop then runs straight through.

The pause length lives in Settings: 1s, 2s, 3s or 5s.

Capo's play, rewind and seek buttons drive the element it detected on the page — two things can break that.

• On Web Audio sites with no media element (QQ Music, Pandora) the whole player strip is greyed out — use the site's own button.
• Otherwise the browser may be refusing to start playback on its own — press play on the page once, and Capo takes it from there.

Those buttons move the playhead on the element Capo detected.

• On a live stream they still work, but only within the stretch the stream keeps buffered.

You can change the jump size (the skip interval) in Settings.

Where Capo's bar can't help, the site's own scrub bar still works.

They're two separate sets of shortcuts.

• Popup: bare keys — A, B, L, C.
• Page: Alt/Option combos — Alt+A, Alt+B… with their own on/off switch in Settings.
• Page shortcuts stand down while you're typing in a search box or comment field.
• Play/seek ship unbound on the page, because sites own those keys.

Rarely an issue — Capo listens before the page does.

Page shortcuts default to Alt/Option combos precisely so they don't collide with what sites claim. The one real gap is a player tucked inside an embed while the outer page holds focus — click the player once and the keys land.

Rebound a shortcut to a bare key? That's when a site can win.

Saved tracks survive a browser restart — so something blocked the save.

• Check Auto-save is on: Settings → Data & privacy
• Confirm something actually changed — a track back at default values isn't stored
• Check whether Capo could identify the track: does it show up in History?
• Remember History holds 500 tracks; the oldest fall off

That is Capo doing its job — settings belong to the track, not the tab.

• When a new song starts, Capo loads that song's saved settings
• If it has never seen the song before, it loads normal settings instead
• The tweak you made to the last song does not follow you into the next one
• Nudge the new track's pitch or speed and it gets saved too, ready for next time

Spotify and SoundCloud keep one address across a whole queue while the music changes underneath. When the next song starts, Capo spots the new track and swaps in whatever’s saved for it, or falls back to defaults.

Not a per-site rule — Capo can't tell those two songs apart.

Every track is meant to get its own entry.

• Tracks are identified from the info a site publishes
• Where a site publishes none, Capo falls back to the page address
• Two songs sharing one address share one entry
• Sites like YouTube, Spotify Web and SoundCloud report each track properly, so they stay separate

Different sites give Capo different amounts of information to work with.

Do report the site to us and we will take a look.

Work through this checklist before reaching out.

1. Get the media playing before you open Capo
2. Check Auto-save is on — Settings → Data & privacy
3. Move a control, then look for the track in History
4. Refresh the page and try once more
5. Try another site to narrow it down

Still stuck? Hit Send feedback in Settings and tell us which site.

Its on/off switch is off — flip the switch on the clip row.

A dimmed clip row means the clip is disabled: its play button and drawer are inert until you turn the switch back on. If a clip is enabled but still won’t play, check it isn’t shorter than the quarter-second minimum and that its start and end still sit inside the track — open the drawer and retype the times if they drifted.

There’s already a marker within the minimum spacing at the playhead.

Capo keeps markers a small gap apart so two can’t stack on the same instant, and the + Add-marker button says so rather than dropping a duplicate. Move the playhead a moment earlier or later and add it there, or just rename/redrag the marker that’s already sitting on that spot.

Work down this list.

No loop yet? The trainer ramps a loop, so set an A–B loop first — the trend-up button lives on the loop card. Start equals Target? There’s nothing to climb; lower Start or raise Target. Seems stuck? It only steps up after Every repeats (two by default), so give it a couple of passes at each speed. Paused? A live session can be paused — the speed holds where it is until you resume. Ending the session returns playback to your normal speed.

Two things to check: the site’s audio, and whether the bands are actually doing anything.

A few sites play through Web Audio with no real media element behind them (some radio and game-music players). The equalizer still works there — it sits in the same audio path as Volume — even though Speed and the loop drop out on those pages. So the usual fix is simpler: make sure the bands aren’t all sitting flat at 0 dB and that you’re listening to a range a band actually covers — a small boost on one band is easy to miss on a busy mix.

Sign-in opens a capotune.com tab — let it finish, then come back to Capo.

When you tap Sign in, Capo opens a tab to sign you in and the popup closes on focus — that’s expected, not a failure. Once the tab confirms, reopen Capo and your account shows. If it didn’t take, tap Sign in again, and make sure you’re signing in with the same account you bought Pro with. A session can also expire after a long time — just sign in again to refresh it.

Give your machine less to do: switch Audio quality down, or turn on Low latency mode.

High audio quality sounds richest but is the heaviest — on a slower machine, dropping it to Med in Settings often clears stutter. Low latency mode (under Audio & playback, on the High tier) trims the delay, though it’s off while formant shifting is active. Running several heavy effects at once — a big formant shift plus reverb plus the vocal reducer — is the most demanding combination, so ease one off if the audio breaks up.