Developers - Why Change Scroll Behaviour!!?!?

I was just wondering why (as of Kontakt 1.5x) the right-click Zoom in the Mapping Editor was removed entirely from 1.5? I loved that feature! I'd like to know how it could possibly be justifiable to remove that feature, leaving users with no quick way of zooming in/out? I have to click individually on the "-" "+" buttons now!

Is there a consipracy to create repetitive-stress injury victims at NI? And is this a permanent change?

Best Regards,

 

OK, nobody's interested in this thread. That's fine. But has anyone noticed less-than-smooth graphical behaviour in 1.5x? I have noticed that the mouse gets all gimpy when you click on certain folders in the Browse - like if I click on "KONTAKT PATCHES" (my main Kontakt Folder), the mouse suddenly goes all 5-frames-per-second! And the audio engine now cuts out when I add ANY modifiers - LFO, AHDSR, etc. This didn't happen before. Anybody else getting that? What's the DEAL??

Best,

 

I can tell you that Kontakt crashes spontaniously under Sonar 3!
That really sucks!

 

Wow! That's like the good old days.

 

I don't experience that with Sonar 3. Kontakt 1.5.2 has been extremely stable for me.

The slow mouse reaction is usually due if your host audio engine is too loaded. Kontakt cannot do anything if you have billions of plugins running in your host at the same time ;-)
For a smoother editing in Kontakt, I usually stop the audio engine.

 

Thanks for the response, but I get the slow-mouse business with nothing but Kontakt loading, with no instruments. I noticed that this doesn't happen with Kontakt standalone; only as a VST in Cubase SX. I don't use Sonar anymore, but I'll try it in there maybe.

 

PS: I should also mention: Kontakt 1.2x NEVER behaved like this, even with on-the-verge-of-crashing CPU loads. I know it's 1.5, there is little doubt.

 

Wow, that´s interesting...my Kontakt crashes spontaniously even when the CPU usage is low.
It´s the only plug-in I have that crashes my system...

Tom

 

Hmmm...I don't use Sonar much anymore, apart from restoring old projects, so I can't help much. I was never happy with Kontakt in DXi (but that has as much to do with DXi problems in general than anything else) and I eventually switched to VST. You may want to contact Cakewalk/NI directly and see if they have any ideas. What's your PC/audio setup?

I'll try messing around with Kontakt and Sonar3, see if I get any crashes.

 

Hey Bduffy,

I too experienced some slowing (of both mouse speed and program operation) in Kontakt with the initial 1.5 update

I found this VERY frustrating

When 1.5.2 was released, I decided to uninstall both Kontakt, Reaktor, and my other audio apps.

I also ditched Logic 5.5 and bought Sonar 3 (for a bloody good deal btw @ www.jdsound.com/store/product1.asp?SID=2&Product_ID=3491)

Before installing Sonar and Kontakt I cleaned my registry and deleted any Native Instruments related entries.

With my fresh install, Sonar and Kontakt are ROCK solid... both under wrapped VST and Dxi.

I'm a happy camper but maybe I'm just lucky

Possibly a system cleanse will help your problem?

Just my thoughts on the matter.


---

oh.. on a side note, how goes your decision making process on purchasing Reaktor?

All the best from Auckland.

 

Hello again, JP!

OK: I really hope it's not a registry-thing. My new computer is only 2 months old! It hasn't had TIME to get that messed up! I wonder if the Reaktor install somehow affects it? I'm going to uninstall the demo and any other NI stuff I have on there - could be a conflict - and see if that helps. Man, what a pain; yesterday a comp crashed when I was loading a drum kit while the song was playing (I used to be able to do that no problem)...I just don't know.

One thing I have noticed is that VST plugins that are coded for Macs first often cause big CPU/Video problems on PC-VST: PSP Audioware's stuff and Nomad factory for example; wonderful plugs, almost useless in Cubase SX-PC. Now prior to 1.5x, Kontakt was obviously PC-VST first (the only truly working format when it was released)and it was a breeze in Cubase - but a nightmare for everyone else. Now the opposite is true. Great. I had to pay for Kontakt to work better on OSX than on PC. Fine: how about next paying gig, we make it worth it?!?

Sorry. Reaktor? Well, I can confidently say that I will pick it up at some point (as long as it isn't messing up Kontakt). It is truly the most vast, powerful synth there is. I'm amazed at what you can do with it AND you can use it all as audio plugins! I can see the source your enthusiasm - except I'm not sure how people ever used it on anything less than a 3ghz!?!? That's the only complaint I have: CPU.

Thanks.

 

I doubt it is a registry thing. I would look at other factors... Some particular operation in Sonar 3 used to be slow and I figured out that the issue was the video drivers by updating to the latest NVidia drivers, it solved the issue. Try to reduce the color depth of your display see if there is any improvements. Then I would look to the ASIO drivers... which version do you have? what buffer size ? Is the computer doing disk or CDROM accesses too when this issue appears ? Is it happening when there are no instrument loaded in Kontakt ?

 

Oh Look at all this good advice! JOY!

Hmm...my video drivers are up-to-date, I think - but I'll double-check. My ASIO drivers will never be updated as Echo Audio has seen fit to discontinue my card - but they are the lastest. My buffer size is 512, and sometimes I'll go higher (but I really don't see much difference in performance unless I go drastically higher or lower). At home, I am exhaustive about making sure there is as little as possible going on in the background. And yes, if I open a blank comp, load a blank Kontakt and load an instrument: the mouse will dissapear or move chunkily. If I click on certain folders in the Browser, the mouse gets chunky.

And besides: My System settings were the same as I used just 2 weeks ago with Kontakt 1.2x and everything was fine! I've tried Kontakt at work and I got the same results on two very different systems...I wonder what's the same culprit between them?

Oh yeah - I just tried it in Sonar 3 and the scrolling worked perfectly, but it still has the same lame mouse-slowdown problem. Yeesh.

Thanks all.