guitarnerdswe
Fractal Fanatic
Oh, so that's why my kitchen sink preset all of a sudden has combinations of channels that go way over 80 %. I was just in the middle of redoing it and my MMGT22 setup to reduce the CPU usage because of this.
I was half kidding.No, fix the software if there is a problem. I'm not in the slightest bit interested in hardware until Axe 4.
Not seeing this here. On 16.05 your preset runs at 81.3%. On 17.00 it runs at 81.5%.Sorry for delay..I was downgrading to 16.05 and the preset was somehow replaced with one I had before on that slot some time ago, so I remake it again...anyway. After I make it again in 16.05, I save it, and then upgrade to 17 and saved the upgraded version also. Both versions attached. In FW17, CPU is between 82 to 85, with warning mgs appearing from time to time. I'm just afraid that the unit will lag during performance, and no one wants that. I know that this can be somehow fixed by reducing the IR length in cab block from max to lets say 1024, and the CPU usage will stabilize around 80% without the warning message, but that's beside the point...There is definitely an increase of CPU usage after upgrade.
Thanks
This preset has been saved for firmware 17.00 so I can't load it in 16.05.I see a rise in CPU load as well.
Please find an example Preset with moderate CPU load attached.
On FW 16.5 it shows a - relatively constant - CPU load ~ 58,5 %.
On FW 17 it shows a varying CPU load ~ 60,5 % .... 64 %.
Sorry, Cliff, I missed to attach the 16.5 file. Here it is.This preset has been saved for firmware 17.00 so I can't load it in 16.05.
We all enjoy your abilities and your relentless work.Some of the increase is unavoidable due to the "Improved scene switching to prevent signal “leaking” into bypassed blocks." This required adding some code to the input of every block.
I'm working on some optimizations and have already improved things a bit.
You're describing an Axe-Edit behavior as a firmware issue... Seems like you are mixing things up.Firmware 17 is a disaster! Every time you turn the axe unit on it re-reads all the cabs and such like you are doing a refresh. Also, the cpu usage is off the scale on some presets now - full for no reason. Anyhow, must simply be a lemon firmware, it happens on occasion
Just did that...it's in a safe zone now...thx for reminding me about shunts..."sometimes you cannot see the forest for the trees" .lolI know it’s not an answer but if you can reduce the number of shunts you can reduce CPU. If row 4 (input 2) is always that “empty” just put In 2 directly near the end without all those shunts.
Are we going to see the CPU usage regression resolved in next release?
I just booted up Axe-Edit III 10.00.01 and it read presets and cabs, but holy sh*t it was FAST. I mean like 3-5 seconds. Mk I unit.I don't see it re-reading the cabs, only re-reading the presets in Axe III Edit, however, the preset re-reading seems to have slowed down quite a bit.