Suno Personalization & Creator Records: Voices, Custom Models, My Taste
Gary WhittakerSuno Personalization Is Support—Not a Workflow Stage
Voices, Custom Models, Personas, Lyricist, My Taste and model behaviour can all shape what you hear or what Suno suggests. The creator still owns the job: define the direction, judge the evidence, choose what survives and document what materially shaped the track.
The old “System Intelligence Layer” is no longer a separate stage
Earlier Jack Righteous v5.5 training grouped My Taste under a System Intelligence Layer. That was useful for distinguishing personalization from direct editing, but it can create the wrong mental model if it looks like another step after Creation or Control.
For the current Find Your Sound architecture, treat personalization as supporting intelligence. It can inform several stages of the work, but it never owns one.
What supporting intelligence actually does
Supporting intelligence is any platform behaviour that helps you notice, translate, explore or reuse patterns without deciding the project for you. A recommendation may reveal useful language. A Persona may carry traits from a source song. A Custom Model may make a catalogue-level pattern easier to reuse. A model variant may behave differently under the same brief.
The important distinction is between what the system offers and what the creator decides belongs.
| Support | What it can contribute | What it cannot decide |
|---|---|---|
| My Taste / style augmentation | Suggestions influenced by account activity or preferences where the feature is available | The song's purpose, audience, emotional job or final style direction |
| Style Persona | Continuity from one Suno source song | Whether that identity is right for this project or whether the result is good enough |
| Voice | An authorized vocal identity where supported | Performance quality, consent sufficiency, release readiness or creative fit |
| Lyricist | Reusable writing tendencies | The message, meaning or final lyric choices |
| Custom Model | Patterns derived from qualifying source material; Suno says Custom Models move forward with V6 | Whether the source set is coherent, rights-safe or creatively appropriate |
| V6 / V6 Wild / V6 Mini | Different generation behaviours for controlled execution, exploration or fast testing | A universal quality ranking or automatic winner |
Listen for what the support changed
Do not ask only, “Did I like the result?” Compare the assisted result with the project brief and, where practical, with a base version. Listen for the actual relationship that changed.
Project fit
Did the suggestion move the song closer to its intended emotional, stylistic or audience job?
Identity
Did recognizable vocal, lyrical, rhythmic, harmonic or production traits survive in a useful way?
Drift
Did the support introduce habits, genres, performance choices or textures that are attractive but wrong for this project?
Discovery
Did the system introduce a surprise that is better than the original assumption and worth protecting?
Personal does not automatically mean relevant
Personalization can reflect what you often make or listen to. That does not mean the same choice belongs in every song. A creator develops judgment by being able to reject a good suggestion that is wrong for the current brief.
Likewise, a more expensive or more advanced model is not automatically the better choice. Use the behaviour that serves the job, then compare the evidence. A fast Mini generation can expose the right direction. Wild can reveal a useful surprise. V6 can execute a clearer direction. Any of them can produce the version worth keeping.
Run the base-versus-assisted check
- Bring forward the current Creative Direction Brief or project direction.
- Write your own concise direction before using personalization or identity assistance.
- Activate only the support feature needed for the current question.
- Keep other major variables as stable as practical.
- Compare the base and assisted results against the same job.
- Accept only the contribution that improves project fit or creates a clearly valuable discovery.
- Reject attractive additions that weaken the brief, identity, structure or performance.
- Record the result before adding another support layer.
Personalization Evidence Note
No new worksheet is required. Add this evidence to the existing creator record when personalization materially affects serious work.
Project / brief · your direction before assistance · stage of the workflow
Feature, model or identity tool · version/date · source material where relevant
Suggestion, augmentation or audible behaviour introduced by the support
What you accepted · what you rejected · why each decision serves the brief
Observable result, comparison and any protected discovery
What this result suggests for this project and whether another comparable test is needed
Personalization increases the need for source awareness
A support feature does not clear rights by itself. When the work matters, record source songs, voice ownership and consent, uploaded catalogue material, collaborators, third-party material, prompts, lyrics, model/version, edits, exports and intended use as relevant.
Commercial-use permission, copyright eligibility, voice/likeness rights, source clearance, distributor acceptance and release readiness remain separate questions.
Do not stop the workflow here
Supporting intelligence is not a destination. Once you have accepted or rejected its contribution, return to the actual job you were doing: DEFINE, REFERENCE, GENERATE, COMPARE, DIAGNOSE, DEVELOP, PRODUCE, FINISH, DOCUMENT, PREPARE, DISTRIBUTE, VERIFY or IMPROVE.
During IMPROVE, platform behaviour can become evidence in the debrief. Keep it separate from creative evidence and process evidence, then carry only a scoped, evidence-backed rule into the next DEFINE brief.
Use the detailed identity guides only when that feature is the blocker
This page owns the supporting-intelligence principle. The feature guides own implementation details.
Completion gate
This lesson is complete when you can explain the difference between creator direction and platform assistance; identify what the support changed; reject an attractive but off-brief suggestion; accept and protect a useful discovery; document feature/model/version and evidence when it matters; and continue to the correct workflow stage without treating personalization as a stage of its own.
This article preserves the durable lesson while Suno features continue to change. For current V6 model behaviour and Custom Model status, use Suno's current V6 documentation. My Taste was publicly documented in the v5.5 generation of Suno help; availability, placement and behaviour should be verified in the current account before relying on older screenshots or instructions.
Suno: Introducing V6 · Suno: V6 FAQ · Suno: V6 model distinctions · Historical Suno: My Taste
