Naming User Drum Patterns
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Naming User Drum Patterns
I'm learning gradually and have created some drum patterns. But I'm not sure how to name them. Actually have named one and can't get to how I did it. Perusal of pdf user hasn't helped yet.
-
- Platinum Member
- Posts: 2206
- Joined: Wed May 31, 2006 11:56 pm
- Location: Vienna, Virginia, USA
- Contact:
Korg's usual scheme is to name things as they are saved - you'll save the pattern, be prompted to name it, and asked to confirm the location.
That's pretty much the only place you'll see a name change cue, so recheck the .pdf manual with that in mind and you'll likely find that.
BB
That's pretty much the only place you'll see a name change cue, so recheck the .pdf manual with that in mind and you'll likely find that.
BB
billbaker
Triton Extreme 88, Triton Classic Pro, Trinity V3 Pro
+E-mu, Alesis, Korg, Kawai, Yamaha, Line-6, TC Elecronics, Behringer, Lexicon...
Triton Extreme 88, Triton Classic Pro, Trinity V3 Pro
+E-mu, Alesis, Korg, Kawai, Yamaha, Line-6, TC Elecronics, Behringer, Lexicon...
-
- Approved Merchant
- Posts: 677
- Joined: Fri Dec 11, 2009 9:10 am
- Location: Bucharest
- Contact:
-
- Platinum Member
- Posts: 2206
- Joined: Wed May 31, 2006 11:56 pm
- Location: Vienna, Virginia, USA
- Contact:
@ Dan,
That sounds like the same convention that the Kronos is following, namely that the pattern, either self-written or imported, has to be in the sequencer or RPPR before it can be saved as a user pattern, at which point the usual name and save routine comes into effect.
The good news there is that you can download MIDI drum patterns from pretty much any source - 'net, your sequencer, extracted percussion tracks from MIDI files, instrument performance files, etc. - and turn them into Drum Track files.
- - - - - - - - - - - -
Next logical question is: does the user pattern playback want to see patterns as a monolithic (all drums on one track) or split up set of tracks @ one track per drum.
I think I read somewhere it all had to be on a single track in order to be successfully saved as a User Drum Pattern. If that's the case, importing from a multi-tracked kit would mean merging the tracks first.
BB
That sounds like the same convention that the Kronos is following, namely that the pattern, either self-written or imported, has to be in the sequencer or RPPR before it can be saved as a user pattern, at which point the usual name and save routine comes into effect.
The good news there is that you can download MIDI drum patterns from pretty much any source - 'net, your sequencer, extracted percussion tracks from MIDI files, instrument performance files, etc. - and turn them into Drum Track files.
- - - - - - - - - - - -
Next logical question is: does the user pattern playback want to see patterns as a monolithic (all drums on one track) or split up set of tracks @ one track per drum.
I think I read somewhere it all had to be on a single track in order to be successfully saved as a User Drum Pattern. If that's the case, importing from a multi-tracked kit would mean merging the tracks first.
BB
billbaker
Triton Extreme 88, Triton Classic Pro, Trinity V3 Pro
+E-mu, Alesis, Korg, Kawai, Yamaha, Line-6, TC Elecronics, Behringer, Lexicon...
Triton Extreme 88, Triton Classic Pro, Trinity V3 Pro
+E-mu, Alesis, Korg, Kawai, Yamaha, Line-6, TC Elecronics, Behringer, Lexicon...