Hi everyone - first off, I’m a newby ……so you probably know what’s coming next……sigh.
Its 30 years since I last bought and played a keyboard (Polysix- in 1985 I think). So back in November when I joined a cover band and rediscovered live music, rather than faff about and buy something that wasn't ticking all the boxes, I decided to get what seemed to be the best tool for the job and jumped right in at the deep end and got myself a KronosX 61 (would have preferred the 73 but not with a fully weighted keyboard). It is truly remarkable……but in good and bad ways!
So here we are three months on and I still have no clue how to get it to do what I’m sure it can. Although I’ve now learnt almost 50 songs and have them as layers and splits saved into Set List OK, I have only used factory Progs + some basic Combis for these songs.
However, I now need to move to the next level but still find the vocabulary of the various tutorials daunting/unintelligible, (I’m certain, most these words used weren’t invented until after 1985!). In particular, I want to introduce sequences, arpeggios and the detail of cover songs, either by triggering them via my set list, or playing over the top of the current set list item.
Can anyone point me at some resources for beginners? I’ve tried the Korg manual which is breath-taking in its technical magnificence but what I need is the technical stuff in context (art over science for me I’m afraid). I’ve also looked through QR tutorials but again, his are a level above where I am at the moment.
By way of an example, I’ve managed to sequence the Bassoon part from Tears of a Clown. So now what I want to do is simply play the flute/piccolo part over that. In my mind, the bassoon and flute part would be created as a single combi and copied into a set list location, so ‘live’, I can quickly trigger the bassoon (somehow?) play the flute part and then switch to the piano/baritone sax combi on an adjacent set list button for the verses. I’m sure I’m being dense but I just don’t see how I can combine pre-recorded sequence (the bassoon) + be able to play over it (flute/piccolo) as a set list choice?
I hope that makes some kind of sense?
Anyway, I am gobsmacked by the sheer depth of knowledge that is represented on this forum, which is in itself a fantastic resource. If anyone can spare a moment to point some of that knowledge and enthusiasm back at my problem, I would be very grateful. Thanks in advance and apologies for the long post.
KronosX learning resources for newby
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
-
wildebeest
- Posts: 24
- Joined: Tue Feb 03, 2015 12:10 pm
- Location: Surrey UK
Hi there, Kronos is a beast, just getting into myself.
In terms of triggering your 'phrase' on the bassoon etc, only way I can think of is to sample the whole phrase, and assign it to a key within a combi, which will trigger it each time you press it. Only issue here is one of tempo - you don't say whether you are playing alone, or with a band etc, but even alone, the sample will always play the phrase at the tempo you recorded/set, so any variation in the tempo you/band are playing at and it wont fit time wise.
Other option is to put it in a song in the sequencer, where it plays at the appropriate points, and use a metronome/click either to drummer, or yourself, to keep time (we do this in live band with songs which have a lots of instruments/production we cant do live, not enough hands!!). This does restrict you to the format of the song, i.e. you cant deviate from the structure etc.
In terms of triggering your 'phrase' on the bassoon etc, only way I can think of is to sample the whole phrase, and assign it to a key within a combi, which will trigger it each time you press it. Only issue here is one of tempo - you don't say whether you are playing alone, or with a band etc, but even alone, the sample will always play the phrase at the tempo you recorded/set, so any variation in the tempo you/band are playing at and it wont fit time wise.
Other option is to put it in a song in the sequencer, where it plays at the appropriate points, and use a metronome/click either to drummer, or yourself, to keep time (we do this in live band with songs which have a lots of instruments/production we cant do live, not enough hands!!). This does restrict you to the format of the song, i.e. you cant deviate from the structure etc.
Have you tried watching Korg's Video Manuals for the basics? These vids are fairly straightforward and easy-going and may help to get a better understand of the vocabulary others are using. Here's a link to a playlist of the vids:wildebeest wrote:However, I now need to move to the next level but still find the vocabulary of the various tutorials daunting/unintelligible
http://www.youtube.com/playlist?list=PL ... tTu64LT6Ge
Do check out the other Kronos vids done by Korg as well. And perhaps bizarrely, some of the Korg M3 vids may also be useful in understanding how stuff also works on the Kronos, particularly the Basic Sequencing and RPPR tutorial vids: https://www.youtube.com/user/KorgUSAVid ... h?query=M3
As for the manuals, the Operation Guide (OG) is by far easier to understand compared to the Parameter Guide (PG). I totally get that some people have an aversion to reading the manuals, but in my opinion, the OG is an absolute must-read. The trick is to read it in small chunks - read a section and do the mini tutorial exactly as described until you understand the process. Then move on to something else. Just set aside 15 minutes a day and learn something new. You don't have to read it cover to cover. Just pick something that looks interesting. When you reallly need to know how something works, then you refer to the PG for that breathtaking detail... or you can do what many people prefer and create a topic here asking how it works. Just FYI: The PDF guides are searchable as well as having click-able links. Any time you see a page number referenced in the text, you can click that to jump right to the page. There's also the on-board help system on the Kronos itself...
In respect of what you're trying to accomplish with triggering a sequenced part and playing over the top of that, you're almost halfway there. You have several options to consider. Unfortunately, you're going to have to decide which option you prefer... I will try to use simple, clear language without too much tech-speak. But there is a lot to cover and I do understand that it can be overwhelming at first.
As Roadman posted, you could sample it and play it back with a key press (requires creating a sample and a new program using that sample, or alternatively recording an Audio Track in the Sequencer, which may be simpler). And as Roadman wrote, you can do it in MIDI sequence (Song) that's all pre-programmed for the entire song.
Another option is to use Real Time Pattern Play and Record (RPPR) in Sequencer mode. This will let you assign your bassoon sequence to a key on the keyboard. This is arguably more flexible, in that you can change the tempo freely to match the tempo of what your band is playing at, particularly if you are not using a click track. You would just have to use the Tap Tempo button to lock in to the tempo that the band is playing -- this is not exactly ideal, since in my experience tempos tend to deviate by several BPM in live play. A click track, however, would ensure the drummer and the rest of the band are always in sync with your sequence. RPPR is perhaps most useful when you have several different sequences to trigger.
There is still another option to consider. This seems a bit unintuitive, but it works if you have only one sequence to trigger. You could convert your bassoon sequence to a Drum Track pattern and trigger it to play with the Drum Track On/Off button. Like RPPR, you still need to somehow sync the tempo with the rest of the band. The idea is to create a copy of the bassoon program and save the bassoon as a Drum program by choosing Drums as the Category whilst saving (you could name the program accordingly, too, e.g. Bassoon (DrumPattern). Next, you convert your pattern/sequence to a User Drum Track Pattern. Then you create your combi, assigning your user Drum Track Pattern on the Drum Track page and choosing your Bassoon (DrumPattern) as the drum track timbre. You will likely want to set the trigger mode to Start Immediately.
So now that I've probably thoroughly confused you, you're going to need to make a decision as to which option is best for you and your band. The only way to do that is to try out the various options. I know I haven't given detailed instructions on any of them, but if one strikes your fancy, I'm sure I can find a previous topic discussing it or write new instructions to suit...
Now, if you go with using MIDI sequence in a song (or audio track), you can combine this with the set list functionality and switch between "active" tracks, letting you change which sound you're playing on the keyboard whilst the song continues to play uninterrupted. What you do is set up a few slots in set list mode with the same song (important!), but each slot has a different active track. This active track option appears only when you add a Song to the set list -- you won't see it for combis or programs.
Coming back to the click track thing, if you decide to go this route, you can have the Kronos output a click track to your drummer. This means your Kronos is the master tempo source for the entire band. If this is your preference, we can help you with that -- there are a few topics already covering that. The other option is to make the Kronos a slave and have some other gear as the Master sending MIDI clocks to your Kronos, for example a drum machine sitting next to the drummer connected by MIDI to your Kronos. This is how I've done it in the past with bands. It lets the drummer create his/her own personalised "click track" on the drum machine and program the tempo (or change it on the fly). Pretty much any old drum machine with MIDI out will do -- it doesn't need to be the latest and greatest. You do need to ensure that the drum machine isn't sending out any note data to your keyboard, though. All you want is the MIDI clock data. But if the drum machine does send out note data, it's just a matter of muting that channel on the Kronos.
Settings for making the Kronos a MIDI Master or Slave are done in Global mode on the P1 MIDI > MIDI screen in the MIDI Clock section. Use "Internal" to make the Kronos a master. To make the Kronos a slave, use one of the External options, or set it to AutoMIDI so that the Kronos will automatically switch between its own clock or an external clock if it's receiving MIDI clock messages.
-
wildebeest
- Posts: 24
- Joined: Tue Feb 03, 2015 12:10 pm
- Location: Surrey UK
-
wildebeest
- Posts: 24
- Joined: Tue Feb 03, 2015 12:10 pm
- Location: Surrey UK
Progress of sorts
Hi Roadman/HardSync and all - I’ve now spent some time working on my sequence as per your advice. I took the re-sampling route as it seemed ideal for what I wanted and straightforward in its application. I was so chuffed that it worked and the bassoon, flute/piccolo mix sounded great together. Suddenly, the power of the Kronos and the opportunities for Live music opened up before me. Then it went pear-shaped.
I have 3 questions around this if you could help again please.
Q1. So later in the same programming session, in my enthusiasm, I started re-sampling all sorts of sounds and instruments so that I could ‘convert MS to Program’ and trigger during Live play from an assigned key. However, when I came to try them out, all the previously sampled sounds (+ my bassoon which was already embedded within my Combi (as a Prog) for Tears of a Clown, were Birdsong, which happened to be the last sound I had re-sampled.. I believe what I’m doing is OK: write a sequence; re- sample it; convert MS to Prog; Write Prog; select and add to Combi; Write Combi. I’m think I must be missing some sort of ‘save’ in this end 2 end process but have failed to spot where that would.
So my question is, how do you segregate and save your re-samples as you go so you don’t break what’s already be re-sampled?
Q2. So having lost the original sounds in the Samples and Combi, I re-did just the Bassoon sample and repaired the Combi OK. The next day of course, the bassoon was missing from the Combi; just silence when I selected the bottom C chord. So I assumed (I think correctly) that I needed to reload the sequence via the Disk interface and hence the sample on start up? So this being the case, I hope the answer to my second question is, “just go into the ‘xxx’ menu and check the ‘yyyy’ box for sequence ‘ZZZ’ that says, ‘Load sequence automatically’ on boot up”? I can’t believe that a busy Live musician would need to ‘load’ potentially hundreds of sequences/samples every time he switches the beast on?
Q3. I wanted the bassoon to be triggered by pressing the C2 (I’ve a Kronos 61). When I went to replay the Combi during my first attempt at re-sampling, this worked fine. But was I just ‘lucky’? I don’t remember selecting ‘C2’ from an ‘assign key to sample’ menu and when I wanted to trigger the other sounds I’d sampled during my first session from C7 instead, it didn’t work. Is the sample triggering in Combi set to C2 by default and if so, can I change it?
Lots of info requested again and I am happy to go dig for the detail if you can advise where this might sit. Thanks again in advance.
I have 3 questions around this if you could help again please.
Q1. So later in the same programming session, in my enthusiasm, I started re-sampling all sorts of sounds and instruments so that I could ‘convert MS to Program’ and trigger during Live play from an assigned key. However, when I came to try them out, all the previously sampled sounds (+ my bassoon which was already embedded within my Combi (as a Prog) for Tears of a Clown, were Birdsong, which happened to be the last sound I had re-sampled.. I believe what I’m doing is OK: write a sequence; re- sample it; convert MS to Prog; Write Prog; select and add to Combi; Write Combi. I’m think I must be missing some sort of ‘save’ in this end 2 end process but have failed to spot where that would.
So my question is, how do you segregate and save your re-samples as you go so you don’t break what’s already be re-sampled?
Q2. So having lost the original sounds in the Samples and Combi, I re-did just the Bassoon sample and repaired the Combi OK. The next day of course, the bassoon was missing from the Combi; just silence when I selected the bottom C chord. So I assumed (I think correctly) that I needed to reload the sequence via the Disk interface and hence the sample on start up? So this being the case, I hope the answer to my second question is, “just go into the ‘xxx’ menu and check the ‘yyyy’ box for sequence ‘ZZZ’ that says, ‘Load sequence automatically’ on boot up”? I can’t believe that a busy Live musician would need to ‘load’ potentially hundreds of sequences/samples every time he switches the beast on?
Q3. I wanted the bassoon to be triggered by pressing the C2 (I’ve a Kronos 61). When I went to replay the Combi during my first attempt at re-sampling, this worked fine. But was I just ‘lucky’? I don’t remember selecting ‘C2’ from an ‘assign key to sample’ menu and when I wanted to trigger the other sounds I’d sampled during my first session from C7 instead, it didn’t work. Is the sample triggering in Combi set to C2 by default and if so, can I change it?
Lots of info requested again and I am happy to go dig for the detail if you can advise where this might sit. Thanks again in advance.
Reading through all of your questions, it does seem as though you are missing a few steps. To begin, what I think you are missing are the saving samples and having your samples auto-load at start up.
I've covered this before and so have quite a few others. It comes up a lot. In brief, what you need to do is:
1. Create Multi-Samples
2. Convert Multi-Samples to Programs
3. Save Programs
4. Create Combis with new Programs
5. Save Combis
6. Save User Sampling Data (KSC)
7. Add User KSC to Auto-Load
You can create all of your various samples and save them into one KSC file, so that you only have one user KSC to auto-load. Or you can create individual KSCs and auto-load them all. You can even combine KSCs and make a master KSC... I would suggest reading the User Sample Banks stuff in the Operation Guide, starting on pg 162. And then keep reading all the way through the sample section. Alternatively, search the Kronos forum for "auto-load" or "missing samples" or whatever... there must be a few hundred topics on that. Maybe someone can jump in here with some links to topics or a tutorial vid for the Kronos.
As for sequences, these cannot be auto-loaded unfortunately. If you've resampled your sequence, you won't need to load the sequence again. But if you use MIDI sequences at all when playing live, then you will need to load those songs into memory before the gig starts. You can, however, combine multiple sequences into a single .SNG file, so you don't have to individually load each song every time you gig.
As for assigning samples to keys, yes the default "first key" is C2. You can change this, but you have to delete multisample's indexes first before assigning the first sample to another key. By default, the first 8 indexes (or key assignments) are already assigned in a new multisample. You can use the CUT button to delete the last 7 indexes, leaving you with one, and this will allow you to set the first index's key anywhere on the keyboard. New indexes can be made using the Create button.
I've covered this before and so have quite a few others. It comes up a lot. In brief, what you need to do is:
1. Create Multi-Samples
2. Convert Multi-Samples to Programs
3. Save Programs
4. Create Combis with new Programs
5. Save Combis
6. Save User Sampling Data (KSC)
7. Add User KSC to Auto-Load
You can create all of your various samples and save them into one KSC file, so that you only have one user KSC to auto-load. Or you can create individual KSCs and auto-load them all. You can even combine KSCs and make a master KSC... I would suggest reading the User Sample Banks stuff in the Operation Guide, starting on pg 162. And then keep reading all the way through the sample section. Alternatively, search the Kronos forum for "auto-load" or "missing samples" or whatever... there must be a few hundred topics on that. Maybe someone can jump in here with some links to topics or a tutorial vid for the Kronos.
As for sequences, these cannot be auto-loaded unfortunately. If you've resampled your sequence, you won't need to load the sequence again. But if you use MIDI sequences at all when playing live, then you will need to load those songs into memory before the gig starts. You can, however, combine multiple sequences into a single .SNG file, so you don't have to individually load each song every time you gig.
As for assigning samples to keys, yes the default "first key" is C2. You can change this, but you have to delete multisample's indexes first before assigning the first sample to another key. By default, the first 8 indexes (or key assignments) are already assigned in a new multisample. You can use the CUT button to delete the last 7 indexes, leaving you with one, and this will allow you to set the first index's key anywhere on the keyboard. New indexes can be made using the Create button.
-
wildebeest
- Posts: 24
- Joined: Tue Feb 03, 2015 12:10 pm
- Location: Surrey UK
Thanks once again for your time HardSync. A perfect and clear response and v. useful links to previous questions. I felt, as you say the info was already buried in the forum somewhere but it's that vocab thing again - I wasn't using the correct terms to search for it. Anyway, I feel I'm close to the solution now so will give this a go at the weekend - I'm not sure I understand this 'indexes' malarkey but I will follow your instructions for assigning samples to other keys by rote and hopefully, the penny will drop.....
-
wildebeest
- Posts: 24
- Joined: Tue Feb 03, 2015 12:10 pm
- Location: Surrey UK
As it turned out, I had a very frustrating time trying to add further samples to Combis. I have taken so many routes, back-tracked and experimented that to provide an audit trail would be impossible and yet, I’m sure, compared to what lots of you get up to with your machines, it seems to me to be a really straightforward and basic requirement.
So as explained a week or so back, I created a sequence (bassoon for Tears of Clown) took HardSync / Roadman’s suggestion of sampling the sequence saving and adding that to Prog and hence Combi. This single instance of that sample is still OK.
Using that same set of steps, I wanted to add additional samples to other Combis, but this is still not working as I had expected.
I had sampled 6 different sounds from Prog (sound effects) and ended up with a corresponding list of L and R entries in Sample mode. Sounds fair. Can’t remember if I had set sample to Save to Disc or Ram at this point – don’t know of that’s significant? I then deleted the indexes as advised previously (by rote I hasten to add – I don’t actually understand what I am deleting here) such that I can assign a different key to each of these sample sounds if I need to. Here is where I think I go wrong because I discovered that the sample sound for the bassoon that I believed I had locked down in my Combi, is now a different sound (one of the new sound effects). It suggests to me that sample sounds are therefore dynamic and are never ‘really’ saved within a Combi/Prog?
I can see I need to re-think the way the Kronos operates as clearly, samples cannot be persistent based on this behaviour so sorry to be a pain but can I ask for some more detail around how this works please?
I have since read and re-read everything I can find on this but again, I’m missing some major step, probably because of my unfamiliarity with the vocab.
As of now, I have just the one sample left in the machine and it is ‘pointed’ OK at the Tears of A Clown Combi; I still have several Progs that no longer have any ‘sound’ within them; I have indexes available from 1 – 8 (at least I think I do) and all the other samples taken have been deleted to provide a clean slate to start yet again.
So I suppose my question is how do I create a second (third etc etc) sample and assign to a Prog/Combi without overwriting that which is already ‘saved’ (Kronos version of saved) in a Combi. So for example, for the following songs I would ideally have a Combi for each of these:-
- Tears of Clown – contains single sample of bassoon sequence (working OK)
- Love Is The Drug – contains footstep, keys, car sound effects (3 samples, or alternatively, I could ‘play’ each sample in sequence in real time when recording as a single sample (or would this now be a multi-sample?) sample.
- Rio - Bird song
- Teenage Dirtbag – tyre squeal.
And then in Sampling mode, this looks like a list 8 new samples (12 I guess if all are recorded separately).
After Converting MS to Prog, I would have 4 new Progs in User G (by default)
Can I assign say D2 to all of these samples (I think not) so that once the samples are embedded in my Combi, C2 plays that sample and that sample only, or must I use a different index/key for each sample and use that key when playing live (but then that doesn’t make sense either particularly if you are sampling heavy in your playing as there are not enough keys)? And is it critical in the process when I save the sample into my global ‘sample’ folder for auto load?
Apologies for labouring this…………!
So as explained a week or so back, I created a sequence (bassoon for Tears of Clown) took HardSync / Roadman’s suggestion of sampling the sequence saving and adding that to Prog and hence Combi. This single instance of that sample is still OK.
Using that same set of steps, I wanted to add additional samples to other Combis, but this is still not working as I had expected.
I had sampled 6 different sounds from Prog (sound effects) and ended up with a corresponding list of L and R entries in Sample mode. Sounds fair. Can’t remember if I had set sample to Save to Disc or Ram at this point – don’t know of that’s significant? I then deleted the indexes as advised previously (by rote I hasten to add – I don’t actually understand what I am deleting here) such that I can assign a different key to each of these sample sounds if I need to. Here is where I think I go wrong because I discovered that the sample sound for the bassoon that I believed I had locked down in my Combi, is now a different sound (one of the new sound effects). It suggests to me that sample sounds are therefore dynamic and are never ‘really’ saved within a Combi/Prog?
I can see I need to re-think the way the Kronos operates as clearly, samples cannot be persistent based on this behaviour so sorry to be a pain but can I ask for some more detail around how this works please?
I have since read and re-read everything I can find on this but again, I’m missing some major step, probably because of my unfamiliarity with the vocab.
As of now, I have just the one sample left in the machine and it is ‘pointed’ OK at the Tears of A Clown Combi; I still have several Progs that no longer have any ‘sound’ within them; I have indexes available from 1 – 8 (at least I think I do) and all the other samples taken have been deleted to provide a clean slate to start yet again.
So I suppose my question is how do I create a second (third etc etc) sample and assign to a Prog/Combi without overwriting that which is already ‘saved’ (Kronos version of saved) in a Combi. So for example, for the following songs I would ideally have a Combi for each of these:-
- Tears of Clown – contains single sample of bassoon sequence (working OK)
- Love Is The Drug – contains footstep, keys, car sound effects (3 samples, or alternatively, I could ‘play’ each sample in sequence in real time when recording as a single sample (or would this now be a multi-sample?) sample.
- Rio - Bird song
- Teenage Dirtbag – tyre squeal.
And then in Sampling mode, this looks like a list 8 new samples (12 I guess if all are recorded separately).
After Converting MS to Prog, I would have 4 new Progs in User G (by default)
Can I assign say D2 to all of these samples (I think not) so that once the samples are embedded in my Combi, C2 plays that sample and that sample only, or must I use a different index/key for each sample and use that key when playing live (but then that doesn’t make sense either particularly if you are sampling heavy in your playing as there are not enough keys)? And is it critical in the process when I save the sample into my global ‘sample’ folder for auto load?
Apologies for labouring this…………!
Hi, firstly, I think the basic problem is getting you head around the architecture of the sampling and how the differing bits relate - I'm no expert as yet, and am going through a similar learning curve.
I have put a couple of links below which will help - one of them is actually for the Korg M3, but it looks like the sampling architecture is very similar, and I found it useful in understanding the structure, how to save etc and make sure you don't get the issues.
Multisample - this is the collection of samples all together In one set/load(ie for one of your songs); can be multiple 'samples (different sounds) spread across the keyboard, or it can be one sample,EG a piano you sampled from another keyboard. each of these 'samples' within a multi sample are called 'Index', and you can have either just one, across the whole keyboard, or differing ones with different sounds/effects etc. Each index is one sample.
When you create a sample (or samples), these are put together into a multisample (samples, settings, original keys, location and spread on the keyboard etc etc), and then once complete, you save this as a program, then insert into your combi (if required). You need to save sample data (save all) and it creates a KSC file, which is all the sampling data you created.. The programme or combi needs to be saved in the normal way after editing.
When it comes to loading, after the kronos has been off, samples do not load automatically unless you put them in autoload (global, sample autoload, add KSC). If you don't do this, when you play the programme or combi you will get a sample not loaded (and no sound from the sampled part), because it has not been loaded. You can load them manually at that stage by going to disc, find the KSC file and load it, but insert them in autload and they load up at boot up, along with the other samples used in the Kronos soundsets/factory stuff.
Below also helps understand the stereo/mono side (I am just doing mono, no point to stereo for live work)
Sorry bit of a ramble -
http://karma-lab.wikidot.com/korg-m3:un ... pling-data
https://www.youtube.com/watch?v=8iVRFL4ewF4
https://www.youtube.com/watch?v=M12ZxF_OdKs
http://www.kidnepro.com/blog/korg-krono ... h-samples/
I have put a couple of links below which will help - one of them is actually for the Korg M3, but it looks like the sampling architecture is very similar, and I found it useful in understanding the structure, how to save etc and make sure you don't get the issues.
Multisample - this is the collection of samples all together In one set/load(ie for one of your songs); can be multiple 'samples (different sounds) spread across the keyboard, or it can be one sample,EG a piano you sampled from another keyboard. each of these 'samples' within a multi sample are called 'Index', and you can have either just one, across the whole keyboard, or differing ones with different sounds/effects etc. Each index is one sample.
When you create a sample (or samples), these are put together into a multisample (samples, settings, original keys, location and spread on the keyboard etc etc), and then once complete, you save this as a program, then insert into your combi (if required). You need to save sample data (save all) and it creates a KSC file, which is all the sampling data you created.. The programme or combi needs to be saved in the normal way after editing.
When it comes to loading, after the kronos has been off, samples do not load automatically unless you put them in autoload (global, sample autoload, add KSC). If you don't do this, when you play the programme or combi you will get a sample not loaded (and no sound from the sampled part), because it has not been loaded. You can load them manually at that stage by going to disc, find the KSC file and load it, but insert them in autload and they load up at boot up, along with the other samples used in the Kronos soundsets/factory stuff.
Below also helps understand the stereo/mono side (I am just doing mono, no point to stereo for live work)
Sorry bit of a ramble -
http://karma-lab.wikidot.com/korg-m3:un ... pling-data
https://www.youtube.com/watch?v=8iVRFL4ewF4
https://www.youtube.com/watch?v=M12ZxF_OdKs
http://www.kidnepro.com/blog/korg-krono ... h-samples/