Blog

How to Keep Your Whole Band on the Same Page — On Stage and Off

Apr 7, 2026

Every band pays a coordination tax. It is invisible until you add it up: the time spent chasing confirmations, the missed message about the setlist change, the dep who showed up for Saturday’s function not knowing “September” has a new outro, the band leader who rearranged the set on Thursday and had to text five people individually to make sure they all updated their printed sheets.

None of this is essential overhead. It is friction from using the wrong tools for the job. Group chats, personal email, shared folders, printed setlists — each one solves part of the problem and creates a different part.

This is what a properly coordinated band workflow looks like in practice.

One Song Library, Every Member

When songs, chord sheets, and setlists live in a single shared library, the question “did you get the updated chart?” disappears. Everyone sees the same data. Changes made at 11pm the night before rehearsal are visible to every member when they walk in the door at noon.

Compare this to the typical alternative: someone exports a PDF from Chordify, sends it to the group chat, the trumpet player does not have notifications enabled, the guitarist downloaded it but has an older version saved in a folder, and nobody knows which version is canonical.

The shared library is not a better folder. It is a live database — one version, always current, visible to everyone with access, updated immediately when anyone makes a change.

Shared vs. Personal Settings

Not everything should sync to everyone. Some things are genuinely personal:

Transpose values — the keyboard player is transposing +2 for B♭ saxophone. The guitarist does not need or want that.
Font size and display preferences — individual per device.
MIDI device configuration — your Helix preset list is yours. The drummer does not have a Helix.
Personal notes — annotations for your own performance that are not relevant to the rest of the band.

Shared settings (song content, chord sheets, setlists, lyrics, key and tempo metadata) sync to the whole band. Personal settings stay on your device. This separation means members can customise their experience without affecting anyone else’s view.

Band Roles: Giving the Right People the Right Access

A four-piece with equal decision-making can share everything. A ten-piece function band with a dedicated sound tech, a booking manager, and regular deps cannot — not without creating noise and privacy problems.

Gigmeister has five roles, each scoped to what that person actually needs:

Role	What they can access
Owner	Everything — billing, settings, full management
Manager	Songs, setlists, calendar, bookings, mailbox
Member	Songs, setlists, calendar — no mailbox or billing
Tech	Rider pack, patchlist, stage plan — production only
Guest	Only events they are assigned to, plus the shared song library

The Tech role is particularly useful for bands with a dedicated sound or lighting tech who needs to maintain the patchlist and rider pack without seeing the booking inbox or the band’s finances. The Guest role handles deps.

Managing Deps Without Oversharing

The dep problem is real. You need the dep to have the setlist, the chord charts for their instrument, the event details — but not your booking history, your internal notes, your hospitality rider, or anything else that is band-internal.

Invite the dep as a Guest. They see the events they are assigned to and the shared song library. That is it. Their access ends there.

The onboarding takes two minutes: send the invite link, assign the Guest role, assign them to the event. They arrive at the gig with the right information and no access to anything they should not have. When the gig is done, their access can be removed or left inactive — no need to chase down shared logins or revoke folder permissions.

Real-Time Sync During Rehearsal

Active practice sessions in Gigmeister broadcast the current song to all connected band members. When the music director moves to the next song, everyone’s screen jumps. Nobody is on the wrong page because they were scrolling through their notes.

For bands that track practice systematically — logging which songs were worked on and how many times each song has been rehearsed — the session data syncs across all members. Everyone sees the same session history.

This is a different kind of coordination problem than the booking or setlist problem. It does not involve communication delays or information asymmetry — it involves the real-time state of a rehearsal session, which previously required the band leader to call out “okay, next song is…” every time. The shared session handles that automatically.

Follow Leader Mode: Running the Show from One Device

Follow Leader is the most immediately impactful coordination feature for live performance. The leader’s device broadcasts the current song and step to all followers over the local network. When the leader swipes to the next song, every follower’s screen jumps to that song automatically.

No one is ever on the wrong song. No missed cues because someone was still looking at the previous chart. No need for a printed setlist on every stand. The leader’s navigation is the setlist for everyone.

This matters most in:

Large stages where shouting across to a bandmate is not practical
Last-minute setlist changes called from the stage — the leader skips a song, and everyone follows without a conversation
Function gigs with a variable order — the MC changes the plan, the leader adapts, the band adapts
Bands with less experienced deps who need to follow rather than anticipate

Platform Requirements

Leading works on the desktop app (macOS) and the iOS/iPadOS and Android apps. The leader role is not available in a web browser — a browser tab cannot host a session. Followers can use the desktop, iOS, Android, or web app. All devices are on the same local network — Follow Leader is peer-to-peer over LAN, not a cloud relay, and can even run device-to-device with no router at all.

This fits most gig scenarios: the band leader runs Gigmeister on a laptop or an iPad at the stage, followers use iPhones or tablets. The connection does not require internet access beyond the local network once devices are paired.

Setting Up a Follow Leader Session

On the leader’s desktop app: open the setlist in performance mode, click Presence, click Lead. A QR code appears on screen.

Followers open Gigmeister on their iPhone or tablet, tap Presence, scan the QR code (or select the leader from the auto-discovered list on the same network), and join. They are now synced.

From this point, any navigation on the leader’s device — next song, previous song, jump to a specific song, advance to the next step — broadcasts to all followers. Followers can navigate independently if needed but re-sync on the leader’s next action.

What Happens When Someone Loses Connection

If a follower drops off the local network mid-show, their screen holds on the last synced song. They do not get a blank screen — just a frozen state. The leader keeps going. Reconnect by scanning the QR code again.

The sensible backup is for each member to know the setlist order anyway — Follow Leader enhances coordination, it does not replace rehearsal.

Calendar Coordination: Gigs, Rehearsals, and Attendance

The band calendar shows every gig and rehearsal in one place, visible to all members with the appropriate role. Each event has:

Date, venue, load-in and soundcheck times, set time
Attendance tracking — confirmed, declined, tentative, no response
Linked setlist (even as a template that gets refined closer to the date)
Notes (parking, contact person, balance due)

The band leader can see at a glance who is confirmed for Saturday. Members can confirm or decline without a separate group message. When someone declines, the leader knows immediately and can line up a dep — without a round of “can everyone make it?” messages.

iCal sync pushes all band events to personal calendars (Google Calendar, Apple Calendar, Outlook) so gigs show up alongside everything else in a member’s life. One sync setup, automatically updated as events are added or changed.

Managing a Multi-Band Life

Many working musicians play in more than one band. Each band is a separate workspace in Gigmeister — independent song library, setlists, calendar, and inbox. Switching between bands is a single tap in settings.

Personal MIDI device configuration carries across all bands. Your Helix setup, your MainStage program change numbers, your SPD-SX mappings — configured once, available in every workspace. You are not reconfiguring your rig when you switch from your function band to your originals project.

Band Chat: Role-Scoped Channels

Band Chat provides six built-in channels scoped by role:

General — everyone
Announcements — everyone
Musicians — Owner, Manager, Member, and Guest (deps see this)
Core — Owner, Manager, and Member only (no guests)
Bookings — Owner and Manager only
Production — Owner, Manager, Member, and Tech

Scoped channels solve the noise problem. The drummer does not need to see contract negotiation threads. The touring sound tech does not need to see discussions about the rehearsal schedule. The dep does not see Bookings or Core.

Everyone sees the channels relevant to their role. The person who sets the agenda for each channel controls its audience by controlling who gets that role — without managing individual permissions per message.

Get Started

Sync your entire band in real time, on stage and off. Create a free Gigmeister account or read the Band Collaboration documentation to invite your bandmates.

AI Tools That Actually Help Working Musicians

Mar 17, 2026

Gigmeister

Most musicians have tried an AI tool once, been unimpressed, and gone back to doing things manually. Usually because the output needed more editing than it would have taken to write from scratch, or because the tool was solving a problem they did not actually have.

This article is not about AI in theory. It is about the specific tasks where AI demonstrably saves time for working bands — and the adjacent tasks where it does not, so you know where not to bother.

The Hype Problem

AI attached to music tools is marketing language for a wide range of things, from statistical autocomplete to capable language models. The bar for claiming “AI-powered” is low, and the usefulness gap between tools is enormous.

The use cases where AI earns its place in a musician’s workflow have something in common: they are tasks that take meaningful time, follow a predictable structure, and produce output that benefits from human review before use. Not tasks that require creative judgment, musical ear, or relationship knowledge — those remain yours.

AI Setlist Generation: The Prompt-to-Playlist Workflow

Building a setlist from scratch for a specific occasion — a corporate event, a private party, an outdoor festival — means pulling from your library with a particular audience and energy in mind. For a band with 60+ songs, this can take 20 minutes. For a band with 100+, longer.

AI Setlist Generation in Gigmeister takes a natural-language prompt and builds a setlist from your actual song library. Not a generic recommendation — your songs, in an order that fits the brief.

A useful prompt: “45 minutes, high energy, rock and funk, corporate crowd, avoid ballads and slow songs”

The model returns a setlist draft with duration, ordered songs from your library, and section markers if the duration splits cleanly into sets.

What the Model Gets Right

Duration math — given a target duration and your songs’ stored lengths, the model fills the time without you doing arithmetic. It accounts for transitions.

Basic energy curve — opener songs are generally uptempo. The set does not start with a ballad or end with a slow number unless the prompt asks for it.

Stylistic consistency — if the prompt specifies genre or feel, the model draws from songs tagged or described that way. Tagging your library pays off here.

Avoiding awkward repetition — songs in the same key back to back, or the same artist twice in a row for cover bands. The model catches these mechanically.

What to Always Check Manually

The opener and closer — the model does not know which song is your strongest or which one gets the best audience reaction. It makes a statistically reasonable guess. You know your songs.

Key transitions — the model considers key metadata, but it does not know that your arrangement of “Higher Ground” in G♭ is awkward to follow with your “Superstition” intro in E♭m because of how your keyboard player transitions. That knowledge lives with the band.

Songs that feel wrong back to back — two songs can be compatible in key and tempo and still clash in feel. Trust your ear on the review pass.

The review step is not optional. Treat AI output as a strong first draft — which is genuinely valuable — rather than a finished setlist.

AI Setlist Optimization: Reordering What You Have

You have the right songs for tonight. The order feels off. Maybe it was copied from a similar gig and does not fit tonight’s venue, or the band has been playing the same order for three months and it is getting stale.

AI Optimize Order resequences your existing setlist based on key flow, tempo pacing, and energy curve — the same variables a human music director considers, applied in seconds.

The optimisation considers:

Key relationships between consecutive songs (relative major/minor, fourth/fifth movement, awkward intervals)
Tempo clustering vs. variation (avoiding three consecutive 140 BPM songs, then three at 80)
Energy arc across the full set (the familiar wave: open strong, dip mid-set, build back up, close strong)
Section integrity — if you have a SET 1 and SET 2, the optimiser treats them independently

When to Use Generate vs. Optimize

Generate — you need a setlist for a specific occasion and want a first draft from scratch. The songs are unknown when you start.

Optimize — you have the songs but want better sequencing. The selection is fixed; the order is what you are changing.

These are different tasks. Generate works best with a rich prompt that specifies duration, energy, and occasion. Optimize works best when the setlist already represents the right repertoire for the gig.

AI Chord Sheet Generation: From Lyrics to Performance-Ready

Getting a chord sheet for a new cover involves finding a source (which may be wrong), formatting it into bracket notation, placing chords above the right syllables, and adding any structural notes. For a busy band learning four new songs before a function gig, this adds up.

AI Chord Sheet Generation in Gigmeister (available on Gigmeister Pro) takes a song title and artist — or pasted lyrics — and generates a bracket-notation chord sheet with chords placed above lyrics. The output is formatted the same way as a hand-written chart: [Am]Walking down the [F]road.

This earns its keep on:

Common pop, rock, and folk songs with well-known progressions
Standard key arrangements (original key or a clearly documented common key)
Songs where the chord structure is consistent across verses and choruses

It is less reliable on:

Jazz standards with complex substitutions and reharms
Songs with unusual time signatures or uncommon chord voicings
Deep cuts from artists who play in unorthodox ways

The Edit-Don’t-Rewrite Principle

The value here is not perfect accuracy. It is getting to 80% in 30 seconds rather than starting from a blank document.

Play through the generated chart once from top to bottom. There will typically be two or three chords that are wrong — a VII chord where there should be a V, a missing passing chord in the bridge. Fix those. Done.

Comparing this to the alternative — finding a tab site, evaluating the quality, copying into a formatter, placing chords manually — even an imperfect AI draft wins on time.

AI Draft Replies for Booking Inquiries

A venue sends a booking inquiry. It is specific enough that a template would not quite fit, but not so unusual that writing from scratch is justified. This is the most common type of booking email in a working band’s inbox — and also the one that takes the most time proportionally because every reply is slightly different.

AI draft replies in Gigmeister’s Shared Mailbox read the context: the incoming message, previous replies in the thread, internal notes added to the thread, and any linked gig details. The draft covers the standard information — availability, rate reference, rider link, next steps — in a professional tone that does not read like a template.

The draft arrives in the reply compose box, ready to edit. You adjust anything that needs personalising — fee negotiation, specific venue requirements, relationship context the model cannot know — and send.

The Template vs. AI Tradeoff

For truly repetitive emails — deposit confirmations, availability checks at a fixed rate, show-day logistics — a reply template with variable substitution is faster and more reliable than an AI draft. Templates are instant and exact.

AI earns its place on the context-dependent replies: the first response to a detailed corporate brief, the reply to a venue with non-standard requirements, the follow-up after a rescheduled gig. The emails you actually stop and think about before writing. Use AI to clear the thinking phase; use templates to clear the mechanical phase.

What AI Cannot Do (Yet)

It is worth being explicit about the limits, because “AI” as marketing language invites over-expectation.

Generate backing tracks — AI can generate audio in controlled settings, but not production-ready backing tracks for a specific song arrangement with your live band’s sound.

Real-time pitch or tempo analysis — Gigmeister does not listen to your band and adjust anything in real time. It uses the tempo and key data you have stored, which you entered.

Replace musical judgment about the room — the model optimises for documented musical relationships. It does not know that this particular crowd wants three slow songs in a row because it is a silver anniversary dinner. You do.

Remember a venue’s preferences across gigs — the model has no persistent memory of how specific clients responded to specific sets. That institutional knowledge lives with the band.

Understanding where AI stops being useful is as important as knowing where it helps.

Building an AI-Augmented Workflow

A practical day before Saturday’s gig:

Rough out the setlist — use AI Generate with a 90-minute, high-energy, general crowd prompt. Takes 30 seconds.
Optimize the order — run AI Optimize on the draft. Review the key transitions. Accept or adjust.
Generate chord sheets for two new covers — upload the songs, generate sheets, play through once to catch any wrong chords, fix them.
Draft the confirmation reply to the venue — use AI Draft Reply on the thread. Adjust the fee reference and the load-in details. Send.
The rest of the pre-gig time — practice.

None of this replaces musical decision-making. All of it removes the non-musical overhead that surrounds a typical gigging week. The tools do the structural work; the band brings the knowledge that matters.

Get Started

Generate setlists, optimize song order, and create chord sheets with AI built into your band’s workflow. Create a free Gigmeister account or read the Setlists documentation to get started.

Running Backing Tracks and Click Tracks Live: A Practical Guide

Feb 24, 2026

Gigmeister

Running backing tracks live is one of those skills that looks simple until the first time you try it on stage. The concept is obvious — play audio alongside the band. The execution requires decisions about audio routing, click distribution, trigger timing, and sync that nobody explains until you are standing in a venue at 5pm trying to figure out why the engineer is hearing your click through the PA.

This guide covers the full workflow: hardware requirements, routing, trigger configuration, and how to organise your track library across setlists.

Why Bands Use Backing Tracks (and Why It’s Harder Than It Looks)

The reasons are straightforward: string sections, synth pads, orchestral beds, programmed elements, choir vocals, sound effects — sounds that are too expensive, impractical, or simply impossible to reproduce live with the musicians on stage. For smaller bands, tracks can also fill out the sonic texture without adding headcount.

The click track is a separate but related concern. A drummer playing to a click is a drummer who stays at the right tempo for the whole song — critical when there are quantised elements in the backing tracks, and useful any time tight timing matters.

The difficulty lies in the plumbing: getting click and tracks to the right places without routing them to the wrong ones. A sound engineer who hears the click in the main mix will fix your routing before the show starts and never forget it. Getting it right the first time takes maybe 30 minutes of planning; getting it wrong in front of an audience takes much longer.

What You Need Before You Start

Audio interface with multiple outputs — at minimum, two stereo outputs (four channels). Output 1–2 carries the backing tracks to the PA mix. Output 3–4 carries the click to the drummer’s monitor send or IEM transmitter. Some rigs add a third output pair for a separate stage mix.

IEM system or dedicated monitor send — the drummer (and ideally the whole band) needs the click in their ears. An IEM transmitter is the cleanest solution. A dedicated aux send from the FOH desk to a stage wedge also works, as long as that send is controlled by the band and not accidentally pushed into the main mix.

Cables — balanced TRS or XLR from the interface to the mix. Unbalanced TS cables are fine for short runs on stage but introduce noise over longer distances.

Software to play the tracks — a DAW, a dedicated media player, or an integrated setlist app like Gigmeister that handles both track playback and song navigation from a single interface.

Click Track Distribution: Who Hears What

The click belongs in the drummer’s ears (and optionally the rest of the band’s). It does not go to the PA. Ever. The routing decision you make at setup determines whether this stays true under all conditions.

Mono vs. Stereo Splits

The classic approach uses a two-channel output with a mono split:

Left channel — the click track, routed to the drummer’s monitor send or IEM transmitter
Right channel — the backing track, routed to the FOH engineer’s input

The engineer uses only the right channel in the main mix. The band uses only the left channel on stage. The channels never cross.

This works reliably and needs no special equipment beyond a two-output interface. Its limitation is that the backing track is mono on the PA side, which is fine for most pub and function gig scenarios but less ideal for larger stages where stereo width matters.

Platform note: Channel routing for the click track (left-only, right-only, or stereo) is available on desktop and Android. On iOS, the click track always outputs in stereo regardless of the routing setting — the L/R split approach described here requires the desktop app or an Android device.

Multi-Output Audio Interfaces

When the setup grows beyond the two-channel split — stereo backing tracks to FOH, separate click send to drummer, separate monitor mix for the rest of the band — a four- or six-output interface handles it cleanly.

A common layout:

Output 1–2 (stereo): backing tracks to FOH
Output 3–4 (stereo or mono): click to drummer’s IEM transmitter
Output 5–6 (optional): monitor mix with click + tracks for the full band

Assign each output pair in your audio software and label them clearly. At every gig, patch the same outputs to the same destinations. Consistency prevents errors under pressure.

Setting Up Backing Tracks Per Song

In Gigmeister, backing tracks are attached to songs in the library. Open any song, go to the Audio tab, upload the file — WAV or MP3, mono or stereo — and configure the playback options.

Trim points — set an in-point and out-point within the file to skip a long silence at the start, fade out early, or loop a specific section. This is faster than editing the audio file before uploading every time you make a change.

Loop count — how many times the track plays before stopping. One play-through is the default. Loop indefinitely for ambient pads or intro loops where the length is determined by what is happening on stage, not the track.

Auto-Trigger vs. Manual Start

Auto-trigger starts the backing track automatically when you navigate to the song — no extra action required. This is the right choice for songs where the track starts on beat one with no intro or where the drummer counts in and everyone hits simultaneously.

Manual start gives whoever is running the show — usually the drummer or the music director — an explicit button to fire the track at the right moment. Use this when the track starts during a specific section, when there is stage banter before the song begins, or when you want the flexibility to hold the moment before the track drops.

Both modes work cleanly with a foot pedal or Bluetooth remote controlling Gigmeister — you can advance to the next song and manually fire the track in a single flow.

Transport-Synced Start

When the click is already running and you add a backing track mid-song — say, an orchestral pad that comes in at the chorus — transport sync aligns the track start to the nearest downbeat rather than firing immediately. This prevents the track from starting on an off-beat because you tapped a fraction of a second late.

Enable transport sync in the track options when timing precision matters more than instantaneous start.

Per-Section (Step-Level) Backing Tracks

Intro strings, verse pad, chorus orchestration, bridge — different audio for different sections of the song. Song Steps in Gigmeister let you define those sections and attach a different backing track to each one.

When you navigate to the chorus step, the chorus track fires. When you move to the bridge, the bridge track fires (and the chorus track stops). The transitions are governed by your navigation actions — tap the next step on screen, step on the foot pedal, or let the section auto-advance after a set number of bars.

This approach is more complex to set up than a single track for the whole song, but it gives you flexibility that a single timeline cannot. You can extend a section, repeat a verse, or skip a solo — and the tracks follow the live performance rather than running on a fixed clock.

Auto-Advance with Audio Cues

For fully scripted sections, auto-advance moves to the next step automatically when the track reaches its end. Set step one to play a four-bar intro track, then auto-advance to step two (the verse). The verse step can have its own track or run without audio. This creates a linear show file where the track controls the pacing.

Pair this with TTS announcements in your in-ears — Gigmeister can read the next step name aloud (“Chorus coming up”) one bar before the transition so the band knows what is coming without looking at a screen.

Soundcheck for Tracks

Run the track system at soundcheck before the band plays anything. The FOH engineer needs to set gain for the track input, and you need to confirm the click is going nowhere near the PA.

Check the routing first — ask the engineer to mute the FOH input while you solo the click output through your headphones. If the click is audible anywhere in the room, the routing is wrong. Fix it before proceeding.

Set gain staging — the track output should hit the FOH input at the same nominal level as the other inputs on the desk. Too hot and the engineer is fighting gain reduction; too quiet and the tracks disappear in the mix. Aim for -18 dBFS on average, -6 dBFS peaks.

Check for phase issues — if you are running a stereo track split to mono at the desk, sum the channels in mono and listen for phase cancellation. This is rare but happens with certain track files. Fix it in the track itself rather than at the desk.

Confirm monitor isolation — have the drummer confirm the click is only in their ears, not bleeding through the wedge into the room. If it is bleeding, lower the wedge level or switch to IEMs for the click send.

Handling Live Mistakes with Running Tracks

The moment a track starts, the clock is running. If the band gets ahead of or behind the track, there are three options:

Hold and follow — the band adjusts to the track tempo. Works well if the drift is small and the drummer can feel where the downbeat is.
Stop and restart — stop the track during applause, a talking section, or stage banter, navigate back to the beginning of the song, and restart. Most audiences do not notice if the transition to the restart is smooth.
Continue without the track — if the track cannot be recovered cleanly, the band plays the rest of the song without it. This is why every song should be performance-ready without the track — the track adds texture, it does not hold up the song.

The best way to prevent timing drift is to choose carefully which songs use tracks. Songs with a fixed intro, a rigid rhythmic grid, and not much improvisation between sections work well. Songs with extended solos, variable endings, or frequent tempo variations are harder. Use your judgement about where the musical and technical requirements align.

Organizing Your Track Library Across Setlists

Tracks are attached to songs in the library, not to setlists. When you add a song to a new setlist, the track configuration — file, playback options, trim points, loop settings — comes with it automatically. There is nothing to re-configure per setlist.

This matters more as your library grows. A band with 80 songs and 10 different setlists for different venue types does not manage 10 copies of the same track configuration. They manage one, and it appears correctly everywhere.

When the track for “September” gets a new intro point, update it once in the song. Every setlist that includes “September” gets the updated version.

Get Started

Upload your backing tracks, configure click routing, and let Gigmeister trigger audio automatically as you move through your setlist. Create a free account or read the Backing Tracks documentation for detailed setup instructions. Tracks and click sit alongside setlists and MIDI on the Stage side of the app.

How to Handle Gig Bookings Without the Email Chaos

Feb 5, 2026

Gigmeister

Most bands run their bookings through someone’s personal Gmail. Which means missed messages. Which means the band leader leaves and takes every venue contact with them. Which means a dep asks “what time is load-in?” and the answer is buried somewhere in a thread that three people were CC’d on four months ago.

It does not have to work this way. Here is a practical workflow for managing gig bookings from first inquiry to confirmed gig — one that scales as your band gets busier and survives personnel changes.

The Booking Email Problem

The core issue is not email. Email is fine. The problem is personal email — an inbox only one person can see, with no shared history, no way to assign follow-ups, and no record that survives if that person steps back from the band.

Think about what gets lost:

A venue emailed six months ago about a recurring Friday slot. Nobody remembers what was agreed.
A promoter sent a follow-up that landed in someone’s spam.
The band manager who handled all the bookings left, and the history walked out the door with them.
Three people are now CC’d on every thread “just in case,” creating reply-all chaos every time someone responds.

The fix is a single shared inbox — one address, visible to everyone who needs to see it, with a thread history that lives with the band rather than any individual.

Setting Up a Dedicated Band Email

Get a proper band email address: bookings@[yourband].com, or at minimum a Gmail address that is not tied to anyone’s personal account. The domain address looks more professional to venues and promoters, but any dedicated address solves the ownership problem.

What matters most is that more than one person has access. Forward it to the band’s shared inbox in Gigmeister, or set up IMAP access for anyone who needs visibility. When the keyboard player joins or leaves, you update access — you do not lose the thread history.

Thread Management: From Inquiry to Confirmation

Every booking starts as a thread — an email conversation with a venue, promoter, or event organiser. The goal is to move each thread from New → In Progress → Waiting → Closed without anything falling through the cracks.

New — unread inquiry, not yet assigned to anyone.
In Progress — someone is actively handling it.
Waiting — you have replied and are waiting for a response. Snooze the thread to resurface it in a week if nothing comes back.
Closed — gig confirmed (calendar event created), declined, or cancelled. The thread stays in the record; close it when no further action is needed.

Assigning a thread to the person who is handling it means everyone else knows not to reply independently. The thread has one owner. If the owner cannot be reached, anyone with access can pick it up — because the full history is right there.

Assigning Threads Without CC Chains

The moment you assign a thread, the CC chain becomes unnecessary. The person assigned handles it. Everyone else can see the thread if they need to — but they are not getting pings every time someone responds.

This is a small cultural change for bands used to adding half the lineup to every booking email. It takes one gig cycle to appreciate how much quieter it makes the inbox.

AI Draft Replies

A venue sends a booking inquiry. You need a professional response that covers your availability, your rate, your sound requirements, and next steps. You write a version of this email dozens of times a year.

Gigmeister’s AI draft replies read the incoming message, the thread context, any internal notes you have added, and the linked gig details — and generate a starting draft. The tone matches how a working band communicates with venues: direct, professional, not overly formal. You read it, adjust anything that needs adjusting, and send. The research and structure are done; you just review.

This earns its keep most on the variable emails — the ones where the inquiry is specific enough that a template would not fit, but common enough that you know roughly what needs to be said.

Reply Templates for Recurring Responses

For the truly repetitive emails, templates beat AI drafts on speed. The six emails every busy band sends repeatedly:

Availability check reply — confirming you are available and providing your quote
Quote with rider — your fee, what is included, link to the tech rider
Deposit confirmation — acknowledging receipt, confirming the date is now secured
Show-day logistics — load-in time, soundcheck time, set times, parking details
Cancellation — short, professional, no hedging
Rebook follow-up — sent a month after a good gig, suggesting future dates

Templates let you send a consistent, professional email in under a minute. The writing is done once and reused — edit the specific details (fee, date, venue name) before sending.

The AI draft and the template are not competitors — they serve different situations. Template for the predictable, AI for the specific.

Distributing Your Tech Rider

Stop attaching PDFs to every booking email. Not because PDFs are bad, but because you update your rider and the venue is still looking at the version from 2023.

The rider share link is a single URL that always serves the current version of your production documents — tech rider, hospitality rider, stage plan, and patchlist. Send the link once. When you add a new channel to the patchlist, or update your monitor requirements, or change the stage plan because your guitarist switched to a Kemper, the link updates automatically. The venue coordinator can bookmark it and always have the right version for show day.

Drop the link into your quote email. It goes out with every booking confirmation. No more “which version is current?” questions at soundcheck.

The Patchlist: What Your Sound Engineer Actually Needs

The patchlist is the most practically important document you send a venue. It tells the FOH engineer — often someone who has never seen your band before — exactly what they are building before you arrive.

A good patchlist row per input:

Channel number
Instrument or source (kick drum, snare, bass DI, lead vocal, acoustic guitar)
Mic or DI type (or just “condenser mic” / “passive DI” if you are not specifying model)
Stand type (boom stand, short stand, clip)
Notes (phantom power required, pad, polarity flip, stereo pair)

The notes column matters. A drum overhead that needs phantom power, a guitar amp that goes DI rather than mic’d, a backing track output that comes in as stereo — these are the details that cause delays at soundcheck when they surface at the last minute.

Keep it in a simple format. Engineers read these on a phone in a noisy venue. Scannable beats comprehensive.

Tracking Payment and Contract Status

Confirmed gig, verbal agreement, no contract. Deposit sent, not received. Balance due on show day — but nobody wrote down the amount. These are not edge cases; they happen regularly in active bands.

For each gig, track:

Contract status — not sent, sent, signed
Deposit status — not requested, invoiced, received
Balance — amount, due date (usually show day)
Notes — anything the venue has agreed to that is not in the contract

This does not need to be a complex system. It needs to be visible to more than one person and linked to the gig event so the information is there when show day arrives.

When the band arrives at the venue and someone asks “what’s the balance?” — the answer should not require anyone to check their messages.

Keeping the Whole Band in the Loop

When a booking is confirmed, two things need to happen immediately:

The date goes into the band calendar — with load-in time, soundcheck time, set time, venue address, and parking notes
The setlist gets linked to the event (even if it is still a template — it can be finalised closer to the gig)

Every band member with access can see the calendar. They get the gig day details in the app alongside their chord sheets and setlists, not buried in a group message that will scroll away by show time.

When the venue sends an update — say, soundcheck has moved from 4pm to 5pm — update the calendar event once. Everyone sees the change. No group message needed.

The Booking Workflow in Practice

A consolidated timeline for a typical gig, from inquiry to show day:

Inquiry arrives — thread opens in the Shared Mailbox, status: New
Assign thread — booking person picks it up, status: In Progress
Reply with availability and quote — include the rider share link
Venue confirms and requests deposit invoice — send invoice, status: Waiting
Deposit received — update deposit status, create calendar event, close the thread
Send show-day logistics email — load-in, soundcheck, parking, venue contact
Show day — balance collected, show notes added to the thread for next time

From inquiry to confirmed gig, every step is tracked in one place. The next person who handles bookings — whether that is tomorrow or two years from now — walks into a complete history.

Get Started

Manage your band’s bookings, rider pack, and gig calendar from one place. Create a free Gigmeister account or read the Shared Mailbox documentation to connect your band email.

Using Gigmeister with MainStage and Gig Performer

Jan 22, 2026

Gigmeister

If you play keys or guitar in a live band, there is a good chance you use Apple MainStage or Gig Performer to host your virtual instruments and effects. Both are excellent at what they do: load plugins, switch patches, and process audio in real time with rock-solid stability.

But they are built for one player at a time. And if you have ever tried to coordinate patch changes across a full band – keyboards, guitar rig, drum triggers, maybe a lighting desk – you know that each player managing their own host independently leads to problems. Missed cues, wrong patches, awkward gaps between songs.

Gigmeister is not a replacement for MainStage or Gig Performer. It is the layer that sits above them and runs the show.

What MainStage and Gig Performer Do Well

Both apps are patch hosts. They load your virtual instruments (piano, organ, synth pads, guitar amp sims) and let you switch between configurations using MIDI program changes. Their strengths:

Low-latency audio processing with optimized plugin hosting
Complex signal routing (splits, layers, effects chains)
Per-patch settings for volume, EQ, effects parameters
Setlist organization of patches in performance order

MainStage is built into the Apple ecosystem and works seamlessly with Logic Pro sounds. Gig Performer is cross-platform, supports both VST and AU, and has a visual wiring view that makes complex routing intuitive. Both are purpose-built for stage use and both are great at their job.

Where the Workflow Breaks Down

The problem is not the host. The problem is everything around it.

Each player is an island. Your keyboard player has their MainStage setlist. Your guitarist has their Helix presets. Your drummer has SPD-SX kits. None of these systems talk to each other. When the band decides to swap songs 4 and 7 in tonight’s setlist, every player has to manually reorder their own rig.

No shared context. The singer is on verse 2, but the keyboard player loaded the wrong patch because they thought the band was on the bridge. There is no single source of truth for “where are we in the show right now.”

Patch switching is per-device. Even within MainStage or Gig Performer, switching patches means the player has to tap a button, click a mouse, or step on a pedal assigned to that specific host. Multiply that by every device on stage and you have a lot of manual actions per song.

No visibility for the rest of the team. Your sound engineer cannot see your MainStage setlist. Your lighting operator does not know what song is next. The band leader has no way to push a setlist change to everyone at once.

How Gigmeister Fills the Gap

Gigmeister acts as the band-level conductor. It manages the setlist, the song metadata, and the MIDI messages that tell every device on stage – including MainStage and Gig Performer – what to do.

One Setlist Controls Everything

Build your setlist once in Gigmeister. Assign MIDI program changes to each song for every device in the band. When you advance to the next song, Gigmeister sends program changes to all devices simultaneously:

Your keyboard player’s MainStage receives PC 23 on channel 1 and loads the Rhodes patch
Your guitarist’s Helix receives PC 4 on channel 3 and loads the clean rig
Your drummer’s SPD-SX receives PC 12 on channel 10 and loads the right kit

One action. Every device switches. No one has to touch their individual host.

Per-Section Patch Changes

Songs are not one patch from start to finish. You might need a piano for the verse, a synth pad for the chorus, and a lead sound for the solo. Gigmeister’s step-based navigation handles this.

Define steps for each song (intro, verse, chorus, bridge, solo) and assign different MIDI program changes to each step. When you advance to the chorus, MainStage or Gig Performer receives the right program change and loads the chorus patch. Your guitarist’s rig switches at the same time.

This is something neither MainStage nor Gig Performer does well on its own. They can switch patches, but they do not know what section of the song you are in. Gigmeister provides that structure.

MIDI Clock Sync

Gigmeister sends MIDI clock at 24 pulses per quarter note, locked to the song’s tempo. MainStage and Gig Performer can slave their tempo-synced effects to this clock:

Delays that are perfectly in time with the band
Arpeggiators that follow the song tempo
Tremolo and modulation effects that pulse on the beat

You can even set per-step tempo changes. If the bridge slows down to half time, Gigmeister adjusts the clock and your host’s synced effects follow automatically.

MIDI Clip Playback

Upload MIDI files to Gigmeister and trigger them on song or step start. These clips play back through your host’s loaded instruments:

Trigger a synth sequence loaded in MainStage
Fire a one-shot sample via Gig Performer
Auto-loop a MIDI pattern for the duration of a section

Clips are tempo-scaled to match the current song BPM, so they stay in sync even if you adjust the tempo.

The Setup

Getting MainStage or Gig Performer working with Gigmeister takes about 15 minutes.

1. Connect via MIDI

Connect your Gigmeister device (iPad, iPhone, laptop, or desktop app) to your host computer via USB-MIDI, a MIDI interface, or a virtual MIDI bus if both apps run on the same machine.

2. Configure Your Host to Receive

In MainStage: Go to Layout mode. Set your Concert to respond to MIDI program changes on your chosen channel. Each patch in your Concert already has a program change number – just make sure the numbers match what you configure in Gigmeister.

In Gig Performer: Open the MIDI settings for your rackspace. Enable “MIDI Program Change” listening on the appropriate channel. Gig Performer maps rackspaces to program change numbers, so rackspace 1 responds to PC 0, rackspace 2 responds to PC 1, and so on.

3. Assign Programs in Gigmeister

Open any song in your Gigmeister library. Go to the MIDI tab. Add your MainStage or Gig Performer instance as a device (generic MIDI device works – just set the channel). Pick the program change number that corresponds to the right patch in your host.

Do this for each song. If you use step-based navigation, assign per-step programs too.

4. Build Your Setlist and Play

Drag your songs into a setlist. Hit play. When you advance songs – by swiping, tapping, or using a foot pedal – Gigmeister sends the program changes and your host loads the right patch.

What Each Tool Does Best

Think of it this way:

Responsibility	MainStage / Gig Performer	Gigmeister
Host virtual instruments	Yes	No
Process audio in real time	Yes	No
Complex signal routing	Yes	No
Manage the band’s setlist	No	Yes
Switch patches across all devices at once	No	Yes
Per-section MIDI automation	Limited	Yes
Share setlist with the whole band	No	Yes
Share setlist with sound engineer	No	Yes
Chord sheets and lyrics on stage	No	Yes
MIDI clock sync to band tempo	No	Yes
Work offline at the venue	Standalone	Yes (offline-first)

MainStage and Gig Performer manage your sounds. Gigmeister manages your show. Together, they cover the full workflow from soundcheck to encore.

Tips for a Smooth Setup

Match your program change numbers. The most common issue is a mismatch between what Gigmeister sends and what your host expects. MainStage and Gig Performer both number from 0, but some documentation shows 1-based numbering. Test every song before the gig.

Use dedicated MIDI channels. Put MainStage on channel 1, Gig Performer (if another player uses it) on channel 2, and hardware devices on higher channels. This prevents crosstalk.

Send changes during transitions. Some patches take a moment to load, especially if they use large sample libraries. Advancing to the next song a beat early, during applause, or during stage banter gives the host time to load without audible gaps.

Keep your host’s own setlist as a backup. If the MIDI connection fails mid-gig, you want to be able to manually step through patches in MainStage or Gig Performer. Set up their internal setlists to mirror your Gigmeister setlist as a fallback.

Getting Started

If you already use MainStage or Gig Performer, Gigmeister plugs right into your workflow. Your host keeps doing what it does best – hosting plugins and processing audio. Gigmeister adds the band-level coordination that a single-player host cannot provide.

Create a free account on Gigmeister and connect your first device. Check the MIDI documentation for detailed setup instructions.