RPPR as a drum pattern librarian
Posted: Sun Nov 08, 2020 4:11 am
I have long considered how to create and organize a library of drum patterns of various styles within my Triton such that I can easily use them in the song production process, similar to what a drum machine or a keyboard arranger can do.
My list of requirements:
1) I can do this with just with my workstation, with no external devices needed (except perhaps a USB flash drive).
2) No nonvolatile internal memory data is modified (no changes to program, combi, or global data).
3) Each pattern is associated with a drum kit program appropriate for that pattern to ensure correct note-to-drum instrument mapping. This is particularly important to distinguish between drum patterns for a general MIDI drumkit versus drum patterns for Korg drumkits, and across Korg drumkits with different instrument-to-key mapping.
What seems to be a good solution is to create a drum pattern library as RPPR user patterns stored in .SNG sequence files, as described in this short video:
https://youtu.be/jUir5oHLwXE
The sources for these drum patterns to be imported into this library could include song template preset drum patterns (PG pp. 91-92), arpeggio drum patterns, and MIDI file drum patterns. This is made possible because RPPR user patterns can be exported to MIDI measures ("Copy to Track"), and RPPR user patterns can be created by importing from MIDI measures ("Get from Track").
We can use the sequencer mode to store RPPR drum patterns in song sequences grouped by style. Each drum pattern library sequence could correspond to a particular style (e.g. DPJAZZ1, DPJAZZ2, DPHOUSE1, etc.). We could have one .SNG file for each style (e.g. DPJAZZ1.SNG, DPJAZZ2.SNG, etc.). Or we could store all of these styles as separate song sequences into a single .SNG file, that being the "master" drum pattern library file (e.g. DP.SNG).
Each drum pattern style could have multiple sets that may be comprised of patterns for Intro, V1, V2, Fill 1, Fill 2, End, etc. Up to 72 RPPR key-to-pattern assignments can be made in a single song sequence. Up to 99 patterns can be stored per song.
You can build up a library of existing drum patterns such that they can be stored, retrieved, auditioned, and recorded into sequencer tracks in a consistent and convenient manner as part of music production. It is applicable to any Korg workstation that implements RPPR.
Any comments or suggestions regarding this approach are welcome.
My list of requirements:
1) I can do this with just with my workstation, with no external devices needed (except perhaps a USB flash drive).
2) No nonvolatile internal memory data is modified (no changes to program, combi, or global data).
3) Each pattern is associated with a drum kit program appropriate for that pattern to ensure correct note-to-drum instrument mapping. This is particularly important to distinguish between drum patterns for a general MIDI drumkit versus drum patterns for Korg drumkits, and across Korg drumkits with different instrument-to-key mapping.
What seems to be a good solution is to create a drum pattern library as RPPR user patterns stored in .SNG sequence files, as described in this short video:
https://youtu.be/jUir5oHLwXE
The sources for these drum patterns to be imported into this library could include song template preset drum patterns (PG pp. 91-92), arpeggio drum patterns, and MIDI file drum patterns. This is made possible because RPPR user patterns can be exported to MIDI measures ("Copy to Track"), and RPPR user patterns can be created by importing from MIDI measures ("Get from Track").
We can use the sequencer mode to store RPPR drum patterns in song sequences grouped by style. Each drum pattern library sequence could correspond to a particular style (e.g. DPJAZZ1, DPJAZZ2, DPHOUSE1, etc.). We could have one .SNG file for each style (e.g. DPJAZZ1.SNG, DPJAZZ2.SNG, etc.). Or we could store all of these styles as separate song sequences into a single .SNG file, that being the "master" drum pattern library file (e.g. DP.SNG).
Each drum pattern style could have multiple sets that may be comprised of patterns for Intro, V1, V2, Fill 1, Fill 2, End, etc. Up to 72 RPPR key-to-pattern assignments can be made in a single song sequence. Up to 99 patterns can be stored per song.
You can build up a library of existing drum patterns such that they can be stored, retrieved, auditioned, and recorded into sequencer tracks in a consistent and convenient manner as part of music production. It is applicable to any Korg workstation that implements RPPR.
Any comments or suggestions regarding this approach are welcome.