So…NDSP gets everybodies hopes up regarding the time frame of the release, then people start bashing those that actually got their hopes up?
The least NDSP could do is provide some communication as to what’s going on.
I mean…this is one of the most expensive units out there. From what I can see, the users are pretty loyal. Communication and respect appear to be deserved.
I will be taking my QC to church and playing like every other Sunday…but, having pitch correction and additional midi control would have been nice to have at the time they told us we would probably have it.
I understand folks getting impatient about this update not being released by now but please keep in mind that this OS includes a feature that no other modeler has ever offered. I’d guess beta testing is probably a lot like playing whack-a-mole. I’m thinking that those who are expressing their frustration most vocally would also be the loudest if v3.0 had been released yesterday but was full of bugs. Personally, I think that NDSP would receive less grief if they released more small updates. At least they would have a short reprieve after each, before the angry mob reboots.
“this OS includes a feature that no other modeler has ever offered.”
Though technically, one can argue that NDSP “offered” this feature, verbally, when the QC was released…2 years ago…so the anticipation on the part of the community is pretty much the fault of NDSP.
I know how my dogs get when I taunt them with treats…woof
additionally…I was on the beta test team for Headrush Prime/Core (I had a Core) and honestly, while I loved being able to use and test the updates before a lot of other people, I would get frustrated when, for all intents and purposes, I could see no reason that the update wasn’t rolled out to everyone. I mean, if we’re talking about a complete “make it crash” bug, that’s one thing, but a graphic on one specific effect not showing changes…yea, we could live with that until a bug fix was released.
So today I gigged with my same old,
Un- updated plugin compatible wizbang does everything but wipe my butt best thing I every played thru. And I enjoyed the no issue, a dialed in tone and just Played…
I can wait, Would rather have a better update than one that hinders the above…
Fan boy??..guess the shoe fits, put me there, call me square but I got the cleanest underwear …is it worth cropping yourself over a day?
What happens if it lingers on?
You could just play your guitar in the meantime…write a song about it
After 3.0 promises, soon, soon, soon, I switched from hx to qc. Now where is my 1600 euro update? The sound is superior but lack of normal midi integration is abysmal.
They’re a little overly tight lipped for my tastes. Going late I can understand. Not giving some descriptive information as to where things stand more frequently would take some of the sting out of things. Fortunately I have an Axe FX III MkII Turbo and an FM9 Turbo that are frequently updated (and everyone gets to make a choice whether to download the beta versions of their software at their own risk. It really works well!),
I think it’s more your cup of tea, buying a unit which hasn’t the features (at the moment) you actually need!?
Never buy anything with the intention that “an update will fix it”.
And I’m a software designer. This is not something that an update will fix, but a core feature of any modern modeler. They did promise it not? By June at the latest as I recall.
Normally I would be completely supportive of this viewpoint. However, Neural was less than transparent with that particular feature.
The QC was advertised as having “full midi support”. When people bought it, they suddenly found that it didn’t actually have full support. While they didn’t outright lie per say, they were misleading to their customers.
Midi is something that has been in every unit since at least the line 6 pod x3 (2007). It’s a feature so ubiquitous that no reasonable person would assume it to not be there. QC themselves stated it was already available in their marketing. In this case, I don’t feel that’s a mistake on the buyer’s side.
It’s an issue compounded by the review cycle since it’s not a feature you would test when your goal is to review a unit on its own merit.
To be fair to the company, they did say they would try to have it by the end of the month. However, I’ve been using Fractal for twelve years and they never disappoint and updates are often and features are beyond what I’ve been able to do with my QC so lots of disapointments here.
For me it’s just like, don’t set deadlines for yourself publicly and then not meet them. Communicate, sure, but setting an end of Q2 goal and then not meeting it with zero communication is just weird. It’s not like the consumers told them it was supposed to be out by Q2, they did.
Agreed. Just stop setting milestones you can’t meet. I think it’s pretty obvious by now this does a lot more harm to the company’s image than just laying out what’s in the pipeline for the next release.
