Kore 1.1

Hi ppl ive installed the kore 1.1 update today but now i can't get any sounds to play at all. Has anybody else had this problem? I'm using FL studio 6

 

Hi,

I didn't see your post there. I just posted a similar problem in the sticky thread about the release of Kore 1.1. I can't get any sound either and for some reason the cpu usage is between 20 and 100 percent, even with the all the single sounds. Most of the time it just crashes because the cpu can't take the load (I think). Don't know what I can do about it though.

cheers

 

im running into the same cpu issues on my mac.(dual 2kgig.2.5megs of ram.osx.4.8) Its crawling...even with nothing loaded. i also updated to komplete 4. i can get it to play..just make sure your controller is turned on in the midi panel...it reset my preferences when i updated.The cpu thing is a big problem though.I've rebuilt the datbase (some plug ins are still greyed out) and now im rescanning my plugins.Nothing seems to be helping.
M

 

Same here. Kore 1.1 does not work in FL. Any sound I try to load, the CPU goes into red.

Shame on an otherwise awesome update...

 

All I can say is try rebuilding your database again; KORE's very touchy until the database is properly rebuilt.

It's going to take time as well. Here's how I'd do it;

First of all, rescan your plugins. For this I'd check the box for rescan at startup. Restart KORE (in standalone) and let it scan your plugins.

After your plugin folder's been rescanned, rebuild your database. When the database rebuild window comes up, choose to let it scan in the background. On my machine, a full database rebuild will take an hour and a half; if you try to exit KORE before the rebuild's done, you'll get a warning to the effect that the rebuild's not done. Don't quit KORE until it's done.

After that's (finally) done, exit KORE, reboot your machine and start your host. Have it rescan ITS plugins. See if that works.

ew

 

Thanks for the suggestions - didn't work for me though. The CPU load may have gone down a bit, but Kore still refuses to make any sound in FL Studio.

The standalone Kore works fine, and I have no problem getting other synths to play in FL. Also, Kore in Cubase4 - no probs.

Heeeelp!

 

Are you using the DXi or VST version in FL?

ew

 

VST. Haven't thought about that, I will try DXI. Normally, though, VST is the better option.

 

Tried the DXI. Didn't work. Kore still makes no sound.

 

Have you tried rescanning your plugins?

Otherwise, I'd probably ask Gol if I were you. I'm not a FL user, so I can't give any solid reasons as to why this would be happening.

ew

 

Yeah, I'll head on over to the FL forum and try that. (Yes, I did rescan my plugins and Kore db). Hope there's a solution.

 

Has this issue been resolved by imageline ?

I as well am using Fl studio 6 (Producer) , and now cannot use Kore at all. It produces no sound no matter what audio settings, and no matter if rebuilding/rescanning pluggins.

Fl studio works perfectly with every other VST i own.

Kore 1.0 worked perfectly in Fl studio 6. NI should not have released an update of this that breaks the plugin. The plugin should still meet all VST standards and work in ANY vst compatible host.

I am expecting NI to release a fix for this ASAP.

 

Please note something interesting:

Kore works fine in the stand-alone program, Chainer.

But when Kore is running from within Chainer, that is within FL-studio, the same issue occurs - no sound. (or very slight pops here and there)

This is regardless of the VSTI loaded up in Kore, and regardless of the audio settings of FL.

 

I'm wondering if it's a variant of the ReWire issue that affected KORE before. While KORE doesn't have ReWire itself, for some reason it acts strangely if ReWire's implemented in a manner not strictly to the Props idea of how it should be in either another plugin on the machine or in the host itself.

Do you have any ReWire apps besides FL?

ew

 

That's a good point. I'll double-check to see if i have any Rewire applications in use.

Also one possible solution that i haven't tried yet would be to use FX Teleport to run Kore on a separate machine than FL.

I thought perhaps placing Kore within Chainer (or FXT) woud resolve the issue, but it does sound like there is a resource conflict between Kore and FL, or something else tying up the audio stream such as a Rewire App.

 

I wrote to Gol (FL) and Henning (NI) a while ago; they're looking into it.

ew

 

Thanks for the update, and for reporting this to imageline.

BTW:
I'm not running any other audio apps other than FL & Kore, and one vsti at a time. I tried this also on a completely different machine as well, and with FL 6.0 and FL 6.4 (beta)

Even within KORE (loaded in FL 6), KORE's audio outputs, plugin out, or master shows no audio levels being emitted from the plugins, but there are occasional audio pops if you play with the instrument enough.

 

Thank you ew!

cline.michael: I've also tried FL6 and the new BETA, as well as FL4 and two separate computers - same problem in all cases.

 

Have there been any updates on this one?

-----------------------
I have also just tried running Kore 1.1 installed on a separate computer via FX-Teleport with Fl-studio 6 on the main computer.

Same issue. Kore plays no sound on the 2nd computer.

I also tried Sytrus Vsti running on the 2nd comp via Fx-Teleport, and it works perfectly.

I then tried Sytrus Vsti loaded up in Kore 1.1 running via Fx-teleport, and no sound was produced, even using Sytrus's built in keyboard.

This is obviously a communication problem between Kore 1.1 and Fl-studio.

 

Just some more information:

If i load Kore 1.1 in fl-studio, then proceed to load 2-Stepper Kick (Absynth 3), after a few seconds, Kore's cpu meter goes up rapidly past 200%, then gives an error message stating the cpu is overloaded and audio processing has been shut-off.

This sounds like the crux of the issue, or at least a definite side-effect.

Also due to the other posted cpu problem posts with Kore 1.1, I would say there may be a larger underlying problem with this software update.

For now i am going to simply uninstall 1.1 and go back to the previous release. Sad for me because i was looking forward to using the software without the controller. Once another update comes out, i'll try this again.