Most music feedback gets written like this: "make the chorus punchier" or "around the second chorus feels off" or "the bass thing in the middle." Sometimes it's accurate, but most of the time it'svague because describing a moment in music with words is hard. Two people listening to the same track will count choruses differently, hear "the middle" as different sections, or have different opinions on what "punchier" means.
A more elegant way to give feedback already exists: pin the comment to the second on the waveform. "I don't like the eeking sound." Done. The producer opens the project, sees the comment hovering at 1:42, plays the track, hears the eeking sound, fixes it. No back-and-forth about "which eeking sound where when" means the same thing in both of your versions of the file. You could have written a text message saying "eeking sound at 1:42", but what if you had 10 or a 100 of these?
That's the whole idea. The rest of this post is about why it works and how to write comments that are even clearer once you can pin them.
When you describe a moment in a song with words, you're translating something precise into something imprecise, and the producer has to translate it back. "The second chorus" could be one of three choruses. "The energy bit" is meaningful only if you share a definition of it, which you probably don't.
Pinning the comment to the waveform skips the translation and it isn't new. Pro Tools has had timestamped comment features for years and some mastering platforms have similar features. What's new is that timestamped comments are now available in a layer that sits between any DAW and any collaborator, which means the producer doesn't have to be in the same software as you, and you don't have to be an engineer to use them - you just click and drag-and-drop.
Say what you're hearing, not what to fix. "The kick is a bit too loud" is much better than "lower the kick by 2dB." You want to leave the mixing work to the mix engineer. Even if you know the fix, the producer is the one with the session open and the full context. They can choose to lower the kick, sidechain it, EQ, or reshape the low end entirely. So "sit down, be humble", and tell them what you're hearing so they can figure out the fix.
One comment per issue. If the kick is too loud at 0:48 and the vocal is dry at 1:12, those are two comments with two timestamps. Don't bundle tasks.
It's fine to be vague about what you want, as long as you're specific about where. Even if you have advanced musical aphasia, a "Something feels off right around here" comment pinned at 1:42 is useful, because the producer can listen at 1:42 and hear what you mean. Over time your communication will refine itself.
The difference between sending feedback in a chat and pinning it to the waveform.
Chat message: "Drop sounds weak at 1:24, vocal feels muffled at 0:32 but gets better by 0:48."
Pinned comments:
1:24: "Drop feels smaller than the build promised"
0:32: "Vocal feels muffled here, gets better later"
0:48: "Vocal sounds clear here for reference"
Both versions communicate the same information. The pinned version splits it into discrete items that are independent of the chat timeline. The producer can address one at a time, mark resolved, and revisit on the next version of the mix. The chat message is text which producer sees once and then either loses track of two messages later when something else comes through, or has to cycle through pinned messages one by one.
In Jamline, any project collaborator can drop a comment anywhere on the waveform. The comment is pinned to the second. It survives across versions, so when the producer updates the main mix tov2 you can see whether the issue was addressed.
You can reply in threads. You can mark comments as resolved. You can attach a voice message or a reference track to a comment if you want to whistle, mumble or otherwise demonstrate something rather than describe it. The comments live next to the song, in the same project as the stems, the versions, and the chat.
You can also chat with the producer in real time, send voice messages, share GIFs and reactions, and switch between project chat and direct messages. The conversation about the song lives with the song, which means a year from now when you're starting a new project together, the context from the old one is still right there.
Invite someone from your Chat to Start your first Collaboration at https://app.freecords.com/