Vincent van Zwieten
New Member
EDIT: I goofed, this was not the issue. My actual problem was that I was changing scenes with MIDI PC mapping. Even though I was already at patch 121 I was telling the axefx3 to go to patch 121 scene 3, instead of just going to scene 3. Apparently this does make a difference and still would be nice to fix I think. I solved my issue by changing scenes with CC instead.
Hey all!
I just noticed something minor that was actually breaking my brain figuring out why it wasn't working properly.
Whenever I'd change scene there'd be a small dropout because (or so I thought) I was changing the Drive block from channel A to channel C.
Which I thought was weird because that shouldn't happen since the gapless firmware update. I also didn't happen when I just changed channels on the same scene, just when changing scenes, but removing the drive block did solve the issue. I also didn't have this problem on other patches.
Caving in I decided to do my old solution of adding multiple drive blocks in parallel en adding a multiplexer afterwards, but the issue was still happening.
After some digging I finally figured it out: I have my drive block linked up in a way that I use "control switch 1" to set the drive to bypass on or off. In the Control Switch per scene section I'd decide which scene had the drive and which scene didn't. This stems from the time that I was using multiple drive blocks and a multiplexer so I could turn of the drive on any scene with just 1 button.
After removing this noticed that the drive block was in bypass on some scenes, but not on others and that was never visible since I was using the CS per scene feature. After changing that it resolved the issue.
So what I think is happening when switching scenes:
- Drive is on in scene 1
- I switch to scene 2
- Drive is off in scene 2 by default
- Axe3 turns drive off
- Axe3 sees Control Switch 1 should be on by default and turns it on
- Axe3 sees Control Switch 1 being on means the drive should not be in bypass and turns it back on.
This results in a small dropout. Or rather it decreases gain and thus volume by a lot for a split second.
It makes sense to me that it works this way, but my point is that I had no way of seeing this or had no way of knowing this was happening.
My suggestion would be either checking the Control Switch per scene earlier upon patch/scene change (since I think most people will use it to bypass groups of blocks with 1 button press, for example reverbs+delays). Or somehow making it more clear the block in a certain scene is in bypass by default. Maybe there's a third (more hacky option and probably has other other problems) to disregard default bypass in scenes on blocks if there's a Control Switch linked to its bypass.
Hopefully this helps someone having similar issues and hopefully this will get resolved in the future.
Hey all!
I just noticed something minor that was actually breaking my brain figuring out why it wasn't working properly.
Whenever I'd change scene there'd be a small dropout because (or so I thought) I was changing the Drive block from channel A to channel C.
Which I thought was weird because that shouldn't happen since the gapless firmware update. I also didn't happen when I just changed channels on the same scene, just when changing scenes, but removing the drive block did solve the issue. I also didn't have this problem on other patches.
Caving in I decided to do my old solution of adding multiple drive blocks in parallel en adding a multiplexer afterwards, but the issue was still happening.
After some digging I finally figured it out: I have my drive block linked up in a way that I use "control switch 1" to set the drive to bypass on or off. In the Control Switch per scene section I'd decide which scene had the drive and which scene didn't. This stems from the time that I was using multiple drive blocks and a multiplexer so I could turn of the drive on any scene with just 1 button.
After removing this noticed that the drive block was in bypass on some scenes, but not on others and that was never visible since I was using the CS per scene feature. After changing that it resolved the issue.
So what I think is happening when switching scenes:
- Drive is on in scene 1
- I switch to scene 2
- Drive is off in scene 2 by default
- Axe3 turns drive off
- Axe3 sees Control Switch 1 should be on by default and turns it on
- Axe3 sees Control Switch 1 being on means the drive should not be in bypass and turns it back on.
This results in a small dropout. Or rather it decreases gain and thus volume by a lot for a split second.
It makes sense to me that it works this way, but my point is that I had no way of seeing this or had no way of knowing this was happening.
My suggestion would be either checking the Control Switch per scene earlier upon patch/scene change (since I think most people will use it to bypass groups of blocks with 1 button press, for example reverbs+delays). Or somehow making it more clear the block in a certain scene is in bypass by default. Maybe there's a third (more hacky option and probably has other other problems) to disregard default bypass in scenes on blocks if there's a Control Switch linked to its bypass.
Hopefully this helps someone having similar issues and hopefully this will get resolved in the future.
Last edited:
