[Solved]Song Parts do not switch in Setlist Mode despite correct incoming Program Changes

this is written with the support of chatGPT as my English is not as good as I wished it would be.

:pushpin: Issue Report: Song Parts do not switch in Setlist Mode despite correct incoming Program Changes

Gig Performer version: 5.1.4
macOS version: macOS (Mac mini, Apple Silicon)
MIDI source: StageTraxx 3 on iPad
MIDI transport: Bluetooth MIDI via MIDI-MTTR (iPad → macOS)
Verification: Global MIDI Monitor in GP shows correct Program Change messages
Hardware used:

  • iPad (USB-C) running StageTraxx 3

  • Mac mini (Apple Silicon) running Gig Performer 5.1.4

  • Bluetooth MIDI using MIDI-MTTR (iOS + macOS versions)

  • No other MIDI hardware involved
    Audio hardware: RME Babyface (not relevant to the issue)


Problem Description

When running Gig Performer 5.1.4 in Setlist Mode, Song Parts do not change in response to MIDI Program Change messages.

I am using StageTraxx 3 on my iPad to send Program Change (PC) messages when I switch songs in ST3. The MIDI routing iPad → Mac mini is handled by MIDI-MTTR, and the connection is stable.

In Gig Performer, I open the Global MIDI Monitor, and I can see all incoming Program Change messages exactly as expected:

  • PC numbers are correct

  • They appear immediately

  • No filtering or blocking is occurring

  • The messages originate from the expected MIDI port

However:

:red_exclamation_mark: Despite the correct Program Change messages arriving, Gig Performer does NOT switch the Song Parts in Setlist Mode.

No Song Part is activated, no Song changes, and nothing in the Setlist UI reacts to the incoming PC messages.


Current configuration

  • In Options → Setlist, I have NOT enabled any special MIDI assignments except selecting the correct MIDI input ports.

  • I have NOT assigned Next/Previous Song or Song Part functions to MIDI.

  • The Song Parts themselves are correctly created (Intro, Verse, Chorus etc.) and linked to valid Rackspaces/Variations.

  • The Songs are visible and selectable manually.

  • Switching Song Parts manually works correctly.

  • Only the MIDI-triggered changes do not work.


What has been verified

  1. Program Changes arrive

    • Verified in the Global MIDI Monitor
  2. Correct MIDI ports are enabled

    • Only the Bluetooth MIDI port from MIDI-MTTR is active
  3. Setlist Mode is active

    • I am working in the Setlist view, not Rackspace view
  4. Song Part PC metadata exists

    • PC numbers, MSB, LSB are visible inside Song Part Properties

    • But assigning those values does not cause GP to react

  5. No MIDI filtering

    • No scripts, filters, or MIDI blocks are used

    • Global MIDI settings are untouched except port selection

  6. Rackspaces are correctly assigned to Song Parts

    • The audio works and manual Song Part switching is functional

Expected Behavior

Gig Performer should:

  • Respond to incoming Program Change messages

  • Select the corresponding Song or Song Part in Setlist Mode

  • Trigger the associated Rackspace/Variation


Actual Behavior

  • Program Changes appear in the Global MIDI Monitor

  • No Song or Song Part changes at all

  • UI does not react to incoming PCs

  • Setlist remains in the current Song/Part unless changed manually


Request / Question

Could you please clarify:

  • Whether Program Change–based Song/Song Part switching is still supported in GP 5.1.4

  • Whether additional configuration is required beyond enabling MIDI ports

  • Whether the PC/MSB/LSB values inside the Song Part Properties are still used for triggering, or only for metadata

  • If this is a bug, an intentional change in GP 5.1.x, or a missing mapping

  • How to correctly map incoming PCs to Song Parts in the current version

Thank you in advance for any guidance.

How looks your section “Program Change Control” in the Options Window?

Did you assign PC Numbers to Song Parts?

Please open the global midi monitor, send some program change messages from your controller and upload a screenshot of the global midi monitor so we can see exactly what is being sent in.

Responding to program changes is very basic functionality which works perfectly so there is clearly something wrong with how those messages are being sent in or how you have GP configured to respond.

I think so, but couldn’t find out.

I don’t understand this sentence - what could you not find out?

mean that’s a core functionality - often done. how could I upload the screenshot?

iPad connected via bluetooth. Select one song after the other…

Try sending changes on channel 1, not channel 11

Does your iPad let you choose program change numbers between 1 and 128 or between 0 and 127?

both, but I use multitracker for backing tracks which needs 1 to 128

sorry, multitracker needs 1 to 64 then lsb 1…

Maybe these infos help?

midi monitor shows pc just with passthrough.

No, it can’t be both. PC numbers, under the covers, are ALWAYS 0 based and so go from 0 to 127

Do me a favor – change the PC number for those two songs to 41 and 32 and then try sending messages again.

@Dagerry

If that is easier for you, please write your messages in German. I’ll then edit each post and add the English translation.

We have many German speaking members so they can jump in @kunst4life @schamass @tripleB and many other.

So no worries, I’ll add the translations.

I changed the pc always on the wrong side. Now I use zero-based PC numbers and it works fine. Thank you so much

Tut Leid dass ich erst jetzt reagiere. Ich war gelocked. Es funktioniert jetzt mit setzen PC von 0 weg. Aber was ich nicht verstehe ist, dass davor der Global midi Monitor zb PC 40 anzeigt, der Song Part auch und ich dann auf zero based setzen muss. Aber seisdrum. Es funktioniert und das ist das wichtigste. Herzlichen Dank fĂĽr die UnterstĂĽtzung.


Sorry for the late reply. I was locked out. It works now after setting the PC value away from 0. But what I don’t understand is why the Global MIDI Monitor shows, for example, PC 40 before, as does the song part, and then I have to set it to zero-based. But anyway, it works, and that’s the most important thing. Thank you so much for your support.

pc 40 is midi pc 39