Just read the first post to see the release notes.Are Big Fonts a part of this Firmware? Sorry, didn't read all seven pages.
I did read the release notes and didn't see it listed. I may have missed it somewhere?Just read the first post to see the release notes.
Sorry didnt read the rest of your post![]()
“Soon”.Man I'm so pumped about this update, but currently waiting for final release. I wonder how close this beta gets us to a release candidate? I'm having patience issues lol!
The CPU bounces between these two numbers:When I tested I was working from a single channel, with three instances of the same IR. It was about 3%.
Possibly, adding additional IRs will add more CPU load.
Describe your methodology and let’s figure out how to estimate the load.
That seems very different than what others have posted... Interesting.The CPU bounces between these two numbers:
In Axe Edit A totally blank preset shows 4.8 CPU.
With nothing in a preset at all, adding a dyna-cab block shows:
One Dyna-cab showed 11.4 CPU to 15.2 CPU.
Two Dyna-cabs showed 17.2 CPU to 20.8 CPU
Three Dyna-cabs showed 23 CPU to 26.5 CPU
Four Dyna-cabs showed 28.7 CPU to 32.5 CPU
Methodology:
I started with a totally blank preset, which shows 4.8 CPU.
The numbers above show the CPU with nothing at all in a preset except a cab block.
So if you subtract the 4.8 that is there with nothing in the preset here is how much CPU is actually added:
One Dyna-cab raised the CPU by 6.6 CPU to 10.4 CPU
Two Dyna-cabs raised the CPU by 12.4 to 16 CPU
Three Dyna-cabs raised the CPU by 18.2 to 21.7 CPU
Four Dyna-cabs raised the CPU by 23.9 to 27.7 CPU
On an FX3 Mk II I'm seeing:The CPU bounces between these two numbers:
In Axe Edit A totally blank preset shows 4.8 CPU.
With nothing in a preset at all, adding a dyna-cab block shows:
One Dyna-cab showed 11.4 CPU to 15.2 CPU.
Two Dyna-cabs showed 17.2 CPU to 20.8 CPU
Three Dyna-cabs showed 23 CPU to 26.5 CPU
Four Dyna-cabs showed 28.7 CPU to 32.5 CPU
Methodology:
I started with a totally blank preset, which shows 4.8 CPU.
The numbers above show the CPU with nothing at all in a preset except a cab block.
So if you subtract the 4.8 that is there with nothing in the preset here is how much CPU is actually added:
One Dyna-cab raised the CPU by 6.6 CPU to 10.4 CPU
Two Dyna-cabs raised the CPU by 12.4 to 16 CPU
Three Dyna-cabs raised the CPU by 18.2 to 21.7 CPU
Four Dyna-cabs raised the CPU by 23.9 to 27.7 CPU
Try it yourself using the same method that I did. I was using an Axe FXIII MK1, (Not a turbo.) One other note. Preamp and Room/air in the cab block were turned off for my tests. Maybe it is slightly different depending on which dyna-cabs you are choosing and which mics? I don't know. Whatever the case, I know I had to delete 3 blocks from my main preset to compensate for the extra CPU being used with the dyna-cabs to keep the flashing warning light from coming on. Getting good sounds but, I'm waiting for the final release to start re-doing all my presets.That seems very different than what others have posted... Interesting.
The CPU bounces between these two numbers:
In Axe Edit A totally blank preset shows 4.8 CPU.
With nothing in a preset at all, adding a dyna-cab block shows:
One Dyna-cab showed 11.4 CPU to 15.2 CPU.
Two Dyna-cabs showed 17.2 CPU to 20.8 CPU
Three Dyna-cabs showed 23 CPU to 26.5 CPU
Four Dyna-cabs showed 28.7 CPU to 32.5 CPU
Methodology:
I started with a totally blank preset, which shows 4.8 CPU.
The numbers above show the CPU with nothing at all in a preset except a cab block.
So if you subtract the 4.8 that is there with nothing in the preset here is how much CPU is actually added:
One Dyna-cab raised the CPU by 6.6 CPU to 10.4 CPU
Two Dyna-cabs raised the CPU by 12.4 to 16 CPU
Three Dyna-cabs raised the CPU by 18.2 to 21.7 CPU
Four Dyna-cabs raised the CPU by 23.9 to 27.7 CPU
This happened to me too last week.I just switched on my Axe III and I thought…
Holy Crap my preset never sounded better and I tried to figure out what is the reason and what did I changed the last time? And then I discovered that last time I saved it with the new Dyna Cab!
![]()
Another trick is to leave it on cap and lower the ribbon mic level. My go to used to be a 57 cap edge and a 121 cap but enough level to add low end.Yeah I STRONGLY suggest exploring the sounds you get with the mic further from the cab. Really controls the lows and opens up the highs in a pleasing way. The ribbon mic in particular sounds fantastic further out from the speaker.
+1. This has been my go to trick for at least the last two years now. Great way to subtly add frequencies while keeping the mids relatively intact.Another trick is to leave it on cap and lower the ribbon mic level.
Thanks for pointing that out. I just tested again today and I'm seeing 5% increase between them in Axe Edit.Yes, relative to a blank preset, a full dynacab block will add about 25%. But that's not what Macfly is asking. He's asking the more relevant question of how much the cpu load is relative to legacy mode. With all 4 slots occupied in the cab block, that delta should be about 3%.
The dyna-cabs definitely have a clarity that is immediately noticeable. Looking forward to the final release.I just switched on my Axe III and I thought…
Holy Crap my preset never sounded better and I tried to figure out what is the reason and what did I changed the last time? And then I discovered that last time I saved it with the new Dyna Cab!
![]()