DropCue lets supervisors and publishers leave comments pinned to exact waveform positions. No more decoding vague feedback emails. Faster revisions, less ambiguity, per-track analytics next to every note. Starting at $5 per month with annual billing.
Start free trial →Timestamped music feedback is a comment pinned to a specific second in a music track. The reviewer plays the track, hears something at 1:42, clicks the waveform at that exact second, and types a note. The pin stays attached to that timestamp. When the composer opens the project, the comment appears as a marker on the waveform at the 1:42 mark with the text visible on hover or click. Playback auto-scrolls each comment into view as the timecode passes its pin.
Before timestamped feedback existed, the workflow looked like this: composer emails finished track to supervisor, supervisor emails back "the snare around the middle of the chorus is too loud and the vocal in the bridge feels buried," composer plays the track 3 times trying to find each spot. Then composer iterates and sends v2. Supervisor responds with another vague description. Repeat for 6 revision rounds. The pre-2018 workflow burned 60 to 80 percent of revision-round time on ambiguity resolution rather than actual creative work. Timestamped feedback collapses that into "snare too loud" pinned at 1:42 and "vocal buried" pinned at 2:18, with no playback hunting and no clarification email loop.
When five music supervisors review the same playlist, each one sees an isolated comment view. Reviewer A sees only their own pins. Reviewer B sees only theirs. Neither sees the other reviewer's notes before listening. This eliminates the group-think failure mode where the second reviewer unconsciously echoes the first reviewer's opinions after reading them. The composer sees all comments across all reviewers in a unified view with each pin attributed to its specific reviewer, which gives you five independent reactions instead of one repeated five times.
Each comment carries a status field (open, addressed, won't fix, rejected) that the composer updates as the revision proceeds. When v2 of the mix uploads, v1 comments stay attached to v1 timestamps for historical reference. New v2 comments pin to v2 timestamps. The version flip lets reviewer and composer both see what changed round over round. This eliminates the "did I fix that note" check-in that follows every multi-round project.
DropCue supports video uploads (MP4, MOV, WebM) and timestamped feedback works identically on video. A music editor sending a reel cut with temp music can pin "hit here on the logo" at exactly 0:42, and the composer sees the pin on the video timeline. Trailer revisions especially benefit from this because the music has to land on specific picture moments and email descriptions of those moments are ambiguous.
When feedback arrives in DropCue, the analytics panel for that recipient sits next to the comment list. You see which tracks the supervisor played, for how long, and whether they came back. A timestamped note from a supervisor who played the full 3-minute track twice carries different weight than a note from someone who skipped after 15 seconds. The analytics tell you whose feedback to weight heavily in the revision and whose to politely incorporate.
The single biggest shift is in the size of each revision round. A revision round that used to take a day (read the email, guess, revise, send back, get another email, guess again) compresses to a few hours. The composer reads the timestamped comments in sequence, makes the edits with clarity, and sends back a single revised version that addresses every note without ambiguity. The director or supervisor opens the new version, leaves new comments at new timestamps if needed, and the next round starts immediately rather than two days later.
The second shift is in the quality of the music itself. When the feedback is precise, the revision is precise. The composer who knows the director wanted the snare pushed at 0:32 makes that exact change, not a generic energy-push that might solve the problem or might create a new one. The cumulative effect across a project is music that lands closer to the brief on each revision round, which often means fewer total rounds before final.
The third shift is in the trust between composer and collaborator. Vague feedback is hard to act on, which means the composer either guesses wrong or asks for clarification. Timestamped feedback removes the ambiguity, which removes both failure modes. The director who left precise comments and got a precise revision starts to trust the composer to deliver predictably. The trust compounds across projects.
The feature also enables a workflow that was impractical before: detailed feedback from someone who is not the primary client. A music editor on a film can leave technical notes on stem alignment without going through the supervisor. A second composer collaborating on a cue can leave notes on harmonic transitions. A picture editor can leave notes on hit points for picture cuts. All of this can happen in parallel, with the primary composer seeing every note in context and resolving them in a single revision pass. Shared playlists with timestamped comment threads become the working document for the project rather than the email chain.