Korg Forums

FILE DOWNLOAD
You can get the file here at Sendspace: http://www.sendspace.com/file/lln0e6

Select the "Click here to start download from sendspace" area. All other links are spam.

The download file "INIT.zip" contains two files:
-- INIT.pcg
-- INITpcg_ReadMeFirst.txt

Note: This file assumes you have Kronos OS 1.5 or later.

Korg Kronos INIT.pcg Read Me First
WARNING:
Read this document carefully, since the "INIT.pcg" file can wipe out all modifications you have made to the Kronos AND the factory data -- specifically Programs, Combinations, Drumkits, Wave Sequences, and Set Lists.


How To Get Started
----------------------
-- To use, copy the "INIT.pcg" file to your Kronos Hard Drive


Description
--------------
-- The "INIT.pcg" is a Kronos .pcg (Program-Combination-Global) data file that can be used to intialize the ENTIRE KRONOS, or specific banks/areas of the Kronos internal memory.
-- the "INIT.pcg" file is to be used in conjunction with the Kronos Factory Preload file (\Disk\Factory\preload.pcg). The "preload.pcg" is a backup file of pcg data that was initially loaded on the Kronos when it shipped from the factory.
-- Both the "INIT.pcg" and "preload.pcg" can be opened in Kronos Disk Mode (Load tab\Open). After initially opening one of these files, you can "drill down" into each file (open each lower layer) to see the exact contents of each file.

*** I HIGHLY RECOMMEND you perform the step above to learn what data is in each file BEFORE you load it ***


Contents of the INIT.pcg File
----------------------------------
["Drill down" into the file in "Disk Mode\Load\Open" to see exact contents]
-- Program Banks: INT-A through USER-GG -- [All 2,560 Programs Initialized]
-- Combination Banks: INT-A through USER-G -- [All 1,792 Combinations Initialized]
-- Drumkits: INT through USER-GG -- [All 264 Drumkits Initialized]
-- Set Lists: 000 through 127 -- [All 128 Set Lists Initialized]
-- Wave Sequences: INT through USER-GG -- [All 598 Wave Sequences initialized]

Note: GM Programs and GM Drumkits are not included above, since they can not be deleted or overwritten.


Why Was This Created?
---------------------------
The Kronos Factory Preload file (preload.pcg) only loads data into banks that have factory content, leaving other banks untouched. I wanted to be able to quickly set my Kronos back to its factory state, and/or quickly clear/initialize non-factory banks I had used.

As an example, the Kronos has 20 Program banks (excluding the GM bank), but only 12 Program banks are included in the factory preload.pcg file. If you load anything into the other 8 Program banks there isn't a super quick way to erase/initialize those 8 banks.


Example Uses
----------------
1. PUT KRONOS BACK TO FACTORY STATE
-- In Disk Mode, load "INIT.pcg". This will initialize all Kronos Programs, Combinations, Drumkits, Wave Sequences, and Set Lists
-- In Disk Mode, load "\Disk\Factory\Preload.pcg". This step is described in detail in the Kronos Operation Guide, Appendix, "Restoring the Factory Settings" section (in the E4 version, page 265).
-- The end result of the two steps above is a Kronos as it was shipped from the factory (excluding ROM/Multisamples which are not impacted by pcg data)

Note:
-- The "preload.pcg" file also contains Global Settings data that will overwrite any changes you have made (e.g. pedal polarity, MIDI settings)

2. INITIALIZE A SPECIFIC BANK
-- Let's say I want to initialize/clear Combination Bank INT-G
-- In Disk Mode, Open "INIT.pcg" and navigate down to the set of Combination banks (Open, Select Combinations then Open). Then select "INT-G" and load to "INT-G". This step is described in detail in the Kronos Operation Guide, the "Loading individual banks from a .PCG file" section (in the E4 version, page 189).

3. INITIALIZE A SINGLE ITEM
-- Let's say I want to initialize/clear Drumkit User D03
-- In Disk Mode, Open "INIT.pcg" and navigate down to any individual drumkit. Select that drumkit then load to "User D03".

Very nice! Thanks for profferring and for the detailed write-up!

Thank you so much

1+. Thanks a lot for developing and sharing!

Thank you Martin.

I haven't tried it but I assume these patches (programs/combis) area really empty (inaudible, no piano)?

I can easily clear the names of patches with PCG Tools, but it doesn't change the sound (yet).

michelkeijzers wrote:Thank you Martin.

I haven't tried it but I assume these patches (programs/combis) area really empty (inaudible, no piano)?

Normally there are sounds associated with initialized data since there are underlying default multisamples. When you select then play an initialized Program, it plays a piano sound.

MartinHines wrote:

michelkeijzers wrote:Thank you Martin.

I haven't tried it but I assume these patches (programs/combis) area really empty (inaudible, no piano)?

Normally there are sounds associated with initialized data since there are underlying default multisamples. When you select then play an initialized Program, it plays a piano sound.

Yes I know ... maybe I should change the clear option in my app to have an inaudible sound. It also clears the name complete (so no Init.... name but just empty).

Sorry if I'm a little thick, but without this file, what's with the usual procedure? Takes longer?

Thanks for sharing.

Martin I have wanted this from day one. Actually day two after saving Global settings and such.
Then moved on and could never get back to the real factory default contents. Thank you for your efforts!

Dniss wrote:Sorry if I'm a little thick, but without this file, what's with the usual procedure? Takes longer?

This file helps with initializing/clearing all of the banks and data that are NOT included in the Factory Preload.pcg file.

Example -- Program Banks
The Kronos has 20 Program Banks (excluding the GM bank).
The factory preload.pcg file contains data for only 12 Program Banks:
-- Program Banks INT-A through INT-F
-- Program Banks USER-A through USER-F

When the Kronos comes from the factory there are 8 Program banks that are empty (initialized):
-- Program Bank USER-G
-- Program Bank USER-AA through USER-GG

Most add-on Programs you buy (or create yourself) normally load into Program Bank USER-G. However, since the preload.pcg doesn't contain data for USER-G, reloading the preload file won't initialize USER-G. If you want to clear out the USER-G bank there isn't a super quick way to do it. This is also true if you put some of your own Programs into any of the USER-xx banks.

Similar situations exist for Combi Banks, Drumkit banks, and Wave Sequences.

The file I created just helps to clear/initialize specific PCG data.

Spend a few minutes examining the Preload.pcg file. Open in up, and drill down into the different parts. When you do, you can see that many banks are missing -- i.e. not included in the preload data. Then spend two minutes examining the Init.pcg file.



Note: There is a way to initialize Program Banks by changing their Bank Type (EXi to HD-1 or vice-versa), then changing them back, but this takes a little while, and is only good for initializing Program banks (not Combis or Drumkits).

Lou wrote:Martin I have wanted this from day one. Actually day two after saving Global settings and such.

I like to treat Global settings separately since those are more stable. I actually have a couple of saved global settings .pcg files I created for myself that ONLY contain Global Settings data and nothing else.

They take advantage of the fact that the "Save PCG" command can be very specific about what pcg data is being saved.

I have one .pcg file I call "Glob_INT.pcg" which only has global settings data (it has pedal settings and Local Control ON for standalone playing). I have a second .pcg file I call "Glob_EXT.pcg" which is identical to the first one but with Local Control OFF for use with an external sequencer.

Thanks for a great explanation. Gonna take some time to digest it all, but I get the idea.

Dniss wrote:Thanks for a great explanation. Gonna take some time to digest it all, but I get the idea.

The picture below might help, using Program Banks as an example. In the example, the Program banks with Factory preload data are in grey. The open banks are white.

If you re-load the preload.pcg data file, only the greyed banks are impacted. Nothing is erased in the other banks. The INIT.pcg file helps clear out everything.

MartinHines wrote: I like to treat Global settings separately since those are more stable. I actually have a couple of saved global settings .pcg files I created for myself that ONLY contain Global Settings data and nothing else.

I have one .pcg file I call "Glob_INT.pcg" which only has global settings data (it has pedal settings and Local Control ON for standalone playing). I have a second .pcg file I call "Glob_EXT.pcg" which is identical to the first one but with Local Control OFF for use with an external sequencer.

Yes, I did the same, I have 3 or 4 I use for 2 different DAWs. As you mention above Local On or Off, Controllers on or off etc.
Huge time saver and flawless setup once you hone in on your preferences and save. .. Nice chart.

Hope you don't mind if I use this thread to ask something about PCG Tools regarding clearing patches.

Currently you can:
- Select one or more program banks, combi banks or set lists and press clear. Then all the patches in the selected banks or setlists will be cleared
Example: select Program bank I-A, I-C, U-A, U-D. Press clear. All programs in these 4 banks will be cleared.

- Select one or more programs, combis or set list slots within a bank and press clear. Then all selected patches will be cleared.
Example: select I-A10 to I-A20, I-A25 to I-A28. Then 15 programs will be cleared.

With clearing, only the name is cleared but the sound stays.
Would it be better to also remove the sound at all? I don't know if I can put a full initialized patch there (it differs per model). Besides, it's used mostly to overwrite by another patch later or to keep gaps (e.g. inside set lists or combis).

michelkeijzers wrote: With clearing, only the name is cleared but the sound stays.
Would it be better to also remove the sound at all? I don't know if I can put a full initialized patch there (it differs per model). Besides, it's used mostly to overwrite by another patch later or to keep gaps (e.g. inside set lists or combis).

I would probably make the initialized patch the same as the Kronos does it internally.

Since some people might be initializing a program to start from scratch to build a new one, just clearing the name (but leaving the rest of the data intact) might leave some weird settings a user is unaware of.

However, if people using the tool are aware Clear only clears the name, they could work with it.