is9582
Well-Known Member
GT22 Firmware 4.8.1 AF3 20.0 MacMini M1 11.5.2
AxeEdit 1.12.02
Hello all,
After uploading the new 4.8.1 firmware on my GT22, the screen for switch #17 is completely dark (but only for the first preset in my AF3). As I move up Banks, the screw for switch #17 is lit whether an empty preset or not.
Even when the screen for switch #17 is dark, on that first preset, I can still press it’s switch, and access the related preset. When I move via the Bank Up / Bank Down switches, and get back to Bank #1, the screen above switch #17 is lit and the name viewable, but only until I either choose another preset in Bank #1, at which point that switch #17’s screen in totally dark. If I press switch #17, after traversing to Bank #1 (all six of the presets in this Bank blinking), it accesses preset #1 and it’s screen is lit and the reverse coloration of the preset’s name is shown as expected.
I’ve rebooted a number of times, and am still having the same behavior. Anyone else experiencing the same, or similar? Does this have any correlation to the new firmware (20.0) for the AF3? Thanks in advance for any knowledge or assistance.
Cheers,
Lee
AxeEdit 1.12.02
Hello all,
After uploading the new 4.8.1 firmware on my GT22, the screen for switch #17 is completely dark (but only for the first preset in my AF3). As I move up Banks, the screw for switch #17 is lit whether an empty preset or not.
Even when the screen for switch #17 is dark, on that first preset, I can still press it’s switch, and access the related preset. When I move via the Bank Up / Bank Down switches, and get back to Bank #1, the screen above switch #17 is lit and the name viewable, but only until I either choose another preset in Bank #1, at which point that switch #17’s screen in totally dark. If I press switch #17, after traversing to Bank #1 (all six of the presets in this Bank blinking), it accesses preset #1 and it’s screen is lit and the reverse coloration of the preset’s name is shown as expected.
I’ve rebooted a number of times, and am still having the same behavior. Anyone else experiencing the same, or similar? Does this have any correlation to the new firmware (20.0) for the AF3? Thanks in advance for any knowledge or assistance.
Cheers,
Lee