What songcode can’t do
No vocals, no live band, no mastering chain. The limits, stated up front, and what to use when you hit one.
Every tool has a shape. Most product pages describe only the flattering side of it. This is the other side of songcode, so you can decide in two minutes whether it is the wrong tool for you.
It does not sing
No vocals, no lyrics, no spoken word. The engine plays synthesizers and short instrument samples, and nothing in it can produce a voice.
If you need a singer, Suno and Eleven Music both generate vocals.
It does not do acoustic realism
The sound library has a sampled piano, a recorded drum kit, mallets, and plucked-string models for nylon and steel guitar. They sound like what they are: single notes and single hits, played by a sequencer. Fine in a track built around synths. Not a string quartet.
A guitarist’s phrasing, a drummer’s feel or a horn section is outside what songcode can make.
Its 51 genres all come out of the same box
The list runs from techno, house and trance through drum & bass, trap and boom bap to bossa, jazz and neo soul. Most of it is electronic. The rest is those styles as a synth and a drum machine would play them.
No rock, no country, no orchestral scores, no pop ballads. You can type anything into the prompt, and the model will pull it toward what the engine does well.
It does not master
A songcode track is the mix the code describes. The only thing on the master is a limiter with its ceiling at -1 dBFS, there to stop clipping. No EQ, no multiband compression, no loudness targeting. The result is clean and it has punch, and it will sit quieter and rawer than a commercial release next to it in a playlist. If you want a finished master, export a WAV and finish it the way you would finish anything else.
It does not take audio in
You cannot upload a song to extend it, split a recording into stems, or ask for something that sounds like a file you have. The stems in songcode are the ones the code names. songcode has no model that listens. Its input is text and its output is text.
For the same reason it has no voice cloning. There are no voices.
It needs your own API key
Today songcode runs on a key from Anthropic or OpenAI that you supply. That means an account with one of them and a few minutes of setup before your first track. The key stays in your browser and we never store it, but it is still a step most music apps do not ask of you.
The model gets things wrong
A language model writes each track, and language models make mistakes. Every new track is compiled and tested in your browser before it plays, and the model gets one pass to repair what the test finds: a method that does not exist, a sound that does not exist, a stem that never plays. When that pass runs, it is a second model call on your key.
The test catches broken. It cannot catch boring. You will still get loops that are correct and dull, and now and then a track the repair pass could not fully fix.
The difference from a sealed generator is that you can see the problem. The stem is on screen, by name. Fix it, regenerate that one stem, or generate again.
It runs on your machine
Synthesis happens live in your browser, so a dense track leans on your CPU. A recent laptop or phone handles it. An old one may crackle.
When to use something else
- A complete song with a singer: Suno.
- Vocals from a model with label and publisher deals behind it: Eleven Music.
- Instrumental audio or sound effects from a model with a published training set: Stable Audio.
The AI music map compares them in more detail.
What is left
Electronic music, written as a short program you can read and change, generated in the time it takes a model to type it, with no audio model anywhere in the chain. If that is the thing you want, very little else gives it to you.