1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

stuck notes and other bugs in K2

Discussion in 'KONTAKT' started by peeddrroo, Apr 21, 2005.

Thread Status:
Not open for further replies.
  1. peeddrroo

    peeddrroo NI Product Owner

    Messages:
    82
    i'm using K2 with Live 4.1.2, and i've noticed that i get stuck notes each time i stop the sequencer. when i play notes on a keyboard everything's fine, but when they come from the sequencer, they keep on playing after the sequencer is stopped, as if no "NOTE OFF" message was sent (or received...). i didn't have the problem with 153.

    another bad thing is that when you select a sample zone in the mapping editor, it kills all voices (just clicking on any zone kills the audio until new samples are played). it is very annoying (though it is usefull to stop the stuck samples mentionned above).

    i've noticed that when i'm loading a multi that was created with K153 and that was loading fine, now i have a message saying that "physical memory is getting low".
    and on first playback of the song, each time a new sample is being played, i have crackles in the audio.

    i've also had plenty of crashes, especially when playing with the convolution and the surround panner.

    that's it for now. as expected, this kontakt version is cool, but it needs to be fixed....
     
  2. tigershark

    tigershark NI Product Owner

    Messages:
    52
    Pedro, noise crackles were an issue for some users in version 2.0.0, when multiprocessor support was enabled in the options. This has been fixed in version 2.0.1, which might possibly help you out. Of course, it might be the case that you simply don't have enough RAM in your PC. These days, you really need 2GB or more for music production to have a life free of pain. Ideally, you should have enough so that you don't need to be using virtual memory at all (hard disk pretending to be RAM). If you have enough RAM, it can be a good idea to disable virtual memory (this is the recommendation in the Cubase manual) as your CPU will be wasting a lot of time moving stuff around from memory to disk.

    The stuck notes that you mentioned were a problem for me also, using Cubase SE. I got Cubase SX and the notes stopped OK. I suggest you report this to tech support as it seems to be a sequencer compatibility issue.
     
  3. peeddrroo

    peeddrroo NI Product Owner

    Messages:
    82
    thanks for your feedback.
    apparently another user has found where the "stuck notes" problem comes from (see the "hanging notes uncovered" thread).

    concerning my memory problem, i have "only" 512MB of RAM, so that might be a problem, but does it make sense since K2 states that the loaded memory for the patch i'm working on is less than 200MB? that should leave enough room for the processing without having too much crackles.

    i'll try it when disabling virtual memory, i'll let you know if it improves the situation.
    cheers.
     
  4. tigershark

    tigershark NI Product Owner

    Messages:
    52
    Peeddroo, I would not recommend disabling virtual memory with such a small amount of RAM in your PC. Your machine probably needs VM just to stay alive.

    Remember that the operating system gobbles up a fair bit, any applications you're running plus, of course, in-memory samples.

    If you can, get more RAM. You will probably notice better performance all round straight away.
     
  5. Jomdom

    Jomdom NI Product Owner

    Messages:
    24
    Pedro,

    Go ahead and follow the steps I mentioned in my thread to see if you can get the hanging to happen under the same circumstances...

    I also have the zone click -> cut all instrument voices problem as well.

    I reported both of these bugs to NI using their support form - hopefully they will be recognized and fixed in the next update.
     
Thread Status:
Not open for further replies.