# Teaching and publishing the course ## What is ready This package contains a complete self-paced text course, a printable handbook, a workbook, original practice illustrations and audio, thirty lesson questions with explanations, four guided project studios and a capstone rubric. The browser course includes local progress, practice notes and quiz feedback. It can be used privately from the folder or placed on a static host after review. Six real-editor screenshot walkthroughs are included, with a printable visual companion in the handbook. Ten AI-narrated video companions are included in the videos folder. Alex is a fictional AI presenter, not a real instructor with professional credentials. Full-project screen recordings and platform approvals are not included. The lesson explanations below remain editable narration scripts; demonstrate the numbered actions on screen and use the practice instructions as pause points. Record actual UI states rather than constructing screenshots that imply a feature ran successfully. See Platform-Submission-Guide.md before submitting the course. ## Teaching approach Show the result of a lesson first, name its one objective, explain the decision and demonstrate the action. Let the learner try before revealing your solution. Finish by comparing against the success criteria. A useful session spends as much attention on why a cut helps as on how to make it. Keep the tone conversational. Say “Watch the first word here” rather than “Optimise temporal precision”. When a run fails, show a real diagnosis or record a separate recovery lesson. If you cut waiting time from a recording, label the time skip; do not imply an instant result. The structure draws on Udemy's outcome-led sections and short lessons, and on course examples that combine instruction, readings, assignments and peer review. The curriculum and all exercises are original. No endorsement or accreditation by those platforms is implied. ## Recording plan Record a two-to-four-minute welcome separately. Say who the course is for, show the four project outcomes, disclose that some optional features use paid access or credits, and explain the text and practice materials. Use a real instructor name and experience; do not invent credentials. For each of the thirty lessons, use the narration and screen plan supplied later in this guide. Aim for a focused demonstration of roughly four to seven minutes, with a longer walkthrough when an operation needs it. These are recording targets, not existing runtime. Record at a readable desktop size and include phone demonstrations for upload, panel navigation, captions and export. Zoom into the relevant UI during editing rather than making viewers decipher an entire desktop on a phone. Use a quiet microphone recording, check pronunciation and caption all lectures. Do not place constant music under detailed instruction by default. Use the original practice files and a dedicated demo account with no customer information, private notifications, keys or billing identifiers. Show the same source names used in the exercise. Record four project walkthroughs after the short lessons. Use the story maps in the project studios, show a rough cut and an improved version, and explain at least one rejected choice. Do not claim the illustrative projects are actual product tests. Film the real object for a real review. ## Checks before selling or publishing Run every core exercise through the currently supported web and phone interfaces using a fresh learner account. Check the displayed plan restrictions and costs. Replace outdated UI wording and record the version and date tested. Verify the first lesson can be completed without buying generation credits. Check the workbook links, keyboard navigation, mobile layout and downloads. The included two-tone control can test a listening workflow, but two tones do not establish general music-recognition accuracy. Likewise, one consistent robot image does not prove identity consistency for every subject. Preserve those teaching limits in demonstrations and sales copy. If publishing on Udemy, recheck its current quality checklist and policies. At the research date, the general marketplace requirements include at least five lectures and thirty minutes of video, plus video-quality and other checks. The PDF and text course alone do not meet that video-course requirement. The curriculum CSV is a mapping aid, not a promised direct Udemy or SCORM import. This local browser course has no accounts, payments, server analytics, graded submission service or accredited certificate. Progress and notes are stored only in the current browser. For a paid hosted product, add appropriate access control, payment handling, data disclosures and learner support in a separate implementation. Do not describe local checkmarks as verified completion. ## Free and paid editions Free introduction: offer Module 1 and the ten-second practice assets as a complete useful experience. Include one honest next step to the full course. Do not hide the ability to finish the starter exercise behind a sales gate. Full self-paced edition: include all thirty lessons, four project studios, workbook and capstone. Its value is structured practice, examples and feedback criteria. If selling it, clearly state whether it is text-only or includes recorded video; do not advertise hours of video before those recordings exist. Supported cohort: use the same content with scheduled reviews and a human capstone assessment. Define the number of reviews, response windows and cohort dates before selling this version. Do not promise unlimited support or a certificate with external accreditation. Set a price after testing the format with real learners and comparing the support cost to the value delivered. No unsupported revenue or completion claims are included here. ## Capstone assessment Score each category from zero to four and multiply by its weight divided by four. Four means the strong description is met; three means mostly strong with a small fix; two means the developing description; one means a major issue with some usable work; zero means the criterion is missing or unusable. Total possible score is one hundred. Suggested completion standard: at least seventy points, every category above zero, and no unresolved misleading claim, privacy issue or essential speech/caption error. A learner may resubmit after feedback. This is an internal course standard, not professional accreditation. Free-plan branding and output limits do not reduce the score when the learner chose appropriate available settings. If a project has no narration, assess sound for intentionality, balance and clean starts and endings. If it deliberately has no sound, the learner must explain the choice and demonstrate that the visual message works; do not force unnecessary music into the story. ## Pilot and measurement Pilot with a small group of actual beginners across web and phone. Ask them to complete Module 1 without live help, record the first point of confusion and verify whether they can export. Track starts, lesson completion, exercise submissions, capstone submissions, resubmissions and learner-rated usefulness. Treat local progress as self-report, not a graded assessment. For a hosted edition, define anonymous or account-linked events deliberately and disclose collection. Useful events include course_started, lesson_opened, exercise_completed, quiz_answered, capstone_submitted and capstone_reviewed. Store lesson identifiers and outcomes rather than private source footage or raw learner prompts. Do not add tracking to this offline package without a product decision. Measure the rate of first-edit completion, the most common failure stage and the percentage of submitted capstones that meet the rubric. Separate people who merely opened a lesson from those who produced a video. Interview learners before assuming a low completion rate is a motivation problem; missing footage, unclear UI and unexpected paid gates are possible causes. ## Maintenance Review this edition whenever upload, chat, references, captions, audio inspection, generation or export changes. Recheck the current plan notices rather than freezing prices in teaching copy. Keep a dated capability matrix with a web and phone test for the core route, a fallback for optional features and a list of recordings that need replacement. Preserve a downloadable archive of each sold edition and a clear update policy. Keep original course assets distinct from customer uploads and third-party stock. Recheck stock and provider terms before adding new downloadable examples. # Lesson narration and recording scripts Read the narration naturally. Demonstrate the screen actions at a pace a beginner can follow, then pause for the exercise. The narration is also available to learners as text. ## 01.01 Choose one person and one useful outcome **Opening:** In this lesson, you will write a brief that gives your first video a clear purpose. ### Narration Imagine someone watching your video while waiting for a train. They have no idea who you are. What would make the next thirty seconds useful to them? That question is a better starting point than choosing a transition. For our main project, you will review a desk lamp you already own. The viewer wants to know whether it would make their desk easier to use. Your job is to show one useful feature, one limitation and a verdict. You do not need a studio, a perfect voice or a new purchase. A mug, keyboard or notebook works just as well. Vidmoat gives you an AI agent and an editable timeline. The agent can help assemble the first version; you decide whether it tells the truth and feels right. Generating new media is optional throughout the core course. Start with material you own, and use the included original lamp illustrations if you cannot film today. Those illustrations represent an imaginary product, so label the result as a concept demonstration rather than a real review. ### Demonstration cues 1. Show and explain: Choose a single viewer: for example, someone working at a small desk. 2. Show and explain: Write the question your video answers in one sentence. 3. Show and explain: Choose a 30-second target and a vertical 9:16 frame for this first exercise. 4. Show and explain: List three things you can actually show. Remove claims you cannot demonstrate. 5. Show and explain: Save the brief in your workbook before opening the editor. ### Prompt demonstration I am making a 30-second vertical review for someone with a small desk. Help me plan a useful feature, an honest limitation and a verdict. Use only facts I provide. Do not edit or generate media yet. ### Pause for practice Write a brief for your own object. Finish: “After watching, my viewer will be able to decide whether…” Then write one claim you will deliberately avoid because you have not tested it. ### Debrief A good brief names a viewer, a question, a length and evidence. Example: “Show a student whether this lamp lights a notebook without taking much desk space.” Watch for this common trap: “Make a viral video for everyone” gives the agent neither an audience nor a decision to support. ### Check understanding Which brief gives an editor the clearest direction? A. Make it professional and viral. B. Show a student how this lamp fits a small desk in 30 seconds. C. Use every available effect. Answer: B. The second brief defines the viewer, the evidence and the time available. It still leaves room for creative choices. ## 01.02 Find your way around Vidmoat **Opening:** In this lesson, you will upload an asset, place it on the timeline and check that the project has saved. ### Narration There are four places to recognise first. The media library holds your source files. The preview shows the current picture. The timeline decides what plays and when. The Inspector or Properties area changes the selected item. The AI chat is another way to work on that same project. An uploaded file and a timeline clip are different things. A file can sit in your library without appearing in the video. A timeline clip points to part of that file. Trimming the clip changes the edit; it does not rewrite the original recording. This is why one long recording can provide several short clips. On a wider screen, several areas can be visible together. On a phone, you switch between them. Follow the names and the job each area does rather than memorising its exact position. The current app may call an area Media, Media Library, AI, or Agent. Before continuing, confirm that the source upload has completed and the project is saved. A thumbnail alone is not proof that a file reached cloud storage. ### Demonstration cues 1. Show and explain: Sign in to Vidmoat and create a project named “Course 01 First edit”. 2. Show and explain: Use Add footage or open Media Library and choose Upload. Select your recording, or resources/lamp-wide.png. 3. Show and explain: Wait for upload progress to finish. Resolve any Retry message before leaving. 4. Show and explain: Add the library item to the timeline. On web, drag it in or use the item action; on phone, tap the item and its add action. 5. Show and explain: Play and pause the preview. Select the clip and find its properties. Wait for the saved state. ### Prompt demonstration Check the media in this project. Tell me which files are available and which clips are already on the timeline. Do not change anything yet. ### Pause for practice Add one source and make it visible for five seconds. Switch from the timeline to chat and back. Find the source again in the library. ### Debrief You can explain the difference between the source file and the clip, and see the expected picture during playback. Watch for this common trap: Style reference is guidance for the agent, not the normal footage-upload button. An empty timeline stays empty if you only attach a reference. ### Check understanding You uploaded an image but it never appears in playback. What should you check first? A. Whether it was added to the timeline. B. Whether the export is set to 4K. C. Whether it has a music track. Answer: A. Library storage does not automatically mean an asset appears in the sequence. Check the timeline before changing export settings. ## 01.03 Make your first ten second edit **Opening:** In this lesson, you will assemble a simple beginning, detail and ending without extra effects. ### Narration Your first finished edit should be small enough that you can watch it several times. Use three shots: the object in context, a useful detail, and an ending. The included lamp-wide, lamp-detail and lamp-desk illustrations make a complete practice set. They are intentionally simple so that you can focus on the timeline. Set the project shape before spending time on text placement. A vertical frame is tall and narrow; a landscape frame is wide. Filling a frame can crop the sides of a source. Fitting the whole source may leave space around it. Neither is automatically wrong. Choose based on what the viewer must see. For this exercise, use cuts rather than transitions. A cut immediately changes from one image to the next. Notice how the sequence already feels purposeful when the shots answer related questions. Later lessons add captions, music and motion. First, make sure a viewer can understand the object and the point without them. ### Demonstration cues 1. Show and explain: In Project Settings, choose 9:16. Use the resolution available on your account. 2. Show and explain: Place the three practice images in order on one visual track. 3. Show and explain: Set their durations to 3 seconds, 4 seconds and 3 seconds. Put each directly after the previous one. 4. Show and explain: Add an ending title: “A little light for your desk”. Keep it clear of the lamp. 5. Show and explain: Play from zero to ten seconds. Check for blank gaps and accidental overlaps. ### Prompt demonstration Use these three uploaded lamp illustrations to make a 10-second vertical concept sequence. Show wide for 3 seconds, detail for 4, desk for 3. Add the title “A little light for your desk” in the final shot. Use straight cuts and no new generated assets. ### Pause for practice Make the same sequence yourself or with the agent, then shorten the middle shot by one second and watch the effect. Restore the version you prefer. ### Debrief The sequence lasts approximately ten seconds, has no blank gap, and the title is readable on a phone-sized preview. Watch for this common trap: Changing an image duration can leave space before the next clip. Inspect the join rather than assuming the timeline closed it. ### Check understanding What is the best evidence that the first edit is ready? A. The agent said “done”. B. You played the whole sequence and checked every join. C. There are many timeline tracks. Answer: B. Completion is something you verify in the saved edit and playback, not only in a chat response. ## 02.01 Turn a vague request into an editing brief **Opening:** In this lesson, you will ask for an edit with a purpose, constraints and an observable result. ### Narration “Make it engaging” is a feeling. An editor still needs to know what would produce that feeling. For a review, it might mean starting with the verdict, showing the feature while you mention it, and removing the time spent sitting down. For a calm tutorial, the same request might mean longer holds and fewer distractions. A useful brief contains the audience, the message, the available sources, the target length and the boundaries. Boundaries protect what matters: keep the full warning, do not invent a price, preserve the speaker’s meaning, or use only uploaded music. Add one or two style choices, not a shopping list of effects. Give the agent a manageable first pass. Ask for structure before polishing every caption. When the first pass is ready, play it. If it missed the point, changing the font will not solve the underlying problem. Separate the story decision from the decorative decision and your feedback becomes much easier to act on. ### Demonstration cues 1. Show and explain: Open the project that contains your intended sources. 2. Show and explain: Name the source files or selected clips so the scope is clear. 3. Show and explain: Write the target audience, message, length and frame shape. 4. Show and explain: List what must stay and what should be removed. 5. Show and explain: Request a rough cut first, then review it before adding finishing work. ### Prompt demonstration Use my uploaded desk-lamp recording to make a 30-second 9:16 review. Start on the first useful sentence, remove sitting down and getting up, keep one benefit and one limitation, and end on my verdict. Preserve my wording and meaning. Make a rough cut with no music or new media first. ### Pause for practice Rewrite “Make this exciting” for a podcast clip and for a quiet cooking tutorial. Give each a different pacing instruction. ### Debrief Podcast example: remove repeated setup, retain the full argument and a natural breath. Cooking example: keep the safety instruction and hold each step long enough to follow. Watch for this common trap: A long prompt with incompatible demands, such as slow and calm plus a cut every half second, makes the result difficult to judge. ### Check understanding What should happen before you polish captions? A. Confirm that the edit tells the right story. B. Choose the most colourful preset. C. Generate a new background for every shot. Answer: A. Structure determines what viewers understand. Styling is more useful once the selected material works. ## 02.02 Use a style reference without copying everything **Opening:** In this lesson, you will attach a reference and explain exactly which qualities should influence your edit. ### Narration A reference works best when you can name what you like. You might admire the large opening title, the space around the subject, or the way a review uses a brief close-up to support a claim. Those are decisions you can describe and adapt. “Do exactly this” often imports details that do not fit your footage. Use Style reference for an image or video that guides the edit. Use Add footage for material that should appear in the finished video. These are separate actions. In this course edition, style references support images and videos, with up to four attached references. Video inspection covers the first two minutes. If the useful moment is later, supply a short excerpt you are entitled to use. A style reference is also different from a character or product reference used during generation. The first guides an edit’s look; the second guides the appearance of newly generated media. Neither guarantees an exact copy. The agent may fail to inspect a reference, in which case you should retry or describe it yourself rather than assume it was understood. ### Demonstration cues 1. Show and explain: Open Style reference in the dashboard or project chat. 2. Show and explain: Attach resources/style-layout.png, or your own permitted example. 3. Show and explain: Wait for upload and inspection. Read any failure message. 4. Show and explain: Describe two qualities to borrow and one quality to avoid. 5. Show and explain: Check the next edit against those specific qualities, not against an imagined perfect match. ### Prompt demonstration Use this reference for its large left-aligned title and generous space around the product. Keep my own footage, wording and orange accent. Do not copy its logo, soundtrack or subject. If you cannot inspect the attachment, tell me before editing. ### Pause for practice Attach one example. Write “Borrow…” and “Keep…” statements. If attachment access is unavailable, write the same guidance in plain text and complete the exercise without it. ### Debrief You can point to the borrowed layout decision in your result while the content remains yours. Watch for this common trap: Attaching a whole ten-minute video does not mean every moment was inspected. Narrow the example to the part that matters. ### Check understanding Where should a video go if you want it to appear in the finished edit? A. Only in Style reference. B. Through Add footage or the media library. C. In a comment without an upload. Answer: B. Style references guide decisions. Timeline source material must be available as footage. ## 02.03 Revise one thing and protect the rest **Opening:** In this lesson, you will give precise feedback and recover from an unwanted edit. ### Narration A first pass is something to respond to. Watch it as a viewer and name the moment that fails: “The title covers the lamp at six seconds” is actionable. “It is still bad” gives the agent no useful location or criterion. Make revision requests small enough to inspect. If you like the cuts but dislike the sound, say so and limit the next change to sound. Distinguish source time from timeline time. Source time is a position in the original file; timeline time is a position in your edited sequence. A cut changes the relationship between them. Use Undo promptly when a change damages the edit. Stop a running edit before making competing changes yourself. Keep a written brief and revision notes for important projects; do not rely on chat memory as the only record of the intended result. A useful revision log says what changed, why and whether the change survived review. ### Demonstration cues 1. Show and explain: Play the saved result and identify one specific problem. 2. Show and explain: Write its timeline time and the affected clip or text. 3. Show and explain: Ask for one change while naming what should stay. 4. Show and explain: Review that moment plus the joins before and after it. 5. Show and explain: Accept the result, or stop further work and use Undo to recover. ### Prompt demonstration At timeline 00:06, move the “Small desk” title away from the lamp and reduce its size slightly. Keep the wording, colour, music and all cuts unchanged. Show me the revised moment before doing anything else. ### Pause for practice Make a title deliberately too large, then correct only its placement and size. Record the before and after decision in one sentence. ### Debrief Only the requested title changes, and it remains visible long enough to read. If other parts changed, you notice and restore them. Watch for this common trap: Sending several correction requests while the first is still running makes it harder to know which result you are reviewing. ### Check understanding Which timestamp is clearest for fixing text in an edited sequence? A. “Somewhere near the middle.” B. “Timeline 00:06, the Small desk title.” C. “The original file has lots of text.” Answer: B. The timeline location and a named element identify the target even after earlier material has been cut. ## 03.01 Choose a hook that the footage earns **Opening:** In this lesson, you will open with a useful promise and support it with evidence. ### Narration A hook is a reason to keep watching. It does not have to be a shout or a surprising claim. “Here is why this lamp stayed on my small desk” creates a question the rest of the video can answer. A close-up showing the useful feature can do the same job without extra words. Watch the source before choosing the opening. Find the strongest complete statement, then check the sentences around it. Removing “for my small desk” from “this is the best lamp for my small desk” changes a personal judgement into a broader claim. An edit that attracts attention by changing the meaning is a poor edit. For the review project, use a simple sequence: reason to care, demonstration, limitation, verdict. These are story functions, not rigid time slots. If the demonstration takes longer than the opening, give it the time it needs. A useful ending answers the question raised by the beginning. ### Demonstration cues 1. Show and explain: Watch the raw take once without cutting. 2. Show and explain: Mark two possible opening statements and their source times. 3. Show and explain: Read or listen to the surrounding context for both. 4. Show and explain: Choose the opening that your later shots can support. 5. Show and explain: Arrange a rough sequence with a benefit, limitation and verdict. ### Prompt demonstration Find two possible hooks in my recording. Quote the exact spoken words with source times, explain what each promises, and flag any context that must stay. Recommend one without making the edit yet. ### Pause for practice Use the review recording script in the resource kit. Choose a hook and write the shot that will prove it. Then propose a second opening that uses a close-up instead of a spoken claim. ### Debrief Your hook is truthful, understandable without background knowledge and answered by the end. Watch for this common trap: A dramatic headline about battery life is unsupported when your footage only shows the lamp switching on. ### Check understanding Which hook is safest when no battery test was performed? A. “Lasts longer than every other lamp.” B. “The light I use for late-night notes.” C. “Scientifically proven to improve focus.” Answer: B. A description of the demonstrated use avoids inventing comparative or scientific evidence. ## 03.02 Trim setup and dead time without chopping speech **Opening:** In this lesson, you will remove unwanted starts, ends and pauses while preserving natural delivery. ### Narration The time before a person starts speaking usually belongs to the recording process rather than the story. You can remove sitting down, reaching for the camera and the final walk away. Leave enough space around the first and last words for them to sound complete. Trimming moves a clip’s edge. Splitting creates separate pieces at a chosen point. To remove a pause in the middle, split before and after the pause, delete the unwanted piece and check the resulting gap. Do not assume every delete closes space automatically. A blank frame or a silent hole can survive on the timeline. Not every pause is dead time. A breath before a conclusion helps a viewer follow the thought. Start conservatively, then compare the tighter cut with the original. If the speaker suddenly sounds nervous or words collide, restore a little space. Speed is useful only while meaning and comfort survive. ### Demonstration cues 1. Show and explain: Select the clip and play the first few seconds closely. 2. Show and explain: Drag the start edge just before the first intended word; check the first consonant. 3. Show and explain: Trim the end after the final word and a short natural release. 4. Show and explain: For an internal pause, place the playhead and use Split on each side. Remove only the unwanted section. 5. Show and explain: Close any unintended gap and play across every new cut at normal speed. ### Prompt demonstration Remove the setup before my first useful sentence and the ending where I leave. Tighten obvious dead air inside the review, but preserve breaths, complete words and the limitation. Do not speed up my voice. ### Pause for practice Record a sentence with a three-second pause in the middle. Make one very tight cut and one with a brief breath. Listen without looking at the picture and choose the more natural version. ### Debrief The first and final words are intact, and the internal cut sounds like a human sentence rather than a stitched list. Watch for this common trap: Using a silence threshold as an automatic delete rule can remove quiet words, deliberate pauses or soft music. ### Check understanding After deleting a middle section, what should you inspect? A. Only the thumbnail. B. The gap, the word boundaries and playback across the join. C. The app icon. Answer: B. The deletion can be technically successful while leaving an empty space or an unnatural speech boundary. ## 03.03 Use supporting shots to show the point **Opening:** In this lesson, you will place B-roll where it adds evidence and preserve the main audio. ### Narration B-roll is supporting footage shown while the main story continues. In a lamp review, a close-up of the switch belongs near the sentence about the switch. A random city skyline may look polished but adds little to that claim. Put a supporting shot on a visual track above the speaking clip when you want the narration to continue underneath. Check its audio: a noisy camera recording can compete with the speaker. Mute that supporting clip if you only need its picture. Listen again after the change so you do not accidentally mute the main voice. B-roll can hide a visible jump between two parts of a talking-head recording. It should still have a reason to be there. Start it around the idea being explained and end it when the viewer has had time to see the detail. Repeatedly cutting away before the viewer understands a shot makes the video feel busy rather than helpful. ### Demonstration cues 1. Show and explain: Identify one sentence that would benefit from a visual example. 2. Show and explain: Add a matching close-up to a track above the main recording. 3. Show and explain: Align it with the relevant sentence, using timeline time. 4. Show and explain: Mute the close-up audio if it is unnecessary. Keep the narration audible. 5. Show and explain: Play the sentence before, during and after the insert. Adjust its duration. ### Prompt demonstration Show my uploaded switch close-up while I explain the switch. Keep the main recording’s voice continuous underneath and mute the close-up’s camera audio. Use the real product shot, not generated replacement footage. ### Pause for practice Cover one visible talking-head jump with a relevant detail shot. Then remove the insert and compare what the viewer understands in each version. ### Debrief The insert supports a specific phrase, stays visible long enough to inspect, and does not interrupt the voice. Watch for this common trap: Putting two full-volume recordings on top of one another can create an echo or a distracting second conversation. ### Check understanding What makes a supporting shot useful? A. It illustrates the idea being discussed. B. It has the most camera movement. C. It was expensive to generate. Answer: A. Its job is to help the viewer understand or believe the point, regardless of how it was made. ## 04.01 Check the transcript before styling captions **Opening:** In this lesson, you will correct words and timing against the actual recording. ### Narration Captions help people follow speech when sound is quiet, unavailable or difficult to understand. They also make transcription errors public. Before choosing a style, listen for names, numbers, negations and product terms. “It does not charge” and “it does charge” are very different reviews. Ask the agent to caption the intended spoken clips, or use the available caption and transcript controls. Check which source is being transcribed. A project with music, camera audio and narration can contain several possible inputs. Finish the main speech cuts first so you do not spend time correcting captions that no longer match the sequence. Transcript corrections and visible caption clips may be separate. After correcting a transcript, confirm that the text on the timeline changed too; regenerate the relevant captions if necessary. Pasted scripts can help, but estimated timing is not the same as timing obtained from the recording. Always watch the displayed words with the sound on. ### Demonstration cues 1. Show and explain: Finish the main speech edit and identify the narration clips. 2. Show and explain: Ask for captions for those clips, or use the caption controls available in your editor. 3. Show and explain: Play the first sentence and check text, timing and punctuation. 4. Show and explain: Correct names, numbers and any missing “not”. Inspect the visible caption result. 5. Show and explain: Remove duplicate caption sets and replay a section after the last cut. ### Prompt demonstration Caption the spoken review on this timeline. Use the actual audio, preserve the words and flag anything uncertain. Check the product name and all numbers. Do not caption the instrumental bed or add a second overlapping caption set. ### Pause for practice Record: “This is a small desk lamp. It does not charge my phone.” Generate captions and verify every word. Deliberately change one word, then correct the visible caption. ### Debrief The words preserve the speaker’s meaning and appear with the relevant phrase. There is only one intended caption set. Watch for this common trap: Styling incorrect words makes the error more noticeable. Fix content before appearance. ### Check understanding An automatic caption drops the word “not”. What should you do? A. Leave it because the style looks good. B. Correct it against the recording and check the visible caption. C. Remove all captions. Answer: B. A small transcription error can reverse the claim. Verify the final displayed text, not just the transcript. ## 04.02 Separate captions from emphasis titles **Opening:** In this lesson, you will use stylish text without making the viewer read two competing messages. ### Narration Captions carry the speech. Emphasis titles carry the important idea. You can use both, but they need different jobs. If every spoken word becomes a giant headline, there is no hierarchy left and the product disappears behind text. For the review, keep captions near the lower part of the frame, with enough clearance for platform controls. Use a larger phrase such as “Small desk” beside the product when that idea arrives. The title can be shorter than the sentence because it is a summary. It must not change the claim. Choose one type family, a small set of sizes and one accent colour. Vidmoat’s orange works well as an accent, while dark or light neutral text can provide the main contrast. Check the actual frame: orange against a warm lamp shade may be hard to read. A restrained shadow or background can help, but a stack of glow, outline and gradient can obscure the letter shapes. ### Demonstration cues 1. Show and explain: Choose one readable caption style and apply it consistently. 2. Show and explain: Find the strongest three ideas in the edit and write short emphasis phrases. 3. Show and explain: Add one larger title for an idea, positioned away from the speaker and product. 4. Show and explain: Use orange on a key word or small accent, while maintaining clear contrast. 5. Show and explain: Play the title at normal speed and confirm it stays long enough to read once comfortably. ### Prompt demonstration Keep the speech captions readable and consistent. Add a larger “Small desk” emphasis title beside the lamp only when I discuss its footprint. Use orange as an accent, avoid covering the product, and do not animate every word. ### Pause for practice Make two title versions: a full spoken sentence and a three-word summary. Compare them on a phone-sized preview and choose the one that supports the picture. ### Debrief A viewer can tell which text is speech and which text is emphasis. Neither blocks the demonstration. Watch for this common trap: Using the same size, position and animation for all text makes everything compete for first place. ### Check understanding Which text should usually carry the complete spoken meaning? A. The captions. B. A decorative sticker. C. A one-word headline. Answer: A. Emphasis can summarise an idea, but captions should preserve the spoken content. ## 04.03 Make a vertical layout survive a phone screen **Opening:** In this lesson, you will check text, cropping and pacing at the size people will watch. ### Narration A title that looks comfortable on a laptop can become tiny on a phone. A caption that sits inside the video frame can still be covered by a platform’s controls. There is no single safe margin that works for every app, placement and device, so test the destination as well as your editor. Keep important faces, hands and words away from the extreme edges. For an initial layout, give text roughly a tenth of the frame width as breathing room and keep the lowest part of the frame clear of essential words. These are starting points, not platform specifications. A private or draft upload is the stronger check. Accessibility also involves timing. A fast reader may follow a flashing title that another viewer misses. Watch once without sound, then listen once without looking. The silent pass tests whether captions and pictures carry the message. The listening pass reveals rushed cuts and music that hides words. ### Demonstration cues 1. Show and explain: Reduce the preview to phone-like size or view a downloaded draft on your phone. 2. Show and explain: Check every caption line break and the smallest essential word. 3. Show and explain: Move text away from faces, hands and likely interface overlays. 4. Show and explain: Watch once muted, then listen once without watching. 5. Show and explain: Use a private destination preview where available to inspect real overlays before publishing. ### Prompt demonstration Review this vertical edit for phone readability. Check caption size, contrast, line breaks, edges and anything covering the product. Suggest specific timeline fixes. Do not claim a universal safe area for every social app. ### Pause for practice Ask someone to watch the draft once without pausing. Have them repeat the benefit and limitation. If they miss one, adjust the layout or duration and test again. ### Debrief Both the benefit and limitation remain understandable in one normal-speed viewing. Watch for this common trap: Shrinking captions to fit a long line often solves the layout while breaking readability. Rewrite line breaks or split the caption instead. ### Check understanding Why test a draft in its destination app? A. To guarantee more views. B. To see the real interface overlays and playback presentation. C. To make the source footage higher resolution. Answer: B. The destination can crop or cover parts of the frame differently from the editing preview. ## 05.01 Make the voice comfortable first **Opening:** In this lesson, you will balance and clean speech before adding music or effects. ### Narration A viewer may tolerate a slightly plain picture while learning something useful. A voice that is painful, muffled or buried is much harder to follow. Start with the original recording and headphones at a comfortable level. Listen for room noise, sudden level changes and distortion. Lowering the volume of a distorted recording does not undo the distortion. Noise reduction can soften steady background noise, but too much may make a voice watery or metallic. Compression reduces the difference between louder and quieter moments; it is not a cure for every recording problem. Make one modest adjustment and compare it with the untreated version. Select the intended clip before changing A/V or audio properties. If the voice and music were recorded together, ordinary clip volume changes both. Separating them perfectly is not something to assume. When a line is beyond repair, re-recording it in a quieter place may take less time and produce a better result than adding more processing. ### Demonstration cues 1. Show and explain: Mute added music temporarily and listen to the main voice. 2. Show and explain: Select the speaking clip and open its A/V or audio properties. 3. Show and explain: Adjust obvious level differences so sentences are comfortable to hear. 4. Show and explain: If needed, apply a small amount of noise reduction and compare before and after. 5. Show and explain: Listen on headphones and a phone speaker. Re-record an unusable line if possible. ### Prompt demonstration Inspect the voice in this clip and help make it easier to understand. Identify clipping or steady noise before changing settings. Use gentle processing, preserve a natural voice and tell me if the source cannot be repaired reliably. ### Pause for practice Record the same sentence near a fan and in a quiet corner. Try a gentle cleanup on the noisy take, then compare it with the quieter recording at similar listening levels. ### Debrief The voice is intelligible and natural. Your decision is based on listening, not on how many processing controls are enabled. Watch for this common trap: Boosting everything until it sounds louder can introduce clipping or make noise more obvious. ### Check understanding What should you try if noise reduction makes a voice metallic? A. Increase the processing further. B. Reduce it and compare with the original or re-record. C. Add a louder soundtrack. Answer: B. Processing has trade-offs. A quieter recording can be a better solution than aggressive cleanup. ## 05.02 Choose music that supports the edit **Opening:** In this lesson, you will balance a music bed and use transitions in sound deliberately. ### Narration Music changes how a scene feels before a viewer understands the words. A bright, light rhythm can suit a friendly tech review. A dense vocal song can compete with the review because the listener is trying to follow two sets of words at once. Choose by the job the music must do, not just by whether you like the track. Start with the voice at a comfortable level, then bring the music up from silence until it supports the pace. If the first sentence becomes harder to understand, the music is too prominent for that moment. Use fades to avoid abrupt starts and stops. Ducking lowers music while speech is present; check that it does not audibly pump between every word. The included practice-bed.wav is an original thirty-second rhythm for this course. It is useful for practising levels and fades, not a promise that one track will suit every genre. You can also use music you own or are licensed to use. A recognisable commercial song is not automatically permitted because it is available online. ### Demonstration cues 1. Show and explain: Import practice-bed.wav through the media library and place it on an audio track. 2. Show and explain: Trim it to the edit length and start it quietly under the voice. 3. Show and explain: Apply short fades at the opening and ending. 4. Show and explain: Use Duck under speech if available, or lower the bed manually during narration. 5. Show and explain: Listen to the quietest sentence and the ending. Adjust levels and fades before exporting. ### Prompt demonstration Use my uploaded practice bed under the review. Keep the voice clearly in front, fade the bed in and out, and lower it during speech. Do not add a vocal song or new sound effects. Check the quietest spoken sentence. ### Pause for practice Make one mix with music too loud, then a second with the voice clearly leading. Compare at the same device volume. Write what became easier to hear. ### Debrief Every word is understandable, the music enters smoothly, and the ending sounds intentional. Watch for this common trap: A louder mix can feel more exciting in a quick comparison. Match playback volume before deciding it is better. ### Check understanding What is the purpose of ducking? A. Lower music during speech. B. Make the video vertical. C. Identify a song’s copyright owner. Answer: A. Ducking creates room for the voice. It does not establish music rights or repair a poor source. ## 05.03 Ask the agent to listen and verify what it reports **Opening:** In this lesson, you will use audio inspection for music, sounds and sung words without treating estimates as certainty. ### Narration Speech transcription and audio understanding answer different questions. A transcript asks what was said. Audio inspection can help describe sounds, locate energy changes or estimate a beat. Lyric listening asks about sung or rapped words. A failed speech transcript does not prove that a song has no vocals. Give the agent a short range and a specific question. In this edition, source audio inspection normally begins with thirty seconds and supports explicitly selected excerpts up to two minutes. Results describe the inspected excerpt, not necessarily the final mix with every effect and track. Ask whether reported times are source, clip-local or timeline times before cutting on them. Lyric phrases may include uncertainty and their timing may drift. Listen to the actual recording and keep unclear words unresolved until you can verify them. Sound descriptions cannot reliably establish the song title or artist. The agent can also fail or be unavailable; that should lead to a manual check, not a guessed soundtrack description. ### Demonstration cues 1. Show and explain: Use sound-check.wav from the resource kit as a simple control. 2. Show and explain: Ask the agent to inspect the first ten seconds and describe the audible events. 3. Show and explain: Listen yourself: the file has two short tones beginning at two and six seconds. 4. Show and explain: For your own vocal music, request lyric listening and uncertainty explicitly. 5. Show and explain: Confirm words and edit points manually before turning the result into captions or cuts. ### Prompt demonstration Listen to the actual audio from source 00:00 to 00:10. Report audible events and the inspected range, with uncertainty. Do not infer sounds from the picture. For sung material, use lyric listening and mark unclear words instead of filling them from memory. ### Pause for practice Inspect the two-tone control and compare the report with what you hear. Then record or use an original sung phrase and test lyric listening. If unavailable, annotate it yourself and continue. ### Debrief You distinguish measured timing, model description and your own listening. You do not treat estimated lyric phrases as word-perfect karaoke captions. Watch for this common trap: “The model says it is rain” is not proof of sound identity. Check the recording, especially when extra events appear in silent sections. ### Check understanding Does failed speech transcription prove a clip has no singing? A. Yes. B. No; use lyric listening and listen to the source. C. Only if the video is vertical. Answer: B. Music and singing can fail a speech-focused path. Absence of a transcript is not evidence of silence. ## 06.01 Reframe the subject before adding effects **Opening:** In this lesson, you will choose fit, crop and position to protect the information in each shot. ### Narration Turning a landscape recording into a vertical video is a composition decision. A centre crop may keep the face but remove the hands demonstrating a product. Before choosing automatic reframing, decide what must remain visible in each moment. Select the visual clip and adjust its scale and position in Motion or the corresponding properties area. Move the playhead through the shot. A crop that works on the first frame can fail when the subject leans sideways. If you cannot keep both the face and the demonstration, consider a supporting close-up, a wider fitted view or a different source shot. Digital enlargement uses the pixels already available. A 4K export does not turn a badly focused small crop into genuine 4K detail. Judge the result at its intended viewing size. Prefer a slightly wider clean image to a close-up that makes the product impossible to inspect. ### Demonstration cues 1. Show and explain: Choose the final aspect ratio in Project Settings. 2. Show and explain: Select the clip and identify the essential subject and action. 3. Show and explain: Adjust scale and position without hiding hands, labels or the product feature. 4. Show and explain: Check the start, middle, end and any large subject movement. 5. Show and explain: Use another shot or a fitted layout if cropping removes essential evidence. ### Prompt demonstration Reframe this review for 9:16. Keep my face and the lamp demonstration visible. Inspect the moments where my hands move. If a crop loses the feature, suggest a wider layout or a cutaway instead of zooming further. ### Pause for practice Crop lamp-wide.png into a vertical frame, then compare it with a fitted version. Identify which choice better shows the lamp’s footprint. ### Debrief The intended feature is visible throughout its explanation, with no accidental head or hand cuts. Watch for this common trap: A frame that looks good while paused may fail during movement. Check the whole action. ### Check understanding What does exporting a blurry crop at 4K guarantee? A. New optical detail. B. A larger output frame, not recovered source detail. C. Perfect focus. Answer: B. Output dimensions and captured detail are different. Upscaling cannot guarantee recovery of information that was never recorded. ## 06.02 Add keyframes when the story needs movement **Opening:** In this lesson, you will create one controlled move and explain why it belongs there. ### Narration A keyframe records a property value at a particular time. Put a normal scale at the start of a moment and a slightly larger scale later, and the editor can move between them. The point is to guide attention, not to prove that you found the animation controls. For a review, a small push towards the product can underline a useful detail. For a tutorial, a brief zoom can help someone read a control. For a quiet interview, holding the frame may be the stronger choice. Movement feels more natural when its beginning and ending are gentle rather than mechanically abrupt. Try a small change first. Moving from 100 percent to roughly 108 percent over two seconds is an exercise starting point, not a universal recipe. Check the frame edges and source sharpness. If the editor uses a different scale unit, ask for an eight-percent relative enlargement. Preserve the subject’s position so the move does not drift away from the detail. ### Demonstration cues 1. Show and explain: Choose a two-second moment with a clear visual reason to move. 2. Show and explain: Select the clip and open Motion or its keyframe controls. 3. Show and explain: Set the starting scale and position at the beginning of the moment. 4. Show and explain: Add a later keyframe with a small enlargement and adjust the end position if needed. 5. Show and explain: Apply gentle easing where available, then play the move and compare with a still version. ### Prompt demonstration Add one gentle two-second push-in while I show the lamp switch. Enlarge by about eight percent relative to the current framing, keep the switch visible and use smooth easing. Leave other shots still. ### Pause for practice Create one push-in and one version with no move. Ask which version makes the feature easier to notice, and remove the motion if it adds no value. ### Debrief The movement supports the exact demonstration and has no sudden jump or unwanted crop. Watch for this common trap: Adding a zoom to every sentence makes all moments feel equally important and can cause visual fatigue. ### Check understanding What does a keyframe store? A. A property value at a specific time. B. An automatic promise of smooth video. C. The rights to a soundtrack. Answer: A. Animation comes from how property values change between times. You still need to judge the movement. ## 06.03 Correct colour before choosing a look **Opening:** In this lesson, you will make adjacent shots feel consistent without damaging skin or product colour. ### Narration Colour correction makes shots believable and compatible. A creative look adds a mood. Start with correction: can you see detail in the bright lamp shade, are shadows readable, and does a neutral object look strangely green or blue? Work on one representative shot before copying adjustments widely. Open Color on the selected clip and make small changes. Compare neighbouring shots rather than grading each one in isolation. A warm lamp and a window-lit desk may naturally look different; matching them does not mean forcing every pixel to the same colour. Preserve the intended lighting while avoiding distracting jumps. Be careful with skin. A global hue change moves skin and product colours along with the background. Do not brighten every face to one fixed target. People have different skin tones, and the surrounding scene matters. Use your eyes, available scopes and before-and-after comparisons. If a strong preset makes the lamp colour or skin implausible, reduce its influence or remove it. ### Demonstration cues 1. Show and explain: Select one representative shot and inspect bright and dark detail. 2. Show and explain: Correct obvious brightness or colour imbalance using small changes. 3. Show and explain: Compare the next shot at the cut and adjust distracting differences. 4. Show and explain: Try a restrained look only after the correction works. 5. Show and explain: Toggle the treatment and inspect skin, neutral objects and the actual product colour. ### Prompt demonstration Make these two shots feel consistent while preserving the warm desk light. Keep skin natural and avoid rotating every hue. Protect detail in the bright shade. Make small corrections first, then show me the comparison before adding a stronger look. ### Pause for practice Apply a strong preset, note what happens to a neutral surface and the product, then reduce or replace it. Explain the version you choose. ### Debrief Shots feel related, key detail remains visible, and the grade does not misrepresent the product. Watch for this common trap: Choosing the most dramatic preset in isolation can create inconsistent shots or unnatural skin. ### Check understanding What should usually come first? A. A strong creative look. B. Basic correction and shot consistency. C. Maximum saturation on every clip. Answer: B. A consistent base makes later creative choices easier to control. ## 07.01 Decide whether a new asset is needed **Opening:** In this lesson, you will choose between filming, existing media, stock and generation. ### Narration A missing shot does not always need an AI generation. If you need to show the real lamp switching on, filming the real switch gives more trustworthy evidence. If you need an abstract illustration of a late-night idea, a generated image may be appropriate. Write the job of the missing asset before opening Generate. Describe the subject, action, framing, lighting and intended placement. Ask for one useful asset first. Large batches can consume credits before you know whether the direction works. Check the available provider, plan and price shown in your account; this course does not require paid generation to complete the main projects. Generated media can invent lettering, change a product feature or create continuity problems. Inspect it before importing it into the final sequence. Do not present a generated demonstration as proof of a real product’s performance. When generation is unavailable, use the included illustrations, a simple title card or another shot you can record yourself. ### Demonstration cues 1. Show and explain: Identify the exact gap in your story and write the job of the missing shot. 2. Show and explain: Decide whether real footage is necessary to support the claim. 3. Show and explain: If generation fits, open AI Generate and choose image or video. 4. Show and explain: Review the displayed cost and settings; request a single short or still asset first. 5. Show and explain: Inspect the result, then add it to the timeline only if it serves the brief. ### Prompt demonstration Create one illustration of a quiet desk at night, with open space on the left for my own title. Warm light, simple composition, no text or logos. This is a concept illustration, not a photograph of the product I am reviewing. ### Pause for practice List three missing shots for your project. Mark each “film”, “reuse” or “generate”, and explain the choice. Complete one with the lowest-cost suitable method. ### Debrief Every new asset has a defined purpose, and evidence about real products still comes from real material. Watch for this common trap: Generating a better-looking product image can accidentally show features the product does not have. ### Check understanding Which shot most needs real evidence? A. An abstract background for a title. B. A demonstration that a specific charger powers a phone. C. A fictional orange robot in a story. Answer: B. A performance claim should be supported by an actual demonstration, not a generated substitute. ## 07.02 Keep a character or product recognisable **Opening:** In this lesson, you will use optional references and a continuity checklist across generated shots. ### Narration Consistency is a choice. A mood montage may need varied subjects; a three-shot story about one robot needs a recognisable robot. Decide before generating. A text-only request remains a valid way to create a fresh subject. For a continuing character, prepare a clean reference image and a short description of the features that must stay. Our original reference is an orange desk robot with a round head, dark face panel, two pale eyes and a small antenna. Keep that description stable while changing only the action or camera view between shots. Use Character / product reference in Generate when the selected provider supports it. In this edition, reference-led image and video generation uses Grok; current controls impose limits that differ by media type. Video references are limited to the supported resolution shown in the interface, currently up to 720p. Reference similarity is guidance, not an identity guarantee. Check colour, face, proportions, accessories and background continuity in each result. There is no saved character library to assume; keep your own reference file and brief. ### Demonstration cues 1. Show and explain: Choose whether this story actually needs the same subject across shots. 2. Show and explain: Attach resources/robot-reference.png using Character / product reference in Generate. 3. Show and explain: Write the character’s fixed features and the action for shot one. 4. Show and explain: Reuse the same reference and fixed features for the next shot; change only the action or framing. 5. Show and explain: Compare results side by side. Reject visible drift before building the sequence. ### Prompt demonstration Use the attached orange robot as the same fictional character. Preserve the round head, dark face panel, two pale eyes and antenna. In this shot it notices a desk lamp. Keep the design simple and do not add lettering. Use the reference only because this story needs continuity. ### Pause for practice Plan three shots: the robot notices the lamp, reaches towards it, and sits in the warm light. Generate one if your account allows it, or use the original reference as a still and practise framing. Fill in the continuity checklist for each shot. ### Debrief You can name what stayed consistent and what drifted. You do not claim that all generated shots are identical. Watch for this common trap: A style reference attached in chat does not automatically become a generation identity reference. ### Check understanding When should character consistency be required? A. In every generated image. B. When the story needs a continuing recognisable subject. C. Only when no reference exists. Answer: B. Consistency serves the story. It is optional for work that benefits from different subjects. ## 07.03 Use generated voice and music thoughtfully **Opening:** In this lesson, you will plan original narration or music and evaluate the actual result. ### Narration Generated narration can help when you cannot record a voice, but the script still needs to sound like a person. Read it aloud before generating. Short sentences and concrete words usually survive better than a paragraph packed with slogans. Use the same available voice selection across a series when continuity matters. For music, describe the role: a light instrumental bed under speech, a sparse reflective opening, or a short energetic ending. If a generation option supports vocals, say whether you want original lyrics or an instrumental. Do not assume a successful generation request produced the requested words; listen to the output. Avoid imitating a real person without appropriate permission. Check the terms that apply to any generated or licensed asset before commercial distribution. Keep a copy of your prompt, selected settings and asset origin. If generation is unavailable or outside your budget, record your own narration and use the supplied practice bed. The editing skills are the same. ### Demonstration cues 1. Show and explain: Write a narration of roughly 40 to 60 words for a short demonstration and read it aloud. 2. Show and explain: Use the available voiceover generation control, or record your own voice. 3. Show and explain: Listen for incorrect names, odd pauses and an unnatural pace. 4. Show and explain: For an optional music generation, request a clear mood, duration and instrumental or vocal intent. 5. Show and explain: Import the accepted assets, balance them against each other and verify any words by listening. ### Prompt demonstration Create an original, light instrumental bed for a friendly desk-product demonstration. Leave room for narration, avoid vocals and a huge dramatic ending. I will review the actual audio before using it. ### Pause for practice Read the supplied lamp narration naturally and time it. If it runs long, remove one idea instead of rushing every word. Use recorded or generated narration and compare it with the silent version. ### Debrief The narration fits the available time without sounding hurried, and the soundtrack supports rather than competes with it. Watch for this common trap: Asking for a famous singer’s voice or assuming generated lyrics are accurate creates avoidable problems. ### Check understanding What proves that generated audio contains the intended words? A. The original prompt. B. Listening to the output and checking it. C. The filename. Answer: B. A prompt describes intent. The produced audio is what viewers will actually hear. ## 08.01 Turn a conversation into a complete short clip **Opening:** In this lesson, you will select a podcast moment that remains fair and understandable outside the full conversation. ### Narration A good podcast clip is a small complete thought. It gives enough context, makes a point and reaches a payoff. Starting on an exciting phrase can fail if the phrase depends on a question the viewer never heard. Use the original podcast script in the resource kit or a conversation you have permission to edit. Listen for the claim and the qualification. Our example says that a simple filming routine helps consistency, while acknowledging that some projects need more preparation. Keep that qualification if removing it would change the advice. In a two-person recording, frame the relevant speaker without cutting away so quickly that reactions become distracting. Captions should identify the words, while a short opening title can state the topic. Avoid generated reaction shots presented as real responses. A pause, a nod or a slight hold can carry useful meaning. ### Demonstration cues 1. Show and explain: Find a 30 to 45 second segment containing one complete point. 2. Show and explain: Retain the question or add a truthful short context title when needed. 3. Show and explain: Trim repetition while preserving qualifications and natural turns. 4. Show and explain: Frame the active speaker and add corrected captions. 5. Show and explain: Watch as if you have never heard the original episode. ### Prompt demonstration Make a standalone podcast clip about keeping a simple filming routine. Preserve the speaker’s qualification about projects that need preparation. Keep enough context to understand the advice, caption the actual words and avoid invented reactions. ### Pause for practice Record both parts of the supplied conversation yourself or with a consenting partner. Make a 30 to 45 second edit and ask a new viewer what advice they understood. ### Debrief The viewer can summarise the point, and the speaker would recognise the meaning of their original answer. Watch for this common trap: Removing every qualifier can make a thoughtful opinion look like an absolute claim. ### Check understanding What should you protect when shortening an interview? A. Only the funniest word. B. The speaker’s meaning and necessary context. C. Every pause regardless of length. Answer: B. You may shorten delivery, but the resulting claim must remain faithful to the conversation. ## 08.02 Make a tutorial someone can follow **Opening:** In this lesson, you will show a task in the order a beginner needs and hold important actions long enough. ### Narration A tutorial succeeds when someone can do the task after watching. It may need a slower pace than a social montage. Start by showing the finished result, then explain the small number of steps needed to reach it. For the small-business project, film how to wrap a notebook as a simple gift. This avoids private customer information and lets you demonstrate a practical process with ordinary objects. Show the paper, the fold and the final presentation. Keep the action in frame; your face is optional when the hands teach the task. Use numbered step titles and narration that matches the current action. Do not cut from a half-completed fold directly to the finished object if that missing movement is what the learner needs. A small zoom can clarify a detail, but a sudden transition can hide it. Replay the tutorial with the question “Could I copy this without guessing?” ### Demonstration cues 1. Show and explain: Film the finished object and three clear steps from a stable position. 2. Show and explain: Arrange a quick result preview followed by the steps in order. 3. Show and explain: Remove waiting time, but keep the essential hand movements. 4. Show and explain: Add short numbered titles and captions for any spoken instructions. 5. Show and explain: End on the finished object and one honest next step, such as trying it with a different paper. ### Prompt demonstration Make a 45-second beginner tutorial from my notebook-wrapping footage. Show the finished result first, then three numbered steps. Keep the hand movements needed to follow each fold. Use simple text and hold the final result for a moment. ### Pause for practice Give your edit to someone who has not seen the recording. Ask them to describe or repeat the steps. Note the first place they need clarification and revise it. ### Debrief The task can be followed in order, with no essential action hidden by a cut or title. Watch for this common trap: Fast editing is not automatically helpful teaching. A missing step costs the viewer more time than a slightly longer shot. ### Check understanding Which part should a tutorial retain? A. An essential movement that explains the step. B. Every second of setup. C. A transition over the hardest detail. Answer: A. Remove waiting, not the evidence someone needs to reproduce the action. ## 08.03 Build a short visual story **Opening:** In this lesson, you will create a beginning, change and payoff using images, footage or optional generated shots. ### Narration A story needs a change. Three attractive images become more interesting when the first establishes a situation, the second changes it and the third shows the result. Our fictional robot begins at a dim desk, discovers a lamp and ends in a warmer working space. You can tell this story with the included stills and reframing, with your own filmed object, or with optional generated shots. The core assignment does not depend on generation. Plan the sequence first so you know what each shot contributes. Sound can make the change clearer. Start quietly, introduce a small sound when the lamp turns on, and let the ending breathe. If you add a switch sound that was not in the recording, treat it as designed sound rather than claiming it was captured live. Keep on-screen words sparse; a visual story can often work with only an opening or ending line. ### Demonstration cues 1. Show and explain: Write the situation, change and result in one sentence each. 2. Show and explain: Choose three to five shots from your own material or the original course illustrations. 3. Show and explain: Build a 20 to 30 second sequence with a clear turning point. 4. Show and explain: Use one deliberate sound or music change at that turning point. 5. Show and explain: Check character or object continuity and show the ending long enough to register. ### Prompt demonstration Build a 30-second fictional desk story: a quiet desk, discovery of the lamp, then a warm place to work. Use my supplied assets, one restrained musical change and minimal text. Keep the same robot only if it appears in more than one shot. ### Pause for practice Create two endings: a quick cut to black and a two-second hold on the result. Ask which ending makes the change clearer. ### Debrief A viewer can say what changed between the first and final shots, even with no narration. Watch for this common trap: A montage of unrelated attractive shots may have atmosphere but no understandable change. ### Check understanding What gives this short story its structure? A. A situation, a change and a result. B. Exactly one transition per shot. C. Maximum generated media. Answer: A. A clear change gives the sequence direction. Visual polish then supports that structure. ## 09.01 Choose an export that fits the job **Opening:** In this lesson, you will distinguish frame shape, resolution and quality, then verify a finished file. ### Narration Aspect ratio describes the shape of the frame. Resolution describes its pixel dimensions. Quality settings affect how the result is encoded. These are related but different decisions. A high-quality setting does not automatically change a vertical project into a landscape one or recover lost source detail. Use Project Settings for the intended frame shape and check the actual dimensions displayed in Export. For a vertical HD delivery, 1080 by 1920 is a useful target when your account and sources support it. A landscape HD delivery is 1920 by 1080. Free or limited accounts may export at a lower resolution and include Vidmoat branding. Use the available output for learning rather than treating an upgrade as a course requirement. Start with a draft to check the edit cheaply and quickly. For delivery, MP4 is a practical option when offered. Use a frame rate that suits the source and destination; changing 30 fps footage to 60 fps does not create genuine captured motion. Watch the downloaded file all the way through. The timeline preview is not the final delivery check. ### Demonstration cues 1. Show and explain: Confirm the intended shape in Project Settings. 2. Show and explain: Open Export and read the actual output dimensions and any plan restriction. 3. Show and explain: Choose MP4 and suitable frame rate and quality settings where available. 4. Show and explain: Render one draft, review it, then produce the required final version. 5. Show and explain: Download and play the final file, checking the start, joins, captions, sound and ending. ### Prompt demonstration Prepare an MP4 for vertical phone viewing. Check the current canvas and permitted output dimensions, preserve the intended frame rate, and tell me about any branding or resolution limit before rendering. Do not start duplicate render jobs. ### Pause for practice Export your ten-second sequence first. Inspect the file dimensions and play it outside Vidmoat. Record the settings and one thing you checked. ### Debrief The actual file opens, has the expected shape and permitted dimensions, and plays correctly to the end. Watch for this common trap: A successful render status does not prove the captions are readable or the final word is intact. ### Check understanding Which number describes a vertical Full HD frame? A. 1920 by 1080. B. 1080 by 1920. C. 1080 by 1080. Answer: B. The taller dimension comes second: width by height. Check the dimensions, not just a preset label. ## 09.02 Diagnose the problem before repeating the request **Opening:** In this lesson, you will separate upload, preview, agent and render failures and take a focused next step. ### Narration “It is not working” can describe several different stages. An upload failure means the source may not be available. A preview failure may happen even when the source exists. An agent failure can leave a valid project unchanged. A render failure concerns producing the output file. Repeating the same prompt across all four does not diagnose any of them. Start with the smallest check. Does the file appear in the library and finish uploading? Does a single clip play? Did the agent actually change the timeline? Does the export have a job reference or a specific error? Record the stage and the message before retrying. On a phone, keep the app active while finishing an upload and check network stability. For an incompatible source, a compatible copy such as H.264 video with AAC audio in an MP4 container can be a useful troubleshooting option; keep the original. A retry should address a likely cause. Several simultaneous exports can add queue pressure without fixing the problem. ### Demonstration cues 1. Show and explain: Name the failed stage: upload, preview, agent action or export. 2. Show and explain: Check the source upload and saved state before closing anything. 3. Show and explain: Test a short single-clip sequence to isolate the issue. 4. Show and explain: Use the visible Retry or recovery action once after addressing the cause. 5. Show and explain: If it persists, use Get help with the project, failed stage, time and error or job reference. ### Prompt demonstration Diagnose this project before editing again. Check whether the source upload completed, whether the selected clip is available, whether the last agent run applied changes, and whether an export job already exists. Report the failing stage and the next useful step. ### Pause for practice Use the troubleshooting worksheet to describe a hypothetical case where the preview is black but the file is in the library. List two checks before deleting anything. ### Debrief You investigate clip placement, source availability and decode or preview errors, while preserving the original file and project. Watch for this common trap: Deleting a project to fix one failed preview can destroy useful work without addressing the source problem. ### Check understanding What should you do before starting another export? A. Check whether one is already queued or running and read its status. B. Click Export repeatedly. C. Delete the source. Answer: A. A duplicate job spends resources and may add delay. Check the existing job first. ## 09.03 Review the final file like an editor **Opening:** In this lesson, you will perform a structured quality check and prepare the correct delivery. ### Narration The final review is where separate choices become one experience. Watch the file at normal speed without stopping. Write down the moments that distract you, then return to them. Constantly pausing during the first pass can hide pacing problems. Use three passes. First, story: does the opening make sense and does the ending answer it? Second, picture and text: are important details visible, words correct and layouts readable? Third, sound: is the voice clear, are levels comfortable and does the ending finish cleanly? A final phone viewing catches problems that a large screen can disguise. Save the file with a name that identifies the project, shape and revision. Keep the source project and a note of the settings. A share link and a downloaded file are different deliveries. Sharing publicly is a separate decision; check permissions and the destination before posting. For the course, a private file is enough. ### Demonstration cues 1. Show and explain: Watch the downloaded file once without pausing and record distractions. 2. Show and explain: Check the hook, evidence, qualification and verdict. 3. Show and explain: Inspect captions, cropped details, blank frames and the final frame. 4. Show and explain: Listen to quiet words, music fades and transitions at comfortable volume. 5. Show and explain: Name the accepted file, save the settings and keep a copy with your project notes. ### Prompt demonstration Review the saved edit for story clarity, text readability, framing and possible audio issues. Name any limitations of your review. I will also play the downloaded file myself before delivery. ### Pause for practice Review the tech project with the capstone rubric. Find at least one improvement, make it, and compare the final file with the previous version. ### Debrief The delivered file is the reviewed revision, not an earlier export with the same vague name. Watch for this common trap: An AI review of sampled frames cannot prove continuous playback or the sound of the final mix. ### Check understanding Which file should you deliver? A. The newest filename without watching it. B. The exact exported revision you reviewed and accepted. C. Any preview screenshot. Answer: B. Version control at delivery prevents a good edit from being replaced by an older or unchecked file. ## 10.01 Build your capstone from a fresh brief **Opening:** In this lesson, you will complete a short video using the course workflow with less step-by-step help. ### Narration Your capstone is a chance to make decisions yourself. Choose a review, a podcast clip, a tutorial or a short visual story. A thirty to sixty second result is enough if it has a clear purpose and careful execution. Length is not evidence of skill. Begin with a fresh brief and your own material or the original course assets. Plan the story before asking the agent to act. Save the first rough cut as a reference in your notes, then improve structure, captions, sound and picture in separate passes. You may use generation if it helps, but it earns no extra marks simply for being present. The submission contains the final video, your brief and a short decision log. Explain two changes you made after reviewing the first pass and one AI result you checked manually. If you use the lamp illustrations, describe the piece as a concept demonstration. If your plan adds branding or limits resolution, state that; the rubric assesses your editing within the tools available. ### Demonstration cues 1. Show and explain: Choose a project lane and complete the one-page brief. 2. Show and explain: Prepare sources, permissions and a short shot or scene list. 3. Show and explain: Build a rough cut, then revise structure before finishing details. 4. Show and explain: Export, review on a phone and score the result with the rubric. 5. Show and explain: Submit the video, brief, settings and decision log to your reviewer or your own portfolio folder. ### Prompt demonstration Help me execute this capstone brief in stages. Start by checking the sources and proposing a rough structure. Keep the audience and non-negotiables visible. Pause after the rough cut so I can review before captions, sound and polish. ### Pause for practice Complete one 30 to 60 second capstone. Budget 60 to 90 minutes for editing and review, plus filming time if you need it. ### Debrief The submission has a clear viewer, a supported message, a complete ending and evidence of at least two purposeful revisions. Watch for this common trap: Copying every instruction from a showcase without adapting it to your own source does not demonstrate judgement. ### Check understanding What earns credit in the capstone? A. Purposeful decisions that improve the viewer’s experience. B. Using every generation tool. C. The largest possible file. Answer: A. The assessment rewards communication, accuracy and craft, not spending or feature count. ## 10.02 Give feedback someone can use **Opening:** In this lesson, you will evaluate a video against criteria and turn observations into revisions. ### Narration Useful feedback describes an effect on the viewer and points to a place in the edit. “At twelve seconds I could not read the second line before it disappeared” gives the editor something to fix. “I dislike that font” may be a preference, but it needs a connection to the brief to become useful guidance. Review the video before reading the creator’s explanation. Write what you think it is trying to communicate. Then compare your interpretation with the brief. A mismatch may reveal an unclear opening, missing evidence or an ending that introduces a new idea too late. Use the rubric consistently and separate required fixes from optional tastes. A missing negative word in a caption is an accuracy problem. Choosing a slightly warmer orange may be a preference. Give the creator room to solve the problem instead of prescribing every click. If you are studying alone, leave the edit for a while and return as a new viewer. ### Demonstration cues 1. Show and explain: Watch once and write the message you understood. 2. Show and explain: Read the brief and score each rubric category using visible evidence. 3. Show and explain: Name one strength that should be preserved. 4. Show and explain: Give two timestamped fixes and explain their effect on understanding. 5. Show and explain: Have the creator revise and resubmit the affected sections. ### Prompt demonstration Assess this edit against my brief. Give one strength and two specific improvements with timeline times. Separate factual or readability problems from personal taste. State what you could inspect and what needs human playback. ### Pause for practice Exchange projects with a peer, or review your own after a break. Use the format “At [time], I noticed [issue], which made [effect]. Try [direction].” ### Debrief The editor can act on the feedback, and your score is supported by something observable in the video. Watch for this common trap: A numerical score without evidence does not explain how to improve. ### Check understanding Which feedback is most useful? A. “Bad captions.” B. “At 00:12 the second line disappears before I can read it; hold or split it.” C. “Use my favourite style.” Answer: B. It identifies the location, the viewer problem and a practical direction without dictating every detail. ## 10.03 Create a routine you can repeat **Opening:** In this lesson, you will build a reusable brief, review checklist and learning plan. ### Narration Finishing one video gives you a process you can repeat. Keep the parts that worked: a brief template, a small caption system, an export checklist and a folder of source files you are entitled to reuse. Keep prompts as starting points, not as commands that must fit every genre. After publishing, look for evidence that matches the purpose of the video. A tutorial might be judged by whether people complete the task; a review by whether viewers understand the trade-off; a business clip by qualified enquiries. Views alone cannot tell you all of that. Use the analytics available on the destination and direct feedback, while remembering that a tiny sample can mislead. Change one important thing at a time when comparing versions. A stronger opening, shorter explanation or clearer title is a useful experiment. Replacing the audience, soundtrack, length and format together makes it difficult to know why the result changed. Your next goal is three finished videos with deliberate improvements, not one endlessly polished draft. ### Demonstration cues 1. Show and explain: Save your brief, prompt and final review checklist in one reusable folder. 2. Show and explain: Write a simple style note covering captions, titles, colour and sound. 3. Show and explain: Choose one meaningful outcome for the next video. 4. Show and explain: Plan three small videos with one improvement to test in each. 5. Show and explain: Keep a short log of source, decision, result and next change. ### Prompt demonstration Turn the decisions that worked in this project into a reusable editing brief and review checklist. Keep them adaptable to other sources. Separate my style preferences from the facts that must be checked for each new video. ### Pause for practice Plan your next three videos. For each, name a viewer, a question, a source you already have and one skill to improve. ### Debrief You leave with a repeatable workflow: brief, prepare, rough cut, review, polish, export and learn. Watch for this common trap: A template should reduce repetitive setup, not force every story into the same pace or layout. ### Check understanding How do you make a comparison easier to interpret? A. Change every variable at once. B. Change one important element while keeping the purpose comparable. C. Judge only by your own favourite frame. Answer: B. A focused change gives you a clearer reason for any difference, although small audience samples still need caution.