Thanks for the reply. This sounds like the solution! I will try to delete any controller data. I don't think I deliberately sent any, but I'll try to delete them if present. I hope there will be enough memory left to perform this editing. Otherwise I have cakewalk that should be able to do this.

Quote:
Originally posted by stigf:
Hei everyone.

First: No, the number of tones in each patch has nothing to do with the capacity used in the sequencer. The sequencer just sends a note over the correct MIDI-channel, and it is up to the synth-section of the XP to actually produce the sound. It does not matter to the sequencer if the sound produced is simple or complex.

Another thing to remember is that the sequencer stores 20000 MIDI-events, and not notes. This means that if you hava a lot of controller-data, sysex, program changes etc, this will use up the sequencer capacity. One prime example here is the aftertouch. If you press a key and make a long sustained note while changing the aftertouch pressure, the sequencer will only record one note-event, but perhaps hundreds of Control-Change-events for the aftertouch.

Data thin helps. It reduces the amount of controller data. This will not normally be audible, but the sequencer capacity is extended. If you are having problems with sequencer-memory, try to use data thin on each track after you have recorded them.

Another trick is to switch off aftertouch on parts where you don't need it, so that you are sure that no aftertouch-changes are generated.

Hope this was understandable.

Stig