MPC 1000 Delay vs. Renaissance Delay, part 2.

Hi,

As I found out ( viewtopic.php?f=36&t=166342 ), the Renaissance Delay that resembles the most to the MPC 1000 Delay is the Ping Pong Delay.

However, I'm lost with it's Time Parameters.

As described in the 1000 manual: "Time field: You can set the delay time of the first delay sound. If the Sq sync field is set to OFF, you can set it to the maximum 999 msec. If the Sq sync field is set to ON, you can set it with the Beat and the Tick."



On my 1000, to get the result I wanted, I put Sync "On", and I put the Time Value to 00.48, and all was perfect.

On the Renaissance's Ping Pong Delay, not only there is no way to Sync to the beat, but also, the Time Values aren't at all the same as the Time field on the 1000.

So after 3 hours, I ended up with these values to get approx. the same results than on the 1000:



I would LOVE not having to go through that again. Could someone explain to me how the Ren's Time Value work, and how I can with no time replicate what I did on the 1000 the next time I transfer a beat?

THANKS!

Have not tried it, but is the MPC Software delay time in milliseconds, so a time of 1000 is one second, and a time of 2000 is two seconds, for example?

If so, you would need to convert the number of ticks at the particular tempo into milliseconds.

SimonInAustralia wrote:Have not tried it, but is the MPC Software delay time in milliseconds, so a time of 1000 is one second, and a time of 2000 is two seconds, for example?

If so, you would need to convert the number of ticks at the particular tempo into milliseconds.

Ouah! Thanks, Simon!

Yes, the MPC Software's Delay Time is in Milliseconds.

What would be the calculation to convert the number of ticks at the particular tempo into milliseconds?

My beat is in 86 BPM.

On the 1000, I put the Sync to "ON", with the Time at "00.48".

So what would be the calculation to get the same thing with the MPC software with its L and R millisecond Time Values?

Thanks, again, man!

DSTR / deStar wrote:What would be the calculation to convert the number of ticks at the particular tempo into milliseconds?

My beat is in 86 BPM.

On the 1000, I put the Sync to "ON", with the Time at "00.48".

Maybe?...

1 tick = ( 60000 / (BPM * PPQ) ) milliseconds.

( 60000 / (86 * 96) ) = 7.267441860465116 milliseconds per tick.

At 48 ticks (1/8 note/beat) = 348.8372093023256 milliseconds.

DSTR / deStar wrote:So what would be the calculation to get the same thing with the MPC software with its L and R millisecond Time Values?

Not sure exactly what the MPC1000 delay is doing in terms of using the time value for different delay regenerations.

Maybe try 349 milliseconds on one side, and 698 milliseconds on the other, if you want a left/right stereo ping pong type affect, or both to 349 if you just want a single mono delay?

The calculator Lamp posted above gives you the millisecond value for various note/beat divisions.

Damn, guys! Thanks!

(Simon, I have to say I have nooo idea how this calculation works with its "PPQ" and "60000", but I swear I will look into it.)

DSTR / deStar wrote:Damn, guys! Thanks!

(Simon, I have to say I have nooo idea how this calculation works with its "PPQ" and "60000", but I swear I will look into it.)

60 is for 60 seconds, 60000 gives the result in milliseconds.

PPQ is the number of pulses (ticks) per quarter note that the sequencer uses, which in the case of the older MPCs is 96PPQ.

BPM x PPQ gives you the number of ticks in a minute, dividing 60000 by that gives you the number of milliseconds per tick.

SimonInAustralia wrote:

DSTR / deStar wrote:Damn, guys! Thanks!

(Simon, I have to say I have nooo idea how this calculation works with its "PPQ" and "60000", but I swear I will look into it.)

60 is for 60 seconds, 60000 gives the result in milliseconds.

PPQ is the number of pulses (ticks) per quarter note that the sequencer uses, which in the case of the older MPCs is 96PPQ.

BPM x PPQ gives you the number of ticks in a minute, dividing 60000 by that gives you the number of ticks in a millisecond.

Man... You rock. Thanks so much.

No probs, let us know after you test it, whether it gives the desired results, or not.

It works perfectly!

Sweet!

Will save you 3 hours every time you want to set it to a new value.

SimonInAustralia wrote:Sweet!

Will save you 3 hours every time you want to set it to a new value.

You have noooo idea!

DSTR / deStar wrote:Damn, guys! Thanks!

(Simon, I have to say I have nooo idea how this calculation works with its "PPQ" and "60000", but I swear I will look into it.)

Just divide your BPM by 60000. This will give you a number equivalent to 1/4 note delay. Divide that number in half and you get a number equivalent to 1/8 note delay. Divide that in half and you get 1/16 and so on. Setting your delay value to these multiples will give you an in-sync delay.

Divide by 40000 for triplets. 90000 for dots.

There's plenty of free delay time calculators in the App Store.