Axe-Fx III Firmware 23.00 Public Beta #4

Status
Not open for further replies.
laxu said:
I don't know if I've just never noticed this, but there's a small UI bug in this fw:

On the onboard UI tuner, the Hz and cents number fonts are slightly squashed horizontally.

If you look at the letter "C" and compare it to the "C" in "Config" up top, the cents one is clearly narrower.
Click to expand...
It's a different font. It's a built-in font which are used when redraw speed is critical. The fonts on the tabs are soft-fonts.
 

Attachments

  • JS410 2023_10_28.syx
    48.2 KB · Views: 20
Last edited:
FractalAudio said:

Axe-Fx III Firmware Release Notes​


23.00

Improved Amp block triode algorithm.

Improved Spring Reverb algorithm:
  • New algorithm is based on a digital waveguide with scattering nodes. This algorithm achieves accurate spring reproduction recreating the iconic “drip” and flutter of classic spring tanks.
  • There are two internal Spring Reverb types. The type can be selected using the Tank Type parameter. This parameter defaults to the appropriate type based on the model.
  • The first type has all the springs in parallel. This is used by the British Spring and Studio Spring models. This is equivalent to an Accutronics Type 8 reverb tank.
  • The second type has a pair of springs in series in parallel with one or more pairs of springs in series. This is equivalent to an Accutronics Type 4 (four springs) or Type 9 (six springs).
  • For the second Spring Reverb type the reflection off the junction between the coupled springs is controlled by the Scattering parameter. Vintage Accutronics reverb tanks exhibit more reflection off the junction than modern, Asian-made reverb tanks.
  • The “Drip” parameter controls the dispersion of the springs.
  • The various models have different tone controls.
  • Several new models have been added. The Tube Spring model is based on a 6G15 Tube Reverb and has an authentic tone control. Studio Spring is a hypothetical spring reverb with six long springs in parallel.
  • Note that the Modulation parameters have been removed as they are not compatible with the new algorithm.
  • Existing presets using Spring Reverb types are reset to default values. Audition as necessary.
Improved Reverb block early reflections. As a result, the default values of Early Level and Late Level for the models have been updated. Existing presets are automatically updated to the new values. Audition as necessary. The Early and Late Level parameters have also been removed from the Basic page of the Reverb block.

Added “Pre-Delay Tap” parameter to Reverb block. This selects the input to the reverb engine. When set to OUTPUT the behavior is as before. When set to INPUT the initial delay is absent. This allows more natural “Echo-Verb” sounds. This is now the default for these types of models and existing presets are automatically updated.

New Plate Reverb algorithm. This new algorithm captures the dispersion (Star Wars™ Laser “pew, pew” sound) and unique stereo imaging of classic plate reverbs. Dispersion is adjustable via the Dispersion parameter. Typical plates are around 25-50%. Set to higher values to exaggerate the effect. Stereo imaging is adjustable via the Pickup Spacing parameter.

Updated many of the Reverb models. Existing presets are not affected. Reselecting the model will load the new default values.

Updated all JS410 Lead models based on a current production JVM410HJS.

Added JS410 Lead Green amp model.

Added Pitch High Cut parameter to Reverb block. This can be used to darken/brighten the pitch-shifted component of the reverb.

Added Smoothing parameter to Cabinet block in Dyna-Cab mode.

Improved Channel switching speed.

Preset, Scene and Channel changes are now gapless, if desired. A global parameter (Setup->Global Settings->Gapless Changes) allow turning this feature on or off. OFF is the behavior prior to this firmware. The default is ON.

Fixed NaN could occur in Euro Uber model at certain combinations of Presence and Speaker Impedance.

Various other fixes and improvements.
Click to expand...
I'm wondering if anybody can answer this question. In the first beta release of 23.00 they introduced gapless preset, channel changes, etc. but they mentioned that it doesn't work for certain outputs like spdif because of an oversight. does anybody know if this has been resolved in the beta 4 release?
 
Piing said:
Here it is.

It is using a commercial IR: Vinai T: Emotive Tones V1 from Live Ready Sound. My favorite one amongst my worth >$3,000 IR collection (I started purchasing them since the Axe-FX Standard in 2006. The number can be shocking, but it is just about $15 per month. Much less than the expenses of a smoker or a motorbiker 😅 )

The first IR of the pack (the pack only contains 4 IRs, which is perfect to avoid option paralysis)

https://livereadysound.com/product/vinai-t-ir-pack/
Click to expand...
Thanks Bud
 
Preset CPU% limits guideline for dependable Gapless operation?

Loving the new Firmware....well done as always.

Is there some guidance about upper limit CPU% load to ensure the Gapless algorithm does not bottom out?

As mentioned above, 80% CPU is the existing "danger zone". Is there a revised upper end limit for expecting Gapless to work smoothly?
Would be good to know so that heavy presets can be tweaked to be in the zone.

Either way great upgrade....thank you.
 
ARF said:
Preset CPU% limits guideline for dependable Gapless operation?

Loving the new Firmware....well done as always.

Is there some guidance about upper limit CPU% load to ensure the Gapless algorithm does not bottom out?

As mentioned above, 80% CPU is the existing "danger zone". Is there a revised upper end limit for expecting Gapless to work smoothly?
Would be good to know so that heavy presets can be tweaked to be in the zone.

Either way great upgrade....thank you.
Click to expand...
Subtract the CPU needed for gapless (~1.5%) from the recommended limit (80%) and you're left with about 78%. Voila, there's your revised limit. :)

It's not quite that simple though because there is a time factor as well. It takes a second or two for the AxeFx to do its internal housekeeping after a gapless change, depending on blocks loaded, etc. So even if you're well below the CPU limit, you could still prevent gapless with a series of rapid-fire scene/preset changes. Fortunately that isn't a very realistic scenario for typical usage. Just don't switch patches every beat at 240bpm and you should be fine.
 
jasonmauer said:
So even if you're well below the CPU limit, you could still prevent gapless with a series of rapid-fire scene/preset changes. Fortunately that isn't a very realistic scenario for typical usage. Just don't switch patches every beat at 240bpm and you should be fine.
Click to expand...
Yea, it's not about absurd 240bpm usage. Just asking for guidance from those "in the know".
Might be good at 78% as you say, but maybe the real window closes at 75%.
 
ARF said:
Yea, it's not about absurd 240bpm usage. Just asking for guidance from those "in the know".
Might be good at 78% as you say, but maybe the real window closes at 75%.
Click to expand...

The 1.5% CPU utilization comes straight from Cliff in this very thread; doesn't get more "in the know" than that. It's basic math, not voodoo.
 
Status
Not open for further replies.
Back
Top Bottom