Are we any closer to a system fix for the "zombie reverb burst"?

Cliff has actually asked for more information not twice, but seven times in this thread!

It is only because he cares about his product so much that he keeps trying and doesn't just say "contact support" and move on to everything else he would have going on. Do you know any other heads of companies who would do this?

The ask has changed, and a full response to all the questions that have been asked are still missing. Why make it difficult for the one guy who can actually help you?

Frustrating!
 
Last edited:
First you said it was happening when changing presets. Now you are saying it's happening when changing channels. Which is it?

I'll ask one more time:
1. Post the example presets.
2. Do NOT post a preset bundle.
3. Simplify the preset as much as possible. Remove any blocks that are not relevant. Disconnect any irrelevant modifiers.
4. Unlink all blocks from global blocks.
5. Use factory cabs if possible.
6. Include clear and concise instructions on how to recreate the bug.
7. Indicate the firmware version you are using.

Help me help you.
It’s when changing presets. Earlier, @strabes suggested what I tried in the last video I posted - setting each channel to a different reverb and switching between them to see if that would cause it consistently. The only thing I recreated consistently doing that is that "pop" you hear. It's similar to the reverb burst in volume and duration, but obviously doesn't have the tonality of the reverb bursting notes or chords.

As I've been saying all along, it's random. Sometimes it does it and sometimes it doesn't. I have not been able to determine a pattern, other than it was way more common with spillover on - sometimes it would do it after every song on every preset change. It still happens when it's off, but not as often, and more randomly. So I'm not sure how to answer question #6 other than to say again, it's random.
@boyce89976 Please provide confirmation and answers to Cliff's questions and suggestions☝ in order. He has asked this twice already and is really trying to help here. I want to see this fixed for you as well. I know you are all busy, but this information will help him determine if this is a bug or not. Thank you.
I appreciate that eyes are on this, but it's random. I haven't been able to consistently recreate it with spillover off.
 
Cliff has actually asked for more information not twice, but seven times in this thread!

It is only because he cares about his product so much that he keeps trying and doesn't just say "contact support" and move on to everything else he would have going on. Do you know any other heads of companies who would do this?

The ask has changed, and a full response to all the questions that have been asked are still missing. Why make it difficult for the one guy who can actually help you?

Frustrating!
As I said in the last post, and probably 7 times prior to that, it happens randomly. I don't know when it's going to happen, or what combination of things makes it happen. What I do know, is that it happens at the worst possible time - between songs, when the band is quiet. I also know there are a dozen others on here that have experienced it also.

@GlennO posted what sounds like a reasonable theory in the other thread from last year (that was linked on the first page of this one)... that it's reverb stuck in a buffer, after a preset change to a reverb that uses a different buffer, and then back to the reverb prior to that on the next preset change.

Lastly, how would I know what blocks are irrelevent? And why would I remove blocks from a preset when I have no idea how the compressor, overdrives, EQ, delays, etc... affect what is happening? This is clearly a beautifully designed, and very complicated product. I've supplied two presets that I know have exhibited the issue in the past.
 
@GlennO posted what sounds like a reasonable theory in the other thread from last year (that was linked on the first page of this one)...
I note in the second post of that thread the question "what firmware" is asked and in the very next post (#3) the question is answered.

We are up to post 64 here.....

What firmware are you on?
 
@FractalAudio The following is my humble summary of the bug report here, according the list of your bug reporting guideline.
(I used Gen-AI agent NotebookLM with the configuration to disable learning from the input. I believe there's no data breach issues as this thread is itself an open-source information, but apologies in advance if I've violated any rules/policies on Gen-AI.)
@boyce89976 Kindly review if the following corresponds to your issues/intended reporting contents and correct if necessary.

Summary of the "Zombie Reverb Burst" Bug Report

1. Post the example presets.

The following individual presets were provided by the primary reporter and others investigating related phenomena:
Presets from Primary Reporter (boyce89976) (Axe-Fx III, used for switching between songs):
S1 - Matchless DC30 EF86 LoGa_20251013_114325.syx
S2 - Matchless DC30 EF86 LoGa_20251013_140641.syx
◦ These two presets are described as the same setup saved with different tempos.
Other Related Presets Provided in the Thread:
59 Bassguy.syx (from user strabes, related to channel switching investigation)
Zombie.syx (from user ARF, related to similar delay issues)
Reverb burst test.syx (from user Randall d, related to scene switching on an FM3)

2. Do NOT post a preset bundle.
This requirement was met by the reporters, as all presets were provided as individual .syx files.

3. Simplify the preset as much as possible. Remove any blocks that are not relevant. Disconnect any irrelevant modifiers.
4. Unlink all blocks from global blocks.

The sources do not confirm if the primary reporter fulfilled requirements Q3 (simplification) or Q4 (unlinking global blocks).

5. Use factory cabs if possible.
The primary reporter addressed the cab requirement (Q5), stating they had to replace a purchased IR with a stock IR in order to post the S1 preset.

6. Include clear and concise instructions on how to recreate the bug.
The central challenge noted by the primary reporter (boyce89976) is that the "zombie reverb burst" is random and not consistently recreatable. It happens "maybe once every three or four songs". The effect is described as a short burst of reverb that sounds like a small chord.

Instructions for Primary Scenario (Preset Switching):
1. Play through Preset 1 (e.g., S1 - Matchless DC30 EF86 LoGa).
2. Switch to Preset 2 (e.g., S2 - Matchless DC30 EF86 LoGa) using an FC12 preset change.
3. The burst occurs randomly, coinciding with the preset change tap.

Specific Preset Context (Applies to S1 and S2):
• The preset uses the Golden Plate reverb model in two channels (A and C).
• The issue still occurs, though less frequently, even when global Spillover is turned off.
• Channel A decay is set to 3 seconds; Channel C decay is set to about 7 seconds.

Alternative Replication Scenario (Scene Switching, FM3 reported by Randall d):
1. Load the Reverb burst test.syx preset with Spillover on.
2. Play on Scene 1.
3. While the Reverb is still decaying, switch to Scene 2.
4. Play a bit, then stop playing.
5. After stopping for a few seconds, switch back to Scene 1 (without playing). This sometimes results in a reverb burst.

7. Indicate the firmware version you are using.
The primary reporter (boyce89976) did not indicate the firmware version of the Axe-Fx III being used for the problematic presets (S1, S2).
• In related reports:
◦ User ARF reported a delay issue on FW 29.01.
◦ User Randall d reported a scene switching test on an FM3 using FW 10.00.
 
This is standard troubleshooting advice to help narrow down the issue and remove variables

Have you tried this to see if doing so makes any difference? This could provide valuable troubleshooting info.
If I can't reproduce the error on command, ie, it happens seemingly randomly, how does adding variables by removing blocks, help?
 
@FractalAudio The following is my humble summary of the bug report here, according the list of your bug reporting guideline.
(I used Gen-AI agent NotebookLM with the configuration to disable learning from the input. I believe there's no data breach issues as this thread is itself an open-source information, but apologies in advance if I've violated any rules/policies on Gen-AI.)
@boyce89976 Kindly review if the following corresponds to your issues/intended reporting contents and correct if necessary.

Summary of the "Zombie Reverb Burst" Bug Report

1. Post the example presets.

The following individual presets were provided by the primary reporter and others investigating related phenomena:
Presets from Primary Reporter (boyce89976) (Axe-Fx III, used for switching between songs):
S1 - Matchless DC30 EF86 LoGa_20251013_114325.syx
S2 - Matchless DC30 EF86 LoGa_20251013_140641.syx
◦ These two presets are described as the same setup saved with different tempos.
Other Related Presets Provided in the Thread:
59 Bassguy.syx (from user strabes, related to channel switching investigation)
Zombie.syx (from user ARF, related to similar delay issues)
Reverb burst test.syx (from user Randall d, related to scene switching on an FM3)

2. Do NOT post a preset bundle.
This requirement was met by the reporters, as all presets were provided as individual .syx files.

3. Simplify the preset as much as possible. Remove any blocks that are not relevant. Disconnect any irrelevant modifiers.
4. Unlink all blocks from global blocks.

The sources do not confirm if the primary reporter fulfilled requirements Q3 (simplification) or Q4 (unlinking global blocks).

5. Use factory cabs if possible.
The primary reporter addressed the cab requirement (Q5), stating they had to replace a purchased IR with a stock IR in order to post the S1 preset.

6. Include clear and concise instructions on how to recreate the bug.
The central challenge noted by the primary reporter (boyce89976) is that the "zombie reverb burst" is random and not consistently recreatable. It happens "maybe once every three or four songs". The effect is described as a short burst of reverb that sounds like a small chord.

Instructions for Primary Scenario (Preset Switching):
1. Play through Preset 1 (e.g., S1 - Matchless DC30 EF86 LoGa).
2. Switch to Preset 2 (e.g., S2 - Matchless DC30 EF86 LoGa) using an FC12 preset change.
3. The burst occurs randomly, coinciding with the preset change tap.

Specific Preset Context (Applies to S1 and S2):
• The preset uses the Golden Plate reverb model in two channels (A and C).
• The issue still occurs, though less frequently, even when global Spillover is turned off.
• Channel A decay is set to 3 seconds; Channel C decay is set to about 7 seconds.

Alternative Replication Scenario (Scene Switching, FM3 reported by Randall d):
1. Load the Reverb burst test.syx preset with Spillover on.
2. Play on Scene 1.
3. While the Reverb is still decaying, switch to Scene 2.
4. Play a bit, then stop playing.
5. After stopping for a few seconds, switch back to Scene 1 (without playing). This sometimes results in a reverb burst.

7. Indicate the firmware version you are using.
The primary reporter (boyce89976) did not indicate the firmware version of the Axe-Fx III being used for the problematic presets (S1, S2).
• In related reports:
◦ User ARF reported a delay issue on FW 29.01.
◦ User Randall d reported a scene switching test on an FM3 using FW 10.00.
I appreciate you doing this. Nicely done!

Everything looks correct from my POV. I'm currently on Firmware 28.08 as I didn't like how FW29.01 sounded. I first started having the issue on Firmware 27.00.
 
I appreciate you doing this. Nicely done!

Everything looks correct from my POV. I'm currently on Firmware 28.08 as I didn't like how FW29.01 sounded. I first started having the issue on Firmware 27.00.
Hate to break it to you, but a fix would come in 29.02 or later. Maybe I’m wrong, but I think you may have blown your chance at a “just for Boyce” 28.08a firmware version.
 
Hate to break it to you, but a fix would come in 29.02 or later. Maybe I’m wrong, but I think you may have blown your chance at a “just for Boyce” 28.08a firmware version.
Yeah, I don't care when a fix is released, just that it gets fixed.
 
The reason for simplifying the preset is three-fold:
1. It's what I asked you to do.
2. It isolates the particular block that is causing the issue. You preset is complicated with multiple delays, etc. You say it's a "Zombie Reverb Burst" which implies the Reverb block but it could actually be the Delay block.
3. See #1.
 
The reason for simplifying the preset is three-fold:
1. It's what I asked you to do.
2. It isolates the particular block that is causing the issue. You preset is complicated with multiple delays, etc. You say it's a "Zombie Reverb Burst" which implies the Reverb block but it could actually be the Delay block.
3. See #1.
Fuck me.

Really is like the teef!
 
For what's it's worth, the problem I used to have with bursts coming from reverb/delay blocks when switching scenes/channels appears to be fixed. The only thing I noticed is a little static like noise at times when switching scenes, going from a scene with a block enabled to a scene with it disabled. I've never noticed it in a live situation, so it's not a problem to me.
 
what i notice (on fm3) is, when switching preset (in fm edit) from the 409 scene 1 to the 410 scene 1,
you can see (in fm edit), that the plex delay and the phaser are engaged a short period of time, although they are
bypassed in the scene. for that short period of time, you can hear the additional/unwanted sound the two blocks
makes from the chord ringing out.
firmware on all is latest and greatest, spillover all, gapless all.

maybe, hopefully, that helps.
 

Attachments

Back
Top Bottom