The ultimate Kontakt 2.0.2 Bug list [was: K2's Problems; list your problems]

There's a bug in the round robin code when using multiple RRs of different length.
Here is how to reproduce the bug. Set up groups with these start conditions:
group A1: key switch C0, round robin position 1
group A2: key switch C0, round robin position 2
group A3: key switch C0, round robin position 3
group B1: key switch D0, round robin position 1
group B2: key switch D0, round robin position 2

The B1 and B2 groups will not work as expected. Every third note will be silent. It seems Kontakt2 detects that 3 is the highest round robin position and then incorrectly use this value for all groups even though there are only two B groups.

 

This has probably been mentioned already but after createing several New Instruments today it became rather tedious.

the "Options/Audio Engine/Default Volume for new Instrument and volume reset" does not work.

Also setting the volume, even with the shift key, can be difficault because the little "db box" keeps flickering on and off.

It would be nice to be able to double click to zereo (0.0db) it.

 

Thanks for reminding me T.S


The fine tuning for individual samples while holding shift is very bad as well. It should be going in steps of 0.1 each time but instead it's more like 0.7 so it's hard to tune something

 

It would be even better if it were possible to edit these - and many other - values by clicking them and being able to TYPE the value! This is rather standard in Cubase and many VSTi's, even in NI's own Battery...

 

Sorry, I posted this on the main page but thought I should post it here as well.

Here is another bug that's been bugging me for a while.

I use two drives for my samples, instrumentsm, and multis. If I do an update for just instruments on one of the drives everything seems to work just fine.

However, if I do an update for multis or samples on just one of the drives then it wipes out the Database for the other drive. I end up haveing to do a complete rebuild for both drives.

Not a big, big deal but it's time consumeing and frustrateing.

TS

 

DAMMIT!!!

...after a complete re-installation of my system last week, the ASIO driver in stand-alone mode isn't working - O.K., it's a freeware driver (ASIO4ALL), but it has been working before without any problems. Furthermore double-clicking on a REX2-file crashes Cubase SX2.2. These bugs didn't occur before the re-installation. This is so lame - I received K2 on March, 31st 2005 - I wonder, if we will make the year without getting a properly functioning software...

 

That is a nuisance to me too.

 

Please post your operating system, memory amount, processor used when posting bug reports, it will help them get rid of the bug.

Windows xp service pak 2
512 megs memory
athalon xp 2 gigahertz processor.

Bugs I notice:
Standalone mode: does not put kontakt 2 into any sequencers output port list, therefor useless eccept for live performance. It mis-leads the user to advertise a stand alone mode, when it does not work with most sequencers.

Load problem: Sometimes with a 100 gig drive, loading a instrument like one that includes all of the section, will take 5 minutes to load with a 2 gigahertz computer and there is no cancel load button. A persons just has to wait it out. It also crashed at times

VST plugin problem: Will not work with any of my sequencers as a vst plugin. For example, Muzy, will not even load it as a plugin.

Visual problem: The program requires high resolution to see all of its screen, but this is much too tiny for me. Wish it had a low, about 800 by 600 mode with more than one screen so I could see its options displayed much larger.

(I have to run windows xp magnifier to even use the program, not nice to do that.)

I am only able to use the program as a dxi plugin. Works with band in a box, and pro audio or other sequencers that accept dxi output.

 

OS 10.4.5, Dual 2 gig, MOTU 828, Logic 7.2

The issue I'm having most difficulty with is a total loss of sound in arpeggiator mode. It works for a few passes and then disappears into a thick German fog of nothingness. The on-board keyboard shows keystrokes but...not a sausage.

Also, like everybody else I'm also missing the first chord of the sequence unless I preroll.

Update ETA?

 

Hello Markus

Just an idea !
Dont know if it is a good idea !

If K2 was using the VM of MAC OS X instead of it's own VM handler (called DFD) ? would it be better ?

How does work the VM of the EXS ? Does it uses MAC OS X VM handler ?

Best

Cyril

 

Re: K2's Problems ; list your problems

Can you please send some examples in with EXS-> and MachFive-> that you regard as faulty? That would help us nail the issues you regard as important.

FTP them to ftp://ftp.chickensys.com/incoming, please email nisupport@chickensys.com when you do so.

 

Re: K2's Problems ; list your problems

Can you please send some examples in with HALion-> and Giga-> that you regard as faulty? That would help us nail the issues you regard as important.

I'm not sure what you mean by "checkboxes" (do you mean the checkboxes in the Group Editor?) and what controllers are not assigned correctly?

I'm also not sure what you mean by "Fully support Kontakt 1.x import, key switches" - for the first part, do you mean support SampleCell?

FTP them to ftp://ftp.chickensys.com/incoming, please email nisupport@chickensys.com when you do so.

 

Can I jump in here, I have never succeeded in importing any halion 3 files. I have over 100 gig of the stuff most of these files I have created myself using H3 import - mostly from giga. We desperately needed an automatic import facility that scans a hard drive and dumps a copy nki in any directory where ther is a foreign format fxp, gig, etc. This would mean that all your customers could convert ALL their samples to Kontakt. Until then we all have to use more than one sampler - does Native want this. I am assuming this import stuff will be fixed (please). Thanks Garth

 

My system 3500 Athlon, 2 gig, XP pro SX3 Halion 3 Kontakt 2 etc

 

Steinberg did it's users a disservice by encrypting every HALion3 file with it's dongle, but gave HALion3 files the same extension as before (.fxp), and also did not document this fact. I think that if you would ahve known that your HALion3 files would not be portable, you'd not have converted so much (maybe yes, maybe no).

Anyway, HALion3 files won't be supported in Kontakt 2, at least not for now. I don't know offhand whether K2 was kind enough to error gracefully with these files, I'll check.

Thank you!

Actually, I think the IMPORT button works this way, just select the drive on top, and click IMPORT.

 

Sorry Garth I am desperately trying to stay postive but this answer is very unsatisfactory. Native instruments website is stating categorically:


Import and Compatibility.......GigaStudio™, Akai™, S-1000™, /S-3000™, EXS24™, HALion™, etc etc

It also says "Having established its place in studios and on stages all over the world, the next generation of this state-of-the-art sampler supports almost every single professional hard and software sample format making it a truly global player" and then goes to list Halion without ANY qualification.

Remove these claims from your website it is deceiving me and other buyers.

Now I am being told it is not even being planned to happen and responsibility is not even with Native Instruments?

Point 2

No you might think that import works like this but it does not, and it can't import anything at all for me so far.

 

Garth, any news on this?

 

I agree, the problem with the list as I see it above is that HALion should be changed to "Halion I & II" - I agree with you. Make sure Markus hears you.

Putting aside HALion3 (we already know the answer to that), what is not working for you and can you point us to files or send us examples so we can take care of it?

And thanks for being positive!

 

Nope, and thank you drawing attention to this, I'll look at all of this today.

 

Sample Cell????