KORE 1.0.2 bug list

Re: KORE 1.02 update

I did the same. It works fine in the first slot. Cubase SX will hang up, when it is in a different slot. Don´t know why.

Quote edited:
Well, now I must say: As long as I don´t load samplebased sounds. If I load a Koreinstrument like Kontakt it will hang up.

 

Re: KORE 1.02 bug list

Windows XP freezes after 30 - 120 mins when Kore is loaded in Nuendo/Cubase SX. No matter if you load it in VSTi Slot 1 or another. After that I´m not able to shut Windows down. The only solution is a very dangerous RESET. Nice !

Please release an update ASAP !

 

Re: KORE 1.02 bug list

Does this only happen when Kore crashed before, or also when you just start and close the Kore standalone version? Btw. it's just a message target for the windows message that a new usb-hardware gots connected/disconnected (and should be closed together with kore).

Best regards,
Steffen (NI, Berlin)

 

Re: KORE 1.02 bug list

Hi Steffen
No
The NI Helper Window only was visible and a problem after I had installed and tried to use the Kore v1.0.2 plugin in Cubase. After the plugin had hung Cubase I had a problem closing Win XP because the NI Helper Window was still active. After one or two times of problems with v1.0.2 plugin I removed it and re-installed the v1.0.1 plugin only. Now WIN XP shuts down fine.

The standalone version of Kore v1.0.2 is absolutely fine so far and not causing any problems.

But mostly I have been using Kore as a plugin within Cubase and I was looking forward to the extra funcionality of v1.0.2
Now I'm looking forward v1.0.3 or even v1.1.0 (!)
Thanks
Volker

ps I should add that the problem I had with the v1.0.2 plugin was not that another instrument wouldn't work as many people have had a problem - no, I could not get the Kore plugin itself to load into the VST rack in Cubase - it simply would not load and Cubase would hang: "not Responding".
Cheers

 

Re: KORE 1.02 bug list

Exactly the same scenario on my system.
I also wondered about NI-helper.

greets, W

 

Re: KORE 1.02 bug list

I'm still getting very glitchy sound from the Kore controller audio at all times (running on a PC laptop with more than enough resources) - even at higher latency settings.

Additionally, complex patches using @35% and above CPU click, pop and scratch like nobodies business (again even at higher latency settings).

Finally, when using an Echo Indigo I/O instead for output, still get clicks, pops and scratches when attempting to manipulate any sounds with the Kore controller with a 35%ish or above CPU load.

The laptop usually deals very well with high CPU loads - seems the Kore controller is interfering with audio pretty much whatever I do - until I unplug it ....

 

Re: KORE 1.02 bug list

Hi,

You could try useing your echo card for audio with the Kore latency set to the lowest value possible. Does this help?

The reason for this is that higher latency settings in the Kore driver increase dpc latency on the system and can cause problems with other drivers.

See http://www.thesycon.de/deu/latency_check.shtml

Cheers

Andy

 

Re: KORE 1.02 bug list

Cheers for the tips - will have a go!

 

Re: KORE 1.02 bug list

Nope - still no joy. Also, I'm not sure how/if changing latency settings on Kore controller has any effect if I've assigned audio output to my Echo Indigo I/O anyway?

The problem seems to me to be a combination of driver issues, and inherent problems in the controller itself.

 

Re: KORE 1.02 bug list

Hi,

If you go to the site I posted you can read about DPC and there is a little app you can use to see the impact of the Kore driver on your machine.

Any driver that increases the DPC on your machine can cause other drivers (such as the echo driver) to miss some of their data, this causes dropouts, crackles etc.

Cheers

Andy

 

Re: KORE 1.02 bug list

Hi Andy,

Thanks for the Latency checker link. Latency Checker says I have problems (see attached) - just with KORE plugged in! Not even using it.
Nice...anybody do C any more?

Craig

 

Re: KORE 1.02 bug list

Hi C-Note,

I have attached two pictures showing the tool on my computer. The first picture shows the tool with no Kore Controller attached, the second shows it while the Kore Controller is used by Reaktor 5 using about 70% of my computer power. The latency I have set is: USB latency=1ms, audio latency=4ms. This computer is far from being optimized and I had several programs open while taking the screenshots (Mozilla, Thunderbird, AIM, WordPad, Paint Shop Pro for taking the screenshot, Adobe Framemaker and the latency checker itself). I have not seen a technical support request by you yet. We can provide you with some possible reasons for the results on your computer. Please fill out the support form as complete as possible when you send us a request. If you use a laptop, please give us the eact model name so that we can have a look at the components used in the model.

 

Re: KORE 1.02 bug list

I have been playing around with plugin-versions 1.0.1 (A) and 1.0.2 (B).

I discovered the following:

A works fine.
Deleting A and copying B to the Vst-plugin folder and then starting Cubase makes Kore WORK!! in Cubase vst-rack.
Closing Cubase and restarting it makes Kore NOT working: cubase freezes again when trying to add Kore in Vst-rack.

Copying A to Vst-plugin folder and then starting Cubase makes Kore work again.

Copying B to Vst-plugin folder and then starting Cubase makes Kore 1.0.2 work again !!!

So after forcing Cubase to rescan Kore at startup it can be used once. After closing Cubase it does not work anymore.

I also noticed, that closing Cubase (with Kore in it) does not end the Cubase process (as seen in task manager)

Killing the Cubase process manually does not cure the problem with cubase freezing after a restart and trying to add Kore to the VST-rack.

 

hypersonic 2 not load in kore

The title says it all!

 

Re: KORE 1.02 bug list

It gets worst!!!! Mac, G5, 1,5GB RAM, 2.3Ghz....
I load Kore in standalone and the sound is totally crackled, and of course I made the latest updates.
What is it?????

 

Re: KORE 1.02 bug list

Hey Andy,

Tried the DPC checker - couldn't really find any specific issues - that is, whether Kore controller was connected or not I would randomly get 'red spikes' that suggested there were problem drivers. Enabled & disabled pretty much everything with no luck in identifying any particular issues.

Strange thing is, I get 'red spikes' when operating as normal running other NI standalone synths - but no evident clicks or pops, or any other problems similar to those I get using Kore.

By the way, just to clarify - when setting 'USB latency' for the Kore controller as mentioned above - I assume this means in the settings dialogue that you set this when the Kore Controller was selected as the soundcard - and then choose the actual soundcard used for audio, and then set latency for this?

I'm confused - I wouldn't have thought that this would affect the Kore Controller's USB latency one way or another - and that the latency setting is for the audio elements of the controller alone - not for the speed of USB communication between the controller and the various parameters it controls in Kore sounds? Am I being dumb here?? Are these settings the same?

 

Re: KORE 1.02 bug list

Hi Marius,

Thanks for the quick reply. I didn't know I had a problem with latency until the checker told me. I don't use KORE audio and my soundcard latency is 11 ms. Where do I set the USB latency?

Regards,

Craig

 

Re: KORE 1.02 bug list

With my old Notebook (Fujitsu Siemens Amilo A 1650 G) the sound was terrible noisy and crackling: Chipset ATI RS480, Graphic ATI X200M shared !

Now my Notebook is the Amilo A 1667 G with ATI X700 externel Graphicpower and VIA-Chipset; it sounds much better.

With driver 1.01 sometimes the sound noisy for a short moment (2ms i.e.). With driver 1.02 it's clean, but after 1-2 minutes sometimes there's a short dropout, so my firewire audio-interface TASCAM FW 1884, too.
Latency 4ms / 8ms

 

Re: KORE 1.02 bug list

Hi Warlock
Yes this duplicates my experience exactly.
Some kind of process remains open and makes a mess after using the 1.0.2 plugin the first time in Cubase and then you can't use it any more - Cubase hangs.
Something related to the mysterious NI Helper Window?
Cheers
Volker

 

Re: KORE 1.02 bug list

Hi C-Note,

You readings without Kore are very bad 1748us is alot you really need less than 500us, my system reads between 50us and 70us without Kore.

Connecting Kore adds around 1200us on your sytem this is also a huge amount of time.

I would say you have a problem with your machine of some kind.

I would take up Marius offer and send the details of your machine to support so they can help you.

All the best

Andy