It took a while, but it crashed again. Here’s the one that it crashed on…
PinkTacoCrunch.gpp_vst3.zip (8.1 KB)
These are my GP files:
Archive 2.zip (696.3 KB)
Thanks, I’ll check the gig files in a bit.
Looking at the preset, in concert with what @dhj mentioned about the crash being BPM related, I’d say try removing the X-VIBE pedal (which has BPM enabled) and see if the crash disappears. The pedal itself is in bypass but it might still be making a strange call to get the host BPM and causing a crash.
Related to BPM… Another data point…
When Ableton on my laptop opens a song and starts playing, the first thing it does is plays midi clips that control our ipad displays… also sends the PC message to the GP computer switch songs… a beat or so later, it pauses until I hit a button to start the song. This is the period in which the instance crashes.
I can see on my GP screen that the tempo varies a LOT (48 - 150ish) as in my little basement setup I am using wireless between the computers. In band space, they are wired and the tempo is rock solid at what Ableton is doing. This was happening even with the rock solid tempo in rehearsal.
I took out ALL the X-VIBES… Still crashing on random switches to any song… Now I also have a delay in the output master rack, that I believe ping-pongs with 1/4 note delay based on the BPM. Should I disable those from BPM synch too?
I use that same delay in some of my racks, so I don’t think its the issue.
Explain more about the chain of progression from Ableton to GP. Ableton plays midi clips that send PC messages to GP for the song change and then…
What pauses? You hit a button where?
On my laptop runs Ableton live. There is a file for each song that has in-ear clicks, cues, any backing tracks, and light-key DMX lighting scenes. I have a streamdeck on my mic-stand with a button for each song. When the button is pressed, it opens the ableton file for the song and creates a space-bar press in ableton to start the song. It plays 2 measures then pauses. In those 2 measures, the commands are sent out to setup equipment and send song selection to our iPads running Songbook+. Also in the 2 measures is were I used to send commands to my Line 6 helix and vocal processor, but now those are disabled and another track sends the program change command to my guitar mac-mini rack. Every song has a unique PC number assigned to it to open.
When everyone in the band is ready, I press another button on the streamdeck and it starts the song…
The GP/Amplitube instance is crashing during the song-load / first 2 measures before the pause.
**** It also happens randomly when not even connected to the laptop and I just switch songs within the setlist. ****
Ok, let’s leave Ableton out of it for a minute then.
You can crash GP just from switching songs.
-
Are there any Actions in song parts?
-
If you go into Panels view and scroll up and down the rackspace list, do any crashes happen? (Make note of the rackspace that crashes so we can look at it)
No issue scrolling through the racks.
I don’t know what actions on song parts are… so I don’t think so… I have a couple song parts where I saved a variation, but that’s it.
Have not been able to make it crash for the past 10min by selecting songs in the setlist.
When you click double-click a song part, the Song Part Properties window has a section called Actions where you can choose from a number of things that will happen when that song part is activated.
Be aware that GP tends to exercise the VST APIs quite a bit more agressively than many hosts and so bugs in plugins can show up in GP much earlier (or much more easily reproducible) than in some other plugins.
If you remove amplitube from your system (easy to do, just open an empty gig file, go to plugin manager and disable Amplitube and then open your real gigfile), do you still get a crash?
Also, did you try changing from AU to VST3 version?
I only have set the PC for opening the song on the first part of each song. Will look through to ensure that nothing was inadvertently set.
@dhj - I am running Amplitube as a VST3 and still having the issues.
I was unable to get it to crash by manually picking songs in the setlist view on the main instance.
Finally I went back to Ableton… Started getting the crash again and it is right after the PC message before the pause. I disabled the feature in Ableton that sends the MIDI clock messages so as to disable an external BPM source for GP/Ableton. Now I am unable to make it crash!!!
Wondering if for my show next week, I keep this disabled. In absence of an external source, is there an easy way to set the tempo in each song in GP manually? It is probably close enough for delay echos to be within a few BPM.
I would disable that feature in Ableton until you can sort out what is happening there.
Yes, per song (or even song part if you need it).
Double click the song to bring up the Song Properties window.
Tempo can be set there.
About an hour later with external BPM disabled (at the Ableton Source) and it is still stable…
It has to be related to the widely varying BPM seen over the wifi in GP, as mentioned earlier. What stumps me is that the crashes occurred even when I was on the wired network in the rehearsal space not seeing the large variations. But there still was a pause after 2 measures - maybe that was the offender (?).
I wonder if someone from Gig Performer should look at this crash…
Thanks for the info on the BPM override. I assume that will affected the downstream instances too (?)
Not sure – it’s still Amplitube that is crashing
It’s crashing on values that GP gives it for BPM… wonder if there’s a bug missing limit checks in GP or Amplitube or both.
This problem is still occurring! It happened 2x last night in a 2.5hr rehearsal. The crash happens (seemingly randomly, on random songs) when I switch songs manually in the master instance setlist or when songs are switched via MIDI from another computer triggering the master instance to switch. When I switch racks within a song (i.e. a different amplitube gets loaded for a lead or rhythm sound, which happens multiple times per son), I have never had a crash.
To summarize what I’ve done so far:
- Turned predictive loading to 1
- Switched Amplitube from AU to VST3
- Eliminated X-VIBE plugins in Amplitube
- Stopped syching tempo externally and set an override for each song to match the desired tempo
- Switched each amplitube pedal to use its own BPM, instead of external
I also ensured each instance has the exact same audio interface settings.
IK multimedia is investigating (I’m providing my GP files to them today), but I’m not sure that the crash isn’t something Gig Performer is doing when it switches songs.
Is there anyone in the GP team that can also look at this? (the GP support page points here!)