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

KONTAKT 4.2.2: loading of libraries slow again!

Discussion in 'KONTAKT' started by PaetzoldR, Feb 23, 2011.

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

    PaetzoldR New Member

    Messages:
    8
    I have installed the KONTAKT 4.2.2 and matching Factory library update.

    To my utter dismay, the loading of large libraries has slowed down again to where it was before the KONTAKT 4.1.3 update which introduced background loading.

    This happens both with Factory [e.g. VSL] and 3rd Party [e.g. Steven Slate Drums, Lyrical Direct] libraries.

    This is not what I expected from an update that promises "increased saving/loading performance"...

    Also, I had a crash in Cockos Reaper 3.75 during the loading of a large library (something I never had with previous versions!).

    Can anybody shed a light on this?

    Machine specs: i7, 6 GB RAM, Windows 7 64bit, Reaper 3.75 64bit

    Thanks,

    PaetzoldR
     
  2. EvilDragon

    EvilDragon Well-Known Member

    Messages:
    19,938
    The loading speed updates are most obviuos on the really big libraries with NKIs referencing many thousands of sounds. For example, Cinesamples VOXOS.
     
  3. PaetzoldR

    PaetzoldR New Member

    Messages:
    8
    Hi ED,

    as a fellow Reaperite, I should have expected you're lurking here as well ;-)

    The problem is that in 4.1.3, even big libaries [e.g. Steven Slate Drums, Lyrical Direct] finished "loading" in next to no time (the window indicating the loading process would pop up for less than a second for each library).

    Now with 4.2.2, I am back to where I was before 4.1.3: I can watch whole lengthy lists of samples being loaded, which is taking several seconds for each instrument.

    I have a Reaper project with Steven Slate Drums, Lyrical Direct gutar and Dan Dean basses that used to load in 3 seconds in 4.1.3. With 4.2.2 it's back to nearly half a minute.

    It seems like something has broken the background loading process.

    PaetzoldR
     
  4. EvilDragon

    EvilDragon Well-Known Member

    Messages:
    19,938
    Did you try to resave the patches again?
     
  5. kb123

    kb123 NI Product Owner

    Messages:
    1,255
    Can't say I'm 100% happy with it either. In previous versions, there used to be visual feedback that kontakt was loading samples, now, on the first load of a large instrument, it just hangs there until the load is complete
     
  6. PaetzoldR

    PaetzoldR New Member

    Messages:
    8
    No, but will try and report.

    The strange thing is that internal libraries (e.g. VSL) are slow as well, although the installation process seems to have run some sort of conversion process on them.

    BTW, is resaving something I have stupidly missed and should have done anyway, or just a guess?

    Thanks,

    PaetzoldR
     
  7. EvilDragon

    EvilDragon Well-Known Member

    Messages:
    19,938
    Resaving enables backgrund loading for NKIs. Of course, you need to have background loading enabled in Options.
     
  8. musos

    musos NI Product Owner

    Messages:
    395
    Just for clarity:
    Are you saying that ALL patches in Kontakt need to be re-saved? If so, how does one accomplish such a task in less than a few days?
     
  9. EvilDragon

    EvilDragon Well-Known Member

    Messages:
    19,938
    Only those files that were created pre-version 4.1 need to be resaved. Kontakt has a batch re-save function (click the Files icon, you'll see it) for such cases.
     
  10. PaetzoldR

    PaetzoldR New Member

    Messages:
    8
    Well -

    it seems that batch re-saving did the trick (thanks, Evil Dragon) and background loading works again. It is not noticeably faster than in 4.1.x, though (mainly because there was little room for improvement anyway).

    Which makes me wonder whether anyone got the factory libraries to load in the background _without_ resaving?

    Thankfully, as kb123 pointed out above, there is now a surefire way of determining whether background loading is being used: if it is, no list of components scrolls by in the status window that pops up.

    PaetzoldR
     
Thread Status:
Not open for further replies.