Kore Player in Protools 8

Every time I open an instance of Kore I get the error message -

"Lost communication with the audio interface. Please try increasing the hardware buffer size, or removing some plug ins, and make sure you have a valid clock source."

When I press ok, the spinning beach ball spins for a few seconds, then the firewire light on the 002 goes off and on and the sample rate light does the same, and then everything is ok.

This happens even when the buffer is set to 1024.
It also happens when I open a session with an instance of Kore in it.
Even when Kore is the only plug in in a session.

I called NI, and they weren't any help.

Anyone else experiencing this?

Thanks -

 

Same here!

I'm on PTLE 8.0.4 and having the same problem with Kore 2. Stand alone runs great. Logic 9.1.1 using built in line out will run Kore 2 at a buffer setting of 128 and up. Anything less and you get bowl crackly pops. What's up? The Kore player was a CPU hog but at least it would work in PTLE. I wish you could use rewire with Kontakt 4 and Kore 2. I guess I will try Reaper next!

 

http://www.native-instruments.com/k...e+of+NATIVE+INSTRUMENTS+plug-ins+in+Pro+Tools

ew

 

Already optimized

Thanks ew, but I have already optimized. I have been using the Komplete bundle since version 5. I am able to run almost all of your VIs at a buffer of 32 or 64 samples in Pro Tools LE including the Kore PLayer. I just picked up Kore 2 with the controller and the troubles started. Sometimes I can change my settings and get kore 2 to function at 64 Samples, other times when I change my buffer PTLE just crashes. The heart of problem is when I instantiate the Kore 2 plug-in or open a session with the plug-in already on a track. That is when I loose my connection and get the warning message. If I am able to change my settings and reconnect to my 003R, kore 2 runs really well at buffers as low as 64 Samples. I'm really not sure what the problem is. :S I have ditched my prefs and removed all older versions of plug-ins such as Absynth 4, Akoustic Piano, B4 II, Elektrik Keys, Kontakt 3 and Pro-53. Any other ideas?

 

Update with workaround!

If I use Kore 2 on an Instrument track I have problems. So I tried the old school way with a midi track and an Aux. It works without a the disconnect problem! So if you are having trouble try it out. EW, do you think this is a PTLE version problem or just another RTAS glitch?
---
It was a fluke! It is still doing it with the workaround. I though I had it!

 

This seems to work for now!

I checked the "ignore errors during playback/record" under the playback engine and now my sessions will open correctly without crashing. I can add and remove the Kore 2 plug-in without a problem at any buffer size. I wonder about what kind of errors Kore 2 is producing. Especially with regard to the clock loss. :S

 

I will give this a try, I am having strange problems with Kore 2 also.

I even upgraded from Vista to Win 7 (needed it anyway), reloaded Protools, and reloaded all NI products, the kore 2 strangeness keeps showing up in different ways.

I will update my findings after a trial or two.

 

ignore errors during playback/record setting Kore2 and PT

I would say that >> checking the "ignore errors during playback/record" under the playback engine << is on to something with Kore 2 and PT locking.

I would say that just toggling and saving the settings window (Ignore "on to off" to "on again" OR "off to on" then to "off" again and saving the form does wonders for me.

If I have pops and clicks that do not leave regardless of "buffer size" and "RTAS processors" settings used - just changing and saving form after toggling the ignore errors seems to help the software stablilty.

If you open up PT blank and change the "ignore errors during playback/record" setting - save - then open up PT files seem to help problem files.

I am wondering if the prefs file settings are not writing or saving correctly in some cases without the toggle (one way or the other)

 

Kore Player and Kore 2 in Pro tools LE 8+

Well after weeks of trial and error - I can truly say I found a problem and a work around with Pro Tools crashing when I use Kore or Kore 2

These lock up problems were on pro tools le 8, 8.0.2, and 8.0.3 (I tried 8.0.4 but gave up and fell back to 8.0.3cs2 in combination with Kore and Kore 2 V 2.1.2

Protools was not letting go of Kore when a file was closed. So for a fresh start of pro tools Kore loaded fine, close the file and open up another file with kore and your locked - full system lock, had to hit the power button.

This was happening on Win Vista 32 bit. I even went to Win 7 32 bit and fully loaded the OS , PT and Komplete and Kore - the problem did not dissapear.

Pro Tools was not letting go of Kore. So the only workaround is to close down pro tools and restart every time I want to change files.

Its a pain - but I can get back to work.

NI and AVID - you need to TALK.

 

Same same...

Kore Player, PT 8.0.4cs2, Win7 64. Just bought a soundpack, money wasted. Very unresponsible by NI to ignore a obvious problem....

Another workaround is to install VST only and wrap with FXpansion but then you can only use one instance of Kore Player.

 

My problems with Kore Player continue. I own Komplete 7 and love it, but Kore is very troublesome in Protools 8. Continued errors and a real cpu hog. I run sessions with 2 or 3 intances of Kontakt + a couple intances of Absynth + Battery, Omnishere, Trillian... no problem. On the other hand, I have a session with 1 instance of KorePlayer and 1 Absynth and it's a problem. Kore cripples the system.

Koreplayer is free, but I have spent quite a bit of money on Soundpacks. I don't use them very often because I don't want to deal with the errors and choking and crashes.

Can anybody say wether Kore 2 (full version) works better than the player in Protools (Mac). I've thought of buying it, but I'm very hesitant.

Thanks

 

I have moved on to PT 9 and Kore 2 is still a cpu hog. I am running a 3.2 Ghz 8-Core Mac Pro and it doesn't bother me so much. On my Macbook Pro it is more of an issue. However, it doesn't crash as long as I use "ignore errors during playback/record". I can say that the power of Kore 2 is amazing. Being able to host AU and VST plugins in ProTools is great. No more " I wish that was available in RTAS" envy. I have Komplete 7 and being able to open and edit patches is nice. Not to mention a single place to search for "that" sound, you know the one you were playing with the other night and now can't remember which NI VI it was! I like turning knobs, so I got the controller and it works flawlessly. I hope that helps a little.

 

Thanks Andy - I'm using a duel 2.8 (8 core) macpro. It's very powerful. I have very few problems with VI's, except for Kore Player. Kore 2 looks like a great tool, but like I said, until I see Kore Player working efficiently, I will not take the chance.

I've seen a lot of discussion on this topic, but not a word from NI. That's unfortunate as I have a great respect for them and their products.

Thanks for the input -

 

Kore Player and Kore 2 have the same problems in 8.0.4 and up ProTools on PC for me.

The only way I can use Kore is to disable all of my other plug ins and tracks - write the Kore track to audio, then disable Kore, activate the rest of tracks and continue working. I have turned in a ticket on this.

 

I'm having the same problem.

PC with Win7 64-bit, Core i7, 6GB RAM
Pro Tools LE 8.0.4 cs2
Kore Player Free version 2.1.2 (R8232), this is the latest according to Service Center.

Although I don't get an error message, probably 80% of the time my sessions do not load... it just hangs... then the mouse pointer freezes. Then I have to reset my computer to get out of it.

Any ideas for resolution would be VERY appreciated.

 

In the past - I was able to have 10+ Kore or Kore 2 plugins - then one fine week - after some upgrade (Windows, NI or PT) things started falling apart. This is what I did to open, clean and get the songs back to a usable state. NOTE I can use Kore and Kore 2 again (just not as many all at once).

To open a file with Kore used as a plugin, that crashes or will not open:

1) move the Kore plugin out of the Protools plugin folder to your desktop.

2) Open protools song file BY double clicking on the song file name (do not have PT up first) this will bring up file with all of Kore disabled. Save file and close song first. Wait a minute then close PT.

3) Put the KORE plugin (on your desktop) back into the protools plugin folder.

4) Open protools song file BY double clicking on the song file name again. NOTE if it does not open, you most likely will need to delete your PT prefs and start #4 again. Once PT song file opens put up a system resources window up and learn to read the CPU usage bar (it can tell you when too much of the system is being used, if you get 60+ CPU usage - look out) NOW one by one reactivate the Kore plugins and do a Kore reduction campain - bounce to audio - and if you have Komplete - open the patch in Kore 2 - save patch, close and remove Kore 2 and replace with instrument that kore called up, like Massive etc. and load saved patch (with much less cpu usage).

5) Try to reduce CPU usage by bouncing finished tracks to an audio track (then deactivating Kore track) or deactivating some unused plugins or changing the buffer settings to pull less on the CPU and more on the discs.

6) if you can get into the habit of deactivating Kore before the final save and close of your session - it will help out a lot next time you open PT/Kore again. I also now deactivate ANY plugin thats a cpu hog (like Ozone4).

When you watch Kore being activated on a PT file while looking at the CPU usage - you can see why it is hard on the system - I get full TILT 100% orange to RED cpu bar readings when opening Kore, all the other plugins from NI and AVID/Digidesign hardly move the cpu bar at all.

Until NI, Avid figure this out, my days of leaving kore plugins enabled all the time are over.

If I have not completely covered your issue - post again - and I can give you more tips (getting to be a pro at opening stubborn older files now)

 

Thanks for the advice! I'll give those a shot.
One workaround I've found is one that you mentioned, was to inactivate the track before closing, then activating it after it's loaded.