System Version 2.1.0

[Cobra Jet]

Or do I want to load "Factory sounds V2 (for KRONOS 2.1.0)"?

[ed_f]

If you don't, go for it, the organs are sooooo much better

Will I get the better Organ sounds after I do the upgrades or will I also need to load “KRS-06: CX-3 Signature Sounds”. If I do load KRS-06: CX-3 Signature Sounds will they overwrite my existing patches or will it created a new bank of organ patches?

You will get the better sounds after the upgrade. KRS-06 is full of great patches though. You can load them in another location if you have something there already.

[X-Trade]

KRS06 is an expansion library so it is a whole bank of entirely new sounds. recommend you load it into a blank bank that you aren't already using.

Factory Preload V2 on the other hand is identical to the factory preload that came installed on your Kronos, except the organ sounds there are updated to use the CX3 organ engine enhancements for a better sound. You don't have to load these but if you aren't using KRS06 and you aren't programming your own sounds, then you won't benefit from the organ improvements at all.

There's no reason you can't use both or any combination of them. For example I like KRS06 a lot, but I didn't bother with the preload sounds because I'm not that fussed about the preload combis, but a few of my own do use those sounds and I prefered the way they sounded before - in the context of those combis I'd programmed myself.

[jduesenb]

I did the whole 2.1.0 update yesterday, including the firmware, all the sound banks, and the editor (Mac version). It all went smoothly and so far no problems noticed. The new CX3 sounds are great, although I don't use organ sounds very much.

The Editor seems to be somewhat more responsive, in terms of graphics updates and xmit/recv to the Kronos. I don't exactly love this editor, but it's now in the category of "usable" and I'm happy to see it still being supported.
I happen to like computer-based patch editing, and I have difficulty with small touch screens, so having an editor is an absolute necessity and a deal-breaker when deciding on what keyboard instr. to buy. (Where are you now, Opcode Systems????)

So thanks, Korg.

[tcornishmn]

Just updated to 2.1.1. Wanted to say that I've been waiting for the Leslie speed indication since I got my OASYS in 2005. Works in Combi mode too!!!! Way to go Korg - this is hugely great!

[Cobra Jet]

Ok I successfully updated to 2.1.1 and Sub-System Firmware Version 6.04. Now I want to try to load Factory sounds V2 (for KRONOS 2.1.0). Would you put the three files in the Factory folder that the originals were in, or in a separate folder. Also, I think I will need to go into the global settings and deselect the preload.ksc to autoload and select the new one. Is that correct? If I do that, what will happen to a few custom Programs I have created?

Custom sounds are in the following:
Combi User G
Program User DD and GG

[Cobra Jet]

Ok, I got impatient and tried a couple of things that answered some of my questions and created a new one.

1. I was not able to paste “Factory sounds V2” into the Factory folder (I’m guessing most of you knew that) so I created a new folder and placed PRELOAD_V2.KGE, PRELOAD_V2.KSC & PRELOAD_V2.PCG in it.
2. I went into Global, KSC Auto-Load, deselected PRELOAD.KSC, selected PRELOAD_V2.KSC and rebooted. Everything came up including my custom sounds (this was a bit of a surprise to me).
I was thinking that this would load all the sounds from that factory and if a slot was blank originally it would be blank again.

Did it ignore the banks that were blank originally?

Was this the correct way to get the Factor V2 sounds working?

[Yuma]

KSC-files contain references to samples. They don't contain program/combi-bank information.
KSC-files need to be loaded into memory (RAM) at the start; this can be done through the KSC auto load panel.

Program/combi-bank information is stored in a PCG-file. You don't have to reload the PCG-file every time though.
After loading the PCG-file for the first time, it's information is being stored persistantly in the Kronos (not in RAM, but in some specific program/combi memory).

[Cobra Jet]

KSC-files contain references to samples. They don't contain program/combi-bank information.
KSC-files need to be loaded into memory (RAM) at the start; this can be done through the KSC auto load panel.

Program/combi-bank information is stored in a PCG-file. You don't have to reload the PCG-file every time though.
After loading the PCG-file for the first time, it's information is being stored persistantly in the Kronos (not in RAM, but in some specific program/combi memory).

So once I load the PRELOAD_V2.PCG will my custom sounds in Combi User G, Program User DD and GG be overwritten? If they are overwritten will I be able to get them back by loading my original PRELOAD.PCG?

Sorry to ask so many questions but I’m nervous about screwing things up and sometime I feel like a caveman trying to understand fire with this thing

[Bertotti]

Back everything up before and after installing. As I understand it they will be overwritten but you could just load the relevant banks instead of the entire v2. That is how several of us did it.

[geoelectro]

My user banks were not overwritten when loading V2.

Geo

[Cobra Jet]

I backed everything up yesterday before I started the system updates.

Here is my biggest concern. If I load v2PCG and it does overwrite my custom sounds, will I get them back by reloading the original factory PCG?

[Cobra Jet]

I backed everything up yesterday before I started the system updates.

Here is my biggest concern. If I load v2PCG and it does overwrite my custom sounds, will I get them back by reloading the original factory PCG?

[danatkorg]

I backed everything up yesterday before I started the system updates.

Here is my biggest concern. If I load v2PCG and it does overwrite my custom sounds, will I get them back by reloading the original factory PCG?

First - I think it would be helpful to read the documentation that I wrote to accompany these updates. The docs will walk you through the process, step-by-step.

As noted in the docs, you should make sure that your sounds are backed up before loading the new PCG. The factory sounds are the sounds that shipped with the KRONOS; your sounds will not be among them.

You can open a PCG file on disk to see the banks that it contains. Only those banks will be overwritten. You can also load individual banks, and for that matter individual sounds, from the PCG.

Hope this helps,

Dan

[ed_f]

I backed everything up yesterday before I started the system updates.

Here is my biggest concern. If I load v2PCG and it does overwrite my custom sounds, will I get them back by reloading the original factory PCG?

First - I think it would be helpful to read the documentation that I wrote to accompany these updates. The docs will walk you through the process, step-by-step.

As noted in the docs, you should make sure that your sounds are backed up before loading the new PCG. The factory sounds are the sounds that shipped with the KRONOS; your sounds will not be among them.

You can open a PCG file on disk to see the banks that it contains. Only those banks will be overwritten. You can also load individual banks, and for that matter individual sounds, from the PCG.

Hope this helps,

Dan

++1 The docs say it all - and following them has worked flawlessly!