Question for Kontakt Users

Hi. I'm now using X1 255 with the latest Kontakt and have this odd symptom.

When loading Kontakt into a track for the first time each session, and attempting to load an instrument, the process stalls and I get "Please re-save the currently loaded patch to speed up loading times". It does eventually load after a minute or so - but wont accept MIDI.

If I crash out of this process (or wait and then and restart), everything works as it should be till I reboot next time. Old projects created on Sonar 8.3 load without issue and do saved X1 projects. So it's always only the first load into my Normal.tmp each time I reboot.

Now, while the instruction is self explanatory, I have thousands of samples that would need re-saving.
Any thoughts?
Thanks CC

P.S. This does not happen if I use the same Kontakt in Sonar 8.3.1 on the same system.

LOL. No, been legit since DOS4.5 :-)
Well it's happening in X1 32 & 64 bit. Not in earlier versions.
The paths are all the same and have been scanned & updated. It's the fact that it only occurs once after boot up that has me mystified. All versions are scanning the same VST location.
Thanks
FS
BTW saving and re-opening per instruction, only has the effect of removing the instruction.

Strange. It sounds like the Kontakt4 proprietary lossless compression format thing where it re-saves the patch and then can do speedy-background loading. I don't know a lot about it since I'm still on 3.5 but I'm wondering if something is causing it to do that every time? And, of course, odd that it's not happening under 8.5... huh. 

sorry, no brilliant insights... probably not helpful but if I see anything similar I'll let you know!

Fearful Symmetry


OK. Latest.
If I load an instance of Kontakt into my normal.cwt, save, and then boot into that, the above problems don't occur.  Only if I load Sonar and then try and fire-up Kontakt do things fall over.
Curiouser and curiouser

I'll try the Kontakt forum too.
Cheers & thanks
FS

Seriously?! What the hell! That makes less sense than before! I wonder if NI has support that might shed some insight. 

Jim. It's 4.2.3 they've just released. Yes I have this: This could be the problem.
Thanks

Fearful Symmetry


Hi. I'm now using X1 255 with the latest Kontakt and have this odd symptom.

When loading Kontakt into a track for the first time each session, and attempting to load an instrument, the process stalls and I get "Please re-save the currently loaded patch to speed up loading times". It does eventually load after a minute or so - but wont accept MIDI.

If I crash out of this process (or wait and then and restart), everything works as it should be till I reboot next time. Old projects created on Sonar 8.3 load without issue and do saved X1 projects. So it's always only the first load into my Normal.tmp each time I reboot.

Now, while the instruction is self explanatory, I have thousands of samples that would need re-saving.
Any thoughts?
Thanks CC

P.S. This does not happen if I use the same Kontakt in Sonar 8.3.1 on the same system.

Fearful, JXM said exactly what I was going to tell you here. I wanted to explain it a bit better though in case he may have lost you. The error you're getting comes from when you first upgrade Kontakt and use it for the first time. It has a quick load feature for all the sounds you run in it. When it tells you to "resave" it doesn't mean your Sonar project....it means just select your sounds/samples and save them with the same name. There is a bulk method to do this that takes about a minute or two in your Kontakt options. Allow it to resave all your libraries of sounds and you will no longer get this error. You'll also notice that load times will be cut in half and the module will work perfectly before all the sounds are completely loaded up.
 
Now, if you are having an issue with Kontakt freezing or acting weird inside of Sonar X1, I have that same problem and for the life of me, I can't figure it out. I believe my issue to be somewhere within my templates I've saved. This does not happen in 8.5, but happens religiously in X1. Not that this is anything like your issue, but just for your head...here's mine and it only happens with Kontakt....and yes, I have the latest updated version.
 
If I load an instrument template of drums using Kontakt while the project is already started, it loads up, starts creating my tracks down the pane and when it hits the last one, X1 shuts down completely to my desk top. No warning, no option to save, just a complete shut down. If I load this same instrument template FIRST before I even start my project, it loads perfectly without a problem. That's the only issue I religiously can reproduce with Kontakt and X1. Maybe it's the template I'm using with the plugins that are included in it clashing with plugs that are already in the project....I have no idea. That's something I need to try. But anyway, do what JXM and I have mentioned to you about resaving your samples in Kontakt and see if it helps your problem any. Good luck!

If I load an instrument template of drums using Kontakt while the project is already started, it loads up, starts creating my tracks down the pane and when it hits the last one, X1 shuts down completely to my desk top. No warning, no option to save, just a complete shut down. If I load this same instrument template FIRST before I even start my project, it loads perfectly without a problem. That's the only issue I religiously can reproduce with Kontakt and X1. Maybe it's the template I'm using with the plugins that are included in it clashing with plugs that are already in the project....I have no idea. That's something I need to try. But anyway, do what JXM and I have mentioned to you about resaving your samples in Kontakt and see if it helps your problem any. Good luck!

 
I suspect Kontakt 4.23 might be just a little flakey...  
I was auditioning the Neil Peart kit and some of our libraries recently... and it bombed X1.
I don't recall this issue happening with 4.22
In fact, I just heard from a ProTools  9 user having a similar issue with Kontakt 4.23.

Jim Roseberry

If I load an instrument template of drums using Kontakt while the project is already started, it loads up, starts creating my tracks down the pane and when it hits the last one, X1 shuts down completely to my desk top. No warning, no option to save, just a complete shut down. If I load this same instrument template FIRST before I even start my project, it loads perfectly without a problem. That's the only issue I religiously can reproduce with Kontakt and X1. Maybe it's the template I'm using with the plugins that are included in it clashing with plugs that are already in the project....I have no idea. That's something I need to try. But anyway, do what JXM and I have mentioned to you about resaving your samples in Kontakt and see if it helps your problem any. Good luck!

 
I suspect Kontakt 4.23 might be just a little flakey...  
I was auditioning the Neil Peart kit and some of our libraries recently... and it bombed X1.
I don't recall this issue happening with 4.22
In fact, I just heard from a ProTools  9 user having a similar issue with Kontakt 4.23.

Hi Jim...I'm curious, when it bombed X1, what did it do? Did you ever get that total shut down to where it brings you to your desk top? To be honest, that's the only crash I get from X1. Other than freakin' Kontakt, it's been super stable for me....if only I could get used to X1.

Damn! I'm not sure if should feel embarrassed or not about yesterday's batch of issues but I believe I've found the problem and it was not where I was looking. It appears that my Normal.cwt boot-up template had become corrupted in some strange way. I cottoned-on to this through another issue with effects. I scrapped the template, rebuilt it, and all the other issues appear to have disappeared. I can now flick between 32 and 64 bit with gay abandon (as they used to say) and Kontakt behaves as it should. Oh Mother -  will this interminable tweaking ever end?
FS :-)

BTW, Thanks for the suggestion to re-save the Kontakt library. It's worked wonders re loading times. Very elegant, this background loading!

Fearful Symmetry


Damn! I'm not sure if should feel embarrassed or not about yesterday's batch of issues but I believe I've found the problem and it was not where I was looking. It appears that my Normal.cwt boot-up template had become corrupted in some strange way. I cottoned-on to this through another issue with effects. I scrapped the template, rebuilt it, and all the other issues appear to have disappeared. I can now flick between 32 and 64 bit with gay abandon (as they used to say) and Kontakt behaves as it should. Oh Mother -  will this interminable tweaking ever end?
FS :-)

BTW, Thanks for the suggestion to re-save the Kontakt library. It's worked wonders re loading times. Very elegant, this background loading!

Don't ever feel embarrassed, Fearful. If posting on here allows you to vent your frustrations and in turn resolves the problem, the forum served its purpose brother. :) You know, I meant to post the details of a new template also in my first post to you but I completely forgot about that. I DID have issues with old Sonar templates wreaking havoc in X1 and rebuilding them from the ground up fixed just about all my issues except for Kontakt. I'm just glad you sorted out your problem...well done. :)
 
That said, I did find out what my issue is. If the plugs loaded in my Kontakt instrument template are already in place within a project, it chokes up because they are already present. I deleted all plugs on the drum template and it loads up fine now. It's still strange that this doesn't happen in 8.5, but heck, if loading it up without plugs during a project in session is the fix, that's fine by me. The other alternative is to load the template WITH my plugs before I start a project.
 
Jim: Thanks for the info....I was just curious how your crash was going down. I never see any white screens on this end...just a total disappearance of X1 and back to my desktop in like less than a second. I got it under control now though. Something in my UAD arsenal was trying to duplicate itself on a bus so killing the plugs in the template solved the problem.