When do you predict the next Fractal Audio Axe iteration will drop, now that they've stated that it will be NAM-compatible?

This is all a load of unchi.

1773001187889.png



I'n totally guessing here, but "unchi" = wet farts? :ROFLMAO:
 
I actually phrased it as a quesiton, and edited it before you posted this to be more clear. I am asking, not shoving.


OK. But what I was trying to ask was whether you felt that adding NAM would in fact directly lead to more highly skilled people being brought on board. I mentioned Cliff since he is the main resource in question at the moment. Because skill level matters a lot when planning development resources (I do it for a living).
I think adding NAM will lead to a lot more sales of IV gen devices than going deeper into the tweaker’s-device pigeon hole. Whether it’s enough to hire/train more folks, I dunno.
 
I think adding NAM will lead to a lot more sales of IV gen devices than going deeper into the tweaker’s-device pigeon hole.
I don't think that's an accurate description of what I mean, but I am very, very happy to let it go.
Whether it’s enough to hire/train more folks, I dunno.
I can appreciate trying to look a few moves ahead, but I think there are way too many variables in play. That said, I am (and have been) resigned to the notion that I am unlikely to get what I want. The fashion is what it is.

It seems some folks want an apology or something. Regardless of how this conversation goes, we are not deciding what will be in Fractal's next gen. We probably aren't moving the needle even a tiny bit. There are no stakes here. It's really gonna be ok that I don't want NAM. It's gonna be ok for me, and I'm the one who is almost certainly not going to get what I would prefer. It'll be ok for the NAM fans, too.
 
Last edited:
Captures serve their purpose and are useful. It’s already stated it’s coming so I’m not sure what the argument is about.

NAM currently crushes everyone in accuracy but there are no ‘major’ players that have hardware for it. The work is done and it’s smart for fractal to pick it up vs. develop their own (which I don’t think they would have done anyways)

All this does is add to the checklist of Fractal being top dog in terms of sound. Best modelling tech and best capture tech in one device. No downsides to that.

I recently bought a Stadium and the Ui is extremely good. There are dials and buttons for when dials/buttons are the best input method i.e. adjusting amps, pedals, levels etc. and there’s touch when touch is the best input method i.e typing preset names (or anything), moving blocks around, quickly selecting something to edit, moving a mic. The best method is a combination of both, each playing to its strengths. It’s the first all in one I’ve used where I haven’t felt the need to connect a computer at all, which to me is a huge plus
 
The discussion isn't whether or not it's coming to the next gen (it is), but whether Fractal NEEDS to have it to move forward. They honestly don't-Cliff has spent the last couple of decades working tirelessly on component level modeling. That is what Fractal is all about.
Who cares if they "need" it, its coming.

Need is a strong word, I'd say having capture tech alongside modelling is an extremely valuable "value add" to your lineup. The good thing with something like NAM is that you don't need to develop your own stack its an open source solution (and arguably the one with the best results right now). It's just easy pickings for it to be supported.
 
There's also something to consider - as soon as Fractal get NAM support, they literally rise to the top in terms of accuracy. Better than Kemper, better than Quad Cortex, better than ToneX, and probably better (I strongly believe so anyway) than Proxy.
Whats crazy is that NAM is open source and the cost / R&D to get it up and running in ANY modeller is negligible to what you'd have to do to develop it from the ground up. If I was part of a team building a modelling unit and the 3 choices were (no captures, making our own capture stack, having a NAM capture player). I'd firmly spend my time getting NAM up and running and thinking of some cool ways of bending NAM in a unique way on that device. There are so many ways to take the NAM technology its not just a pigeon holed one shot capture tech.

I know you know this its more just like... these guys have done the 90% work. Why would you leave it out or start your own? Take what they've done, run with it and make it better.
 
And why wouldn't it go both ways, with modeling being "table stakes" for Tonex and Kemper?
Because creating a component modeling system is vastly more complex than captures. That's why it's easier for products that traditionally relied on component modeling to add capture systems than the other way around.

When several of the competition have some sort of capture system, it makes sense for your product to have it too. Especially with a vocal minority asking for it.
 
Whats crazy is that NAM is open source and the cost / R&D to get it up and running in ANY modeller is negligible to what you'd have to do to develop it from the ground up. If I was part of a team building a modelling unit and the 3 choices were (no captures, making our own capture stack, having a NAM capture player). I'd firmly spend my time getting NAM up and running and thinking of some cool ways of bending NAM in a unique way on that device. There are so many ways to take the NAM technology its not just a pigeon holed one shot capture tech.

I know you know this its more just like... these guys have done the 90% work. Why would you leave it out or start your own? Take what they've done, run with it and make it better.

Add to that the current "popularity" of null tests to measure and compare the accuracy of various capture systems, and NAM makes even more sense. I hope that Line 6 Proxy will be amazing and all, but I doubt that it will "beat" NAM in terms of accuracy, at least not with this pseudo-scientific way that some people promote and use to test profiles accuracy. So yeah, FAS made a smart choice there: fulfilling the wish of some of their users to have capture-enabled devices while limiting to a minimum the effort to implement it thanks to NAM.
 
I know NAM support is confirmed, but do we know if it'll be A1 or A2? I mean, I would assume it would support both, but I'll pose the question anyway.
 
I hope that Line 6 Proxy will be amazing and all, but I doubt that it will "beat" NAM in terms of accuracy,

I'd be pretty surprised if it doesn't effectively match NAM in terms of accuracy with improved functionality. I would be far less surprised to find out Proxy is leveraging NAM or parts of NAM under the hood.

I think a lot of people in this thread have inaccurate opinions on the accuracy differences between NAM, Tonex V2 and QC V2. They are MUCH closer to each other now, and there isn't an obvious clear winner. I see no reason Proxy won't join the group.

That said, NAM in 18 months is going to be different than NAM today. By time the Axe IV comes out, NAM could be different, by time the AXE IV hardware life is coming to an end, NAM WILL be significantly different. It makes a lot of sense for Fractal to support it from day 1 with the expectation that the value will increase with time. The short sighted "I hate captures" guys will be eating crow in a few years.
 
That said, NAM in 18 months is going to be different than NAM today. By time the Axe IV comes out, NAM could be different, by time the AXE IV hardware life is coming to an end, NAM WILL be significantly different. It makes a lot of sense for Fractal to support it from day 1 with the expectation that the value will increase with time. The short sighted "I hate captures" guys will be eating crow in a few years.
In what way do you think NAM will be somehow ground breaking? Parametric captures are the only thing I could see making a real difference at this point.

To me the issue with captures is all about workflow, and not sound with Tonex V2, QC2 or NAM. It's a file browser with shit tier metadata on literally every competing product on the market.
 
Parametric captures are the only thing I could see making a real difference at this point.

That's a pretty fucking big thing though. If they get just that right, it will kill the component modeling market due to the time/cost factor alone. But there is also much more to be had in capturing effects and signal chains. The ability to bake a bunch of blocks down into a single capture, will open up options, especially on smaller/lower powered units.
 
Cliff’s confirmation that their next gen will have NAM support was posted before the distinction between A1 and A2 was introduced.

Yes, hence my question if there's been any clarification afterwards. I assume by your answer that there's been no further information. Thanks!
 
Back
Top