rossmalone@gmail.com

I've made a 16 step sequencer where the tempo is controlled in milliseconds.

I want to change this to BPM but I don't know the equation to do so. 

Hey everyone!
I've made a 16 step sequencer where the tempo is controlled in milliseconds.
I want to change this to BPM but I don't know the equation to do so. 
If anyone can help, please do!
thanks a lot,


millisecond-to-bpm-conversion

not sure if this is entirely accurate, but it works...

> I've made a 16 step sequencer where the tempo is controlled in

> I want to change this to BPM but I don't know the equation to do so.

On 12/01/2008, Ross Malone  wrote:
>
>
> Hey everyone!
> I've made a 16 step sequencer where the tempo is controlled in
> milliseconds.
> I want to change this to BPM but I don't know the equation to do so.
> If anyone can help, please do!
> thanks a lot,
>

Is this the calculation for an entire bar?

If so, If i multiply my millisecond metro by 16 and put it into the patch, it should work?

Thanks!
Is this the calculation for an entire bar?
If so, If i multiply my millisecond metro by 16 and put it into the patch, it should work?
Thanks again


It calculates the metro interval into single beats per minute. If your metro

is ticking every 500 milliseconds, then that is 120 beats per minute.

(though for some reason it rounds it down to 119, you might need to try

putting a float number box at the end of that, will probably give you 120)

> Is this the calculation for an entire bar?

> If so, If i multiply my millisecond metro by 16 and put it into the patch,

It calculates the metro interval into single beats per minute. If your metro
is ticking every 500 milliseconds, then that is 120 beats per minute.
(though for some reason it rounds it down to 119, you might need to try
putting a float number box at the end of that, will probably give you 120)

On 12/01/2008, Ross Malone  wrote:
>
>
> Thanks!
> Is this the calculation for an entire bar?
> If so, If i multiply my millisecond metro by 16 and put it into the patch,
> it should work?
> Thanks again
>

There are some rounding errors in your patch. Try this.

> not sure if this is entirely accurate, but it works...

> #P number 167 173 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 167 91 78 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P comment 167 74 61 196617 milliseconds;

>> I've made a 16 step sequencer where the tempo is controlled in milliseconds.

>> I want to change this to BPM but I don't know the equation to do so.

There are some rounding errors in your patch.  Try this.

> not sure if this is entirely accurate, but it works...
>
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P comment 167 191 61 196617 BPM;
> #P number 167 173 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 167 144 47 196617 * 1000.;
> #P newex 167 119 37 196617 !/ 60.;
> #P number 167 91 78 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P comment 167 74 61 196617 milliseconds;
> #P connect 3 0 4 0;
> #P connect 2 0 3 0;
> #P connect 1 0 2 0;
> #P window clipboard copycount 6;
>
>
> On 12/01/2008, Ross Malone
>  > wrote:
>>
>> Hey everyone!
>> I've made a 16 step sequencer where the tempo is controlled in milliseconds.
>> I want to change this to BPM but I don't know the equation to do so.
>> If anyone can help, please do!
>> thanks a lot,
>>
>
>

Cheers
Gary Lee Nelson
Oberlin College
www.timara.oberlin.edu/GaryLeeNelson


Yeah, using a float number box seems to solve it. Strange that the two

number boxes receiving the same number display different integers.

> There are some rounding errors in your patch. Try this.

> #P number 206 235 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P flonum 264 173 87 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P flonum 263 90 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 113 235 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> On 1/12/08 7:00 AM, "Joe Bicker" wrote:

Yeah, using a float number box seems to solve it. Strange that the two
number boxes receiving the same number display different integers.

On 12/01/2008, Gary Lee Nelson  wrote:
>
>  There are some rounding errors in your patch.  Try this.
>
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P comment 206 253 61 196617 BPM;
> #P number 206 235 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 187 197 27 196617 + 0.5;
> #P flonum 264 173 87 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P flonum 263 90 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P comment 113 253 61 196617 BPM;
> #P number 113 235 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 167 145 47 196617 * 1000.;
> #P newex 167 119 37 196617 !/ 60.;
> #P number 167 91 78 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P comment 167 74 61 196617 milliseconds;
> #P connect 8 0 9 0;
> #P connect 3 0 4 0;
> #P connect 3 0 8 0;
> #P connect 3 0 7 0;
> #P connect 6 0 2 0;
> #P connect 1 0 2 0;
> #P connect 2 0 3 0;
> #P window clipboard copycount 11;
>
>
>
> On 1/12/08 7:00 AM, "Joe Bicker"  wrote:
>
> not sure if this is entirely accurate, but it works...
>
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P comment 167 191 61 196617 BPM;
> #P number 167 173 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 167 144 47 196617 * 1000.;
> #P newex 167 119 37 196617 !/ 60.;
> #P number 167 91 78 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P comment 167 74 61 196617 milliseconds;
> #P connect 3 0 4 0;
> #P connect 2 0 3 0;
> #P connect 1 0 2 0;
> #P window clipboard copycount 6;
>
>
> On 12/01/2008, *Ross Malone*
>   > wrote:
>
>
> Hey everyone!
> I've made a 16 step sequencer where the tempo is controlled in
> milliseconds.
> I want to change this to BPM but I don't know the equation to do so.
> If anyone can help, please do!
> thanks a lot,
>
>
> ------------------------------
>
>
>
>
> Cheers
> Gary Lee Nelson
> Oberlin College
> www.timara.oberlin.edu/GaryLeeNelson
>
>
>

If you are applying the bpm to tempo, I suggest keeping the fractional part.

> Yeah, using a float number box seems to solve it. Strange that the two number

> boxes receiving the same number display different integers.

>> There are some rounding errors in your patch. Try this.

>> #P number 206 235 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>> #P flonum 264 173 87 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>> #P flonum 263 90 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>> #P number 113 235 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>> #P number 167 91 78 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>> #P comment 167 74 61 196617 milliseconds;

>> On 1/12/08 7:00 AM, "Joe Bicker" wrote:

>>> not sure if this is entirely accurate, but it works...

>>> #P number 167 173 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>>> #P number 167 91 78 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

>>> #P comment 167 74 61 196617 milliseconds;

> Yeah, using a float number box seems to solve it. Strange that the two number
> boxes receiving the same number display different integers.
>
> On 12/01/2008, Gary Lee Nelson   wrote:
>> There are some rounding errors in your patch.  Try this.
>>
>> #P window setfont "Sans Serif" 9.;
>> #P window linecount 1;
>> #P comment 206 253 61 196617 BPM;
>> #P number 206 235 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P newex 187 197 27 196617 + 0.5;
>> #P flonum 264 173 87 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P flonum 263 90 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P comment 113 253 61 196617 BPM;
>> #P number 113 235 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P newex 167 145 47 196617 * 1000.;
>> #P newex 167 119 37 196617 !/ 60.;
>> #P number 167 91 78 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>> #P comment 167 74 61 196617 milliseconds;
>> #P connect 8 0 9 0;
>> #P connect 3 0 4 0;
>> #P connect 3 0 8 0;
>> #P connect 3 0 7 0;
>> #P connect 6 0 2 0;
>> #P connect 1 0 2 0;
>> #P connect 2 0 3 0;
>> #P window clipboard copycount 11;
>>
>>
>>
>> On 1/12/08 7:00 AM, "Joe Bicker"  wrote:
>>
>>> not sure if this is entirely accurate, but it works...
>>>
>>> #P window setfont "Sans Serif" 9.;
>>> #P window linecount 1;
>>> #P comment 167 191 61 196617 BPM;
>>> #P number 167 173 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>>> #P newex 167 144 47 196617 * 1000.;
>>> #P newex 167 119 37 196617 !/ 60.;
>>> #P number 167 91 78 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
>>> #P comment 167 74 61 196617 milliseconds;
>>> #P connect 3 0 4 0;
>>> #P connect 2 0 3 0;
>>> #P connect 1 0 2 0;
>>> #P window clipboard copycount 6;
>>>
>>>
>>> On 12/01/2008, Ross Malone
>>>  > wrote:
>>>>
>>>> Hey everyone!
>>>> I've made a 16 step sequencer where the tempo is controlled in
>>>> milliseconds. 
>>>> I want to change this to BPM but I don't know the equation to do so.
>>>> If anyone can help, please do!
>>>> thanks a lot,
>>>>
>>>
>>>
>>
>>
>>
>> Cheers
>> Gary Lee Nelson
>> Oberlin College
>> www.timara.oberlin.edu/GaryLeeNelson
>>
>>
>>
>
>
>

I prefer the following patch and keeping integers !

#P number 226 86 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

#P comment 309 237 114 196617 BPM or ms interval;

#P number 206 235 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

#P comment 315 90 109 196617 ms interval or BPM;

> If you are applying the bpm to tempo, I suggest keeping the 

I prefer the following patch and  keeping integers !

max v2;
#N vpatcher 100 100 700 500;
#P window setfont "Sans Serif" 9.;
#P number 226 86 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P window linecount 1;
#P comment 309 237 114 196617 BPM or ms interval;
#P number 206 235 83 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 167 162 41 196617 + 0.5;
#P newex 167 127 55 196617 !/ 60000.;
#P comment 315 90 109 196617 ms interval or BPM;
#P connect 5 0 1 0;
#P connect 1 0 2 0;
#P connect 2 0 3 0;
#P pop;
> Adding .5 rounds the result
>
> expr  $f1/60000.+.5
>
> Does it all in one object.
>
> If you are applying the bpm to tempo, I suggest keeping the  
> fractional part.
>
>

or maybe 60000 depending on what you count as a beat

On Jan 13, 2008, at 4:14 PM, Andrew Robertson wrote:

> or maybe 60000 depending on what you count as a beat

>
>
> In general,
>
> BPM = 30000/BEAT_IN_MILLISCONDS
>
> or maybe 60000 depending on what you count as a beat
>
>
> So in Max
>
> expr (30000/$i1)
>
>
>
>


Again, integer calculations can sometimes lead to gross errors in timing.

For example, with integer calculations, a 10 minute piece would be shorter

with a time interval of 333 ms compared to 334. That is a 1 ms error on

each of 1800 beats making an error of 1.8 seconds. And neither 333 or 334

accurately represents a precise tempo of 180 bpm.

Beats per minute is calculated with reference to intervals of 1000ms that

On 1/13/08 4:14 PM, "Andrew Robertson" wrote:

For example, with integer calculations, a 10 minute piece would be shorter
with a time interval of 333 ms compared to 334.  That is a 1 ms error on
each of 1800 beats making an error of 1.8 seconds.  And neither 333 or 334
accurately represents a precise tempo of 180 bpm.

Beats per minute is calculated with reference to intervals of 1000ms that
would result in 60 bpm

Cheers
Gary Lee Nelson
Oberlin College
www.timara.oberlin.edu/GaryLeeNelson

On 1/13/08 4:14 PM, "Andrew Robertson"  wrote:

>
>
> In general,
>
> BPM = 30000/BEAT_IN_MILLISCONDS
>
> or maybe 60000 depending on what you count as a beat
>
>
> So in Max
>
> expr (30000/$i1)
>
>
>


And pulse. Pulsemetro and my new favorite el.samm

http://www.maxobjects.com/?v=objects&id_objet=1550

this is the BPM2ms object by Karlheinz Essl, it comes in a set of objects that I've found VERY useful and have come to rely upon.

Millisecond to BPM conversion