Amplitube and Predictive Loading

[jhaimerl]

I am running Gig Performer on a mac-mini (Tahoe 26.3.1). There are 3 instances:
1 - main instance which has a gig script that controls the midi foot pedal display to show song parts

2 - My guitar rig, running Amplitube 5

3 - other guitarist’s rig running Amplitube 5

These are synched via OSC to switch songs/songparts (instance 1 triggers instance 2, which triggers instance 3). A midi PC triggers the main instance to switch song parts in normal operation… Song parts are mapped to CCs on the foot controller.

It seems pretty stable for long periods of up to 30-40min through song changes and song part changes… then (seeming) randomly when I change songs (, instance #2 crashes… Attached are a few of the crash reports. I’m not sure how to interpret them or how to start debugging this. Any suggestions?

Archive.zip (68.1 KB)

Thanks!

[jhaimerl]

Just another data point:
I started everything up a few minutes ago, and started clicking songs randomly in the setlist on the main instance. After about 20 times with no errors I opened Ableton Live on my other computer and started changing songs with PC commands (Ableton is normally used to run our show, and is what normally commands my guitar rig to switch to a song). After about the 10th song change, instance 2 crashed again. “Gig Performer quit unexpectedly”.

[jhaimerl]

… and now it crashed just by manually changing songs in the main instance setlist…. so apparently not related to PC commands

[pianopaul]

All crash logs state that AmpliTube 5 is crashing.

[jhaimerl]

oh boy… how do I figure out why… and it is only one of the two instances…

[pianopaul]

Contact IK Multimedia and give them the crash log

[jpt]

Out of curiosity…which Amplitude plugin are you using…VST3 or AU?

[jhaimerl]

I’m using AU plugins

[dhj]

@jhaimerl

I’m not sure how to interpret them or how to start debugging this

@pianopaul is correct that Ampitube 5 is crashing and you might want to try the VST3 version instead.
It is crashing from inside the audio processing thread and apparently (based on what I can see) it doesn’t like responding to the call to set the BPM

Thread 5 Crashed:: com.apple.audio.IOThread.client
0   AmpliTube 5                   	       0x1392e9c80 IK::Comp::ArrayBase::Document::OnSetBPM(float, unsigned int) + 152
1   AmpliTube 5                   	       0x138db4024 IK::Products::AT4::MainDocument::OnSetBPM(float, unsigned int) + 132
2   AmpliTube 5                   	       0x138b4add0 IK::Products::AT5::AudioProcessor::UpdateBPM() + 316
3   AmpliTube 5                   	       0x138b46600 IK::Products::AT5::AudioProcessor::ProcessBlock(juce::AudioBuffer<float>&, juce::MidiBuffer&) + 96
4   AmpliTube 5                   	       0x138b447f4 IK::JTK::MainAudioProcessor<8, 64, 2, 2>::processBlock(juce::AudioBuffer<float>&, juce::MidiBuffer&) + 656
5   AmpliTube 5                   	       0x138a8799c JuceAU::Render(unsigned int&, AudioTimeStamp const&, unsigned int) + 3464
6   AmpliTube 5                   	       0x138a9f450 ausdk::AUMethodRender(void*, unsigned int*, AudioTimeStamp const*, unsigned int, unsigned int, AudioBufferList*) + 1360
7   AudioToolboxCore              	       0x19e05128c AudioUnitRender + 436
8   GigPerformer5                 	       0x1033c4c18 0x102bd8000 + 8309784

[jhaimerl]

Thanks. I just saw that too. I am scratching my head. It now gives same crash when starting up! I disabled external BPM, but that made no difference. Switching to VST will be lengthy, as I have about 20 racks in 2 different instances. I also have problem report in to IK, but so far no response. Considering switching platforms to something like Helix Native, but I’m sure it has its own issues.

[jhaimerl]

Could it be I’m running out of memory when it is starting? 16GB physical memory and both guitar instances show using 14.2GB, while the main is 831MB. I am only using about 30% of the racks that I created and would be willing to reduce to a minimal set.

[jhaimerl]

I turned predictive loading back on and set to 3. Now it loads again. Wondering now if I should leave it on and maybe even try 1.
I have all our ~60 of our songs in just one setlist and we just jump around in it.

[jpt]

@jhaimerl

I’m using AU plugins

For grins…try VST3 and see if it makes a difference.

[jhaimerl]

I will but it will take a while to switch everything.

[jhaimerl]

I have reduced my set of racks to only those currently used - went from 20 to 10.
I am setup for predictive loading of 1 (so that only the current song’s racks are loaded).
Also switched all Amplitubes in every instance/rack to be a VST3.

It all worked good for about 15min of switching back and forth between songs. I was watching the meters on my main instance and could tell from the noise that the 3rd instance was still up and running. As soon as I switched desktops to view the 3rd instance, it crashed.

(In our rehearsals, this is what was happening… we’d get through a song and decide we wanted to change my sound or other guitarists… and when I went into an instance and reassigned the song part to another rack, one of the instances would die).

I’m wondering if this is a GP problem not an Amplitube problem, as it seems to happen when switching windows of GP. (Just because amplitube crashed, doesn’t make it an amplitube issue, if it is provided some invalid input, right?).

@jpt @pianopaul

I sent a problem report to IK multimedia yesterday, but no response yet.

[jhaimerl]

It crashed again without changing windows…

[edm11]

I use multiple instances of GP and Amplitube with no such crashes.

There could be something going on with a particular preset(or a few) inside Amplitube. I would suggest paying attention to precisely which preset inside Amplitube was being switched to when a crash occurs. Then when you restart, save that Amplitube preset as a GPPreset and share the file here(zip it first) and I’ll take a look at it.

[jhaimerl]

@edm11,

I tried the same songs and sequence of songs and the instance wouldn’t die again… Seems more random than being song / rack dependent.

I am considering a test of shrinking down to a single instance and moving amplitube into the global rackspace for each of the two guitars… and using a knob to change presets within amplitube. I see you suggested a method for preset switching in:

Changing Presets in Amplitube

I understand this is not the recommended way of working, but it is the way that works best for me. And I hope maybe I can get some advice/help. I am trying to change presets in Amplitube. I have no no problem doing so Amplitube standalone, however the the exact same message sent to Amplitube in GP does not work and no MIDI activity shows on Amplitube MIDI meter. I have also tried setting up at MIDI input assigned to Amplitube and assigning a widget connected to that MIDI input to PC and that do…

Is that similar to how you run? Or are you more like my current method with an Amplitube in each rack that is saved with the desired preset selected?

[edm11]

I use separate rackspaces for each distinct preset. PC switching inside Amplitube isn’t the greatest. The same can be said for most plugins though-- some handle it ok, others not. That’s why utilizing different rackspaces works best.

[edm11]

Does the crash only occur when you’re switching associations of rackspaces to song parts inside a particular instance? If not, which other conditions made it crash?