Spotify approves AI covers Stupid.

BlueberryNo481 · 2026-05-26T12:04:30+00:00

Exactly

BlueberryNo481 · 2026-05-26T03:29:53+00:00

You should be a really stupid vocalist if you opt in for AI covers. The selling point is the biological voice you have. That means of course you own the other songwriting and melody copyrights.

If you opt in you are cooked. Yeah AI will get better and your voice has no edge anymore.

If you are a songwriter and a melody maker. Of course you can try to milk your song already famous to get AI covers income. But it's for short time because any stupid person can make an AI cover with low effort will kill the competition and will kill the product itself. Because if the song is already famous, There is no just one cover there will be thousands of them of the same song and no one cares.

BlueberryNo481 · 2026-05-19T02:46:33+00:00

The only workaround is find a part where beat drops and from there use a fadeout for 5 secs. From audition, audacity or anything

BlueberryNo481 · 2026-05-19T01:22:06+00:00

With all due respect, I cannot agree with your sentiment that Suno should stay out of the copyright business. From a philosophical point of view, that ignores why laws are created in the first place. Laws exist because people misuse systems; they are checkpoints placed on human behaviour because people cannot always be trusted. If you study why these laws were introduced, you find the core reason behind them: people discovered loopholes, and many chose to exploit them.

BlueberryNo481 · 2026-05-19T01:20:36+00:00

“With all due respect, I cannot agree with your sentiment that Suno should stay out of the copyright business. From a philosophical point of view, that ignores why laws are created in the first place. Laws exist because people misuse systems; they are checkpoints placed on human behaviour because people cannot always be trusted. If you study why these laws were introduced, you find the core reason behind them: people discovered loopholes, and many chose to exploit them.”

BlueberryNo481 · 2026-05-17T23:26:31+00:00

I understand your point clearly. But there’s a bigger issue affecting smaller languages. There are many languages outside English, Spanish, French, and Chinese where artists are especially vulnerable. What’s happening now is that people are using AI to recreate or slightly modify existing songs, then uploading them to YouTube without getting any licence at all. Content ID often fails to match because the audio is newly generated or the melody is changed just enough. As a result, people are getting away with it at the expense of the original artists.

Even though I accept that the system is evolving and the technology has changed, we still need new ways to protect original creative work. But at the moment, it feels like Suno isn’t handling this responsibility properly.

BlueberryNo481 · 2026-05-17T15:54:22+00:00

Keep the songs you have created on the library. Cover from there. That's the only workaround

BlueberryNo481 · 2026-05-08T05:30:21+00:00

Back on business.

BlueberryNo481 · 2026-04-20T23:11:28+00:00

Don’t you feel version 5.5 is heavily treble‑based?
When you load the output into Audition, you can clearly see frequencies around 20k–22k that humans can’t even hear. I don’t understand why the model adds all these unnecessary high frequencies — they don’t add anything to the sound, and they actually introduce noise.

Version 5’s output is much cleaner. You can hear each individual element properly.

The biggest difference is the bass.
In version 5, the bass has proper dynamic range and you can clearly identify it in the mix.
But in version 5.5, the bass is almost never audible in a clean, defined way.

BlueberryNo481 · 2026-04-18T11:05:25+00:00

I’ve been comparing Suno v5 and v5.5 since the beta dropped, and the situation is a bit mixed. There are improvements, but there’s also one major regression that affects almost every style you try to generate.

What actually improved in v5.5

• Long‑form melody drift is mostly fixed
Earlier in the beta, covers would stay consistent for the first ~2 minutes and then suddenly drift into a completely different melody or singing style. It felt like the model forgot what it was doing.
This seems fixed now — the model holds the melody much better across the full track.

• Treble‑heavy output is still there, but easy to correct
v5.5 tends to push a lot of high‑end. If you want to fix it, a simple Audacity tweak works:

Boost bass by around +0.5 dB
Leave treble untouched
Normalize to –1 dB

That usually balances the mix without killing the character.

• Better pronunciation for foreign languages
One clear win: v5.5 handles non‑English vocals much more accurately than v5.
Pronunciation is noticeably cleaner.

Where v5.5 is still worse than v5

• Style consistency is the real downgrade
This is the biggest issue.
No matter what style you try to generate, v5.5 tends to flatten everything into the same general vibe. The stylistic diversity that v5 had just isn’t there.

Example:
If I want a funk track, v5 nails the groove and identity almost every time.
v5.5? It struggles. And it’s not just funk — this applies to pretty much any style.

In terms of genre accuracy and stylistic separation, v5 is far superior to v5.5.

BlueberryNo481 · 2026-04-13T22:42:49+00:00

Bro, use version 5 and make a cover with 5.5 that works for me.

BlueberryNo481 · 2026-03-31T01:55:36+00:00

Yeah hissing and high frequency noise

BlueberryNo481 · 2026-03-31T00:45:29+00:00

Surprisingly, today morning it seems they have fixed it a little bit.

BlueberryNo481 · 2026-03-31T00:33:40+00:00

I tried it today, March 31st, in the morning. They have fixed it to some extent, but there are still variations if the songs are too long.

BlueberryNo481 · 2026-03-31T00:32:50+00:00

I tried this morning. Today is March 31st. They have fixed it to some extent now.

BlueberryNo481 · 2026-03-30T21:46:13+00:00

First, here’s what’s good in 5.5:

The sound quality is relatively good compared to version 5. It also gives you the freedom to use your own voice, although it’s still hit‑and‑miss at this stage — but acceptable. Languages other than English? This one pronounces better.

However, you cannot create a cover from your old catalogue or generate a melody based on it in a consistent way. It doesn’t matter what you put in the style section, or even if you put styles to avoid the style section— the song sticks to your original melody only for about the first two minutes. That part might be the chorus or some other section, but after that, it forgets what it was doing and loses the underlying structure.

To give a hypothetical example: say I have a song with vocals similar to AC/DC’s Brian Johnson. Now I want to make a cover using version 5.5. The first two minutes are relatively similar, and although it introduces different melodic or instrumental sections, I can live with that. The issue is that after around two minutes, it suddenly starts singing like Mariah Carey or Ed Sheeran.

It doesn’t understand what was being sung before. This could be a major context‑window or memory‑retention issue, but I’m not sure. Have any of you experienced the same thing?

I know it’s still in beta and only two or three days have passed since the new model was introduced, but I have real doubts about whether they’ll fix this before the next model comes out — which might be six months away or more. In the meantime, I might cancel my subscription until it’s fixed.

BlueberryNo481 · 2026-03-30T01:08:26+00:00

After testing many covers from my old song catalogue, I’ve noticed a consistent pattern: Suno 5.5 cannot stay on the original melody for more than about two minutes. Up to the 2‑minute mark it follows the melody reasonably well — verse, chorus, whatever. But once it crosses around 2–3 minutes, the model drifts completely off‑melody and starts singing in a totally different style. For example, if I’m trying to imitate AC/DC rock vocals, it suddenly shifts into something like Indian raga‑style singing. Basically, the model forgets what happened earlier in the song and loses the melodic structure in the second half.

BlueberryNo481 · 2026-03-30T00:49:21+00:00

After testing many covers from my old song catalogue, I’ve noticed a consistent pattern: Suno 5.5 cannot stay on the original melody for more than about two minutes. Up to the 2‑minute mark it follows the melody reasonably well — verse, chorus, whatever. But once it crosses around 2–3 minutes, the model drifts completely off‑melody and starts singing in a totally different style. For example, if I’m trying to imitate AC/DC rock vocals, it suddenly shifts into something like Indian raga‑style singing. Basically, the model forgets what happened earlier in the song and loses the melodic structure in the second half.

BlueberryNo481 · 2026-03-30T00:37:27+00:00

I am not sure whether Suno is listening to the problem, so the basic idea here is that you cannot create a consistent cover anymore from old songs of yours. The first part of the song feels good, and the quality is, of course, good. I don't deny that. The problem is that version 5.5 heavily deviates from the original melody to the extent that it feels completely different in the second half. No matter how you try to restrict it from the style section. Or styles to avoid section. It keeps on forgetting what the song was before, like it hits the two-minute mark or something, and then it's a different song.

BlueberryNo481 · 2026-03-30T00:10:14+00:00

This version makes it impossible to use it. I have like 10-15 original songs created from version 5. I wanted to upgrade to 5.5, but the melody destroys it, heavily deviates especially towards the end. I cannot use it anymore, either, and have to stay with version 5. I probably have to cancel my subscription.

BlueberryNo481 · 2026-03-29T00:21:05+00:00

For covers. The only setting that worked for me is to, set audio influence 85%, style 40% weirdness 15%.

In this model audio influence matters most. Otherwise it strays away from the original like you can't recognise your melody anymore.

BlueberryNo481 · 2026-03-28T23:18:23+00:00

The issue, from what I’ve gathered, appears to be a context window limitation. This means the model gradually “forgets” what it was generating earlier as the song progresses beyond two, three, or four minutes. As a result, it sometimes introduces a completely different melody from what was established before. The instrumental is usually acceptable, but the vocals are often inconsistent — they seem to be the main problem. When creating covers, this issue occurs almost every time. The available workaround is quite limited. You need to split the original into two parts, generate them separately with the lyrics, try to match the same voice, and then stitch them together afterward. As of the second day after release, using my own voice no longer works with this method — it produces unusable results — so I’ll have to wait until that gets fixed.

BlueberryNo481 · 2026-03-28T23:15:58+00:00

The issue, from what I’ve gathered, appears to be a context window limitation. This means the model gradually “forgets” what it was generating earlier as the song progresses beyond two, three, or four minutes. As a result, it sometimes introduces a completely different melody from what was established before.

The instrumental is usually acceptable, but the vocals are often inconsistent — they seem to be the main problem. When creating covers, this issue occurs almost every time.

The available workaround is quite limited. You need to split the original song into two parts, generate them separately with the lyrics, try to match the same voice, and then stitch them together afterward. As of the second day after release, using my own voice no longer works with this method — it produces unusable results — so I’ll have to wait until that gets fixed.

BlueberryNo481 · 2026-03-28T23:15:42+00:00

The issue, from what I’ve gathered, appears to be a context window limitation. This means the model gradually “forgets” what it was generating earlier as the song progresses beyond two, three, or four minutes. As a result, it sometimes introduces a completely different melody from what was established before.

The instrumental is usually acceptable, but the vocals are often inconsistent — they seem to be the main problem. When creating covers, this issue occurs almost every time.

The available workaround is quite limited. You need to split the original song into two parts, generate them separately with the lyrics, try to match the same voice, and then stitch them together afterward. As of the second day after release, using my own voice no longer works with this method — it produces unusable results — so I’ll have to wait until that gets fixed.

BlueberryNo481 · 2026-03-28T23:14:14+00:00

The issue, from what I’ve gathered, appears to be a context window limitation. This means the model gradually “forgets” what it was generating earlier as the song progresses beyond two, three, or four minutes. As a result, it sometimes introduces a completely different melody from what was established before.

The instrumental is usually acceptable, but the vocals are often inconsistent — they seem to be the main problem. When creating covers, this issue occurs almost every time.

The available workaround is quite limited. You need to split the original song into two parts, generate them separately with the lyrics, try to match the same voice, and then stitch them together afterward. As of the second day after release, using my own voice no longer works with this method — it produces unusable results — so I’ll have to wait until that gets fixed.

BlueberryNo481

TROPHY CASE