comments like this are why threads get closed
5 Likes
Itās pretty clear looking at this thread we all want 2.0. Nowā¦ Yesterday. No matter who thinks there needs to be more communication from NDSP on this update status or not (which I do).
1 Like
There is a couple of things that strike me about these threads
- They invariably get locked which leads to further frustration as people feel they are ignored.
- There are varying requirements for QC users. Some are happy with the lack of desktop editor and the unit as it is. Others clearly not. However, and it tends to apply to the facebook page more, those that are happy with it just sneer at those that arent and tell them to buy something else.
Everyone who shelled out almost 2 grand for this unit is entitled to their opinion, even if the company or other users dont either like or agree with it. But a lot of the unhappiness and frustration stems from:
- Promises made by the company at release
- The lack of communication by the company.
There isnt much can be done now about promises made two years ago. It is what it is. But its not too late to communicate better with your customers.
5 Likes
I think thatās the rub, because for me, thereās a ton to like about the it, enough so that it doesnāt make me want to get rid of the unit. Thereās so much potential for growth and itās so close to reaching itās full potential, but I feel like the little things that could make this unit get to where it needs to be isnāt really mentioned by the devs. I donāt know if itās ignored, but itās certainly knocked by the wayside (conversationally, at least) in favor of Hybrid Mode, which is the only thing that has really been mentioned about the new firmware. Iām sure Hybrid Mode very useful, but itās not exactly a selling point for me or what I aspire to be included in 2.0.
3 Likes
wellā¦ i couldnāt agree more.
they keep saying they are still rather small company, but they act noting like one.
small company will cherish their community , and be responsive to them.
and yes, its time for them to grow up and face the criticism that boiling among us, but, it still seems they donāt care (i wanted to use different words, you can guess).
btw, i donāt think we are special then other companies customers , we are not asking anything more then the stuff that was promised , and communication .
i have to say i am amazed. i taught after yesterdays comments , they will do something different. i donāt even know why i taught something will change. but hayā¦ maybe āin the coming daysā.
3 Likes
CorOS 2.0.0 is still being beta tested. Several builds have been released to our team of testers, and as stated in our development updates, āProvided no showstoppers are found in the new build, we are confident that we should be able to releaseā¦ā
As was the case in November and Decemberās updates, showstopping issues were found in the build preventing us from releasing the update. Bugs have to be fixed and everything has to be tested. This process cannot be rushed.
In Julyās development update, we showed that CorOS 2.0.0 focuses primarily on the redesigned Directory. This is a huge revamp with a lot of changes and new ways to navigate the OS.
There are also several new features such as the IR Loader, Global EQ, Master Volume Knob Assignment, which we revealed in August, and of course, Hybrid Mode, which we revealed in September, is also included in this update. In addition, there are plenty more additions and changes that have not been covered.
We have felt close to the finish line for some time and itās a shame when everything seems to be perfect and then a tester finds an issue that sets us back by a week or more, but of course weāre not going to rush or deliver something unstable.
Itās never our intention to mislead you or break promises, so I apologise if thatās how you feel. We are still learning the best ways to communicate about this incredibly complex ecosystem. We know this update has been a long time coming and weāre looking forward to getting back to a more regular update cadence and addressing more of the features weāve promised.
Thank you for sticking with us.
46 Likes
Thanks for the update Dan.
I must caveat this by saying I am a disgruntled QC owner. I love the tones Iām getting and I use it live weekly. But I find the communication regarding the device (pre and post launch) to be abysmal.
Iāve need an NDSP customer for a long time and also own several plugins, but have made the decision to stop purchasing new plugins until plugin integration is sorted.
Dan and the rest of the update team, this is what should be posted on the development updates, not on the forum.
I think a lot has been said about the way that NDSP has chosen to communicate regarding the QC and that it has left much to be desired. Sadly, nothing much has changed since. I do hope that this post heralds that there is some change coming in relation to this.
2 Likes
Thank you for your intervention
Thanks for the update. Donāt think anyone here is asking for anything more than this and no one wants an update with issues. Its not hard lads. Few more posts like this and a lot of complaints vanish.
3 Likes
I appreciate that, and boy we cannot wait to get plugin compatibility out the door!
For the sake of clarity, and to better understand what you want and expect from our communication, could you elaborate on this? Everything I just posted has been said in the development updates. The last one was 15 days ago. So, are you seeking somebody from Neural to confirm that things are still as they were/share the latest status? Or do you want a follow-up development update where we say āa new issue was found, unfortunately this will delay the release by a while longerā?
7 Likes
To be honest. This is the first time I hear from showstoppers. The last update only mentioned a few small issues. Donāt want to be nitpicky but to me this a something different.
Maybe this was something that confused a few people.
Hi @dan,
first of all thanks for the update and summing up of all that was (and as we know now!, so that is a āgood to knowā update) still is planned for this release. And all the best to the team!
Secondly I apreaciate, that you mentioned, that there has been a set back for a certain amount of time. The transparency and if possible the amount of draw back time is to me something reassuring.
And without knowing how the announcement for that release was planned (it is actually the second major release so maybe retrospective from here) the time span between announcement and ready to market could maybe used better. From outside the company, there is not really a notable progress visible, I think.
Thanks for your participation in this Thread!
ā¦ it means to me, that we were heared by you guys. 
2 Likes
I think the issue here for some people is the phrasing used (in the coming days) and the two weeks of silence afterwards. I think if you use that phrase, and showstoppers are then found then you should probably update people because naturally in their head, they are hoping for the best.
For the record, it doesnāt bother me at all but at the same time i can understand where some people are coming from, simply because of the wording used (not because of actual delays, any reasonable person knows that these things happen).
1 Like
For starters I think there areā¦ issues which need to be addressed. One of them being the purported replacement PSUs.
Much has been said about this and more on TGP (where Doug and some others were active for awhile).
In specific relation to the updates, I think there is a mismatch in expectations of consumers and NDSP.
To be clear, I donāt profess to be a software engineer nor am I intimately familiar with development and timeframes. I am an attorney by trade. If I left clients āaloneā without updates for that long, Iād be out of business.
I think part of it has to do with word choice. I elaborate on this below.
October Update:
We are pleased to say that CorOS 2.0.0 was released to beta testers on Sunday 23rd October. Given the size of this update, we expect the beta to take at least a few weeks.
If CorOS 2.0.0 has not been released when it comes time to write Novemberās update, we will update you on our progress.
November Update:
The CorOS 2.0.0 beta is still in progress. A new build is being prepared fixing several issues found in the beta. Provided no showstoppers are found in the new build, we are confident that we should be able to release CorOS 2.0.0 before the end of the month.
Thank you for your patience.
December Update:
A few small issues were found in the recent beta build of CorOS 2.0.0. A new version was released to testers on Dec 30th. Provided no showstoppers are found in the new build, we are confident that we should be able to release CorOS 2.0.0 in the coming days.
Comments:
The labelling of issues as āsmallā gives off the impression that they are easily surmountable. Which then begs the question as to why it it taking this long for them to be resolved. Further, the lack of detail then leads to speculation (which doesnāt help given that consumer trust in NDSP at the moment is already wanting) and then more unrest. At some point, we were promised more frequent and indepth updates/blog posts. I understand that it takes time - but itās time worth investing in my opinion.
So to go from āsmall issuesā to āshowstoppersā - thatās clearly a mismatch.
To consumers, it seems pretty evident that there is quite a fair bit of dissent (nearing pitchfork level occasionally) and it seems like much of it is being ignored / swept under the rug. The tone of some of the updates also doesnāt help. Touting new features that were unannounced previously doesnāt do away with all the unhappiness about promised features / captures / models which have at present, not been delivered. Especially not when it has previously been said that a capture / model only takes X amount of time.
In plugin world, there are definitely plugins that feel like they have been abandoned. Iām hazy on this, but I think there were promised MIDI updates (or something else, donāt quote me on this) for Darkglass and Plini that were done for other plugins but have not been done for Plini / Darkglass.
To be perfectly frank, the product is great. There is great promise. But the QC release (and present state) IMHO was definitely a massive āover promise and under deliverā from the moment that it was announced that shipping was still on track. And subsequently, in relation to Hybrid mode and the āimplementationā saga, a bait and switch. I came from the Helix platform and the communication etc, was great. No surprise that such comparisons would be made. QC Platform, Helix-style updates and answers on TGP would be a total win. At present, Iām of the respectful view that the company and its communication are taking huge chunks out of the overall āscoreā I would ascribe to the product.
I think there are hard questions to be answered, I think the best way to āresolveā this and the move on is for Doug or someone else to do an AMA to tackle them. Iām of the view that much needs to be done to win back customer trust.
There should be a clear roadmap (with realistic timelines) that is (at least broadly) in line with consumersā expectations. Suffice to say, QOL updates such as adding some form of metadata to classify captures, changing the file management, hybrid mode, a desktop editor, are high on most customersā priority list.
I say this in genuine hope and with a desire for the company to get better. Certainly hope that itās not read as being malicious, because there is none of that. I have made references to some things which I remember have been said / have happened, but do not have the specific references to them. If I have said anything that is inaccurate, I seek your understanding that I wrote this to the best of my memory.
While I have your attention, ātransparentā mode for tap tempo is a crucial, crucial missing feature thatās present on the competition. lol
18 Likes
discrepance?
Example: i write a statmentā¦ and iām happy to be near the releaseā¦then a tester find a MAJOR bugā¦ and? why discrepance?
How we can predict the future?? (we all together i mean)
The last comment is a knife in a wound
Understood. I agree that the communication about the severity of these issues and their impact on the schedule should have been more clear. Thatās something we can certainly improve and will endeavour to do so in future communication.
We are working on an up-to-date device list that covers all of the announced devices, new devices, and devices/Captures that were provided as a solution to a previously listed device. I think having all of this in one place will help clear a lot of this up, in addition to of course adding the missing devices (and others), a handful of which are coming in 2.0.0 and more are of course scheduled for future updates.
This is understandable. Truth of the matter is that bringing those older plugins up-to-date to work on the newer plugin framework is very time consuming, and particularly challenging because we have to be extremely careful that the sound of anything does not change at all. All plugins that havenāt been updates will be updated and they are being worked on.
Iām going to work on putting something like this together on a semi-regular basis.
Agreed. A lot of these are, fortunately, coming in 2.0.0.
I truly appreciate the feedback. It would be a great shame for this community to be neglected, and I donāt feel we have been serving it as well as we could, so I hope we can change this and make a more transparent and positive space for everybody.
I hope this is in the feature suggestions forum!
21 Likes
So to all participants in this Topic:
What do you think?
How should we continue from here?
ā¦ what about maybe having this Topic closed and replaced by a category for shorter announcements and questions similar to Bug Reports and Feature Requests?
I am happy with the results and donāt see a need to continue discussions hereā¦
ā¦ but also would like to thank everyone who added to the conversation!!
Thanks again for listening to us!
BR
3 Likes
Update is appreciated if only to be reminded that you know weāre out there eagerly waiting.
thanks
-dave
Great points James and I like your responses Dan. James, quick question, what is ātransparent modeā in regard to tap tempo?
thanks
-dave
why close a thread that has achieved more in a few hours than all the others in months? keep the discussion goin, let people vent
6 Likes