Forums > MaxMSP

Midi Beat Clock

Sep 21 2009 | 10:57 pm

I was wondering if timing resolution is relative or standard. I thought it was 96 ticks per beat, but the transport says the resolution is 480 ticks/beat.

Can anybody offer some info on this?


Sep 22 2009 | 12:13 am

As far as I know it is actually 24 ticks per quarter note = 96 per bar if 4/4.

And is standard regardless of the tempo – faster ticks at faster tempo etc.

at least thats what is is on all of my midi equipment.

This is for clock timing – the speed of midi messages sent via knob movements is much faster.

Sep 22 2009 | 1:35 am

Right. That’s what I expected. I actually meant per bar. I wonder why the transport says 480 ticks.

Sep 22 2009 | 2:01 am

Many sequencers (in fact all that I know of) have a temporal resolution much finer than MIDI beat clock. I’d guess (though I’ve not even looked at it yet) that transport’s internal resolution is 480, though the MIDI beat clock is still standard at 24 ppq.

Sep 22 2009 | 2:58 am

While using translate and converting from ticks to bbu, the ticks are returned with this finer resolution of 480.

I need the return to be in the coarser resolution of 24 PPQ. Is this possible?

Would it be accurate to use a scale object to scale the 480 to 24 ppq? Or would it be better to design my own translate abstraction?

I ask this because i am performing bbu subtraction to locate positions in the time line of Ableton Live. Which itself only reports 4 ticks per beat in it’s transport but i am assuming that each one of those steps actually represents 24 PPQ.

Thanks for all of your help so far!!

Sep 22 2009 | 3:07 am

Not 100% sure what you are doing but I think modulo [%] should do the trick – however be careful – for if my maths and understanding of Max is correct – the data speed limit of max – 1ms will mean that 125 bpm will be the maximum tempo you will achieve before loosing discreet values at 480 ticks per quarter. There’s probably a better way.

Viewing 6 posts - 1 through 6 (of 6 total)

Forums > MaxMSP