Quad Cortex Development Update #44 & Plugin Development Update

Quad Cortex
22

That blurb you included from Neural simply reinforces what I was saying. As a matter of fact, I think a better way to convey the status of the “X” plugin versions would be to just include the blurb above in the development updates and get rid of the “free” description.

Sure, no debating there are companies that charge for upgrades, particularly when it comes to enterprise level software. That just doesn’t happen to be the current paradigm for modeler firmware (may it stay that way!). Just think the “free” terminology for the plugin in the context of the ‘QC Development Update’ is confusing. Best not to refer to it that way.

23

I don’t see it that way, but I’m tired of talking about it. Let’s all high-five each other and be glad that rad stuff is happening.

1 Like
24

High five! Or maybe ten!

25

There is a difference between a free update and paid updates says one who regularly has to pay for software updates from various companies/versions

26

As someone who has been a software developer for many many years, I can say that’s exactly how you say it. When you buy a software plugin such as these neural plugs, you are not getting firmware. The firmware changes/upgrades will be in CorOS
updates (currently also happily free :slight_smile: There are plenty of under $100 app software business models out there that depend on paid upgrades. I respect your opinion but it is counter to how many vendors do their biz. I’d expect Neural to continue to follow the convention.

27

This is fantastic. Thanks for the detailed communication. I’ll be super stoked if the bass plugins work in QC someday.

28

Wow, just being able to pin my favorite devices to the top of the lists has significantly improved my workflow.

I hope that now most of the crashing bugs seem to be worked out, NDSP will focus on these QOE/user custom configurations more.

1 Like
29

At the risk of belaboring the point, I respectfully disagree. It looks like certain effects, amps, and cabs for the QC will only be available if you make an additional purchase of the corresponding plugin. I can’t think of a perfect analogy because Neural’s approach is relatively unique with their plugin-to-modeler sales model. Some very rough distant analogies would be, for example, Line 6’s “HD Model Packs” or Fractal’s Dynacab packs. However, these are clearly marked as for sale, not “free”. That is my only point, these “X” style plugins are only free if you want to admire them from afar. If you want to use one on the QC, other than any Neural decides to give away, you are going to have to buy the corresponding plugin.

Don’t want to get into the weeds about whether or not other software companies charge for upgrades. Some do and some don’t. Joyfully, most modeler companies, including Neural, still offer free upgrades that include a host of new amps, cabs, effects, and enhanced functionality. I just think that the blurb below, direct from Neural, is more accurate than describing the version of the plugins (“X”), that can be used on the QC, as “free”.

30

Not a fortuneteller, but I suppose in the future we could possibly see a few new “X” updates for purchase where there is no comparable plugin. Or conversely, new plugins with no equivalent “X” offering. Although the latter option would compromise a vision of supporting all plugins in “X” format. Might come down to how efficient they can get their porting process and/or how they decide to proceed with sales and marketing of both their software/plugins and hardware/QC.

If this happens there might be plugins or “X” updates available for purchase only in plugin form or alternatively only as a QC “X” update, but not both. Saves them the trouble of having to do accurate/identical ports of the plugins across two platforms.

31

Disappointed to see the wifi connection problem isn’t fixed. So it’s back to my mobile hotspot for that. :frowning:
But yet, I am happy on the whole - there were a lot of fixes and upgrades! :+1:

32

Fair point. The plugin itself isn’t firmware, but in a way, when Neural delivers on their plugin translations to the QC, when you buy a plugin, in some respects, you will be “getting firmware” too. Maybe not literally, but at least the ability to unlock premium ‘X’ blocks, and perhaps even functions, within the firmware/CoreOS.

That said, I can see where my post might have muddied the waters a bit relating to the differences between firmware, OS, software/plugins. Firmware, OS, and software tend to get conflated when users talk about modeler updates. And now, “plugins” are probably going to get caught up in that too.

I don’t know exactly how Neural is going to translate plugins to their corresponding blocks on the QC. Maybe by simply ensuring a customized set of ‘X’-blocks can accurately emulate a given plugin. As far as I know they have no intentions of actually running plugins on the QC (could be wrong).

So, in the future I am speculating, to activate a “plugin” on the QC, under the covers, Neural will just be granting you access to the premium blocks required to emulate that plugin. Blocks that may already be in the firmware/CoreOS, and also accessible to CoCo, but unusable without having purchased the corresponding plugin. I suppose another alternative would be having ‘X-packs’ of blocks that would need to be loaded. That seems like it would be tricky to implement.

We might be seeing a new CoCo version with each new firmware that includes any substantial changes, excepting the strictly bugfix versions. Similar to, for example, when Line 6 adds blocks in a new firmware, they also have to release a new editor version. Might also be seeing new firmware and CoCo versions whenever new ‘X’ updates get delivered for use on the QC. No idea though really if this will be the case or not.

Theoretically you could code an editor to pick up new blocks in CoreOS (or any modeler’s OS) without requiring an editor update every time. Might be more hassle developing that than just modifying the editor for each firmware version though. Depends on the architecture/design.

Really curious to see how the whole Plugin Compatibility (PCOM) and ‘X’ updates thing ends up getting implemented. Total mystery to me right now. Wonder if anyone in the know can chime in with additional details.

You’re right. That and subscription models have become common.

33

It will be interesting to see how this is implemented. I wouldn’t be surprised if support for all of their software plugins gets baked into future versions of CorOS and them they just have some method for you to be able to unlock functionality for the plugs you own.

34

Neural confirmed this in the September 26th update. Plug-in compatibility will be “block-based”.

image
image732×319 25.7 KB

2 Likes
35

This pic seems to disclose that plugins on QC will be block based. I hope one of them is the Transpose function as a block:

image
image708×413 30.4 KB

4 Likes
37

I’m hoping for the doubler to make its way to the QC.

2 Likes
38

All right dad, sorry for the stupid question. :roll_eyes: