Published by PitchChanger · Updated · How these guides are made
How to use this workflow
Locate the passage
Choose a passage containing an isolated short note and a longer note. Preserve a little audio before and after both.
Compare the evidence
Listen to bass solo, then the full source at the same positions. Note attack, candidate release, residual tail and next attack separately.
Save a usable reference
Practice the phrase with the candidate articulation. Leave unclear endings marked uncertain instead of rewriting the performance from an artifact.
Worked example and evidence boundary
Consider an authored timeline: attack at 2.00 s, apparent musical release at 2.35 s, residual tail to 2.60 s, next attack at 2.75 s. The candidate played duration is 0.35 s and the gap to the next attack is 0.40 s. Using the tail instead gives 0.60 s and 0.15 s. Neither interpretation is a measurement of your file; the example shows why the chosen endpoint matters.
What to verify before using the result
PitchChanger estimates the bass role; it does not transcribe articulation or detect a note-off event. Slowing an exported reference may help listening, but judge release against the unchanged source too. Avoid using a noise gate to manufacture evidence for the ending you expect.
Common questions
Should I trim every tail after a bass note?
No. A tail may belong to the original articulation or room sound. Compare the full source before making a destructive edit.