A single-string fault log for half-step-down viola after travel

Start with a fault-isolation mindset

A traveled viola can arrive at a session with a pitch problem, a handling problem, and a documentation problem at the same time. The pitch problem is obvious: the open strings are not where the cue needs them. The handling problem is quieter: one peg may have backed out, one string may be catching in the nut, or the bridge may have leaned during the trip. The documentation problem is what makes the first two expensive: nobody writes down which string is misbehaving, so the player retunes everything until the room loses time.

Half-step-down viola gives the player a fixed map: B2, F#3, C#4, and G#4 from low to high. That map should be written before the tuner comes out. Once the map is visible, the useful question changes from "what note is this?" to "why does this string fail to repeat the same reading?" A jumping display is not a verdict. It is evidence that needs context.

For a session player, the goal is not a perfect workshop report. The goal is a short fault-isolation pass that protects the take. Identify the target, isolate the string, describe the jump, decide whether the cause is signal or hardware, and only then correct pitch.

Build the three-column note before the first take

Use three columns: target, displayed behavior, and physical clue. The target column is simple: B2, F#3, C#4, G#4. The displayed behavior column captures what the tuner does after the noisy attack: stable, flickers sharp, flickers flat, jumps to neighbor, or loses the note. The physical clue column records what the hand and ear noticed: peg slipped, nut caught, fine tuner bottomed out, bridge leaning, string rattled, room too loud, bow attack too scratchy.

This note can fit on the back of a chart or in the session notes. It is more useful than a long cents history because it ties the screen to an observable cause. If G#4 flickers only when the bow attack is harsh, that is a player-and-signal issue. If C#4 drops after every correction while the peg feels soft, that is a mechanical issue. If F#3 cannot be read until neighboring strings are muted, sympathetic resonance is part of the evidence.

The note also prevents accidental retuning of stable strings. If B2 and F#3 sit still, leave them alone while you investigate C#4. A session clock rewards narrow work.

• Column 1: B2, F#3, C#4, G#4.
• Column 2: what the display does after the attack.
• Column 3: what the instrument, bow, room, or hand suggests.
• Rule: fix the repeated pattern, not the most recent flash.

Use TuneLT as the controlled reading, not the whole diagnosis

TuneLT can give the controlled reading in this pass. Choose viola, use the half-step-down targets or a saved preset, and place the phone where the local microphone hears the instrument clearly. Keep that placement fixed while you test the suspect string. If the phone moves each time the note jumps, you have changed the measuring device and the instrument at once.

Read the sustained part of the note rather than the scrape at the front. Bow attacks can throw extra noise, and a lowered viola string may speak with a strong transient before the pitch settles. Let the note bloom, then mark what the app reports in the middle of the sound. This is especially important for lower targets such as B2, where weak fundamentals and room resonance can make overtones look more persuasive than the note itself.

Do not overstate the app role. Store services, subscriptions, ads, analytics, and platform features may use the network, but the pitch read in this situation comes from the local microphone signal. That distinction is enough for the session workflow: make the sound clean, make the phone position repeatable, and compare readings across passes.

Classify the jump pattern before turning anything again

A jump that appears only at the first scrape usually asks for a cleaner bow stroke or a different microphone position. A jump that appears after the note begins cleanly and then steps sharp or flat asks for a contact-point check. A jump that returns every time the same peg is touched asks for peg seating. A jump that gets worse near the end of fine-tuner travel asks for resetting the fine tuner before using the peg again.

There are also clues that sound more like the room than the viola. Headphone bleed, another player warming up, HVAC rumble, and a reflective booth can confuse the reading. Mute neighboring strings, ask for a quiet ten-second pass, and move the phone only once if the first placement is clearly bad. If the reading stabilizes under quiet conditions, write "signal" in the fault log and avoid unnecessary hardware work.

The important distinction is repeatability. Random jumps across all strings are usually a measurement environment. A repeatable jump on one string after the same correction is a setup clue. That is the point where a player should slow down, because another turn may deepen the problem.

• Attack-only jump: improve bow and signal first.
• Stepwise pitch catch: inspect nut or bridge contact.
• Post-correction drop: check peg seating.
• Unstable near fine-tuner limit: reset the fine tuner range.
• All-string chaos: treat the room and microphone path as suspects.

Make one correction and preserve continuity

After the pattern is named, make one correction that matches it. If the fine tuner is bottomed out, back it to a useful middle range and retune with the peg. If the peg appears loose, seat it carefully while protecting the lowered target. If the bridge is leaning or the string is binding badly, the right move may be to pause for a setup-safe adjustment rather than forcing pitch in front of a microphone.

Preserve continuity for the take. If the part has already been rehearsed against a guide track, the half-step-down map must stay tied to that reference. Do not quietly drift toward standard CGDA because the open strings look easier there. Do not accept a visually centered note that fails against the drone, piano, or previous layer. Session tuning is about repeatable pitch in context, not a private perfect number.

When the string responds, retest only what the correction could have affected. A peg change on C#4 might disturb neighboring tension slightly, but it does not require rebuilding the whole setup from zero. Narrow retesting saves time and keeps the player from losing the feel of the part.

Save or share only after the fault is understood

A preset is useful once the lowered map and the instrument behavior are known. TuneLT presets, setlists, QR sharing, Universal Links, and Android App Links can help a player, assistant, or teacher reuse the half-step-down targets. But a shared preset is not a repair note. If the string was catching in the nut or the peg was rolling back, that information needs to travel with the chart or session log.

For recurring sessions, name the preset in a way that includes the reference and the job. "Viola half-step down A440" is clearer than "low viola". Add the fault note separately: "watch C#4 after case travel" or "G#4 attack reads noisy unless muted." The next player then receives both the target map and the condition that made the tuner jump.

This is where the workflow becomes durable. The player is no longer asking an app to remember the whole situation. The app carries the pitch map; the musician carries the cause and the fix.

End with the cue that would expose the problem

The final test is not another random open string. It is the cue that would reveal the failed setup: the first entrance, a sustained doubled note, a soft exposed line, or a drone against the guide. Play it after the suspect string has been corrected and logged. If the cue agrees, stop. If the cue still beats or sours, the problem has moved from open-string target to intonation, arrangement, or reference mismatch.

This ending matters because half-step-down viola can feel visually correct while still making the hand uncertain. The lower tension changes response. A player may press differently, bow differently, or hear the relationship to the track differently. The tuner confirms the open-string evidence; the cue confirms the musical job.

A useful session note after the cue might read: "B2 and F#3 stable; C#4 peg seated after second pass; G#4 attack noisy but holds when bowed clean; cue 14A agrees with guide." That is enough to resume work without reopening the whole tuning problem after every break.

Questions this guide answers