Skip links

Feedback on a demo, a mix or a version

Get useful feedback on your music.

Ask the right question, have a specific version listened to, and turn your guests' comments into next steps.

TuneLockr gathers feedback from the people you invite. Sharing does not provide an audience or professionals tasked with listening to your track.

Illustration of an audio file, an orange sound wave and a document
The same version for all feedback from a listen.

Ask for advice that helps you decide.

"What do you think?" lets your counterpart choose on their own what to listen to. Give them context, then one or two useful questions at the track's stage.

For a demo

What idea stays after the first listen? Does the chorus arrive at the right time? Which part do you feel like listening to again? Ask for a reaction on the structure or intent before discussing each detail of the mix.

For a mix

Is the voice still understandable in the chorus? Which part seems unbalanced? Specify what you have changed since the previous version.

For a final listen

Is there a specific defect left to correct before delivery? Indicate the expected decision and the deadline, rather than opening a new discussion on the entire artistic direction.

A four-step method

The right file. The right question. The follow-up.

  1. Name the version

    Use a clear title and number. Check the file before creating the link so everyone listens to the same submission.

  2. Enable feedback

    Choose the comments and download useful for the exchange. Specify in your message what you want to understand.

  3. Locate the comments

    On the audio, feedback can target a moment or a passage. The recipient explains what they hear and the change they suggest.

  4. Decide what's next

    Group the feedback, choose the corrections to test and name the new version. You retain the creative decision.

You can prepare the file before registration. It stays in this browser until you log in. To create the link, log in with a verified email address, then confirm the sending; your recipients can open it without an account.

A precise comment facilitates a successful exchange.

Indicate where you hear something, what you observe, and the desired effect. Distinguish an artistic preference from an issue that can be verified.

Educational example, not actual client feedback

“At 00:53, the beginning of the sentence is difficult to understand. Could you try a little less effect on the voice?”

“Between 01:10 and 01:28, I lose the energy established by the chorus. I prefer a shorter transition; this is a structural suggestion.”

A moment for an event

A click, an attack too strong, or an unintelligible word: a precise marker helps to find the point to listen to.

A passage for an impression

A transition, a chorus, or an annoying frequency range might concern several seconds. Delimit the passage rather than adding identical comments.

Listening context matters

Specify if you are listening with headphones, on speakers, or on a phone. This information helps to compare observations without automatically turning them into file defects.

When opinions contradict, categorise them.

Two people may expect different pieces. Look for what is repeated in the same passage, then separate the observations from the proposed solutions.

Example of a synthesis to be carried out yourself after listening
Feedback received Question to be verified Next possible action
“The voice is too distant” Does the problem appear everywhere or only in the chorus? Re-listen to the indicated passage on several systems.
“I prefer a shorter chorus” Is this a structural preference shared by other guests? Test a variant and compare the two intentions.
“This version suits me” Which version and which stage are concerned? Note the creative decision and the next expected delivery.

This summary is a working method, not an automatic analysis provided by TuneLockr. A version validation expresses a creative opinion; it does not constitute a signature or acceptance of a license.

A short message is enough to frame the listening.

Provide the stage of the piece, the question, and a return date compatible with the link's expiration.

Hello [prénom],

Here is [title — mix 03]: [TuneLockr link]. I have revised [element]. Can you tell me if [specific question]? For a comment on a passage, indicate the relevant moment in the comment.

Feedback before [date and time] would help me prepare [next step]. The link expires on [actual date]. Thank you!

Music workspace with a keyboard, headphones and representations of audio tracks
A clear file name helps to distinguish each working version.

Adapt sharing to the project.

An instrumental to be listened to by a singer

Indicate the tempo and key if you know them. Ask if the structure, breaths, and intended range are suitable. An initial listen may suffice; downloading the original is decided separately if a work recording is necessary. The conditions for using a voice and the piece are handled separately.

A final validation before a deadline
  • Lock the sent file and indicate its version in the message.
  • Request the precise decision you need, with a date and time.
  • Ensure the link’s expiration allows time to listen and respond.
  • Distinguish essential corrections from ideas for another version.
  • Keep the involved version and the received decision in your own records.
Comments to pass on to another collaborator

Provide a summary limited to the elements necessary for the work. Avoid copying names, addresses, or documents that are not useful for correction. Sharing a new link grants access to the file according to the permissions of that link: choose the recipients and appropriate options again.

No feedback on my demo: distinguish access problems, instructions, and availability

Silence after sending a demo does not suffice to conclude it's disliked. Before repeatedly following up, find out what prevents a response: unusable access, unclear request, lack of time, or absence of a question suitable for this person.

Check the blockage point

The first message should make it easy to respond: "Were you able to open the link, and do you have time to listen for four minutes this week?" It separates access from availability. Do not claim the person hasn't listened based solely on a lack of comment. Individual listening tracking functions are not established in this resource.

Change just one thing

In the four constructed scenarios of the table, the response depends on the declared obstacle. A closed link calls for valid access. A person who is available but lacks instructions needs a question. An unavailable person needs a new possible deadline or the end of the request. Sending the same message to everyone doesn't precisely solve any of these issues.

Educational scenario Available hint Minimal message Next action
Access The person reports a closed link Thank you, I am sending you a valid access for this listening. Check access before resending
Instruction They ask: what do you want feedback on? Can you spot where the chorus seems to start? Limit to this question
Availability They announce a busy week I’m finalizing on Friday; we can resume on a next version. Do not block correction
Unexplained silence No response, no proof of listening Is feedback possible this week? If not, I'll continue. One follow-up, then move forward without interpreting the silence
Filled pedagogical example, except explicit mention of calculation or actually produced file.

Properly close a request

Specify what happens if no feedback arrives: you proceed with available elements, and the person can listen to a subsequent version if they wish. This framework protects your schedule without turning follow-up into an obligation. Keep a known cause or "unknown cause" in your tracking, then a single next action. No tool can turn silence into creative consent.

Use the tree as a conversation aid, not as a person classification. The same person can be available to listen to a structure and not wish to comment on a mix. Adjust the size of the request before adding a new recipient.

Turn vocal feedback into remarks that can be applied

Vocal feedback often contains several intertwined ideas. To make it applicable, keep the person's words, link each observation to a passage, and separate what they hear from the solution they propose.

Preserve meaning before shortening

Here is a written demo script, not a transcription of a real recording: "Upon arrival of the motif, around five seconds, I don't know if I should enter. Then the bass helps me. Further on, around twenty-four seconds, it feels like we're starting over; maybe remove something?" This text contains an entry difficulty, a useful marker, and a hypothesis of variation. Summarizing it as "arrangement to review" would lose these differences.

Transform without inventing

First copy the concerned passage and the degree of certainty. "Around five seconds" remains approximate until verified. "Maybe remove something" is a suggestion, not an order to remove the bass. If you use an automatic transcription external to the service, check names, negations, and markers before sharing it. This resource does not announce any native transcription in TuneLockr.

Script formulation Observation retained Proposed action To be confirmed
I don't know if I should enter Insufficient entry marker around 5 s Add a marker in the entry map Exact measure targeted
The bass helps me Useful support after introduction Maintain this support during the trial No implicit removal
We start over the same Impression of repetition around 24 s Compare a targeted variation Which element seems repetitive?
Filled pedagogical example, except explicit mention of calculation or actually produced file.

Get ambiguous points confirmed

Send a short summary: "I note a difficult entry to spot, a useful bass as support, and a repetition to review around 24 s. Is this faithful to your message?" The confirmation is about the meaning, not about validating the piece. You can then associate remarks to the listened version and decide which ones trigger action.

Keep the long version until the summary is confirmed, then archive only what is useful to the project and according to the participants’ agreement. The filled table shows an editorial transformation; it does not constitute a user testimony.

Identify moments when attention drops during a demo

To understand where attention changes, ask the reviewer to mark a moment and describe what happened to them. A declared dropout can come from the piece, the listening context, or an external interruption. The time marker is the beginning of the analysis.

Draw a stable musical map

Workshop A serves as a support: introduction from 0 to 4.8s, motif setup from 4.8 to 14.4s, development until 24s, return of motif until 33.6s, then end. These markers stem from file construction, not from automatic audience tracking. The map allows people to talk about the same event even if their time estimation varies.

Request a declared path

A possible directive is: "After listening, flag up to two moments when your attention changed. Indicate what you noticed just before and if there was an external interruption." It is not about continuously measuring concentration. The three paths in the table are fabricated to illustrate heterogeneous responses; they are not usage data of TuneLockr.

Educational path Declared moment Added context Proposed continuation
P1 Around 24s, impression of starting over Continuous listening in the scenario Compare a targeted variation of the motif
P2 Around 15s, lost thread then return External notification declared in the case Relisten without attributing the loss to the piece
P3 Around 4.8s, stronger attention Motif entry spotted Preserve this entry in the variant
Filled pedagogical example, except explicit mention of calculation or actually produced file.

Choose the next experience

If two responses target the same motif return but describe different sensations, keep both formulations. A trial could shorten a repetition, then ask what this cut improves or removes. An interruption linked to a notification does not justify a musical cut by itself. Also keep the places where attention returns: they may reveal a marker the next edit should preserve.

The map is a musical conversation aid. It represents neither a measured retention curve nor a dropout rate. To exploit your own feedback, note the version and declared conditions with the observations.

Test the sequencing of two tracks before deciding their order

Testing the order of two pieces involves examining the artistic journey they form together. Prepare both orders with the same files and the same transition, then ask what each sequence brings. You can distinguish the choice of order from a technical linking touch-up.

Build the two sequences

The folder provides A then B and B then A from the two original instrumental versions of Atelier. These are exercise materials, not two commercialized tracks. Each sequence uses the files without additional linking treatment. The order variation is therefore explicit; numerical measures do not replace an appreciation of the transition when listening.

Describe the intended journey

Before listening, formulate an intention: to establish a motif and then increase its activity, or to start with the densest version and then open up space. The table contains pedagogical observations deduced from the constructed arrangements, not collected reactions. It shows two defensible journeys without declaring one universally better.

Provided actual sequence Proposed pedagogical journey Point to listen to Conditional decision
A then B Motif established, then counterpoints added Does the new activity renew the listening experience? To be retained if the rise serves the project
B then A Dense start, then space regained Does the withdrawal seem chosen or endured? To be retained if relaxation is sought
Same pair on an EP Position dependent on the previous and next title Journey over three pieces Do not generalize from just the pair
Filled pedagogical example, except explicit mention of calculation or actually produced file.

Decide the order before finishing

If the project aims for a rise in activity, A then B is a coherent hypothesis to listen to. If it aims for relaxation after a dense entry, B then A is worth a try. Also note what remains undecided: the placement of a track in a complete EP depends on the other pieces. Once the order is chosen, separately check silences, levels, and the behavior of the final medium; these are other decisions.

The right deliverable is an order decision accompanied by a reason and a remaining question. Sharing sequences allows this decision to be discussed on the same rendering; it is not presented as an automatic playlist function of the service.

Resources to put into practice

Find the completed examples, tables, and files used in this guide. Open the folder that corresponds to your need.

No feedback on my demo: distinguish access problems, instructions, and availability
Turn vocal feedback into remarks that can be applied
Identify moments when attention drops during a demo

Associated audio examples: Workshop — version A at 100 BPM.

Test the sequencing of two tracks before deciding their order

Associated audio examples: Workshop — sequence A then B ; Workshop — sequence B then A.

Listen to the audio examples

These instrumental excerpts were created for the exercises. You can listen to them here or download the files to work in your audio software.

Workshop — version A at 100 BPM (WAV · 1.9 MB)
Workshop — version A at 100 BPM

Download: Workshop — version A at 100 BPM

Workshop — sequence A then B (WAV · 3.8 MB)
Workshop — sequence A then B

Download: Workshop — sequence A then B

Workshop — sequence B then A (WAV · 3.8 MB)
Workshop — sequence B then A

Download: Workshop — sequence B then A

Questions about the feedback.

Who can give feedback on my music?

The people to whom you send the link, when you have enabled feedback. You invite your collaborators or interlocutors; TuneLockr sharing does not grant them expertise and does not provide you with new listeners.

Can multiple comments be left?

Yes. A version can receive multiple feedbacks, currently limited to a total of 100. On the audio, each comment can target a moment or passage. Find the terms and service status in the app.

Do you need to enable feedback for each link?

No. A link can be used for listening, authorised downloading, or exchanging remarks according to your choices. Enable feedback when a decision or correction is expected, then indicate the question in your message.

How to distinguish multiple versions?

Give each file a clear name and specify which version should be listened to. Free sharing concerns a temporary independent sending. The Share Space option, in addition to an active basic offer, allows you to link versions and their feedback to a creation. Check the offers and their terms.

Does positive feedback give the right to use the track?

No. Feedback or creative validation neither constitutes a signature nor a licence. If you wish to authorise use, define it separately with the concerned parties. If you wish to document a version with a timestamped proof, deposit it separately from sharing.

Play the right version.

Choose your file, enable useful feedback, and ask your guests a specific question.

🍪 This website uses cookies to improve your web experience.