NDSP Quad Cortex

[mbenigni]

March 5, 2025
Quad Cortex Development Update #55

We’re still deep in development on CorOS 3.2.0, which will bring Parallax X and Archetype: Nolly X to Quad Cortex, along with some other highly requested features.

 

[mbenigni]

We’ll share more details when CorOS 3.2.0 is approaching beta, including a closer look at what’s coming in the update.

Thank you for your patience.

 

[mikah912]

Two lost years (2024 and soon to be 2025). That's tough.

 

[mbenigni]

Two lost years (2024 and soon to be 2025). That's tough.

There were some cool improvements in 2024 (from my perspective, at least) and it's still a little early to be putting nails in 2025's coffin. (I mean, the odds are in your favor, but still...)

 

[2dor]

March 5, 2025
Quad Cortex Development Update #55

We’re still deep in development on CorOS 3.2.0, which will bring Parallax X and Archetype: Nolly X to Quad Cortex, along with some other highly requested features.

Porting these plugins has been more technically challenging than we anticipated while maintaining our high standards for audio quality and user experience. Progress is steady, but we’re not quite at the beta stage yet.

We’ll share more details when CorOS 3.2.0 is approaching beta, including a closer look at what’s coming in the update.

Thank you for your patience.

Quad Cortex Development Update #55

Quad Cortex Development Update #55

neuraldsp.com

Whooo boy

Same lousy excuses; can't even say I'm upset anymore - it's just Neural as usual.

 

[Mongillo19]

Same lousy excuses; can't even say I'm upset anymore - it's just Neural as usual.

Yeah at this point it's not a shock and should be expected. It's too bad. I wonder what the QC would have looked like if they had not even mentioned PCOM

 

[Jarick]

Good to see the update but yeah that's not great news. It makes zero sense that they would completely redevelop the plugins to be cross compatible, but then struggle immensely with porting the cross compatible plugins to hardware.

 

[Lysander]

Porting these plugins has been more technically challenging than we anticipated while maintaining our high standards for audio quality and user experience. Progress is steady, but we’re not quite at the beta stage yet.

Oh, Neural.

 

[JiveTurkey]

Spoiler

JK FAM

 

[mikah912]

There were some cool improvements in 2024 (from my perspective, at least) and it's still a little early to be putting nails in 2025's coffin. (I mean, the odds are in your favor, but still...)

I'm setting the bar for a major modeling company in year three (what really should be the beginning of the prime of the device) for an entire year of firmware development higher than "they made some cool improvements".

Like, I'm sure they were cool and/or useful. Good for them for working on quality-of-life stuff! But that's not good enough for 12 months of opportunity. And especially not with the newsworthy and revolutionary TINA in the arsenal. /sarcasm

Given the only update 1/4 into 2025 is that "It's taking longer than we thought. Sowweeeee....", I feel very safe in calling this a lost year too. Even after they manage to get all of the current X plugins on the device....there're still another 10 plugins to convert to X status!

 

[JiveTurkey]

I got off the complaint train a good ways back. And this is sort of hypocritically popping in to say hi to that train in it's own way; but they should have never promised plug-in porting. Imagine if they didn't have that still hanging around their neck.

 

[Lysander]

And this is sort of hypocritically popping in to say hi to that train in it's own way; but they should have never promised plug-in porting.

What grinds my gears is that they advertised on a feature they didn't even have a proof of concept for. Plugin support was clearly not even on the drawing board when the QC launched.

 

[JiveTurkey]

What grinds my gears is that they advertised on a feature they didn't even have a proof of concept for. Plugin support was clearly not even on the drawing board when the QC launched.

 

[Orvillain]

Ehhh. Hard to care really. Especially having just sold it!!

Not a professional device, not a professional company.

 

[Orvillain]

What grinds my gears is that they advertised on a feature they didn't even have a proof of concept for. Plugin support was clearly not even on the drawing board when the QC launched.

Yep. Clearly zero code actually existed for that feature at launch.

 

[mbenigni]

I'm setting the bar for a major modeling company in year three (what really should be the beginning of the prime of the device) for an entire year of firmware development higher than "they made some cool improvements".

Like, I'm sure they were cool and/or useful. Good for them for working on quality-of-life stuff! But that's not good enough for 12 months of opportunity. And especially not with the newsworthy and revolutionary TINA in the arsenal. /sarcasm

Given the only update 1/4 into 2025 is that "It's taking longer than we thought. Sowweeeee....", I feel very safe in calling this a lost year too. Even after they manage to get all of the current X plugins on the device....there're still another 10 plugins to convert to X status!

This is fair. And I wouldn't even "sarcasm" the TINA comment. Assuming TINA exists outside its promo video, it should have resulted in a ton of new content by now. (Exactly what it has to do with PCOM remains a mystery.)

I've always said PCOM was a misstep, and that NDSP would have been better off walking it back. A hare-brained misnomer, a series of false promises and misleading ETAs, and now, more of a technical challenge than they seem able to handle. The last part is the one that surprises me most. But they just don't want to let go of the paywall opportunity.

That said, zero buyer's remorse. Just some interesting history to banter about on gear forums.

 

[Mongillo19]

Assuming TINA exists outside its promo video, it should have resulted in a ton of new content by now. (Exactly what it has to do with PCOM remains a mystery.)

Nah bro, the mods on their discord say it was never meant to speed up the process. It just means real people don't have to turn the knobs

 

[mbenigni]

Nah bro, the mods on their discord say it was never meant to speed up the process. It just means real people don't have to turn the knobs

Is this real?

 

[Mongillo19]

Is this real?

I can't quite follow the mods point, maybe I just don't understand, but yes. He states that TINA doesnt make capturing faster but instead the time between captures faster therefore we shouldn't have expected an increase in amp models? Whether it's a human or TINA, it will still be say 10x longer to recreate more complex amps. But idk who is going to tell him 10 x 5 min for a robot vs 10 x 60 min for a human (obviously made up numbers) is a huge difference lol

Idk it just sounds like mental gymnastics to me. And very confusing.

 

[mikah912]

This is fair. And I wouldn't even "sarcasm" the TINA comment. Assuming TINA exists outside its promo video, it should have resulted in a ton of new content by now. (Exactly what it has to do with PCOM remains a mystery.)

I've always said PCOM was a misstep, and that NDSP would have been better off walking it back. A hare-brained misnomer, a series of false promises and misleading ETAs, and now, more of a technical challenge than they seem able to handle. The last part is the one that surprises me most. But they just don't want to let go of the paywall opportunity.

That said, zero buyer's remorse. Just some interesting history to banter about on gear forums.

Yeah, I try not to relitigate their history anymore. Is what it is.

I just can't fathom why they didn't take a different tack with this particular communication. You know it's been months since you said anything and people are getting a bit restless. They've shown no problem with talking about new features or models to be incorporated down the line in the past - heck, the PCOM schedule for the next 3 major releases is out there.

Now's the time to assure people of the future of the device. Drop all of the hype and crumbs you can muster, but this....wasn't it.