live-performance

5 posts with the tag “live-performance”

Soundcheck Prep: What to Send Your Engineer Before You Arrive

May 5, 2026

Gigmeister

A soundcheck that runs 90 minutes instead of 45 is a soundcheck that eats into your set, strains the relationship with the venue, and leaves the band starting their first song already tired. Most of the delays are caused by information that could have been shared days in advance: what channels the engineer needs to build, what monitors each player requires, what the stage layout looks like.

None of this should be figured out in the venue. Here is what to prepare before you arrive, how to format it so the engineer can actually use it, and how to share it without four separate PDF attachments.

The Cost of Arriving Unprepared

The house engineer at a Thursday night pub gig might have 30 minutes from the time you arrive to when doors open. A corporate event’s AV team might have two hours — but also three other acts on the same stage.

When you arrive with a patchlist in your head rather than on paper, the engineer is writing down what you tell them in real time, asking clarifying questions, and hoping they got it right. When you arrive with a patchlist sent 48 hours ago, they have already built the initial channel layout and spent those 30 minutes doing something useful.

The band that makes the engineer’s job easier gets better treatment — faster checks, more time dialling in the mix, a sound person who is already invested in making the show work.

The Patchlist: Your Engineer’s Most Important Document

The patchlist is a channel-by-channel breakdown of every input on stage. It tells the engineer what they are building before a single cable is plugged in.

A complete patchlist row includes:

Field	Example
Channel	1
Source	Kick drum (inside)
Mic / DI	Shure Beta 52 / Beta 91A (if dual-mic)
Stand type	Short boom on floor
Notes	No phantom, low-cut at 80Hz

The notes column carries the information that causes surprises at soundcheck when it is missing:

• Instruments that need phantom power (condenser mics, active DIs)
• Sources where you want a pad engaged at the preamp
• Stereo pairs that must go to adjacent channels
• DI outs from keyboards that go to two channels
• Click track or backing track outputs and which channel they are on

Keep it scannable. Engineers read patchlists on a phone in a noisy venue with one hand while doing something else with the other. Dense paragraphs do not get read. A clean table with one row per input does.

Building a Patchlist That Works for Any Venue

The house engineer at a bar does not have the same rig as the A1 at a theatre. Write the patchlist for the instrument and source, not for a specific mic model — the engineer may not have your preferred microphone, but they know how to mic a snare drum with what they have if they know it is a snare drum.

Specify: instrument type, source (DI vs. mic’d, overhead vs. clip), stand type, phantom and pad requirements, any stereo routing.

Leave optional: preferred mic models (note as a preference, not a requirement), EQ settings (the engineer has their own approach), effects (discuss at soundcheck).

A patchlist that works at every venue is one that describes what you have and what it needs — not one that prescribes what the engineer must provide.

The PA Notes Field

Some songs have details the FOH engineer should know in advance: a long outro that fades to silence (they do not need to chase a fader), a song where the vocalist moves to a handheld mic mid-song, an intro where the band plays quietly before the first downbeat.

In Gigmeister, you can add per-song PA notes to each entry in your setlist. These notes appear in the Soundman View — the real-time read-only link you share with the FOH engineer. They see the notes for each song as it comes up in the set, before the song starts.

This is the difference between a reactive engineer (scrambling to adapt) and a prepared engineer (already set up for what is coming).

The Stage Plan: Getting Everyone in the Right Place

A stage plan is a visual diagram of who stands where — instrument positions, monitor wedge positions and assignments, amp placement, and cable runs. Its purpose is to get the physical stage set up before you arrive, so you are not spending the first 20 minutes moving amplifiers.

Most bands use the same stage layout for the majority of their gigs. The drummer is in the back centre, the bass amp is stage right, keyboards are stage left, the guitarist moves between centre and stage right depending on song. Build the plan once and reuse it.

What to Include in a Stage Plan

• Musician positions — labelled by name or instrument. If the vocalist and the guitarist share centre stage, show it.
• Monitor wedge positions — which wedge faces which player, and which aux send it is on. “Monitor 1 faces vocals and keys, Monitor 2 faces drums” is enough.
• Amp positions — with a note for whether each goes direct-in (DI) or mic’d.
• Drum kit position and orientation — including whether the kit is elevated on a riser.
• Keyboard and guitar riser positions — if applicable.
• Cable run notes — anything that crosses a walkway or audience area that needs to be addressed before people are moving around.

The goal is for the venue’s crew to have the stage mostly right before you arrive. You will still adjust things — but “mostly right” is far faster than starting from scratch.

Building the Plan Once and Reusing It

In Gigmeister’s Rider Pack, the stage plan editor is a visual canvas: drag positions, label them, save. The plan is part of your rider share link. Every venue that receives the link gets the current version.

When your guitarist moves from a combo amp to a Kemper and the input routing changes, update the plan once. Every venue with the link sees the new version immediately. There is no version to recall.

The Tech Rider: What the Venue Owes You

The tech rider describes what the venue needs to provide for your show to work. It covers PA system requirements, monitor setup, power, backline (if applicable), and any specialist equipment.

A practical tech rider for a working band without excessive demands:

PA system: full-range stereo system appropriate for the room size, with subwoofers. No specific brand required.

Monitor system: minimum two independent monitor mixes (wedges or IEMs compatible). For larger bands: four independent mixes.

Inputs: minimum 16-channel capability at FOH (more for larger bands — specify based on your channel count).

Power: clean power with a dedicated circuit for the backline if possible. Specify any high-draw requirements (Leslie cabinet, high-powered keyboard rig).

Backline (if venue-supplied): specify exactly what you need. If you bring your own, say so clearly so the venue does not set up something that will not be used.

How Detailed Is Too Detailed?

A venue reading a 12-page technical rider for a Thursday bar gig will ignore most of it. Match the detail level to the gig type and the venue’s capacity to respond.

For pub and club gigs: a one-page rider covering channel count, monitor sends, and power requirements is right.

For corporate and private events: two to three pages, covering everything above plus any AV integration (HDMI for visuals, walk-in/walk-out music from a laptop, wireless handheld mics for speeches).

For festivals and theatres: full technical specification with addenda for backline and power requirements.

Include a short “essentials” block at the top — three or four items that are genuinely non-negotiable — for venues that will not read beyond page one. Everything else is a preference.

The Hospitality Rider

The hospitality rider covers what the venue provides for the band off stage: catering, dressing room, parking, and load-in access. Keep it proportionate to the gig.

A sensible hospitality rider for a mid-tier function or event band:

• Parking: clearly marked spaces close to the load-in entrance, held from arrival to departure
• Dressing room: one clean room with chairs, a mirror, and a power outlet per device (or a power strip)
• Water and refreshments: water on stage throughout the show; light snacks or a hot meal for multi-hour bookings
• Meal allowance: a fixed amount per head if catering is not practical

Leave out demands that signal inexperience for your tier — a headlining stadium act’s hospitality requirements do not translate to a private birthday party booking. Unreasonable riders create friction with venues and do not get honoured anyway.

Sharing Everything With a Single Link

Four separate PDFs in an email — patchlist, stage plan, tech rider, hospitality rider — is how important documents get missed. One gets moved to a folder, one gets forwarded to the wrong person, one is the version from two years ago.

The Rider Pack share link in Gigmeister is a single URL that surfaces all four documents in one view. Send it once in the booking confirmation email. The venue coordinator, the stage manager, and the house engineer can all access the same link.

When you update the patchlist before a run of gigs, everyone with the link sees the new version. No re-send required. No “which version is current?” question at soundcheck.

The link requires no login to view. It is printable. It works on any device. For venues that prefer a physical copy, the engineer can open it on their phone or print it from the URL.

The Soundman View: Setlist Mode for Front of House

During the show, the FOH engineer benefits from knowing what song is next — especially on variable-order setlists or gigs where the band calls songs from the stage. Gigmeister has a dedicated Soundman View mode built into the setlist page: a cleaner, read-optimised layout showing song titles, order, and per-song notes without the performance navigation controls.

What the Soundman View Shows

• The full setlist with song order
• The currently playing song (highlighted)
• Per-song notes (PA notes, stage banter cues, instrument changes)
• Duration of each song

The view updates live as the band leader advances through songs.

Using Soundman View at the Desk

The practical setup: a dedicated device (tablet or spare phone) at FOH, logged into the band’s Gigmeister account, open on the setlist in Soundman View mode. The engineer follows the set without a printed sheet, and per-song notes are visible before each song starts.

An engineer who can see “keys-led intro, vocal enters bar 5, big reverb tail on snare in second verse” before the song starts is set up rather than reacting. These notes live on the song in Gigmeister and are visible in the Soundman View alongside the setlist order.

Soundman View is a mode within the authenticated app — the FOH device needs to be logged in. A public no-login share link for the sound engineer (combining setlist and patchlist) is on the roadmap.

The Pre-Show Checklist

A consolidated checklist for every gig:

• Patchlist updated and included in rider share link
• Stage plan current and in the rider share link
• Tech rider accurate for tonight’s setup
• Rider share link sent to the venue contact
• Setlist locked for tonight (or finalised at soundcheck)
• PA notes added for any songs with specific requirements
• FOH device logged in and open on Soundman View mode
• MIDI program changes tested against all devices
• Backing tracks verified (levels, routing, trigger settings)
• Calendar event updated with load-in and soundcheck times for all band members

The first time through this list takes a few minutes. After the first gig, it takes 90 seconds to confirm that nothing has changed.

Get Started

Build your rider pack, share it with venues, and give your sound engineer real-time setlist visibility. Create a free Gigmeister account or read the Rider Pack documentation to set up your production documents.

Tags:

• gig-management
• live-performance
• guides

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:

1. 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.
2. 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.
3. 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.

Tags:

• live-performance
• backing-tracks
• guides

Chord Sheet Formatting for Live Performance

Jan 14, 2026

Gigmeister

A chord sheet that is easy to read in your living room can become impossible to read on stage. Between dim lighting, a music stand two feet away, and the pressure of a live performance, formatting matters more than you think.

Here is how to format chord sheets that actually work when it counts.

The Problem with Most Chord Sheets

Chord sheets you find online are formatted for screens, not stages. They have tiny text, inconsistent spacing, chords jammed between lyrics with no clear alignment, and way too much content on a single page. Printing one of these and putting it on your music stand is a recipe for squinting through half your set.

Good stage chord sheets share a few qualities: large readable text, chords positioned unambiguously above the lyrics they belong to, minimal clutter, and no page turns mid-song if you can avoid it.

Bracket Notation

The most reliable way to embed chords in text is bracket notation. Place the chord name in square brackets at the exact position where it falls in the lyric line:

[Am]Sitting on the [G]dock of the [C]bay
[Am]Watching the [G]tide roll a[C]way

This format is clean, unambiguous, and works consistently across rendering engines. Every chord is clearly tied to a specific word or syllable. There is no guesswork about where the change happens.

When rendered, the brackets are stripped and the chords appear above the lyrics, aligned to the exact character position. Gigmeister uses this bracket notation throughout — you type chords inline and they render with correct positioning automatically.

Chords Without Lyrics

For instrumental sections, chord-only lines work with the same bracket syntax:

[Em] [G] [D] [A]
[Em] [G] [D] [A]

Section Labels

Mark sections clearly so you can jump to any part of the song at a glance:

[Verse 1]
[Am]Sitting on the [G]dock of the [C]bay

[Chorus]
[G]Sitting on the [Em]dock of the [C]bay [D]

Keep section labels consistent across all your songs. If you use “Verse 1” in one song, do not use “V1” in another. Consistency means your eyes know what to look for.

Two-Column Layout

Longer songs can run to two or three pages, which means page turns during performance. A two-column layout solves this by fitting more content into the same vertical space.

Two-column works best when:

• The song has more than 20 lines of content
• You are reading from a tablet or a landscape-oriented screen
• You want the entire song visible at once without scrolling

It works less well when:

• The song has very long lyric lines that wrap within a column
• You are on a narrow phone screen

Gigmeister supports two-column layout as a per-song toggle. Enable it in the song editor and the chord sheet splits into two columns automatically.

Font Sizing and Readability

On stage, you are typically reading from 2 to 4 feet away. Here are practical guidelines:

Tablet on a music stand (2-3 feet): 16-20pt for lyrics, 14-18pt for chords. Most tablets handle this well in portrait mode.

Laptop on a keyboard stand (3-4 feet): 20-24pt minimum. You have more screen real estate, use it.

Printed sheets on a music stand: 14pt minimum for lyrics. Bold the chords or use a contrasting color if printing in color.

Phone on a mic stand clip: Honestly, avoid this if you can. If you must, use the largest font that fits and strip everything except chords and section markers.

The rule of thumb: if you have to lean forward to read it, the font is too small.

Transpose Without Rewriting

Different instruments, different keys. Your vocalist wants the song in Eb, your guitarist learned it in E, and your keyboard player can play in anything but prefers concert pitch.

Per-user transpose solves this cleanly. Each band member sets their own transpose offset for each song. The underlying chord data stays the same, but everyone sees the chords in their preferred key.

This is far better than maintaining multiple versions of the same chord sheet. One source of truth, personalized display. Gigmeister handles transpose per user — your +2 semitone offset does not affect what your bandmates see.

Stripping Content by Role

Not everyone needs the same information:

Vocalists mostly need lyrics with section markers. Chords are visual noise.

Instrumentalists mostly need chords and structure. Full lyrics get in the way.

Consider offering both views from the same source. A “hide lyrics” mode shows only chord markers and section labels. A “hide chords” mode shows clean lyrics. Same chord sheet, filtered by role.

AI-Assisted Chord Sheets

If you are starting from plain lyrics and need to add chords, AI can speed up the first draft significantly. Paste in your lyrics, and AI analyzes the harmonic structure to place chord markers.

A few caveats:

• AI-generated chords are a starting point, not a finished product. Always review for accuracy.
• Complex jazz harmony, unusual voicings, and slash chords trip up AI models regularly. Expect to correct these.
• Simple pop, rock, and folk songs with standard progressions get surprisingly accurate results.

Gigmeister Pro includes AI chord sheet generation that outputs bracket-notation chord sheets you can edit immediately.

Formatting Checklist

Before you take a chord sheet on stage, run through this list:

• Font size: Readable from your performance distance?
• Section labels: Clear and consistent (Verse, Chorus, Bridge)?
• Chord placement: Unambiguous — every chord aligns to the right word?
• Length: Fits on one page or screen without scrolling? If not, use two-column.
• Transpose: Set to your instrument’s key?
• Clutter: Stripped out tab notation, comments, and other studio-only content?

Get Started

Build your chord sheet library with bracket notation, per-user transpose, and two-column layout. Create a free Gigmeister account or read the full chord sheet documentation for setup details.

Tags:

• chord-sheets
• live-performance

Building the Perfect Setlist: A Musician's Guide

Jan 10, 2026

Gigmeister

A great setlist is not just a list of songs. It is a plan for how you are going to take an audience on a ride over the course of a night. The difference between a band that gets rebooked and one that does not often comes down to how well the set flows — not just what songs you play, but the order you play them in.

Here is a practical framework for building setlists that work, whether you are playing a 45-minute opening slot or a four-hour wedding.

Start Strong, Finish Stronger

Your first song sets the tone. Pick something the band plays confidently, that gets energy into the room quickly, and that does not require a long intro or buildup. You want to make a statement in the first 30 seconds.

Your last song is what people remember. Save one of your strongest tunes for the closer. If you are doing an encore, the real closer is the encore — the song before it just needs to make the audience want more.

The Energy Curve

Think of your set as a wave, not a straight line. The energy should rise and fall intentionally:

Opening block (songs 1-3): High energy. Establish the vibe. Get the audience engaged. These should be songs you could play in your sleep.

Mid-set dip (songs 4-7): Bring it down slightly. This is where you can put a ballad, a deep cut, or a song with a longer instrumental section. The audience needs contrast to appreciate the highs.

Build back up (songs 8-10): Ramp the energy again. Each song should be a small step up from the previous one.

Climax and close (last 2-3 songs): Your biggest songs. Maximum energy. Leave everything on stage.

For multi-set gigs, apply this pattern to each set independently. Each set should have its own arc.

Key Transitions

Playing three songs in a row in the key of G is fine musically, but it can start to sound monotonous. Vary your keys across the setlist. Some transitions that work well:

• Same key: Works when the tempo or feel changes significantly
• Up a half step or whole step: Creates a natural lift in energy
• Relative major/minor: Smooth transition (Am to C, Em to G)
• Fourth or fifth: Strong, satisfying movement (C to F, G to C)

Avoid awkward jumps like tritone intervals (C to F#) back to back unless you have a clear transition planned. A few seconds of silence or stage banter can reset the listener’s ear between songs that clash harmonically.

Tempo Pacing

Tempo is as important as key for flow. Three fast songs in a row will exhaust the audience (and the band). Three slow songs will lose the room.

A good rule of thumb: alternate tempos in groups. Two uptempo songs, then a mid-tempo, then a ballad, then back up. The exact pattern depends on your setlist length and the venue.

For dance bands: your audience needs tempo variety to catch their breath. Nobody dances for 90 minutes straight. Give them peaks and valleys.

Timing Your Set

Know exactly how long your set needs to be and plan accordingly. Add up song durations, then add transition time between songs:

• Tight transitions (straight into the next song): 5-10 seconds
• Normal transitions (brief tuning, count-in): 15-30 seconds
• Banter breaks (talking to the audience): 30-60 seconds

For a typical 45-minute set of 10-12 songs, you will lose 3-5 minutes to transitions. Plan for it.

The Setlist as a Living Document

Your setlist should evolve with every gig. After each show, note what worked and what did not:

• Did the energy dip too long in the middle?
• Was there an awkward key change that needed a longer transition?
• Did the audience respond better than expected to a particular song order?

Use this feedback to refine your next setlist. The best setlists are not built in one sitting — they are iterated over dozens of gigs.

Get Started

Build your setlists with drag-and-drop ordering, automatic duration tracking, and section markers for multi-set gigs. Create a free Gigmeister account or read the full setlist documentation for setup details.

Tags:

• setlists
• live-performance

How to Use MIDI Program Changes in a Live Band

Jan 7, 2026

Gigmeister

If you play keyboards, guitar effects, or any MIDI-capable instrument in a live band, you have dealt with the scramble of switching patches between songs. You are mid-set, the last chord of “Take Me to the River” is still ringing out, and you need to get from your Rhodes patch to a synth pad before the intro of the next tune. Fumbling through menus on stage is not a good look.

MIDI program changes solve this. Here is how they work and how to set them up for a seamless live show.

What Is a MIDI Program Change?

A MIDI Program Change (PC) message tells a device to switch to a specific preset. It is a single byte value from 0 to 127, giving you access to 128 programs on any given MIDI channel.

When you send PC 42 on channel 1 to your keyboard, it loads program 42. Simple enough. But most modern instruments have far more than 128 presets, which is where bank selection comes in.

Bank Select: MSB and LSB

The MIDI specification added Bank Select messages to extend beyond the 128-program limit. Bank selection uses two Control Change (CC) messages sent before the Program Change:

• Bank Select MSB (CC 0): The “coarse” bank selector. Values 0-127.
• Bank Select LSB (CC 32): The “fine” bank selector. Values 0-127.

Together, MSB and LSB can address up to 16,384 banks, each containing 128 programs. That is over two million possible patches — more than enough for any device.

The message sequence always goes in this order:

1. CC 0 (Bank MSB) — select the bank group
2. CC 32 (Bank LSB) — select the specific bank
3. Program Change — select the patch within that bank

Some devices only use MSB, some use both MSB and LSB, and some ignore bank select entirely. Check your device’s MIDI implementation chart to know which messages it expects.

MIDI Channels

MIDI supports 16 channels per connection. Each musician’s gear typically lives on its own channel. A common setup:

• Channel 1: Main keyboard (piano, Rhodes, organ)
• Channel 2: Synth (pads, leads)
• Channel 3: Guitar multi-effects processor
• Channel 4: Backing track trigger

This isolation means one program change message will not accidentally switch patches on another player’s gear.

The Problem with Manual Patch Changes

On a typical gig night, you might play 20 to 30 songs. If you have two MIDI devices, that is 40 to 60 patch changes. Do any of these manually and you will eventually:

• Load the wrong patch
• Miss the intro of a song while scrolling through presets
• Forget which program number goes with which song

The answer is automation. Store the correct program change for each song, and let software send the messages as you advance through the setlist.

Setting Up Automated Program Changes

The basic workflow for automating MIDI program changes on stage:

1. Document Your Patches

Before you touch any automation, make a list. For every song in your repertoire, write down which patch you need on each device. Be specific: device name, bank number, program number, and the patch name for reference.

2. Configure Your MIDI Routing

Connect your devices via USB-MIDI or 5-pin DIN cables to your tablet, phone, or laptop. Make sure each device is assigned to a unique MIDI channel.

3. Assign Programs to Songs

In your setlist software, assign the correct bank and program number to each song for each device. When you advance to the next song in your setlist, the software sends the program changes automatically.

4. Test Before the Gig

Run through your entire setlist at home or in rehearsal. Verify every patch loads correctly. MIDI numbering is notoriously inconsistent — some manufacturers number programs starting from 0, others from 1. A program listed as “001” on your keyboard might be MIDI program change 0.

Device-Specific Quirks

Every manufacturer handles MIDI slightly differently:

• Nord keyboards use a lettered bank system (A:11, B:23) that maps to specific MSB/LSB combinations
• Line 6 Helix expects Bank MSB for setlist number and PC for preset within that setlist
• Kemper Profiler uses CC 0 for performance slot and PC for rig within it
• Boss GT-1000 uses Bank MSB/LSB pairs that map to user and preset banks

This is where pre-configured device profiles save you hours of reading MIDI implementation charts. Gigmeister supports 51+ devices out of the box with correct bank/program mappings already set up.

Per-Song Configuration

The most practical setup is one where each song in your library has MIDI programs saved for each device. When you build a setlist and start performing, advancing to the next song triggers all the right patch changes at once.

In Gigmeister, you configure this in the MIDI tab of each song. Select your device, pick the program by name (no need to memorize numbers), and you are done. During performance, swiping to the next song or pressing a foot pedal sends all program changes simultaneously.

Foot Pedal Navigation

Hands-free navigation is critical for performers. Map a MIDI CC message from a foot pedal to advance songs in your setlist. This way, your hands stay on the instrument and your patches change automatically as you step through songs. Learn more about MIDI foot pedal controls.

Tips for a Reliable MIDI Setup

Use short cables. Long MIDI cable runs introduce latency and data errors. Keep cables under 15 feet when possible, or use USB-MIDI for direct connections.

Send program changes early. Some devices take 100-500ms to load a patch. Advancing to the next song a beat early, or using software that sends changes during the transition, prevents audible gaps.

Have a backup plan. If your MIDI rig fails mid-gig, know how to manually select your most critical patches. Write the top five on a piece of tape stuck to your keyboard.

Test with your full rig. MIDI issues that do not appear with a single device can surface when you add a second or third device. Test everything connected together.

Getting Started

If you want to stop fumbling with patches on stage, set up MIDI automation in Gigmeister. Add your devices, assign programs to songs, build your setlist, and let the software handle the rest. Read the full MIDI documentation for setup details and supported devices.

Tags:

• midi
• live-performance