AI cover songs, done honestly.

In Octa, a cover is a style transfer of a performance you already have. You give the engine an audio source — a track from your library, or a file from your computer — and describe the version you want instead. It keeps the shape of the song and rebuilds everything else: instruments, tempo feel, production, and the voice singing it.

That makes it useful for things a text prompt cannot do. A demo you hummed into your phone becomes a produced record. A track you generated last week as a ballad comes back as drill. The same melody gets a male and a female version to compare.

Your recording, reimagined — not someone else’s record, copied.

Fair game:

• Anything you made in Octa — every track in your library.
• Your own recordings: voice memos, hummed melodies, a guitar take, a demo you own.
• Audio you hold the rights to, including work you commissioned.

Blocked by design:

• Commercially released recordings, whether you uploaded the file or linked it.
• Anything that fingerprints as a match against the commercial catalogue.

The reason is simple: a track Octa hands you should be safe to publish. Covers of protected works are blocked so that everything reaching your library is yours to use.

• Open Cover modeIn the web studio or the Android app, switch the console from Generate to Cover.
• Choose your sourcePick a track from your library, or upload an audio file straight from your computer.
• Describe the new versionThis is a normal prompt: “turn it into slow neo-soul with Rhodes and brushed drums”. Naming the genre and one instrument is usually enough.
• Choose the voiceMale, female, or instrumental. Leave the lyrics box empty to keep the original words, or paste new ones to rewrite them.
• GenerateThe source is checked, then rebuilt. It lands in your library on every device at once, usually in about a minute.

• Format: MP3 or WAV.
• Length: at least ten seconds. Very short clips do not give the engine enough to work with.
• Size: under 20 MB.
• Not DRM-protected. Files bought from a store with copy protection cannot be read.

Clean sources produce better covers. A phone recording is fine — background noise and room echo are not, because the engine treats them as part of the performance.

If your source matches a released recording, the run stops and the studio tells you exactly why — with the reason, what happened to your credit, and what to try instead. Three things are always true when that screen appears:

• Nothing was generated. The check happens before the first note, so there is no half-finished track anywhere.
• Your credit is returned automatically. No ticket, no email, no waiting — the balance updates within seconds.
• Nothing is saved to your library. Blocked runs leave no broken entries behind.

The same screen appears for the other reasons a run can stop — a source file that cannot be read, a prompt the content filter refuses, or an engine timeout — and the credit comes back in every one of those cases too.