Dubstep drum programming

[TherapyBE]

I'm having the same problem as the TS, only I am working in FL Studio 8.
Can someone maybe help me out ?

ez

[oregon1]

I think everyone just did

[smutek]

Anybody using an electronic drum kit these days? i get really irritable using a keyboard for drumlines they just make less sense in the aftermath.

Yes, using an Alesis control pad to send midi to Ableton live.

Was ready to smash it against the wall yesterday but decided I'm going to sell it instead. It's just not for me. Saving for an HPD-15 now.

[lilt]

10 midi dubstep drum loops to load up and see who they are placed on the piano roll:

http://nzdubstep.com/forum/?forumaction ... 40&start=0

(download link in the first post on the right of that page)

[lowtek]

I highly recommend putting the reggae/dub "skank" noise on bar 4, 12, 20, 28 etc so you get used to that dubby rhythm. Once you get it down, it's no problem. It all lies in making the beat sound 70 bpm when it's really 140 bpm.

[darkbeats]

It all lies in making the beat sound 70 bpm when it's really 140 bpm.

to expand upon this, if you are using a step sequencer like fl and only creating a drums loop/group to export; it can be helpful to double your usual pattern length and double the project bpm as well, giving you 8 positions where you can place drum hits instead of the standard 4 steps per bar without having a bunch of piano roll channels going. good for situations where you want a bit more control over swing, ghost hits etc. but not as applicable or useful to linear sequencer users (again, piano roll). after you export, you can use soundforge ->special-> acid bpm tool to force the xx half tempo bpm back to the wave file by resaving the file. reload it in a slicer, rex, etc. and the fact you sequenced the loop at 280 instead of 140 is totally negligible. it's still going to sound like 70 bpm if you do it right.

the majority of the time you see this being done, it's primarily by producers writing really chopped up, glitchy idm or edit laden dnb in step sequencers. but it does give you an extra level of control over where your hits are really falling on the grid in any genre of computer music.

[slightlybored]

also worth mentioning is that you need to be patient.

dubstep is pretty complex to programme and get a groove but after a while, like most things it becomes really easy.

Practice makes perfect.

[TSDREX]

if your using reason.. put the kick on first, put a open hat on the 7th so it'll open the snare.. put the snare on the 9th and chuck some closed hi-hats..

[Dr_Driller]

It all lies in making the beat sound 70 bpm when it's really 140 bpm.

to expand upon this, if you are using a step sequencer like fl and only creating a drums loop/group to export; it can be helpful to double your usual pattern length and double the project bpm as well, giving you 8 positions where you can place drum hits instead of the standard 4 steps per bar without having a bunch of piano roll channels going. good for situations where you want a bit more control over swing, ghost hits etc. but not as applicable or useful to linear sequencer users (again, piano roll). after you export, you can use soundforge ->special-> acid bpm tool to force the xx half tempo bpm back to the wave file by resaving the file. reload it in a slicer, rex, etc. and the fact you sequenced the loop at 280 instead of 140 is totally negligible. it's still going to sound like 70 bpm if you do it right.

??? simply increase the quantification value will produce the same without changing bpm..