I support this standpoint though. It wasn’t clear for me, that they confirmed full midi support already in the advertising process.
So i have to apologize for my take on this.
Misleading is a bad thing in any case.
1 Like
Take your time NSDP! There is 0% room for mistakes.
4 Likes
This is exactly where I stand. While I do agree that “Q2” caused a high expectation on people, my QC sounds amazing as it is, so I rather prefer them to release with the minimum risk as possible.
I will not update until several days/weeks later, when I’m sure it doesn’t cause any problems or constraints on my gigs. I cannot afford to rush an update “just because” and compromise any shows.
That being said, I do agree with some that perhaps they shouldn’t give any timeframe and/or, explain why they couldn’t meet the deadline they themselves created.
4 Likes
In all of my years dealing with customers the main thing I’ve realized is, most of them can deal with bad news, technical issues or delays. What they CAN’T deal with is the lack of communication. NDSP’s “fuzzy” release date is completely understandable but to miss the date and not communicate about it only makes things worse. Honestly, have they EVER hit an update release date?
I am heartened by seeing SO many “we’d like full midi control” requests! I requested this in April of 2022. MAYBE, HOPEFULLY we’ll see it in this release.
Hang in there everyone! We all know that when the release does show up it’s gonna be great!!
5 Likes
This hits the nail on the head!
Sure nobody is gonna be happy if the CorOS 3.0, and thus PCOM, is announced to be delayed but it sure causes less anger and mistrust than missing the self imposed deadline and not saying anything about it.
5 Likes
As a professional optimist, I think maybe the reason is that the release is just around the corner, so instead of communicating a new deadline, they release the software in the next days.
But don’t hold me accountable if I’m totally wrong 
5 Likes
While that could be the case, wouldn’t it still be nice to get a short notice for that?
Just something along the lines of:
“Sorry that we didn’t meet the deadline of Q2 for the PCOM update, it will however be only a few days late and we expect a release until day x”
1 Like
that’s what I’m saying: Is it really that hard to communicate? Would have prevented a lot of discussion and guesswork. But who knows, maybe NDSP think it is kinda funny how a lot of us are discussing the uncertainties (cf. “soon”). But IMO it isn’t remotely funny and adds up to a bad reputation. 
I’m guessing busy with this update?:
Excuse the language, but what a shit show…
Can’t update us on the state of the PCOM update but they can push another X update, that no one can use on the QC…
3 Likes
The update we deserve, not the update we need right now lol
1 Like
For the last time, folks:
The plug-in group and the Quad Cortex group are two different teams.
Parallax X being released (and surely more X plug-ins being worked on) does not adversely affect CorOS 3.0.
3 Likes
Fully understand that it’s two teams, but it’s one company, and one would think they’d try to avoid the optics.
Thats not even the point I made, I am fully aware that these are separate teams/departments.
It was related to the communication to the customer (which is probably not done by either team) which is very lacking.
Getting a notification that another X plugin is released while the deadline of the PCOM update, which NDSP imposed on themselves, passes without anything from them, just leaves me baffled.
2 Likes
It is still a matter of where to focus the company resources and time. They only have so much of each.
2 Likes
re: “communication”-
they already told us ALL OF THIS WOULD Happen.
They said more X updates would drop before PCOM/CorOS3.
Q2 was an estimate barring unexpected bugs.
There was never any PROMISED date.
They did communicate. They told us ALL of this.
We will either get a dev update soon explaining the delay, or we will get CorOS3. If it’s only a matter of days, not weeks, I could see why they might be waiting instead of posting. Can’t you? It’s only been 3 DAYS since the end of the month.
6 Likes
For the last time, folks:
The plug-in group and the Quad Cortex group are two different teams.
Parallax X being released (and surely more X plug-ins being worked on) does not adversely affect CorOS 3.0.
How is that relevant to me? I seriously need the CoreOS update 3.0 or I’m going to cry and nobody wants me crying right?
4 Likes
I’m OK w/ a little crying. 
1 Like
5 Likes
