The four-slot slate that catches a wrong viola preset before the lesson take

A shared link is not yet a lesson map

In a video lesson recording, a custom viola tuning preset is only useful after it becomes a lesson map. A link can carry the right collection of pitches while still assigning them to the wrong physical strings. That mistake is harder to spot than an obviously sharp note because the screen may look organized and the player may be busy managing camera framing, teacher instructions, and the first demonstration take.

Live performers need a stronger handoff than a link pasted into chat. The handoff should say which target belongs to the C-string side of the instrument, which target belongs to the next string, which target belongs to the third string, and which target belongs to the A-string side. Without that physical sequence, a custom preset can turn a clear lesson into a confusing recording where the displayed target and the teacher's fingering language point to different strings.

The practical move is to approve the map before approving the tuning. If the map fails, stop there. Do not tune the instrument into a preset that the lesson cannot explain.

Make a four-slot slate on camera

A slate is a small piece of visible evidence for the lesson file. It can be a card, a line in the session notes, or a shared document shown briefly at the start of the recording. The important part is the four-slot form: C-side string, second string, third string, A-side string. Put one target in each slot before the tuner listens.

This phrasing keeps the check tied to the instrument instead of to the software list. The issue is not whether the preset item appears first or last on a device. The issue is whether the performer, teacher, and later viewer understand the same physical string when they hear the instruction. A four-slot slate gives the teacher a chance to catch the swapped row before the student copies it.

Keep the slate short enough to read aloud. Name the lesson cue or exercise, name the reference if there is a drone or track, and then name the four targets in physical order. If the shared preset disagrees with the slate, the slate wins until the preset is corrected.

• Slot 1: C-string side target.
• Slot 2: next string target.
• Slot 3: third string target.
• Slot 4: A-string side target.
• Approval rule: no corrected slate, no shared preset.

Use TuneLT to audit slots, not to guess the lesson

TuneLT is useful in this workflow because it can turn each slate row into a controlled pitch check. Choose viola, open the custom tuning, and compare the displayed target against the slate before bowing. Then play one open string and let the sustained part of the note settle into the local microphone. The app should be confirming a row that already has a named physical position.

That distinction matters. If a performer asks the tuner to identify the lesson map from scratch, the wrong order can survive because the screen keeps offering plausible information. If the performer audits slot one, then slot two, then slot three, then slot four, the error becomes visible as soon as a displayed target belongs to a different physical string than the slate says.

Keep the phone position stable during the audit. A music stand position, a table position, and a handheld position can all hear the viola differently. Pick one clear spot, keep the call audio out of the room as much as practical, and check the four rows under the same listening conditions.

Do not let the call audio become a fifth instrument

Video lesson recording creates a strange room. The teacher's voice may come through speakers, the laptop may run noise suppression, and a backing track or drone may be present for the exercise. None of that should be allowed to vote on the tuner reading while the preset order is being approved.

Set a short tuning window. Use headphones if the teacher needs to stay connected. Mute the lesson audio for a few seconds if possible. Bow at a moderate dynamic and avoid talking over the open string. The local microphone pitch check is only as good as the sound that reaches the phone.

This is also where TuneLT's product boundary should be stated plainly. The pitch check uses the local microphone signal; it is not a claim that every app service is offline. Store services, subscriptions, ads, analytics, and platform services may use network access. For this audit, the musician's job is narrower: make the viola the clearest sound in the room while the four slots are verified.

Reject the preset instead of annotating around it

A wrong-order preset should not be patched with a chat note that says to swap two rows mentally. That may work for one expert during one call, but it fails as soon as the link is reused, the lesson is replayed, or another performer opens the setlist. The preset itself needs to match the corrected slate.

Rejecting the preset is faster than teaching around it. Rebuild the custom viola tuning in the correct physical order, rename it with the lesson context, and run the four-slot audit again. If a target changes because the teacher revises the exercise, update the slate first and the preset second. That sequence keeps the visible lesson record ahead of the shareable object.

This habit protects intonation work. A swapped map can make a double stop sound sour while the player blames finger spacing, pressure, or bow speed. Once the map is fixed, those musical problems can be judged honestly.

Send a preset receipt, not just a preset

After the four rows pass, send the preset with a receipt. The receipt should include the lesson name, the four physical slots, the target in each slot, and the reference source if one matters. It can be brief, but it should be readable without reopening the whole lesson thread.

TuneLT presets, setlists, QR sharing, Universal Links, and Android App Links can move the corrected map quickly between devices. The receipt is what keeps that speed from becoming ambiguity. A performer who scans the QR code before a later take can compare the app display with the receipt and know whether the same map is still active.

The useful timing is deliberate: first slate, then local microphone check, then corrected preset, then share. Sending the link before the four slots are approved is how a wrong order escapes into the lesson archive.

• Name the lesson or exercise.
• List the four physical slots and targets.
• Mention the reference source when relevant.
• Share by preset, setlist, QR code, Universal Link, or Android App Link only after approval.

Record one proof take before teaching from it

The last approval should be a short proof take in the same camera and microphone setup the lesson will use. Play the opening gesture, drone check, or open-string pattern that would expose a swapped row. The proof take is not for beauty. It is there to confirm that the corrected map produces the intended register, resonance, and teaching language.

If the proof take sounds wrong while the tuner rows are centered, keep investigating. The issue may be reference pitch, a drone mismatch, left-hand intonation, bow pressure, room noise, or a still-hidden order error. A custom viola tuning often changes the feel of familiar intervals, so the ear gets the final vote before the lesson proceeds.

When the proof take agrees with the slate, stop editing the map. Start the lesson, keep the receipt with the recording notes, and share the corrected preset as the version of record. The article's whole workflow can be summarized in one rule: the preset is ready only when the four physical slots, four target notes, and one musical proof take tell the same story.

Questions this guide answers