K3 Update....not

Well this week has come and gone and the promised k3 update has not appeared.

NI have not even bothered with the courtesy of letting us know that there is a delay.

I received this from NI support on 17/10/07

"We are currently building the 3.0.1 Update which should fix all mentioned issues and come out next week.

Your NATIVE INSTRUMENTS Support Team"

I paid a lot of money for this software and I haven't been able to use it yet. NI then promised a fix which hasn't been delivered, to add insult to injury they just leave users in the dark..

These NI guys need a lesson in communications. If I'm kept appraised of the situation at least I feel like NI values me as a customer.. but to be totally ignored is utterly infuriating and not acceptable at all.

NI, wake up and behave like responsible adults.

JA

 

well...
at this moment it is only 16:46 here in Berlin, still enough time left...
common NI!
-bw

 

@ assagai

I can understand your anger about this, but what you heard from my support colleague was just his personal assumption at that time, and he shouldn't even have shared that with you.

Unfortunately in software development it is not really possible to commit to a precise release date unless a new version is entirely finished and tested. Therefore NI never officially gives out specific release dates for updates in advance, only the "development phase" information that you can find here:

http://www.native-instruments.com/forum_us/showthread.php?t=55371

The 3.0.1 update is as close to release as it gets, but it won't be out before next week. Sorry for any inconvenience this might cause in the meantime.

Regards, Thomas

 

Thanks for commenting Thomas.

In these situations where the ETA for something is total unknown - it really does more good than you guys and gals at NI might think to just throw us a bone every now and then. It's way better than feeling ignored.

 

Also note, that while I am put out that I can't use K3 reliably at present, I would much rather the time was spent to ensure that the patch worked as advertised and didn't introduce more errors that would have to be patched later.

 

maybe a good idea would be to post updates on the update, you have the stages but lets say you run into an unexpected problem or you have to go back in the beta stage for example it would be nice to mention these issues so you are seen to be doing something, thats what people need some times i have to admit it can be a little daunting watching the bold print of final testing remain the same for weeks as if you have just forgotten about it which we know isn't the case but it's the simple reassurance i believe that can go a long way.

sureno

 

i'm with deafblind. i'd like the patch to be as tight as possible, because the updates usually leave some things unresolved anyways. i can only imagine how hard those guys are freaking out, probably working 22 hour days. i know i'd be really embarassed if i were them.
or maybe it's just a joke.

 

When it comes to update releases you should compare the estimated date to a weather forecast. It may no always come true.

Still, just getting an approximate date is nice, though. For instance I plan to clean my harddisk and start from scratch now that Cubase 4.1 has arrived. So knowing there is K3.01 coming I might postpone reinstalling Kontakt 3 until it is there. The idea is to avoid installing outdated software as much as possible, because sometimes they interfere with more recent versions.

 

http://www.native-instruments.com/forum_us/showthread.php?t=55371

v3.0.1 is now available.