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

Status
Not open for further replies.
Let me ask a heretical question - can anyone hear this aliasing difference?
Especially younger people with less battle damaged ears than mine?

Things that show up on a graph I only partly understand versus things I can actually hear are not a 1:1.

I'm not saying it's not worth doing, I'm saying I don't know if it matters at a show or a recording.
Maybe in the studio I should care but live no one will hear it? IDK.

My point, so many things people get hot about on the internet have been things I literally couldn't hear. This is also true with home audio gear, it's not just a musician thing.
 
Hah! : ) it doesn't bother me, it never has. I barely hear half of the differences people go on about here!
The last update that was a truly big deal for me was adding dyna-cabs the Halo delay. I can hear those, it's a whole thing.

I am genuinely curious, can anyone actually hear this aliasing difference or are we chasing specs? Nothing wrong with chasing specs. I just don't have golden ears is all.
 
Last edited:
FPFL said:
Let me ask a heretical question - can anyone hear this aliasing difference?
Especially younger people with less battle damaged ears than mine?
Click to expand...
No, but it's become a specmanship thing so we have no choice but to address it.

It's like latency. People compare latency of products and because they don't understand the subtleties simply assume that lower = better.

I've explained why lower latency isn't necessarily better and usually means worse but it's a losing battle.

Another one is "32-bit converters". 32 is more than 24 so it must be better, right? It doesn't matter that the actual dynamic range of the 32-bit converter is less than the supposedly inferior 24-bit converter, people only know that 32 > 24.
 
FractalAudio said:
It's like latency. People compare latency of products and because they don't understand the subtleties simply assume that lower = better.

I've explained why lower latency isn't necessarily better and usually means worse but it's a losing battle.

Another one is "32-bit converters". 32 is more than 24 so it must be better, right? It doesn't matter that the actual dynamic range of the 32-bit converter is less than the supposedly inferior 24-bit converter, people only know that 32 > 24.
Click to expand...

This was post #24 in this thread so I'm looking forward to post #32 because it will should be better.
 
Rex said:
Click to expand...

Yes this is the effect / error in the abstract. Good for people who have no idea what it is. Thank you.

That said, it doesn't mean anything in context of the AF3, like if it's audible to humans versus merely measurable.

People can create factual graphs that illustrate many objective truths about products my simple human ears can never notice - because I am human whose hearing has upper bounds that aren't impressive, even in the animal kingdom, never mind compared to computers.

It's why graphs can be both true and useless, and why I asked if anyone could actually hear this.
 
BROCKSTAR said:
My rule of thumb is if it didn't bother you then, then it probably won't now. :D

However it's always a good thing if things can be fixed and improved even if we don't hear it or understand it.
Click to expand...
I mostly disagree. If humans can't hear it, 'fixing' it is a waste of developer cycles that could be better spent on things we can hear... unless I am torturing my dog, then do something about it please. : )

Improving for the sake of graphs? is wasting time in a way the internet loves.
 
FPFL said:
I mostly disagree. If humans can't hear it, 'fixing' it is a waste of developer cycles that could be better spent on things we can hear... unless I am torturing my dog, then do something about it please. : )

Improving for the sake of graphs? is wasting time in a way the internet loves.
Click to expand...

Well if the issue pops up and you have the means of fixing it now, why not? Why wait until later when something else could make it worse etc.. etc.. I don't see no harm in adjusting it even if some of us don't understand it or hear it.
 
Regarding the oversampling, I can hear a difference with the 5150 and 808 in the factory preset when switching between the two modes. Much prefer the higher mode. It seems to add up to 5% cpu, it fluctuates a bit though so hard to be exact.
 
FPFL: "If humans can't hear it, 'fixing' it is a waste of developer cycles."

It may well depend on context. Some things coming after it may expose it someday.
Why do you think we'll never get an Aural Exciter?? ;) ;) (joke)

I could also imagine how removing detail from a stream may reduce CPU for some applications too.

BTW: Did they add a "Big Prince" flanger preset...? ;)
 
Fjelltronen said:
Regarding the oversampling, I can hear a difference with the 5150 and 808 in the factory preset when switching between the two modes. Much prefer the higher mode. It seems to add up to 5% cpu, it fluctuates a bit though so hard to be exact.
Click to expand...
When you start feeding a signal with aliasing artifacts into another distorted signal, the potential for it becoming audible is increased. Stacking drives, would be more likely to make any aliasing artifacts audible (increasing intermodulation distortion) than just using a single drive into a clean amp. So use case can matter.
 
Imo, the accumulation of successive less audible or inaudible tweaks over time, contributes to the ultimate high level of quality, accuracy, and feel, clearly audible within Fractal products. Just because I can't hear / feel a given specific adjustment, doesn't mean I won't be able to hear / feel the cumulative effect of several such small adjustments combined.
 
And to ask my question again from the previous thread...

Is the High option on drives an enhancement to how it used to be, or was a new non-high default necessary to save cycles with the now fixed aliasing issues, please?

The way it was worded I will guess it's an enhancement option though, otherwise there might have been info how older presets are handled.

In the latter case I assume part of the previous bug is only fixed if you use High -- which is a clever way to address it ;)
 
Last edited:
javajunkie said:
When you start feeding a signal with aliasing artifacts into another distorted signal, the potential for it becoming audible is increased. Stacking drives, would be more likely to make any aliasing artifacts audible (increasing intermodulation distortion) than just using a single drive into a clean amp. So use case can matter.
Click to expand...
Makes sense. I just tried it again and the clarity the higher mode provides is easily noticeable.
 
I can clearly hear the difference between the Normal and High driver settings. Both in touch and sound. It's a shame that in some models the CPU usage increases by up to 10%. Since I have the Axe FX MK I, I hope it meets my needs.

Thank you Fractal and your entire team.
 
Status
Not open for further replies.
Back
Top Bottom