Big Problems With New AMD X2 K2.02 SX3.1

Hi,

I got a new PC a month ago. Works GREAT. AMD X2 4400, ASUS 8V Deluxe. Windows XP2 2GB RAM.

Except... The only thing that gives me fits is K2.02. It appears that I have to often re-load a CPR (project) a few times in order to get samples to play back properly.

When I first load the CPR, the K2 channels either will not sound at all, or 'burp' with just a few 10ths of a second of sound on one or two notes. The CPU bar in Kontakt jumps around a bit.

The same exact CPR played -fine- on my previous PC (AMD Dual Athlon 1800+)

Any ideas?

---JC

 

Hi,
Im getting this problem on Athlon64 2000.

As a quick-ish workaround, every time I load a cubase project I load up the Multi in Kontakt.
This means saving a Multi every time you save a Cubase project which NI should fix!!!
Its driving me a bit nuts.

 

Well, I got this reply from NI:


"enter cubase settings and disable multiprocessing there.
enter kontakt options and alter the dfd settings
defrag your hard drive
try the standalone with the instruments you use in you projects.
check cpu and ram use while playing a cpr

the k6 is the worst processor ever. I believe a k6-2 dual system
might have been the wrong choice."

While I thank them for replying, my overall reaction is: "Gimmee a break." All my other plugs, including Halion 2 and 3, UAD-1 and PoCo cards work just fine. Please don't blame the CPU.

Please, just fix the issue!

 

replies like that make me never want to buy another NI product ever again

 

Naaah. I love their products.

[RANT]
And if you think NI's attitude is bad, just try the other German companies (particularly the one in Hamburg.) Man I -hate- to sound -whatever-, but I always thought of German companies as 'craftsmanship' and 'precision'. Until I started getting into DAWs.

There -are- music software companies that are great about customer service and don't release 'beta' versions of software.

But I think people got used to unreliability in the early days, -and- thinking that writing DAW software is 'rocket science'. And now some devs use that as a continuing excuse to keep putting out products that aren't properly tested.

After all, most people don't buy products based on 'reliability'. They buy based on sexy ads and feature lists as long as your arm. So companies have very little incentive to change their ways.

That said, I have -rarely- had any problems with either B4 or Reaktor so I guess I was about due.
[/RANT]

Thanks for writing.

---JC

 

K2 IS a mess but I haven't had this problem. An occasional midi volume or pan may unexpectedly malfunction & other nasties. You may want to consider of factors.