Jack Righteous Updates: Neuigkeiten, Werkzeuge & Ankündigungen
Why I Used SoundCloud to Test the Unison Project
How Jack Righteous used SoundCloud as a testing ground for the Unison project—without mistaking plays for proof—and a practical workflow for feedback, insights, private sharing and release decisions.
AI music project testing · Updated July 2026
Before the Unison project became a finished album, I used SoundCloud as a public testing ground. The goal was not to treat every play as proof of success. It was to hear the songs outside Suno, organize them as a project, observe which tracks held attention and learn what still needed work before a wider release.
The correction this article needed
The original version made unsupported claims about guaranteed plays and the percentage of tracks flagged for copyright review. Those numbers were not a reliable basis for creator education. SoundCloud is more useful here as a listening, playlist, feedback and insights environment—not as a promise of automatic reach.
Why move the music outside the generation platform?
Listening inside a creation tool can distort judgment. The creator remembers the prompt, the discarded versions and the effort that produced the result. A listener encounters only the song.
Moving the Unison candidates to SoundCloud created several useful tests:
- Could the tracks stand beside one another as a playlist?
- Did the titles and artwork help a new listener understand the project?
- Which songs earned repeat attention rather than only an initial click?
- Where did listeners comment or stop engaging?
- Did the project feel like one album or a folder of unrelated experiments?
Hear the original Unison project playlist
What SoundCloud could show
SoundCloud’s creator insights include plays, likes, comments, reposts and downloads when enabled. Some paid creator plans provide additional information such as top listeners, locations and external sources. Comments can also appear at specific moments on the waveform, which makes them potentially more useful than a general “sounds good” response.
| Signal | Possible interpretation | What it cannot prove alone |
|---|---|---|
| Plays | The track was started | That the listener finished, remembered or valued it |
| Likes | A listener chose to save the track | That it fits the final album |
| Comments | A listener reacted strongly enough to respond | That the comment represents the intended audience |
| Reposts | Someone believed the track was worth sharing | That sharing created a lasting fan relationship |
| Repeat listeners | Some listeners returned to the song | Why they returned or what should be changed |
| Source and location data | Where attention may be coming from | Whether that audience will follow the project elsewhere |
My five-stage testing workflow
1 · Export a defined candidate
Do not upload every generation
The track should already have a reason to be tested: a promising hook, a possible album role or a question that outside listening can help answer.
2 · Package it like a listener will encounter it
Use a clear title, artwork and description
Weak presentation can create confusion that has nothing to do with the music. A test should reveal the song’s response—not a preventable metadata problem.
3 · Ask one useful question
Specific feedback produces actionable information
Instead of “Do you like it?”, ask whether the chorus arrives soon enough, which lyric is remembered, whether the vocal feels credible or where attention drops.
4 · Compare behaviour over time
Do not judge from the first burst
Initial plays may reflect the people who received the link. Repeat listening, saves, specific comments and organic sharing can be more informative than a one-day total.
5 · Record the decision
A test is incomplete until it changes the project
Mark the track as keep, revise, reposition or remove. Save the reason so later decisions are based on evidence rather than memory.
Public testing versus private testing
Use private sharing when
- the song contains sensitive personal material;
- rights or collaborators are still being confirmed;
- you want feedback from a small defined group;
- the track is not ready to become part of the public catalogue.
Use public testing when
- the work is rights-cleared for public sharing;
- presentation and metadata are ready;
- you need behaviour from people outside your immediate circle;
- you accept that the version may remain discoverable or archived.
What I learned from the Unison playlist
The playlist made the project’s ambition visible: several genres, a Canadian cause and a message of creative access. It also exposed the risk of breadth without enough connective tissue. Individual tracks could work while the sequence still felt inconsistent.
The most useful feedback therefore was not simply which track had the highest number. I needed to know:
- which songs listeners remembered without seeing the title;
- which tracks represented the album’s central promise;
- where genre changes felt refreshing and where they felt random;
- which songs needed lyric or structural repair;
- which strong standalone tracks weakened the album sequence.
A testing scorecard
- Concept fit: Does the track belong in this project?
- First-minute clarity: Can a listener understand the direction quickly?
- Hook memory: What remains after the song stops?
- Vocal credibility: Does the performance support the message?
- Structural movement: Does the song develop rather than repeat at one intensity?
- Repeat value: Is there a reason to return?
- Sequence role: What function does it serve beside the other tracks?
- Rights readiness: Are the source, voice and plan permissions documented?
Current SoundCloud references
- SoundCloud Creator Insights
- Sharing public and private tracks or playlists
- SoundCloud comments and waveform feedback
Test with a decision in mind
Move from listener signals to a stronger project
The AI Creator Roadmap helps identify whether the next problem is sound, voice or brand. Ask Jack when you have feedback and statistics but still cannot decide what to change.
Platform features and plan names can change. Check SoundCloud’s current documentation before choosing a testing or release workflow.
Stay connected to what changes
Do not lose the next useful creator update.
The Righteous Beat connects consequential platform changes, practical tools and new free resources.
Discussion