Programming in double time . . .

Been having some questions about this for a minute. Didn't see a point in using this method when I was soley using reason 3.0 cuz the resolution is already 64.

But i like the idea of increasing the MPC's resolution, but i tried that shit with some quantize and it was locking to odd spots on the grid, without quantize it was actually on beat, but i'm trying to see if anyone has any techniques with this method, besides practice cuz that goes without saying.

I don't feel its a necessity, but what do you think? Enlighten me

double time + quantize, double time without quantize, regular tempo, etc.

(I'm not really trying to hear 'do what feels good' cuz i'm not really trying to change what I already do, just tryn'a learn about the technique)

Lampdog wrote:HAHA 64. HAHA. I doubt that Reason is only 64 ticks per beat.


No matter what you trying to not hear, if you wanna learn them do them.
Try all the combinations of everything u cant think of. U don't have to change the way you make music, but if you wanna learn it you must practice it, even if you don't use the techniques in actual songs.

When you double the resolution you are doubling the amount recordable events in your sequence in comparison to whatever resolution you were using before. Simple.

Indeed indeed, to be honest i don't know what i was trying to say when i typed that thing about reason. . . maybe i meant i can get in there and change the snap to 1/64 as opposed to 1/32 trip. I dont even remember my thought process.

but yea the idea seems dope, guess i just gotta **** wit it a lil bit more, good lookin out

I mostly make beats around 75- 95 bpms unquantized when my pads were responsive. For kicks lately i been making my beats at 160 - 185 bpms... but if i do i usually quantize them at 1/16 ths. I did this just to see if it would work... and there is no spoon let me tell you. Its possible to retain that old boom-bap at high tempos cuz in the end its all in how YOU rock. When i finally get my pads working again... A silly D.I.Y job, very ghetto indeed. but as soon as i can get them somewhat back to normal Ill go back to making unquantized beats. for example check out "The Keys" on my space.

i use double quantise to get what becomes 192 tick resolution
just think in half bars instead of bars, etc.
gives you more places to move your sounds.

Antonym wrote:i use double quantise to get what becomes 192 tick resolution
just think in half bars instead of bars, etc.
gives you more places to move your sounds.

Yea i understand the thought process and the idea of it, sounds dope as hell, but when i tried it iono it came out sloppy the first couple times with quantize

what do you mean sloppy?
what do the ticks tell you? record something at 1/8 with 56% swing and describe the sloppiness

fasttrackpimp wrote:glad I used the search funtion to find this.

Example??? Either I already do this and dont know that I do and what to call it or Im f+cking lost................maybe a combination of the 2!

normal: 4 bars at 85 bpm
double: 8 bars at 170 bpm

Never mind ya'll, i don't know wtf i was doing at first. . . but I'm doin it perfectly now, without quantize.

thanks for the help tho!!!

Antonym wrote:normal: 4 bars at 85 bpm
double: 8 bars at 170 bpm

increasing the tempo from 85 to 170 doesn't make it 8 bars..

It's:

Normal: 4 bars at 85 bpm
Double: 4 bars at 170 bpm (Or 8 bars at 85 bpm)

I think antonym meant that you have to double the bars as well the tempo in order to keep the pattern the length you want it.
4 bars at 85 bpm =11.3secs
4 bars at 170 bpm =5.65secs
4 bars at 170 bpm. = 5.65secs = 2 bars at 85bpm.
8 bars at 170bpm = 11.3 secs = 4 bars at 85bpm.