Korg Forums

This is a repeatable problem - and only occurs when using the Editor. As has been suggested it's perhaps not designed to be used with the Editor as a plugin - all other setups work perfectly - only the Kronos Editor screws it up.

It's a shame but there it is - just the way it seems to be

OK I see - that's interesting - seems a little perverse, but I guess that's fine. But I am at the moment left wondering somewhat.. "what is the point of the Kronos Editor? Does it really give a project any added value over just track-laying a bunch of ext. instruments?" Is there in that case a ...

No I'm afraid that doesn't help..

No I'm afraid that's not the answer

- as posted elsewhere it is now known only to occur if the Kronos editor is selected as a plugin - otherwise it doesn't happen

I have discovered that this only applies when using the Kronos Editor. If I set up an external instrument channel - it works absolutely fine - if I copy the midi region to the external instrument track it works fine - just not from the one where I've opened an instance of Kronos Editor. I haven't ...

Yes CC64 says it is receiving OK - so it's clearly the Kronos that is failing to receive the correct messages.

As my other post suggests - sustain messages from outside the kronos are not being received by the kronos.

Ok so I notice following my previous post that sustain pedal is not working on the playback. The info is recorded on the DAW - up down etc.. on the sustain pedal in piano roll - but it doesn't affect the playback of the Kronos. I noticed an old post with same issue - but there is no answer there ...

My subject line says it all really. I'm using the Kronos as a midi keyboard input for the first time, as well as for its sounds in a DAW environment. Not that I think it makes any difference to the situation but I'm using logic 9 with Mountain Lion and called up the Kronos Editor as an instrument ...

danatkorg wrote:

richford wrote: It did this with three different libraries - each time this parameter becomes reverted to "Protected"

Which libraries?

- Dan

The three libraries are EXS84 , EXS95 and KRS-80.

It's a topic that's been much on my mind for some time. I originally bought a Kronos for gigging - but it seemed a waste not to use it in the studio as well. As you will see elsewhere on the forums I'm still ironing out issues implementing that, but getting there now. I also have an Access Virus TI ...

1. Press the GLOBAL switch to enter Global mode. 2. Go to the Global P0: Basic Setup– Basic page, and select the Basic page. Press the Basic tab at the bottom, and then press the Basic tab above it. 3. Press the “Memory Protect” check box for each type of data you wish to write or save, so that the ...

I'm working on this again tomorrow and will go through the reply posts. In the meantime I got an email from Korg but it really isn't very helpful - it just tells me obvious stuff which I've been through already. I have in the past saved PCG data etc.. set the auto-load file for my live setup and so ...

I've done some programming today on thie Kronos but cannot write properly to the HDD. 1) I keep getting a message that the disk is write protected when I try to copy things to it (from for example a USB stick) 2) When I select Disk ->HDD save mode - from the drop down menu I only get: Hide Unknown ...

I notice that all the Kronos controls send sysex messages.

Is there a way to map midi CC numbers to these so that I can for example edit the automation of the filter cutoff?

Yes I've had a look at all that now - I can see that must be the answer - but it all seems a bit buggy.

The aggregate devices thing is something I'd never spotted before - I don't know what the fields all mean so a spot of careful tweaking looks like it might be needed.