Quad Cortex PCOM (Plugin COMpatibility) slated by Q2 2024

[Lysander]

Also, CorOS 2.3.0 and Cortex Control are officially releasing today.

Quad Cortex Development Update #44 & Plugin Development Update

neuraldsp.com

 

[MirrorProfiles]

EXTREMELY BORING but genuinely curious how they are going to handle ilok/copy protection, wonder if they'll move to another system when PCOM comes. Given that users will have already forked out a good £1500 or so on a QC, and that most of the plugin amps are already in the QC, they're probably better off keeping a more rigid protection on the plugins, and something less secure on the QC.

 

[Lysander]

The QC is very cloud-centric, so handling licenses should be straightforward for Neural: if your registered user doesn't own plugin X, you don't get to use it on the device.

 

[ian_dissonance]

 

[laxu]

The QC is very cloud-centric, so handling licenses should be straightforward for Neural: if your registered user doesn't own plugin X, you don't get to use it on the device.

Makes me wonder how that plays out for extended offline use (e.g on tour) and whether it requires "calling home" periodically to check for a valid license. I assume it would use something like an expiring unique, per user and per plugin certificate or something like that to validate purchases on the QC side.

iLok does not seem to run on Linux so there's no option to just have that as a service on the QC.

 

[Orvillain]

I don't care anymore.

 

[Lysander]

Makes me wonder how that plays out for extended offline use (e.g on tour) and whether it requires "calling home" periodically to check for a valid license. I assume it would use something like an expiring unique, per user and per plugin certificate or something like that to validate purchases on the QC side.

Welp, this is why you shouldn't rely on cloud-centric hardware for music gear. It's bad enough for a plugin, but this is a box designed to play live.

ngl, the constant phoning home is one of the reasons i got rid of my QC back then. Mine would randomly log off my Cortex Cloud user every couple weeks; i don't know what would happen with plugin support in such a scenario.

 

[mbenigni]

We are sorry that PCOM has taken so long, but we know that you're going to absolutely love [giving us more money for any new content].

I'm the QC's biggest fan and I don't care (about this) anymore never cared about this.

 

[mbenigni]

Welp, this is why you shouldn't rely on cloud-centric hardware for music gear. It's bad enough for a plugin, but this is a box designed to play live.

ngl, the constant phoning home is one of the reasons i got rid of my QC back then. Mine would randomly log off my Cortex Cloud user every couple weeks; i don't know what would happen with plugin support in such a scenario.

I think we're probably borrowing trouble where this specific point is concerned. There's no reason to assume the QC would change state and revert access to content in absence of a connection.

And I only care to the extent that I'll probably eventually be strong-armed into buying a plugin with a spring reverb that doesn't sound like ass. (At 50% off, naturally.)

 

[DrewJD82]

When they put out an update addressing this shit, or have actual working functions to discuss, I’ll pay attention.

 

[mbenigni]

Any word as to whether 2.3.0 will include any new content or improvements? It seems odd that they'd do a full minor revision just to give their official blessing to functionality that was already working in beta.

 

[SeeD]

 

[mbenigni]

And here I thought you were the QC's 2nd biggest fan. Not in the market for plugins, maybe?

 

[SeeD]

And here I thought you were the QC's 2nd biggest fan. Not in the market for plugins, maybe?

This is me `acting to be a QC hater`

I have most of the plugins in capture form, but I look forward to having a model of the Darkglass b7K and Parallax plugins as I own these

 

[Mongillo19]

here I thought you were the QC's 2nd biggest fan.

Id argue he's #1 in this forum

 

[OrganicZed]

It is telling that they chose to include the comment about how releasing / updating plugins has no affect on the speed at which they will finally deliver on the promise of plugin compatibility for the QC. They must be seeing all the comments in the forums complaining that the company diverts too many resources to developing new plugins when all people want is for the plugins to actually work on the QC.

 

[Orvillain]

When they put out an update addressing this shit, or have actual working functions to discuss, I’ll pay attention.

View attachment 16669

RectumRemus.

 

[mbenigni]

This is me `acting to be a QC hater`

This was my first guess, actually. :)

 

[Orvillain]

EXTREMELY BORING but genuinely curious how they are going to handle ilok/copy protection, wonder if they'll move to another system when PCOM comes. Given that users will have already forked out a good £1500 or so on a QC, and that most of the plugin amps are already in the QC, they're probably better off keeping a more rigid protection on the plugins, and something less secure on the QC.

Doug will come round yer house and turn you into a protein patty for his workouts, if you pirate their stuff.

 

[mbenigni]

Id argue he's #1 in this forum

It's a toss up. I'm not afraid to criticize NDSP where warranted, but I really do love this QC.