Professional development concepts through demonstrations, teach-backs and evidence-based assessment. 8 designed hours; actual participation is reviewed separately. Each module asks you to do the practical work on the setup you expect to teach with. Keep a before and after example and check that someone else can replay or reopen it. Teach the method to a colleague or reviewer, score the sample case, and revise after feedback. Record the time you actually spend. If equipment is unavailable, mark the hands-on skill for a later check. Before each demonstration, identify the source, route and playback conditions and ask for a prediction. After the comparison, ask what changed, what stayed fixed and what remains untested. If the explanation misses the point, use a simpler example and check again.
8 modules plus a final portfolio review.
Preview: Teach instructions versus sound
Show the difference between MIDI instructions, an instrument's sound and a portable audio reference.
Prepare
Choose a school-approved DAW that creates instrument tracks and edits notes. Test MIDI import/export, audio export and project reopening with a student account. Assign a built-in pitched instrument. Download the First Steps MIDI, event table and both renders. If MIDI export is absent, retain the native editable project and event table; mark MIDI exchange as not demonstrated. No keyboard is required.
Student lesson to teach
One performance, two sounds: Imagine handing the same tune to a piano player and a bell player. The tune can survive even though its sound changes. MIDI stores instructions such as which note starts, when it starts, and how strongly it begins. A virtual instrument turns those instructions into sound. Audio stores that result. The project connects notes, instruments and other choices. To keep your work useful, preserve the editable performance, the instrument settings and a listening copy. A note number is a useful shared pitch label because applications may use different octave names.
Build one playable route: A playable route has two sides. Notes go into an instrument; audio comes out. In your DAW, locate the project play/stop controls, an instrument track, the note editor and the audio output. A track may need to be selected or armed before it accepts a controller. Its on-screen keyboard is a useful test input. If that works but your physical keyboard does not, the instrument can already make sound: investigate the incoming controller route. Start at a comfortable listening level and test one note before adding more tracks.
Record a phrase worth keeping: A short deliberate performance is easier to improve than a long accidental one. Use eight to sixteen notes with a beginning and an ending. You may play, draw or combine both methods. Leave a little space after the final note so its release can finish. Save the editable version before rendering. Rendering makes an audio copy; it does not remove your need for the note version. Include the instrument name, preset and tempo in the notes so the next person has a useful starting point.
Prove the handoff opens: A download icon proves that a file was created, not that your work can be recovered. Test a copy while keeping your original safe. Open the project from its saved location, play its phrase, and compare it with the audio reference. Open the audio outside the DAW. If possible, import the MIDI into a fresh project and choose an instrument. That last test checks event exchange, not exact sound recovery. A clear report of a missing instrument is more useful than an unchecked claim that everything works.
Teaching principle
The educator plays identical notes through two sounds, keeps performance/state/audio separately and reopens the delivered copy. Drawn notes are accepted as an equal entry route.
Student practice sequence for your demonstration
One performance, two sounds: Import first-steps.mid, or enter the first four events from the table. Set 96 BPM. Choose a pitched instrument and play the phrase. Keep the note events unchanged. Choose a contrasting instrument and replay. Describe attack or release rather than only good/bad. Save the original MIDI and record both instrument names in your project notes. Evidence: Three sentences explaining MIDI, audio and project roles; one unchanged musical feature and one changed sound feature.
Build one playable route: Create one instrument track and select a built-in pitched sound. Enter or play notes 60, 64 and 67 separately at moderate velocity. Label the note input, instrument, track audio and output in a simple route drawing. Save the project with a name you will recognize, then reopen it before continuing. Evidence: A route drawing and a saved project with three notes; state whether input was drawn, on-screen or physical.
Record a phrase worth keeping: Make an original 8–16-note phrase, using First Steps only as practice if needed. Listen once without editing; name one intended focal note. Save the editable project and export MIDI if available. Export audio including the final tail. Name the files consistently and record tempo, instrument and preset. Evidence: Editable performance or native project, audio render and a short instrument/tempo record.
Prove the handoff opens: Fill in the handoff template with real filenames and instrument dependencies. Save a copy, close the working project and reopen the saved copy. Play the exported audio in a separate player and check its beginning and ending. Reimport MIDI where supported; record each test as passed, failed or not available. Evidence: A completed handoff record with actual results and a correction for any failed check.
Demonstrate
Play First Steps A, then B. Follow the event table. Identify one repeated musical feature and one changed sound feature. The supplied renders are simple teaching synthesizers, not recordings of named commercial instruments.
1. Import first-steps.mid, or enter the first four events from the table. Set 96 BPM. 2. Choose a pitched instrument and play the phrase. Keep the note events unchanged. 3. Choose a contrasting instrument and replay. Describe attack or release rather than only good/bad. 4. Save the original MIDI and record both instrument names in your project notes.
Ask the student diagnostic: You send only the MIDI file. Must the recipient hear your instrument? Collect an explanation, not just yes/no. Offer text or spoken/transcribed response.
Practice and teach back
Change one note instruction, switch the instrument sound and compare each result with a rendered WAV.
Case to assess
An educator says MIDI contains the exact synth sound and accepts a download notification as recovery proof.
Evidence
A MIDI export where supported, or the native editable project and event table; two audio renders and an explanation of what each file preserves.
Full lessons, listening files and downloads require enrollment. Answer keys require separately approved instructor access. Completion is based on reviewed work; certificates are not issued automatically.