Korg Forums

I now own an original Kronos and Kronos 2. The Kronos 2 will be reserved as a backup in case the K1 takes a dump. Until I can afford to update the K1 with the new EXs and KRS I want to load my K1 PCGs into the K2 should the need arise. I am wondering what the ramifications might be. The K1 has EXs16 installed and I believe the K2 has a portion of that Library already loaded. Has anybody had any experience with what I am trying to do. Will it go off without a hitch or will I have a lot of programming and editing to do?

ronnfigg wrote:I now own an original Kronos and Kronos 2. The Kronos 2 will be reserved as a backup in case the K1 takes a dump. Until I can afford to update the K1 with the new EXs and KRS I want to load my K1 PCGs into the K2 should the need arise. I am wondering what the ramifications might be. The K1 has EXs16 installed and I believe the K2 has a portion of that Library already loaded. Has anybody had any experience with what I am trying to do. Will it go off without a hitch or will I have a lot of programming and editing to do?

Do you have many combis in your K1 PCG to bring over ?

I think you will have to do some bank changes to keep those combis intact.

Look at the PDF of Programs for both and compare. I believe its the INT for program bank A is where you could start, if necessary

I think its smart to get a 2nd Kronos, esp if you gig. I would think most pros do something similar.

I must have been dreaming this topic last night, as I woke thinking about posting this very question today!... and here it is! That was weird!

I've pondered the same thing with my 2 beasts, but was going to read the documentation a little more in case I could answer the question myself first.
I was simply thinking that as long as I had all the same sample libraries in both, that I could just load the pcg of one to the other, and the programs and combis would all be in the same slots on both machines.
I am planning on trying it soon anyway, to see what happens. It's no big deal, because if I stuff it up, all I have to do is reload the working pcg for the instrument anyway....and I'm pretty diligent at having backups of everything

In my case I wanted to take the pcg in my Kronos 2 and load it onto the Kronos X. But in the end it should be the same in both directions.
Both instruments have vers 3.04, so I can't see what other differences there would be. The pcg being loaded wouldn't know whether it's a 2 or a 1 or X?

Not having brushed up on that documentation yet, I am happy for anyone to dispute my reasoning

Ronn,

today I did some pcg loading to see what would happen. I know your question is particularly concerned with the fact that you don't have the K2 libraries installed yet, but I think I know what would happen in your case.

I do have the K2 libraries installed on my Kronos X, as I purchased them some time back. I saved my latest K2 pcg and then loaded it into my Kronos X.
All the program and Combi mappings then appeared the same as on my K2, and all appeared to function correctly. In other words both my Kronos were synced.
My guess is, that if you don't have the K2 libraries installed, anything that uses the samples from these won't work, however the programs and combis will match on both machines in matching locations, and any common samples etc. that are in both will work correctly. I'm guessing too, that any new K2 programs or combis that do use the original K1 sample, drums, arps or waveseq's should also work ok, and be mapped on the K1 as if on the K2.

My suggestion is to just make backups, and then try it. I didn't exhaustively go through every prog/combi, but all the one's which are important to me, and which would have had libraries that were originally not in the K1 factory worked ok for me.

I still have a lot to learn about Kronos architecture, and I've pretty much managed to get a fully maxed out pcg on each machine with as many onboard libraries as possible by loading some progs and combi's individually in other than the default banks. This for me, has on the whole been quite successful but I still have the odd drumtrack or wavseq which isn't referencing the correct prog or combi. Still a bit to learn then

Chris

I had loaded previous sequences to my K2 from my K1. My soundsets are not exactly duplicated. I had purchased many sounds on my K1 and do not want to pay double to have them on the K2. So when I loaded the sequences to my K2 I just found some of the sounds that would be most similar to some of the tracks on my K1 changed them to approximate the sounds of the K1 and I just live with it.

If you wanted an exact clone...it might be expensive if you have numerous exi's on your K1. I'm a happy camper! Great forum, love my Korgs!

Okay. So I took the plunge. Went ahead and loaded the PCG from the K1 to the K2. So far, so good. About the only issue I can see is EXs 16 but I haven't verified that yet. If I understand correctly there is a partial set programs from EXs 16 under the guise of EXs 18 in the K2. I mainly use combinations in live performance situations. I will keep you all posted. I am actually going to have to put this to work this weekend. As I have a double header in one day. I will be having to set up a second set of gear earlier in the day for a performance later that night, and then have to go to another venue to perform before that one. There is only one hour between the two gigs and I have about a half an hour of travel time. So to have everything set up for the later performance will be a big plus. Just keeping my fingers crossed that all will go well.

So at this point it seems like the K2 is backwards compatible short of any the EXs libraries that are not installed on the K2.

What you also can do is using PCG Tools and copy/paste the combis/set lists, it will also copy the needed programs/combis ... only samples/wave sequences and drum pattern (programs) are not supported.