# Add NAM A2 Capture Support for the Quad Cortex

**URL:** https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571
**Category:** Feature Requests
**Created:** [June 26, 2026, 10:21pm UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571 "2026-06-26T22:21:14Z")
**Posts on this page:** 20
**Page:** 11

<div class="post-metadata">

### Author: ![DiffractionCircuit](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/diffractioncircuit/32/3793_2.png) [@DiffractionCircuit](https://unity.neuraldsp.com/u/DiffractionCircuit)
#### Post date: [September 3, 2026, 1:14pm UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/208 "2026-09-03T13:14:18Z")

</div>

Oh man we went a whole 17 days without insinuating how The Competition is going to destroy NDSP, that’s like a new record for us.

---

<div class="post-metadata">

### Author: ![MP\_Mod](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@MP\_Mod](https://unity.neuraldsp.com/u/MP_Mod)
#### Post date: [September 3, 2026, 1:46pm UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/209 "2026-09-03T13:46:18Z")

</div>

NAM is so yesterday 🙂 Kidding but I am impressed with how much this request is growing!

---

<div class="post-metadata">

### Author: ![anartist](https://avatars.discourse-cdn.com/v4/letter/a/41988e/32.png) [@anartist](https://unity.neuraldsp.com/u/anartist)
#### Post date: [September 4, 2026, 9:45am UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/210 "2026-09-04T09:45:35Z")

</div>

I have an issue with the wording “insinuating how The Competition is going to destroy NDSP”, because that smuggles in a prediction that simply isn’t present in any of the recent comments.

My last comment was already about how a relatively modest claim was being turned into a much stronger one, so I’m not going to do that again. But it does highlight something I’ve noticed repeatedly… some people seem remarkably sensitive to any suggestion that NDSP might be behind the competition in _any_ respect.

That’s a strange and, frankly, somewhat self-defeating attitude. Pointing out where competitors might be doing something better is precisely the sort of feedback that can give a company a kick up the arse and encourage it to respond with something even better.

In fact, the original comment explicitly says it would be cool if this prompted a reaction from NDSP. I agree! Competition is good. Ultimately, it benefits all of us as customers.

Turning every criticism or observation about the competition into “you’re insinuating that NDSP will be destroyed” only discourages people from asking for more. And that, in turn, gives the company less incentive to improve. Why work extra hard to improve when the whole user base seems to be perfectly happy and content with what they already got, you know?

Ironically, _that_ is the kind of thing that can actually make a company to fall behind. If you want NDSP to keep improving its products, huffing and puffing whenever someone points out anything, or asks for more is pretty counter intuitive as far as I’m concerned.

Let’s encourage it. Let’s keep NDSP’s feet to the fire. That’s doing them a favour, really. No time to rest on their laurels in this increasingly competitive market 😉

That doesn’t mean we don’t appreciate what NDSP has already achieved, or that we’re unhappy with what we already got. Those things aren’t mutually exclusive.

---

<div class="post-metadata">

### Author: ![sopedro](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/sopedro/32/10456_2.png) [@sopedro](https://unity.neuraldsp.com/u/sopedro)
#### Post date: [September 4, 2026, 10:03am UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/211 "2026-09-04T10:03:58Z")

</div>

This is alive again.  
I don’t know if the QC is behind the competition. One thing is for sure: I’m playing hundreds of times more than before, when I was constantly searching for good stuff. Now , I got things done faster and better with one platform.

---

<div class="post-metadata">

### Author: ![StewC76](https://avatars.discourse-cdn.com/v4/letter/s/49beb7/32.png) [@StewC76](https://unity.neuraldsp.com/u/StewC76)
#### Post date: [September 4, 2026, 12:33pm UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/212 "2026-09-04T12:33:59Z")

</div>

Here we go again. So correct me if I’m wrong but the QC was released before NAM so it wouldn’t be on NDSPs radar to have a capacity to add it without serious money being used up, that would mean further delays in COROS updates and then there would be more complaints!!

Jeez just be happy with a top tier piece of equipment and stop worrying what other companies are doing.

Can the human ear even discern the differences between the different capture tech? It just appears to me that to many people want to gripe about something.

Just see the QC for what it is, a fantastic piece of kit that even years after its release is still ahead of newer kit!!

---

<div class="post-metadata">

### Author: ![gridif](https://avatars.discourse-cdn.com/v4/letter/g/838e76/32.png) [@gridif](https://unity.neuraldsp.com/u/gridif)
#### Post date: [September 4, 2026, 1:12pm UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/213 "2026-09-04T13:12:05Z")

</div>

Well said. Part of the reason why it took so long for us to get PCOM is because of the need to convert NDSP’s plug-ins to support the QC’s architecture–not the other way around (converting CorOS to just run a VST).

I keep seeing the argument, “NAM A2 runs on this cheap embedded chip so the Quad Cortex likewise should easily be able to run it” but it’s not a 1:1 comparison

---

<div class="post-metadata">

### Author: ![chacoff](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/chacoff/32/10707_2.png) [@chacoff](https://unity.neuraldsp.com/u/chacoff)
#### Post date: [September 4, 2026, 8:07pm UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/214 "2026-09-04T20:07:10Z")

</div>

people asking nam-A2 support have the vibes of the u.s. tourist going to italy, or france, and complain about the hot dogs.

---

<div class="post-metadata">

### Author: ![anartist](https://avatars.discourse-cdn.com/v4/letter/a/41988e/32.png) [@anartist](https://unity.neuraldsp.com/u/anartist)
#### Post date: [September 4, 2026, 11:02pm UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/215 "2026-09-04T23:02:19Z")

</div>

> [@StewC76](#):
>
> Jeez just be happy with a top tier piece of equipment and stop worrying what other companies are doing.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/neuraldsp/original/2X/1/19c458d1101fc7d792f4f06877202f19c05272cd.jpeg)

…mere hours after I explicitly pointed out that wanting additional features in a product you’re already happy with does not mean you’re not already happy with it.

You can be perfectly happy with what you have **and** still want it to get better. I repeat, **those things aren’t mutually exclusive.**

It does make me wonder, though. If you’re happy with the QC, why are you hanging out in a feature request forum? By your own logic, wanting any additional features in the QC means you’re not actually happy with it 🤔

And you’re wrong btw. NAM was released before the QC, so consider yourself corrected. It was probably not on NDSPs radar though. Who can really say they knew about NAM back in 2019?

---

<div class="post-metadata">

### Author: ![Bredala](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/bredala/32/6344_2.png) [@Bredala](https://unity.neuraldsp.com/u/Bredala)
#### Post date: [September 5, 2026, 7:09am UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/216 "2026-09-05T07:09:18Z")

</div>

It’s quite striking to see how resistant some are to dialogue, and how quickly they overanalyze anything that doesn’t fit their narrative.

At this point, I don’t really care what other companies are doing. I’d just like to get a sense of whether NAM support is on NDSP’s roadmap or not. Knowing that NAM is open source, it’d be only for the benefit of all.

---

<div class="post-metadata">

### Author: ![kamui](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/kamui/32/11096_2.png) [@kamui](https://unity.neuraldsp.com/u/kamui)
#### Post date: [September 5, 2026, 9:32am UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/217 "2026-09-05T09:32:06Z")

</div>

> [@chacoff](#):
>
> people asking nam-A2 support have the vibes of the u.s. tourist going to italy, or france, and complain about the hot dogs.

What kind of vibes do people who go into a **feature request thread** shouting to those people they should shut up, be happy with what they have, that they hope they don’t get what they want, and deride them for even asking have?

---

<div class="post-metadata">

### Author: ![kamui](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/kamui/32/11096_2.png) [@kamui](https://unity.neuraldsp.com/u/kamui)
#### Post date: [September 5, 2026, 9:38am UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/218 "2026-09-05T09:38:00Z")

</div>

> [@gridif](#):
>
> I keep seeing the argument, “NAM A2 runs on this cheap embedded chip so the Quad Cortex likewise should easily be able to run it” but it’s not a 1:1 comparison

Read further up the thread, there was a conversation about feasibility, about the NAM library/sdk written against ARM architecture and not SHARC DSP. But, even if that is true, almost none of us know how difficult it is. I don’t know if it’s easy. I don’t know if any of the feature requests in this forum are easy, but that does’t mean it hurts to ask, to vote, and leave it up to NDSP.

The Darkglass Anagram has a 6-core SHARC DSP, but it has NAM A2 support. Maybe it also has an ARM cpu on which NAM runs, or maybe they spent a lot of time and effort to implement it, or it’s a reasonable amount of dev effort. 🤷‍♂️

---

<div class="post-metadata">

### Author: ![Bredala](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/bredala/32/6344_2.png) [@Bredala](https://unity.neuraldsp.com/u/Bredala)
#### Post date: [September 5, 2026, 12:00pm UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/219 "2026-09-05T12:00:48Z")

</div>

The message you replied to was a copy-paste response from June 29. At best, that’s just trolling…

---

<div class="post-metadata">

### Author: ![StewC76](https://avatars.discourse-cdn.com/v4/letter/s/49beb7/32.png) [@StewC76](https://unity.neuraldsp.com/u/StewC76)
#### Post date: [September 5, 2026, 8:20pm UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/220 "2026-09-05T20:20:39Z")

</div>

Well that’s me scolded!! I didn’t realise I wasn’t allowed to read the feature requests if I hadn’t requested one, some gatekeeping going on here.

You didn’t answer the question about being able to hear the difference between Nam captures and the Qc captures.

---

<div class="post-metadata">

### Author: ![h2loh](https://avatars.discourse-cdn.com/v4/letter/h/fbc32d/32.png) [@h2loh](https://unity.neuraldsp.com/u/h2loh)
#### Post date: [September 5, 2026, 8:24pm UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/221 "2026-09-05T20:24:29Z")

</div>

I couldn’t care less about NAM but I do agree people should be able to make their own feature requests without having to defend it. NDSP will do what it does regardless.

---

<div class="post-metadata">

### Author: ![anartist](https://avatars.discourse-cdn.com/v4/letter/a/41988e/32.png) [@anartist](https://unity.neuraldsp.com/u/anartist)
#### Post date: [September 5, 2026, 10:51pm UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/222 "2026-09-05T22:51:16Z")

</div>

I was pointing out the irony in telling people to just be happy with what they got in a feature request forum, as though wanting improvements somehow means they aren’t happy. And you did this right after I had pointed out that requesting additional features does not mean you’re not happy with what you already have, which was rather odd, hence the meme.

It’s interesting that when I flip the script and apply your own logic back to you, you feel scolded and gatekept to the point that you have to invent a strawman argument about how you’ve supposedly been told that you’re not allowed to read feature requests. And I didn’t even huff and puff with words like ‘jeez’.

I’m glad I managed to give you a sense of how your comment comes across when the same logic is applied in the other direction though, because that was exactly the effect I hoped it would have.

As to your question, how many times do I have to answer the same question? Isn’t these times enough:

> [@anartist](#):
>
> Just to be clear, this is not about A2 being a superior technology (allegedly) for me, I’m actually perfectly happy with the converted NAM format my current modeller supports, for me it’s more about losing Tone3000 as a resource.

> [@anartist](#):
>
> I’d prefer to capture my pedals and amps in an open standard so if I wanted to move to Fractal, L6, or whatever later, I could easily do so, bringing with me my NAM library.

> [@anartist](#):
>
> **NAM’s main advantage isn’t better sound quality** , but its **openness and portability**. Because it’s an open standard, captures can be used across different hardware brands, avoiding vendor lock-in. It also benefits from a larger community library (such as Tone3000), meaning, you’re more likely to find a NAM capture of exactly what you’re looking for than a Neural capture of the same thing.

> [@anartist](#):
>
> The practical sense of NAM support should be pretty obvious, **especially** if you’re a complete QC fanboy that will never switch away from Neural (which there seem to be a few of here), you’d get access to what is deemed to be a far superior database of captures.

> [@anartist](#):
>
> Nobody is arguing that Neural Captures don’t sound fine, or that the platform doesn’t work well.

> [@anartist](#):
>
> I think arguing over which one sounds “better” is mostly a moot point. Personally, I’m not convinced I’d reliably hear the difference in a blind test, and I’m sure I’ll be perfectly happy with the quality of my Neural V2 captures.
> 
> That’s also beside the point of why I’d like NAM support. As has been mentioned several times already, capture quality is only one factor, and in my opinion it’s not even the most important one. The real strength of NAM is its ecosystem: the huge library of captures, community contributions, and broad compatibility. Yet most of the discussion defending Neural V2 focuses almost exclusively on capture quality while largely ignoring the ecosystem argument.

What a good quote to end on as this is exactly what you did. Unfortunately, you’re late to the party, so it has already been done many times already and at this point it’s getting a bit tiring.

Is NAM better/more accurate? Maybe.  
Does some people on here want it because they think it is? Maybe.  
I can’t speak for them, but that is not my reason. In fact, a paper could come out tomorrow with data proving that NAM is objectively worse and I would still think it would be cool to have support for it in the QC.

Does that answer your question?

---

<div class="post-metadata">

### Author: ![GMGM](https://avatars.discourse-cdn.com/v4/letter/g/c6cbf5/32.png) [@GMGM](https://unity.neuraldsp.com/u/GMGM)
#### Post date: [September 17, 2026, 9:20pm UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/224 "2026-09-17T21:20:29Z")

</div>

Your move, NDSP…

The thread on the Fractal forum is already 5+ pages long, which I haven’t read.

 ![1789672342301](https://us1.discourse-cdn.com/flex020/uploads/neuraldsp/original/2X/4/4b710acb81de614202778c95fedef2bfcd4cfca8.jpeg)

---

<div class="post-metadata">

### Author: ![xush](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/xush/32/5100_2.png) [@xush](https://unity.neuraldsp.com/u/xush)
#### Post date: [September 17, 2026, 10:09pm UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/225 "2026-09-17T22:09:25Z")

</div>

NAM has become the new PCOM

---

<div class="post-metadata">

### Author: ![LCW](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/lcw/32/6670_2.png) [@LCW](https://unity.neuraldsp.com/u/LCW)
#### Post date: [September 17, 2026, 11:49pm UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/226 "2026-09-17T23:49:41Z")

</div>

> [@GMGM](#):
>
> The thread on the Fractal forum is already 5+ pages long, which I haven’t read.

Now 8 pages and counting…

---

<div class="post-metadata">

### Author: ![anartist](https://avatars.discourse-cdn.com/v4/letter/a/41988e/32.png) [@anartist](https://unity.neuraldsp.com/u/anartist)
#### Post date: [September 18, 2026, 3:07am UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/227 "2026-09-18T03:07:33Z")

</div>

![image](https://us1.discourse-cdn.com/flex020/uploads/neuraldsp/original/2X/a/ac28a9af66d4e05e95713db5c7d80f0d5318a520.png)

👀

---

<div class="post-metadata">

### Author: ![SelfTitledLP](https://avatars.discourse-cdn.com/v4/letter/s/ecc23a/32.png) [@SelfTitledLP](https://unity.neuraldsp.com/u/SelfTitledLP)
#### Post date: [September 18, 2026, 4:48am UTC](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571/228 "2026-09-18T04:48:55Z")

</div>

Yeah, I mean the next Fractal AXE FX 4 rack unit will probably cost around 3+ grand, so I guess it should be able to do everything possible. Maybe they can fix their UI to not be something designed by aliens. Their models sound awesome, but what a confusing and convoluted UI/workflow

[Previous page](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571.md?page=10)

[Next page](https://unity.neuraldsp.com/t/add-nam-a2-capture-support-for-the-quad-cortex/22571.md?page=12)
