Bass lesson preset receipt for bandmates sharing a custom setlist tuning

Turn the preset into a receipt, not a rumor

Custom setlist tuning is fragile in a video lesson because the name rarely tells the whole story. One bandmate may remember the song title, another may remember a lowered string, and a third may open the lesson file days later with no idea which reference approved the bass. If the group only shares a preset name, the next player still has to guess the actual target.

A better handoff is a preset receipt. It says what the bass should be tuned to, which octave each string belongs in, who or what supplied the reference, and which lesson section was checked before sharing. That sounds administrative, but it solves a musical problem: a take can sound in tune by itself and still become uncomfortable when the rest of the lesson audio arrives.

The receipt keeps the band from arguing over memory. Everyone can see whether the tuning was approved against the teacher guide, the backing track, a keyboard reference, or a previous bass take. If that authority changes, the preset gets a new note instead of silently carrying the old assumption forward.

Choose the tuning authority before opening the tuner

Before anyone touches a peg, decide what the bass is supposed to agree with. In a lesson project, the authority may be the instructor performance, the guide guitar, a click-track keyboard, or an already approved backing file. The tuner can show whether a string is near the target, but it cannot know which recording in the folder is the source of truth.

This step prevents the common bandmate problem where two people are both careful and still create different results. One player tunes to a scratch guitar exported last week. Another tunes to a corrected backing track. Both can make honest tuner passes, but their presets will not match once the lesson is assembled.

Write the authority into the preset receipt in plain language: approved against chorus guide guitar, checked to keyboard A, or matched to final backing export. If the authority is uncertain, write uncertain. An honest uncertainty note is safer than a confident preset that points everyone to the wrong center.

Check note names and octaves as separate facts

Bass handoffs fail when note names and octaves get blended together. A custom setlist tuning may include a familiar note name in an unfamiliar register, or it may move one string while leaving the others in standard relationship. Write the target low to high and include octave numbers when the group uses them. If the player only writes D, another bandmate may not know whether the note belongs below the E string, above it, or as a fretted reference inside the part.

Octave mistakes are especially easy in video lessons because the camera often focuses on the left hand, not on the headstock or a complete tuning chart. A player may copy the fingering correctly while setting the open string in the wrong register. The result is not always an obvious wrong note; sometimes it is a bass line that seems heavy, thin, or strangely tense against the teaching track.

A preset receipt should therefore list each target as a string position, not only as a cloud of pitch names. If the setlist tuning changes between lesson sections, make separate receipts. One shared preset that tries to cover several arrangements is harder to trust than two clearly named targets.

Use the same pluck the lesson will hear

Checking every target note does not mean attacking the string any way you like. Bass pitch moves during the first part of the note. A hard pluck can begin sharp, then settle. A soft pluck can make the tuner read more calmly but fail to match the performance energy. For a video lesson, use the touch that the student will actually hear in the demonstration.

Mute neighboring strings, keep the phone or computer microphone in a consistent spot, and let each note settle long enough to identify the pitch center. TuneLT can be used here as a bass tuner with local microphone pitch detection. Choose bass, confirm the custom target, and verify the strings in the order written on the receipt.

Do not describe the whole app as offline. The pitch check uses the local microphone, while store, subscriptions, ads, analytics, sharing, and platform services may use network access. That distinction matters because the handoff can involve links or QR sharing even though the tuning reading itself is local microphone work.

Approve the preset against the lesson section, not a mood

After the open strings are checked, play the exact lesson section that will carry the preset name. Do not approve the tuning by playing a comfortable riff in isolation. Use the bar where the bass first has to agree with another pitch source. That may be the first held root, a unison figure with guitar, a walking line under a chord, or the entrance where the student play-along begins.

This is the brief problem in practical terms: the take sounds in tune alone, but it feels rough when other lesson material is present. The fix is not to stare longer at the tuner. The fix is to name the section that proves the preset belongs to this recording. If the section does not pass, the receipt should say what failed before anybody shares the target.

Use musical language the next player can act on. Bar 12 low string beats against guide guitar is more useful than sounds bad. Chorus entrance approved against final backing track is more useful than tuner ok. The preset becomes a record of a musical decision, not only a saved configuration.

Keep cents, intonation, and reference pitch in the conversation

Bandmates do not need a lecture every time they share a preset, but the receipt should leave room for the reasons tuning can disagree. Cents measure small pitch distance, and a few cents can become audible when bass sustains under another instrument. Reference pitch matters when older exports, software instruments, or real instruments were not created from the same source. Intonation matters when the open string is right but the fretted lesson phrase leans sharp or flat.

Those concepts help the group choose the next action. If all open strings are correct but fretted notes in one position are sharp, the preset may be fine and the fingering pressure or setup needs attention. If the entire bass part rubs against the guide, the authority may be wrong. If only the first transient feels tense, the player may need a softer attack before changing the target.

Write the smallest useful clue. No one needs a paragraph in the preset name. A short note such as fretted chorus checked, guide guitar slightly high, or use softer attack on low string can save the next recording pass from repeating the same question.

Share the TuneLT preset after the audit, not before it

TuneLT supports practical handoff features around presets, setlists, OCR tuning scan, QR sharing, Universal Links, and Android App Links. For a band working on a lesson, those features are most useful once the target has been audited. The flow is: confirm the authority, verify every bass target, approve the lesson section, then share.

Sharing before the audit creates a false sense of completion. Everyone receives something official-looking, so the group may stop asking whether the tuning was checked against the right file. Sharing after the audit does the opposite. It makes the preset a compact version of the decision the group already made.

If a bandmate imports the preset later, ask them to read the receipt aloud before recording: target order, authority, approved section. If they cannot do that, the handoff is not clear enough yet. Fix the note before fixing the take.

• Authority named before tuning starts.
• Low-to-high target written with octaves when needed.
• Every string checked with the lesson-performance pluck.
• Specific lesson section approved or marked as failing.
• Preset shared only after the receipt is complete.

Version the preset when the lesson changes

Video lessons change. A teacher replaces a backing track, a guitarist rerecords the guide, a chorus is moved, or the tempo edit changes which note sustains under the explanation. When that happens, do not quietly reuse the old bass preset. Duplicate it, rename it, or update the receipt so the band knows which lesson version it belongs to.

Versioning is not busywork. It protects the player who records last. Without version notes, the final bass take may be tuned to an earlier reference while every other part has moved on. The more custom the setlist tuning is, the more important this becomes, because there may be no standard label to rescue the group from ambiguity.

A clear version line can be short: Lesson 4 backing v2, chorus approved, previous guide obsolete. That is enough to stop a bandmate from importing the older target by accident.

The quick handoff script

Use this spoken script before recording: This is the custom bass setlist preset for the video lesson. The authority is the named guide or backing file. The strings are written low to high. I checked every target note with the performance pluck. The approved section is named in the note. If you record from this preset, keep the same authority unless the lesson file changes.

The script may feel formal the first time, but it is faster than repairing three takes made from three different assumptions. It also lets non-technical bandmates participate. They do not have to understand every cents reading; they only have to confirm that the receipt matches the lesson they are recording.

That is the whole purpose of the workflow. Tune the bass, yes. But more importantly, share the decision that made the tuning useful for this specific video lesson.

Questions this guide answers