The sequencer has a capacity of 200,000 events. When you enable
multi-track record, the available memory is divided by the number of
enabled tracks, and then by 2 (to allow for the compare function). In
other words, a memory buffer is provided for each enabled track. If any
track exceeds this buffer while recording, you get the out-of-memory
situation.
Here’s an example: Assuming starting with an empty sequencer, if 16
tracks are enabled, you have (200,000/16)/2, or 6,250 events per track.
Some KARMA GEs generate large amounts of MIDI data, when there are
3 or 4 different CCs being generated, in addition to notes, pitch bend
info, etc. 6,250 events is not all that much, especially where KARMA is
concerned. In some combis, you could run out of memory after 48 bars
or so.
But this is because ALL 16 TRACKS ARE RECORD ENABLED.
If you copy a Combi into the sequencer, at the most you will be recording
the output of 4 KARMA GEs, and maybe the keyboard sound. If you only
enable the tracks that are actually being used, you greatly increase the
amount of available memory for recording.
A quick fix is to disable tracks 9-16 (assuming you copied a Combi to
tracks 1-8, or the other way around if you copied to 9-16). In this case,
you’ve doubled the amount of available memory to 12,500 events per
track. But let’s say you then go look at the channel routing assignments,
and determine that you can turn off 4 other tracks that are not actually
being used - you’ve now quadrupled the available memory 25,000 events
per track!
Note that if you are familiar with the Triton, this is not any different than
the Triton sequencer. One difference is that KARMA generates large
amounts of MIDI data, so your events can get eaten up more quickly
than using the Triton’s arpeggiators, for example.
There are 2 places to check for MIDI routing:
(1) (3.1-1/2) [Menu]->[PRM1]->[MIDI...8] or [MIDI..16]
Here you can see which MIDI Channels are assigned to which tracks.
(2) (6.1-2) [Menu]->[KARM]->[MIDI I/O]
Here you can see which timbres (on which channels) are actually being
sent data from KARMA.
Let’s take a simple example. Combi A016: Earthy Groove.
As you can see by looking in both places, only tracks 1, 2 and 3
(receiving on channels 2, 3 & 4) need to be enabled to record, because
they are the only tracks doing anything.
Another (more complex) example: Combi A000:==Voice Of KARMA==
Using Method (2) above, we see that KARMA Modules are generating on
timbres 4,5,6,7 & 8. Using Method (1) above we also see that tracks 1, 2
& 3 are on Channel 1, to be played live.
However, here’s another interesting thing: in this case, tracks 1,2 & 3 are
all set to MIDI Channel 1 (this is the LH Pad sound and the RH Lead
Sound, configured with key zones into a split). Even with multi track
record on and all tracks enabled, when you play on the keyboard the
system only records 1 track of data (on to track 1), because the other
tracks are set to the same channel. Tracks 2 & 3 will record nothing.
However, because they are record enabled, they probably still eat up
potential available memory. The same thing goes with tracks 7 and 8
(the KARMA drum groove), which are both receiving on MIDI Channel 5.
Even if both of these are enabled, data only gets recorded on the first
one.
So in this case, to record just the KARMA output (and have the most
memory available), enable 4,5,6 and 7. To record the live keyboard parts
along with it, just additionally enable track 1.
If all this sounds complicated, just remember that you don’t have to do
this unless you are having problems running out of memory while
recording. Many of you may never run into this problem.