Korg Forums Forum Index Korg Forums
A forum for Korg product users and musicians around the world.
Moderated Independently.
Owned by Irish Acts Recording Studio & hosted by KORG USA
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Combis & Programs, Add Ons, How Are They Stored?

 
Post new topic   Reply to topic    Korg Forums Forum Index -> Korg Kronos
View previous topic :: View next topic  
Author Message
JuneauUnderground
Senior Member


Joined: 12 Sep 2011
Posts: 258
Location: Juneau, Alaska & Tempe, Arizona

PostPosted: Sat Apr 14, 2012 7:52 pm    Post subject: Combis & Programs, Add Ons, How Are They Stored? Reply with quote

If I understand this correctly, the factory Combis and Programs are stored in the Factory folder in the PreLoad.PCG. When the Kronos boots up it loads what ever it finds there, correct?

If any modifications are made to the factory sounds and saved via global write then the Preload.PCG contents are modified with the changes, correct?

Ok, so now we add either Korg or Karo or other third party stuff and these patches are mapped to default empty banks. Combi banks IE, IF, IG or UA in the case of combis and in the case of programs Prog UG. Then hopefully AA-GG.

So my question is this: I see that these banks holding the expansions now hold the patches permanently. Is the mapping for these add ons storred in the Preload.PCG somehow? Is it like an autosave? I know from observation that something like that is going on, but I want to understand a little better the technical aspect.
_________________
KORG: Kronos 61, (EXs 54, 60, 61, 63, 90; KRS 01, 02, 04, 05, 55, 57, 59, Catalyst); M3-88 loaded, MS-2000R, M1REX, Wavestation SR
ROLAND: Jupiter 80, V-Synth, Fantom XR, XV-5080, XV-5050 x 2, XV-3080, JP-2080, JP-1080, JD-990 x 3 "stacked", D-550, R-8 MII, PMA-5
OBERHEIM: Matrix 1000
YAMAHA: Motif Rack XS, DX7II, DX-7, TX-802
NORD: Piano-88, Lead 1 Rack
ARTURIA V Collection (seriously cool); All Things Spectrasonics & Camel Audio (Alchemy)
EWQL: Fab Four, Symphonic Voices, Voices of Passion, Dark Side
UAD-2 Satellite Quad Omni; APOGEE: Ensemble; Duet x3; AXIOM Pro 49 & 61
Eilers Duo-Tonal Upright Grand (stunning)
Back to top
View user's profile Send private message
EddyDeegan
Junior Member


Joined: 23 Dec 2007
Posts: 70

PostPosted: Sat Apr 14, 2012 8:42 pm    Post subject: Re: Combis & Programs, Add Ons, How Are They Stored? Reply with quote

JuneauUnderground wrote:
If any modifications are made to the factory sounds and saved via global write then the Preload.PCG contents are modified with the changes, correct?


I don't think so. The changes are written to internal memory, but not the preload file on the SSD. The preload.pcg file in the factory folder is read-only by default, although you can lock/unlock it from the utility tab in disk mode (I've never tried to overwrite it though).

JuneauUnderground wrote:
Ok, so now we add either Korg or Karo or other third party stuff and these patches are mapped to default empty banks. Combi banks IE, IF, IG or UA in the case of combis and in the case of programs Prog UG. Then hopefully AA-GG.

So my question is this: I see that these banks holding the expansions now hold the patches permanently. Is the mapping for these add ons storred in the Preload.PCG somehow? Is it like an autosave? I know from observation that something like that is going on, but I want to understand a little better the technical aspect.


The preload.pcg file doesn't contain any data in some banks, so when you load the PCG file it doesn't overwrite whatever is in them. If you want to have a file with these banks in it, you need to save your own.

If you go into disk mode and look inside the preload.pcg you'll see what's in there.
_________________
Korg: Trinity+ HDR, Triton Rack, M3 + Radias-R, Kronos 88. Yamaha: 2xSY85, S90, Motif ES7, Motif XS8. Kurzweil: K2500.
Back to top
View user's profile Send private message Visit poster's website
michelkeijzers
Platinum Member


Joined: 08 Feb 2007
Posts: 6866
Location: Netherlands

PostPosted: Sat Apr 14, 2012 10:13 pm    Post subject: Reply with quote

You never should change the factory PCG file.

I don't know exactly where the PCG memory from the Kronos (internal RAM) is stored, not in PRELOAD.pcg file. It is only to restore to the factory default PCG file.

Probably the internal memory PCG information is stored in a hidden file (or still in non volatile memory as it was in other Korg workstations, but this is not really needed anymore).
_________________

Developer of the free PCG file managing application for most Korg workstations: PCG Tools, see http://pcgtools.mkspace.nl
Back to top
View user's profile Send private message Send e-mail Visit poster's website MSN Messenger
jg::
Platinum Member


Joined: 14 Aug 2003
Posts: 625
Location: Melbourne, Australia

PostPosted: Mon Apr 16, 2012 1:17 am    Post subject: Reply with quote

The Factory.pcg file is not loaded at start-up. It's there so you can load it up should you ever want to.

All Programs and Combis that were on-board on power-down will be automatically loaded on power up. As Michel assumes, the "internal memory" is stored in a hidden file somewhere. That's why you see your new banks automatically loaded at start-up. But you should back this up periodically by saving your own .pcg to the internal drive (Disk mode, Save tab) and then copying this file to a memory stick>computer.

jg::
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Korg Forums Forum Index -> Korg Kronos All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group