Hey everyone,
I just got my Axe FX III this week, and may have come across a bug. I'm on the 12.03 firmware it shipped with.
When I try and import this preset from Axe Change my CPU usage jumps to ~90%, and both the Axe and Axe Edit become unresponsive (as expected, at that level of CPU usage I assume the UI and Axe Edit communication threads aren't getting enough CPU time to run consistently.)
However, when I dig into the patch as it's been loaded, it seems it's only been partially loaded, with all the blocks and layout loaded but all the settings are 0. This includes amp type, amp settings, input level on the IN1 block, etc. And this seems to be part of the problem because all 4 cabs on both CAB blocks are set to Factory 1 Cab 1 and On, rather than muted. If I mute cabs 2-4 on both cab blocks I'm only around 70% CPU usage.
I haven't tested by making my own large preset and exporting then importing to confirm, but I have a guess what may be happening:
I suspect that when loading the Preset, all the blocks are loaded to the layout first. Then all the settings are loaded to those blocks next. So before the settings are loaded, the blocks aren't even at their "Default" value as defined in the system, but are instead in a completely uninitialized state. And the uninitialized state of the cab block is Factory 1 Cab 1, and On, for all four cabs. So when both cab blocks load in that state, the CPU usage jumps, the transfer from Axe Edit falters, and the patch gets stuck in this state with max CPU usage from 8 unmuted cabs, 59 bassman amps, and a dozen other effects at default values.
Am I way off base and there's something simple I'm missing? Is there a way to view and edit presets without loading them to the Axe FX III so I can confirm that preset file isn't corrupted/in an invalid state and double check what the block settings are to confirm those cab blocks aren't supposed to be loaded at a setting that eats all the CPU time?
I just got my Axe FX III this week, and may have come across a bug. I'm on the 12.03 firmware it shipped with.
When I try and import this preset from Axe Change my CPU usage jumps to ~90%, and both the Axe and Axe Edit become unresponsive (as expected, at that level of CPU usage I assume the UI and Axe Edit communication threads aren't getting enough CPU time to run consistently.)
However, when I dig into the patch as it's been loaded, it seems it's only been partially loaded, with all the blocks and layout loaded but all the settings are 0. This includes amp type, amp settings, input level on the IN1 block, etc. And this seems to be part of the problem because all 4 cabs on both CAB blocks are set to Factory 1 Cab 1 and On, rather than muted. If I mute cabs 2-4 on both cab blocks I'm only around 70% CPU usage.
I haven't tested by making my own large preset and exporting then importing to confirm, but I have a guess what may be happening:
I suspect that when loading the Preset, all the blocks are loaded to the layout first. Then all the settings are loaded to those blocks next. So before the settings are loaded, the blocks aren't even at their "Default" value as defined in the system, but are instead in a completely uninitialized state. And the uninitialized state of the cab block is Factory 1 Cab 1, and On, for all four cabs. So when both cab blocks load in that state, the CPU usage jumps, the transfer from Axe Edit falters, and the patch gets stuck in this state with max CPU usage from 8 unmuted cabs, 59 bassman amps, and a dozen other effects at default values.
Am I way off base and there's something simple I'm missing? Is there a way to view and edit presets without loading them to the Axe FX III so I can confirm that preset file isn't corrupted/in an invalid state and double check what the block settings are to confirm those cab blocks aren't supposed to be loaded at a setting that eats all the CPU time?