Kore 1.0.3 Buglist

I'm sorry I haven't posted in this thread for a while- the real job interfered (I've been working mandatory overtime since May, and the real crunch time has been the last month- thank God it's over). I'll read through everything here and give what answers I can; the rest I'll pass on to someone who hopefully can answer.

ew

 

Try resampling them at 24 bits and see if you still have the problem- the present KORE driver isn't fond of 16 bit material.

ew

 

After updating to v. 1.0.3, Kore will no longer initilize in Acid Pro 6b (it hangs the program indefinately). Did a system restore to original drivers and it works perfectly.

 

Hi there,

Well at least you guys have been able to actually run Kore !!

Following what can only be described as "The authorisation from Hell" which took 2 weeks, I load Kore and it just hangs usually while scanning the Absynth plug in but it has got further.

I know about the deleting the 2 files and rescanning the plugs but the app just comes up not responding in task manager.

I've now uninstalled it as it also screwed all my FXpansion wrapped plug ins with Pro Tools.

Anyone "Share my pain" and has been here before ?

Is there a solution ?

Cheers

Lizardpoint

 

My Kore crashes every time i load it up! Ive tried everything and it just wont work???

I run Logic 7 on a G5, ive never had any issues with any of my other gear except this pretty little paper weight Pointless isnt it!

 

I took mine back for a refund.

I wouldnt bother trying to make it work 100% until Ver.1.1

figure out the limitations then contact the store and get them to go through it with you.

AND

Dont let anyone make you feel like you are crazy because they are unable to fix it.

OR

Wait for Version 1.1

 

They reckon i might have a faulty unit??

We will see!

 

Hello

I already posted this in another thread...

I also have problems with kore crashing in Cubase SX 3. In standalone mode everything seems to be fine so far.

I'm using the latest version of kore (1.0.3) and SX 3.

I just took some time and tried to narrow down when exactly kore seems to have problems.

Thats what I found out, maybe someone can try to reproduce this.

No1:
- I open up Cubase, start a new empty project, navigate to the vst instruments window and open my first instance of kore everything works fine for me in nearly all cases.

- Now I can open up a second instance of kore or as many instances of kore as I want and close them again, everything is fine as long as at least one instance of kore stays opened.

- When I close down all instances of kore from the VST instruments window and want to open up a new one Cubase cashes all the time!

- It makes no difference how many instances of kore I've opened up before or in which cells of the VST instrument window they where placed or in which order they have been closed down. Whenever I close down the last instance of kore I cannot open kore again or cubase crashes.

No2:

- I also found out that kore crashes when there is another VST intrument opened up before you open the first instance of kore

- I start a new and empty Cubase projekt, open up any VST instrument, after that I try to open kore but it always leads to a crash.

- When you open up kore in the first place, and any other vst instrument after that, there is no problem, even if you open a second kore instance after opening up 1 or more other VSTs.

No3:

- Loadning an existing Cubase project including Kore doesn't allways work. When trying to load the Kore plug in Cubase hangs sometimes

Somehow kore tries to demand beeing the first plug in opened up in Cubase and also gets really pissed once you close down all instances of it.

Can anybody approve this?

Martin

 

Glad to report that this bug has been fixed with the 1.10 update.

 

Sorry if this has already been reported - really couldn't be bothered to scroll through 4 pages of bug reports:

When using Massive inside of Kore, and using the Massive browser to explore synth patches rather than the Kore browser, the mappings of the 8 control knobs to the macro controls of the newly selected patch never really seems to work properly, as the knob assignments still seem to reflect those of the first selected patch.

 

Ive got the Komplete 4 and Kore.
And it just dont work.
So Ive decided to sell it all - This is to much hazzle.
This matter just drained me.
I got this package NOT having to spend time on TECH but
to be focused on my MUSIC in the first place.
And now its worse times 10.

Maybe I will keep Guitar Rig 2, its nice when it doesnt crash.

Running Protools HD2 on 7.3, Dual G5 2.5 PowerMac, 4 GB RAM, OSX 10.4.8

 

Uhhhhhh, have you updated Kore to 1.1? Updated the K4 apps? I find it hard to believe it "just dont work"

 

I believe "It just dont work".


Try the updates.


If the shop cannot get it working for you,
GET A REFUND.

Give it back to them.
Ask for a receipt of return.
Then It is CLEAR that It Is THEIR problem.

That will end up a lot quicker and cheaper than selling it yourself.


But do try the updates first.