Weird glitch - songs started to jump when I choose certain presets

spikeymcspikeface

spikeymcspikeface

Well-Known Member
Hi, a strange glitch has started to happen - it's not all the time, but it's enough that it's becoming a problem ...

Sometimes when I choose a preset loaded as part of a song the GT jumps to another song in the set that happens to use the same present (eg. if I select my lead patch in Song A, it jumps to Song B which uses that lead patch as well). It's not always the same presets effected, and it's not clear if there's any reason for the song it jumps to (it's not as if it's always the previous song that used that preset or the next song or whatever - it seems random, albeit it is a song programmed as part of that setlist). As you'd imagine, this is a bit of a challenge when you're in the middle of a show and suddenly you find the GT's jumped to the wrong song and you have to cycle forwards or backwards through the set to get back to the right song ...!

I've not really changed anything about my set-up for a long time, other than occasionally adding new presets or new songs, and everything's been fine for ages. I can't see or think of anything obvious to explain why this happens, so I'm at a bit of a loss ...

Any thoughts / suggestions ? Thnx.
 
I haven't seen any other reports of this so that's a good thing, but it does make it much more difficult to try and resolve, unfortunately.

I know this is a tough ask, but if you could somehow document or note the setlist, song, and presets involved, that could possibly help shed some light on the issue. At a minimum it would provide a starting point of where to look.

I have always been a huge proponent of backups. Whether it's computers, phones, effect processors or even MIDI footcontrollers. Date and organize them, you never know when they might come in handy.
 
A few things that might be relevant:

- Make sure that you have the GT's MIDI Receive Channel parameter set to None. Or, if you need it enabled (because, perhaps, you're controlling the Mastermind with a PC or other MIDI device) make sure that MIDI Receive Channel is set to a channel other than the one the Axe-Fx is on.

- Make sure MIDI PC Mapping is not enabled in the Axe-Fx. This is pretty much guaranteed to cause problems.

- Last, try turning off Poll State in the Mastermind's device settings for the Axe-Fx.
 
rjmmusic said:
A few things that might be relevant:

- Make sure that you have the GT's MIDI Receive Channel parameter set to None. Or, if you need it enabled (because, perhaps, you're controlling the Mastermind with a PC or other MIDI device) make sure that MIDI Receive Channel is set to a channel other than the one the Axe-Fx is on.

- Make sure MIDI PC Mapping is not enabled in the Axe-Fx. This is pretty much guaranteed to cause problems.

- Last, try turning off Poll State in the Mastermind's device settings for the Axe-Fx.
Click to expand...
Great, thanks - I've checked all of that, and have turned off Poll State for the AxeFx. I'll see how I go - as mentioned in my original post, it's a bit random insofar as sometimes this problem happens, sometimes it doesn't (I had 3 shows this weekend and it was a problem each time, hence my post); it's not always the same patches that cause the songs to jump, and there's no pattern I can see in terms of which songs it jumps to ... all very mysterious. So I'll report back if I'm still having problems ...

Thanks again.
 
I've been experiencing occasional weird presets jumps throughout the last years. (GT22 with Axe-Fx III)
Fairly certain my config is okay, so I've attributed it to a firmware quirk, possibly MIDI Bank-related.
I can't pinpoint it to a specific preset.
 
Yes, IIRC I disabled Poll State and that seemed to work.
But I can't really do without 'Poll State' for various reasons.

I'm relying on memory now, because I'm currently 8000 km away from my gear. ;)
 
Gotcha regarding the necessity of Poll State. Please give it another try when you're reunited with your gear and let us know.
 
For what it's worth, disabling 'Poll State' also worked to solve my original problem - like Alexander, I'm using an Axe FX 3 (with a GT16) and had put the problem down to a firmware update glitch as it hadn't been an problem for all the time I'd been using this set-up (until suddenly it was). For me, turning off 'Poll State' isn't an issue so I'm ok with this as a workaround. But Alexander's experience does seem to mirror mine so I wonder if there is indeed a firmware hiccough that crept in sometime around about mid last year ?
 
spikeymcspikeface said:
For what it's worth, disabling 'Poll State' also worked to solve my original problem - like Alexander, I'm using an Axe FX 3 (with a GT16) and had put the problem down to a firmware update glitch as it hadn't been an problem for all the time I'd been using this set-up (until suddenly it was). For me, turning off 'Poll State' isn't an issue so I'm ok with this as a workaround. But Alexander's experience does seem to mirror mine so I wonder if there is indeed a firmware hiccough that crept in sometime around about mid last year ?
Click to expand...
There's likely something that needs to be fixed, but I have yet to be able to reproduce the problem here. That's why it still exists. If anyone ever finds a reproducible case, it's likely that I could fix it.
 
You must log in or register to reply here.
Back
Top