Bug report:
Output volume of the Amp block maxed out (but there was no output to the monitors).
Had to switch off and reboot.
Happened when I switched the Cab block channel.
Unfortunately the issue was not reproducible.
View attachment 146360View attachment 146361
A very similar issue happened to me when updating to 27.01.
A day prior I added a filter block to a long standing preset, and was mucking about and exploring the filter settings with new "mysterious ways" stuff. This preset sits at about 54% routinely, about the same with added filter block. No anomalies at this point. The filter block was then bypassed
Did the update to 27.01, all went well. Was still in this preset post-update and just jamming. I switched scenes from a crunch to a lead, and immediately lost sound, outputs were pinned, unit locked up, had to power cycle the AxeFX. Of course tried the same thing again aafter reboot, this time from clean scene to crunch. Locked up same symptoms. Started to get that panicky vibe, rebooted and tried a 3rd time, lead to crunch and again, locked up, no sound, no response, LEDs are pinned, both AxeFX and axe edit are frozen, had to reboot.
So now I'm getting ready to restore first bank of presets from backup (where this preset lives) and it occurs to me the filter block was still there, and to delete it, insert shunt.
Problem solved, never to return. I've since added back a filter block to this preset with no ill effects.
I chalked it up to corruption or a "things happen" sitch. Its never happened again. I don't know exactly what the cause was and didn't figure it was worth reporting as it was a one off and deleting that filter block I'd recently added resolved it. It would only lock up when switching scenes, which in this preset's case, primarily changes the Amp block channel.
If this output lockup is being pursued as a bug, I figured I'd toss this experience in as it may help. I too was unable to recreate the issue once I deleted the filter block, but mine happened immediately post update so I haven't gone to the trouble of downgrading and reattempting to recreate the issue, but maybe this info will help in some way if its pursued for resolve.
Glad it wasn't a persistent issue for you either.