A useful way through
- Give a new idea a short name and date. Note whether it began with words, rhythm, harmony, melody or an image.
- Capture one small unit in a form you can retrieve: a voice memo, a written line or a simple description. Do not upload another person’s private recording without permission.
- Choose one constraint for the next version, such as fewer words or a contrasting rhythm. Keep the original alongside the variation.
- Return later and record what changed. Decide whether to continue, combine or set aside the fragment, using a version label instead of overwriting it.
Read the map as text
LISTENING MAP · 01 · Name and date · 02 · Capture a fragment · 03 · Change one · constraint · 04 · Keep both versions
- Name and date
- Capture a fragment
- Change one constraint
- Keep both versions
One fragment, two saved versions
The following two-line fragment is an original teaching example written for this page. It is not a Michael Thurber lyric, a quotation from a released song or evidence of a real co-writing session.
Use the bass-listening examples as a prompt for a small revision: keep a melody and change only its bass movement, then describe what you hear differently. Save both versions with your note. This is your own practice, not a technique newly attributed to an archived musician.
I leave a light beside the door.
The street goes quiet, then one step more.
| Version 01: spoken pulse | Four beats per line. Speak the first line with leave on beat one, light on beat two, beside on beat three and door on beat four. Keep the second line in the same four-beat space. This is a rhythmic instruction, not a supplied recording. |
|---|---|
| Version 02: change one constraint | Keep every word, but leave beat one silent and begin I leave on beat two. Try fitting the remaining words before the next line. If the words feel crowded, mark that result rather than changing the lyric at the same time. |
| Decision note | Compare where door lands and whether the words remain intelligible. Choose a version for the next attempt only after trying it; this example does not claim one sounds better. |
| Files to save | door-light-v01-spoken and door-light-v02-delayed-entry, each with the date, beat instruction and unchanged words in its note. Add an audio extension only if you actually make an audio file. |
| Next action | Record one short attempt of each version, label what changed and listen back tomorrow before adding chords. |
Keep an unsuccessful attempt useful
If the delayed entry compresses the last words, write “v02: ending crowded at this tempo”. That is more useful than “bad version”: it identifies the condition you could change next. Preserve v01 so a later lyric revision can be compared against the same starting point.
A collaborator should be able to tell which words, rhythm and version you mean without guessing from a file called new-song. If the fragment develops into a recording request, carry its chosen version into the filled demo brief. Agree authorship and permissions with actual collaborators; the example does not allocate rights for anyone else's song.
Illustrated lyric fragment, naming scheme and exercise. No completed recording or musical outcome is claimed.
Your take-away checklist
Build a songwriting notebook you can return to
- □ Name and date: ____________________
- □ Capture a fragment: ____________________
- □ Change one constraint: ____________________
- □ Keep both versions: ____________________
Before you act
Use the linked artist, publisher or presenter for exact credits and current availability. These listening and planning exercises are additional exercises, not quotations from a lesson by Michael Thurber.
Sources & context
The learning section of Michael Thurber’s artist site groups songwriting and composition separately from production, theory and bass. This notebook procedure is a new exercise inspired by that distinction; it does not promise the outcome of a lesson or offer enrolment.
Michael Thurber — biography, photographs & official links ↗
Hand over a song version someone else can identify
A session file, a listening export and an approval note are three different handover objects. Use this original fictional “Doorlight” record to keep them aligned. It adds no lyrics, recording, credit or new work attributed to Michael Thurber or Baldwin.
- Give the version an unambiguous identifier before exporting. Record tempo/meter only if known, the project application/version, referenced audio dependencies and the exact change being reviewed. Do not call an archive complete while its linked media are missing.
- Create a listening copy suited to the agreed review route and identify its filename and duration. A file that opens in the producer’s application may still be unusable to a collaborator without that application. An export is not a substitute for editable source when that is the agreed deliverable.
- Ask one bounded review question and save the response against the same version. If a new export changes the bridge or timing, increment the identifier and do not silently reuse the previous approval.
Worked record
| Fictional source | Doorlight_v03.project; application/version __; referenced media __. This is a manifest example, not a downloadable project. |
|---|---|
| Listening copy | Doorlight_v03_review.wav; duration __; export settings __; hash __. No real audio file is supplied or claimed. |
| Review question | Does the second verse enter where the agreed cue requires? Response __; reviewer __; date __; version explicitly heard __. |
| Changed version | Doorlight_v04 changes the verse entry. v03 approval does not automatically approve v04. |
| Handover checklist | Editable source present __; media paths resolved __; listening copy opens __; rights/credits __; version-specific decision __; unresolved item __. |
Do not fill unknown software settings, timing or reviewer names with plausible guesses. The notebook remains a creative procedure, not proof of a completed session, a collaborator’s consent or a listening test.
Primary sources: Audacity: project files and audio exports · MichaelT: notebook and source context