Axe-Fx III Firmware 32.02 Public Beta #2 (Beta 3)

Status
Not open for further replies.
But „normal“ now saves some cpu and lacks some quality in comparison
From the presets I've tested so far, "normal" uses the same amount if CPU as before (leading me to assume "Normal"=no change from previous fw). Setting oversampling to "High" uses more CPU than previous fw (so raising quality from prev fw). There's no drive
oversample setting that saves CPU compared to prev fw from what I've seen so far but I haven't tested all the drives.
 
I’d expect it to show up like reverb, as mentioned.

Even on the am4, reverb defaults to economy but you can goose it all the way up to high quality.

Depending on your blocks it’s no biggie to run HQ reverb on an am4. Some amps eat more CPU than others.

It would surprise me if it wasn’t implemented across the products as such.
 
I’d expect it to show up like reverb, as mentioned.

Even on the am4, reverb defaults to economy but you can goose it all the way up to high quality.

Depending on your blocks it’s no biggie to run HQ reverb on an am4. Some amps eat more CPU than others.

It would surprise me if it wasn’t implemented across the products as such.
On effects with "economy" options, those were added as lower quality less CPU intensive options.

This change is not providing that...
 
I’m just trying to say that it seems to me that cliff has only given the possibility to choose between “high” or “low” oversampling modes because you could save some CPU with “low”. Therefore “low” would be the new economy mode. And you would not need a parameter that has no counterpart in the “real world”, therefore it could be easier to understand what it basically does.
 
I’m just trying to say that it seems to me that cliff has only given the possibility to choose between “high” or “low” oversampling modes because you could save some CPU with “low”. Therefore “low” would be the new economy mode. And you would not need a parameter that has no counterpart in the “real world”, therefore it could be easier to understand what it basically does.
While I agree that relabeling the low oversampling as eco mode for the drive block would make things simpler and consistent with other blocks like reverb I prefer to know what the control does so having it labeled as oversampling high and low is my preference.
 
I’m just trying to say that it seems to me that cliff has only given the possibility to choose between “high” or “low” oversampling modes because you could save some CPU with “low”. Therefore “low” would be the new economy mode. And you would not need a parameter that has no counterpart in the “real world”, therefore it could be easier to understand what it basically does.
As stated already multiple times, you are NOT saving CPU.

The CPU will be the same as it was before or it will be higher than before.
 
Added “Oversampling” parameter to Drive block. When set to HIGH the oversampling rate is doubled which results in less aliasing. NOTE: This will increase CPU usage considerably.
But what about the Preamp-Boost in the AMP-Block? For example the 808? Is it running without "oversampling" and therefore a worse option than the dedicated Drive block with "oversampling" activated or isn't it making any difference because it's nit a "full Drive Block" but rather a "simple boost"?
 
But what about the Preamp-Boost in the AMP-Block? For example the 808? Is it running without "oversampling" and therefore a worse option than the dedicated Drive block with "oversampling" activated or isn't it making any difference because it's nit a "full Drive Block" but rather a "simple boost"?
That's a pure EQ effect, no (additional or different) sampling required.
 
Turn it on and off. Do you like the sound better? If you don't hear anything, then just leave it off if you want/need to save CPU.
Yea I get it, ‘use your ears’ & I plan too.

Was just curious until I get the chance to update. I’m guessing that with no gain the difference will not be noticeable at all.
 
Status
Not open for further replies.
Back
Top Bottom