Collab Performances and Guest Musicians

Why This Lesson Matters

Sequence you are in:

• Previous: Music Rights and Safer LIVE Choices (MU-07) — repertoire tiers before you invite someone else's catalog into your room
• This lesson: Collab Performances and Guest Musicians (MU-08) — run-of-show, audio plan, promo, recovery
• Next: Monetizing Music LIVE Ethically (MU-09) — soft monetization layers that do not hard-sell the concert

Prerequisites in spirit: Performance Audio (MU-02) and Requests / Interaction Systems (MU-05). Brief callback only: Community guest-hosting lessons (CM-07) help with hospitality; this lesson stays on musician collab ops — signal flow, monitoring, and performance roles.

Skip this and collabs become hope-plus-panic. Complete it and Capstone reviewers can see you host a shared stage on purpose.

Learning Objectives

By the end of this lesson, you will be able to:

• Write a collab run-of-show with timed segments, owners, and repertoire gates
• Complete a Guest Audio Plan covering sources, monitoring, latency, and fail-safes
• Assign clear roles for host, guest, and (if present) chat/mod support
• Plan promo without overpromising or last-minute chaos
• Run a troubleshooting recovery sequence under pressure during a collab
• Deliver rehearsal evidence with a guest or a documented solo simulation of guest roles

Estimated Study Time

• Study and templates: about 30 minutes to draft run-of-show and audio plan
• LIVE Mission: rehearsal with guest OR full solo simulation with role docs filed
• First full pass: roughly 90–120 minutes including promo checklist and a short tech rehearsal

Prerequisites

Complete Performance Audio for Musicians on LIVE (MU-02) and Requests, Tips, and Fan Interaction Systems (MU-05). Complete MU-07 so guest repertoire is tiered before you promote it.

Recommended: Guest Hosting That Elevates Both Audiences (CM-07) for hospitality framing.

You should already have:

• A working solo performance-audio pass (MU-02)
• A request/interaction policy you can explain in one sentence (MU-05)
• Willingness to postpone a collab that fails audio rehearsal

Main Lesson

Roles before songs

Write roles in plain language on the run-of-show header:

• Host — owns stream start/end, room rules, repertoire veto, recovery calls
• Guest musician — owns their parts, their inputs, and their promo sentences
• Optional third — mod/chat lead, or a second player with a defined seat (not "whoever feels it")

Collab run-of-show structure

Use the Collab Run-of-Show Template. Minimum blocks:

1. Pre-LIVE — call time, soundcheck window, repertoire lock, rights tier check (MU-07) 2. Open — host welcomes; guest intro in one breath; show promise for tonight 3. Shared set blocks — song order with who leads, who supports, talk breaks 4. Solo feature windows — each artist gets a defined spotlight without apology 5. Interaction window — requests only if both agreed; otherwise park requests 6. Promo exchange — handles, next LIVE times, how to find each other 7. Close — thank-you, next solo shows, hard out time

Time-box everything. An open-ended "we'll jam" is how you overrun voices and patience.

Guest audio plan — logistics that matter

Open the Guest Audio Plan Worksheet. Document:

Sources

• Vocal mics (count, type, stands)
• Instruments (acoustic mic, DI, amp mic — pick one primary path per source when possible)
• Backing tracks / click — who owns playback; one clock only
• Platform guest audio vs local mixer — know which world you are in

Monitoring

• What each performer hears (phone ear, IEMs, wedge, headphone mix)
• Host mix vs guest mix — "I sound fine in the room" is not "chat hears balance"
• Feedback risks — speaker-to-mic loops when two people share a small space

Latency between guests

• Remote guests: expect delay; prefer call-and-response or staggered parts over tight unison
• Same-room guests: still check interface buffer and app monitoring
• Rule: if latency makes harmony painful, rearrange the arrangement — do not "play through" a broken grid

Levels and balance

• Pre-LIVE balance pass: spoken count-in, soft verse, loud chorus
• One person watching chat/replay ear if available
• Capstone-grade habit: note target balance ("guest vocal slightly under host lead" or equal duo)

Fail-safes

• Mute guest / mute bed / fall back to host-only path
• Safer song alternate if a DI dies
• Phone hotspot / secondary device note if the host stream dies (keep short)

Promo without chaos

Use the Collab Promo Checklist:

• Agree title language and time zone
• Cross-promote once with clear roles ("guest feature," not "takeover" unless true)
• Share handles spelled correctly
• Do not promise songs you have not rights-tiered
• Post a short after-note with both next solo LIVE times (MU-06 conversion)

Troubleshooting recovery under pressure

When the collab wobbles, run this tree out loud:

1. Stop the bleed — mute the bad source; keep talking calmly 2. Name the plan — "Switching to host-only for one song while we fix DI" 3. One fixer — guest stays off-mic unless asked for a cable check 4. Time box — two minutes of fix, then either resume shared plan or finish host-led 5. Log it — after LIVE, write the Technical issue log line for Capstone

Never shame the guest on stream. Never fake that the train wreck is "part of the show" for more than one breath of humor — then recover.

Band / duo / single-guest variants

• Single guest: simplest — host clock, guest feature block, promo exchange
• Duo equals: co-host clock agreed in writing; still one recovery captain
• Band: assign seats (click owner, vocal lead, talk lead); longer soundcheck mandatory

If you cannot rehearse with a real guest this week, run a solo simulation: empty chair, second mic path if you have it, full run-of-show and audio plan filled as if the guest exists. File it. Capstone prefers real rehearsal when possible; simulation still proves ops thinking.

Hard exclusions

• No guilt-gifting contests as the "collab hook"
• No repertoire bullying guests into Avoid-tier songs
• No surprise "we're battling now" unless both prepared (Battle path is separate)
• No skipping soundcheck because you are famous to each other

Capstone connection

Run-of-show + audio plan + promo notes + issue log feed Capstone collaboration and technical reliability evidence. Optional Music LIVE Lab / Honors never gates certification.

Examples

Example 1 — Same-room duo. Shared interface, two mics, one DI guitar. Soundcheck includes chorus balance and talk-break levels. Latency fine. Recovery: mute DI, finish vocal+acoustic if cable fails.

Example 2 — Remote guest vocalist. Accept latency; arrange call-response song; avoid tight three-part stacks. Promo exchange at minute 40. If guest audio drops, host continues with planned solo block.

Example 3 — Solo simulation. Creator fills guest columns with a peer's real inputs from a planning call, rehearses intro and recovery scripts alone, files worksheets. Books real guest next week with the same docs.

Real Creator Scenarios

Scenario A — "Guest shows up late with a new song." Action: rights tier + audio plan first. If either fails, feature the prepared songs only. Host owns the veto.

Scenario B — "Chat says the guest is too quiet." Action: host narrates a 20-second level fix once; if unfixable, rearrange to host-led verses. Do not spend the show apologizing.

Scenario C — "We sound great in the room but replay is muddy." Action: room volume lied. Rebuild monitor strategy; record a short test to phone ear before next collab.

From Brad's Experience

Pro Tips

• Lock repertoire 24 hours before promo posts go wide.
• Soundcheck the loudest song first — soft songs lie.
• Give guests their own water, stand, and mute awareness.
• Put next solo LIVE times in the promo exchange — convert both rooms (MU-06).
• Record a one-minute pre-LIVE test clip for balance.
• Keep a host-only set in your pocket the length of the collab.
• Thank mods if they catch level issues before you do.
• End on time — stamina (MU-03) still applies with company.

Common Beginner Mistakes

• No recovery captain. Fix: host owns the tree unless pre-assigned.
• Tight harmonies over bad latency. Fix: rearrange; protect dignity.
• Skipping rights tiers for guest songs. Fix: MU-07 applies to everyone on mic.
• Promo with wrong times/handles. Fix: checklist, not memory.
• Fixing for ten minutes in silence. Fix: two-minute box, then host-led continue.
• Letting requests derail a timed collab. Fix: park requests unless pre-agreed.
• Calling vibes a soundcheck. Fix: verse + chorus pass on the real path.

Reality Check

Your first collab ops packet will feel overbuilt. Then the DI fails and you will be glad it existed. Mission success is a completed run-of-show + audio plan with rehearsal or honest simulation — never whether both chats exploded or gifts appeared.

Summary

Collab Music LIVE succeeds when roles, audio logistics, promo, and recovery are written and rehearsed. Use the run-of-show and Guest Audio Plan; respect latency and monitoring; protect rights tiers; recover with one captain. Document rehearsal or solo simulation for Capstone. Optional Music LIVE Lab / Honors never gates certification.

LIVE Mission

Mission: Complete Collab Run-of-Show + Audio Plan

1. Fill the Collab Run-of-Show Template for a real or planned guest session. 2. Complete the Guest Audio Plan Worksheet (sources, monitoring, latency, fail-safes). 3. Complete the Collab Promo Checklist. 4. Rehearse with a guest or run a fully documented solo simulation of guest roles (including recovery script aloud). 5. File a short technical note: what broke or what you stress-tested.

Success is graded on completed ops docs + rehearsal/simulation execution — never on viewer counts, gifts, or "how hype" the collab felt.

Downloads

• Collab Run-of-Show Template — timed blocks, role owners, repertoire lock, hard out
• Guest Audio Plan Worksheet — sources, monitoring, latency, balance, fail-safes
• Collab Promo Checklist — titles, times, handles, rights confirmation, after-notes

Quiz

Take the interactive lesson quiz on this page (70% to pass). It includes scenario questions on roles, latency, recovery, and promo — not gear-brand trivia.

Key Takeaways

• Clear roles and one recovery captain prevent collab chaos
• Audio plans must cover sources, monitoring, latency, and fail-safes
• Rights tiers (MU-07) apply to guest repertoire too
• Promo is part of ops — wrong handles waste both audiences
• Rehearse with a guest or document a solo simulation
• CM-07 recommended for hospitality; this lesson owns musician audio ops
• File run-of-show + audio plan for Capstone
• Optional Music LIVE Lab / Honors never gates your certificate

Before You Move On

☐ Finished reading this lesson

☐ Completed Collab Run-of-Show Template

☐ Completed Guest Audio Plan Worksheet

☐ Completed Collab Promo Checklist

☐ Rehearsed with guest OR filed full solo simulation

☐ Practiced recovery tree once out loud

☐ Passed the Lesson Quiz (70%+)

☐ Filed docs for Capstone evidence

Next Lesson Preview

Next up: Monetizing Music LIVE Ethically. You can host a clean shared stage — now design tips, goals, merch mentions, and booking CTAs that fund the work without turning the concert into a hard sell.