I’m 99.9% sure i read “all existing plugins” would be PCOM’d but i can’t seem to find where that’s posted now.
I remember this update:
But I don’t see that it will be necessarily for all plugins… at least the way I understand it.
I believe it is NDSP’s intention to make all their plugins X compatible, but not sure if that’s even possible. I’ll take what they get though. I’m not even sure if it will be that important to me until I see how they work. As it is now, the QC works great for my needs so anything else is gravy.
The one thing that could really make it better for me, is I could be more precise, and versatile playing live if I had more control of the blocks with midi. I’m sure they are working on it though
Sorry my English is not good, I used software translation.
QC is pretty good for me, convenient operation, intuitive display, relatively rich functions, etc.
But compared to other products in a similar price range, QC is not amazing enough. I believe that most hardware users don’t care about plugins. It has been 4 or 5 years since the QC was released, and there are only a pitiful number of factory models, and the quality of the FX is not satisfactory. Although the official provides 1000+ factory clones, there is no folder retrieval, and the experience is very scary.
There are also some strange bugs, noises, and so on. I think the NDSP should focus on the product itself, the QC itself is good enough to keep attracting new users, after all, a lot of guitarists who use hundreds of dollars of equipment have the need to update the hardware, and at the same time, new people are constantly joining the guitarist circle. Instead of making money by selling plugins.
Under the premise that the QC itself is sufficiently complete and stable, the regular update vitality is maintained, and the model is constantly increasing. It’s also feasible to sell modest paid expansions. I don’t know if the NDSP can see the user’s voice.
10 Likes
I love my QC and i’m totally happy with it’s functionality atm. But these development updates are reminding me a bit of Microsofts dev update messages, which are mostly empty 
1 Like
we begged for communication for years!
Now that they are posting updates regularly, we can’t really fault them for having nothing new to report when there is nothing new to report.
It’s a bit of a paradox; if they don’t say anything for a while, they get complaints.
If they have nothing to say but say it anyway for the sake of regular comms, they get complaints.
11 Likes
I don’t think the communication is the problem, i think it’s just the emptiness of the QC update that is concerning some folks (including me).
I personnaly look at what they do more than what they say and it’s not quiet there for the QC at the moment (it could change with 2/3 great updates)
The problem is that it’s just one ‘feature’ so seems like very little, however, it’s a (technically) huge feature that likely requires a hell of a lot of work to complete.
Who knows, they might add other bits in too, but the focus is definitely PCOM for now, so just need to wait til that’s done.
1 Like
You are right on that and I totally agree that they seem to focus exclusively on PCOM as the next big thing. And exactly that is what I don’t like. IMO they should schedule their time on the current big project (now it’s PCOM, later it may be something else) and on smaller fixes and requests at the same time… Like maybe 75% big project / 25% smaller stuff (or even 50 / 50). That way users that don’t wait on PCOM also would be served and wouldn’t be angry about the silence. The System as a whole would progress steadily and continuously by fixing all the small quirks and adding some QOL features while the big project would also progress in a good pace. Probably even more important: The users would be able to see/“feel” the continuous progress, what could be a huge boost in customer satisfaction. Every software company I know (and/or worked for or with) works that way. 
7 Likes
It’s likely that PCOM requires such an extensive change, that it would be too complicated to implement other fixes at the time time as it would just add more code that needs to be rewritten, and further delays the main objective. A kind of ‘all or nothing’ change.
It is also possible that they are adding small upgrades/fixes in the background, but tracking them and updating people on them is just not worthwhile.
It’s all conjecture though, and discussing it isn’t going to change the outcome. Just need to wait for ‘sometime in Q2’, and see what happens.
1 Like
If PCOM does affect things like LED colors and Hybrid Mode GUI (or UI in general apart from new icons, new parameter popups, new categories in the effects list) they did something horribly wrong during concept / architecture development. 
Couldn’t agree more with those that are saying they want more than just the PCOM update. And I agree with you - in part - the QC does sound great. However it really doesn’t play great, in some ways not at all; as per the YT vid posted by one of our forum friends here, asking what we want for the QC in 2024, to my mind the most desperately needed fixes should be some of the easiest to achieve, and could surely piggyback on the PCOMN update when it launches, but I don’t hold out much hope.
Those fixes are;
"1) Please please please change the awful way that you change Modes, which is currently done by pressing Preset Down and Tuner switches at the same time; IMHO this is absolutely the worst thing about the QC… It is so easy to accidentally change preset halfway through a song if you catch the Preset Down a fraction before the Tuner switch.
Suggestions to improve this; a firmware update so that Preset Changing is only ever accomplished by a LONG press on the Up or Down switch.
This would prevent any accidental changes to a preset either while changing mode or, and this is just as big a problem, when editing a preset, in Grid view;
- a number of times when I’m tweaking a preset, the Preset Down rotary encoder is available to adjust a parameter by turning it.
- HOWEVER, all of the lights under the rotary encoders that are assigned to a parameter are lit in the same colour, no matter what Mode you’re in.
- The only way to see what Mode you’re in when you’re editing a Block, is the small white writing at the top right.
- This is always in WHITE no matter what Mode you’re in. (WHY NOT HAVE A COLOUR CODE FOR THIS, SO ‘SCENE’ ‘PRESET’ AND ‘STOMP’ ARE WRITTEN IN DIFFERENT COLOURS?)
- I can’t tell you the number of times in this scenario I’ve accidentally pressed the Preset Down thinking I was in Stomp Mode, and turning off a Block to hear the changes as I’m editing, only to find I’ve changed preset by mistake
-
An update to STOP the ridiculous way the ‘Undo’ button works; for example, you’re in an overdrive block, editing the gain. You change it from 4.0 to 5.5. Then you decide to undo that change, using the rather convenient ‘Undo’ button. So you press it. And it exits the block edit window, and takes you back to the Grid. Every time. WHY, NEURAL, WHY?!
-
The most positive of all; a Looper update that lets you save loops, and even assign them to a Preset to be recalled automatically. The Headrush units have been able to store loops since the first floorboard came out.
Addressing even only the first of these would make using the QC an entirely different (ie far far more positive) experience.
6 Likes
Thank you for the update, I’m a simple soul, I’d just like matched cabinets on selection of an amplifier and models of the three reverb tanks that fender use on a variety of their classic amplifiers. Thank you in advance. 
2 Likes
Of course I would also like to see more frequent updates, but when it comes to priorities, I remember that a desktop editor and plugin compatibility were promised since the beginning, so I understand that they are way overdue and need to be implemented.
(And the post did not say that there is no other new features in the coming update, let’s see)
As for the priorities for new features / fixes, I always had the feeling that Neural were at least somehow taking into account the feature requests on this forum.
So at least we can influence a bit by giving our votes.
I think if you are desperately lacking a feature, the best way to get it “soon” ( 
) is to advertise the feature request and try to get as many votes as possible.
4 Likes
Why would I be excited about the plugins? To me this sounds like the beginning of subscription-based content to the world of modelers. What is there to be happy about? I can finally pay $100 to get some more sounds on the QC to offset the fact that it has fewer FX options than the competition? And it took one year for this privilege during which they could have worked on free features and improvements? Nice…
6 Likes
Yes, for me personally it also doesn’t make too much sense to pay 100€ or more for a plugin just to extend my QC sounds or effects. (Although there are sales sometimes where you can get them much cheaper)
I guess it’s more for the people who anyway use the plugins for recording on their PC. Then it’s probably nice to use the same presets on the QC.
And I remember that on this forum, there were many many complaints about the plugin compatibility not implemented yet.
I think and hope that NDSP are thinking this way:
- Common blocks (Transpose, Doubler…) release a update for free on CorOs
- If you REALLY want that weird amp or one of kind effect you should get a plugin
But, in general, common effects should be released on CorOS updates for free. Its not fair not having a Transpose or Doubler when you paid a lot of money for this hardware. I do think and hope this is how NSDP is approaching the subject.
6 Likes
I had the plugins way before there was a QC.
When they announced the QC, it seemed like a great way to take those plugins on the road.
That’s why a lot of folks DO care about the plugins. They were here first. They were supposed to be a priority since the QC was released
2 Likes
Priority yes, exclusiveness no.
5 Likes
Yes great way to take plugins on the road no doubt. But when I bought the QC it was not written anywhere that “BEWARE: new features available ONLY by purchasing a plugin”
So it can be priority I agree but shouldn’t be the only way to get some basic blocks/effects (and in anyway I’m saying you are implying this, I was just complementing your post)
3 Likes