Olaf Matthes hat gesagt: // Olaf Matthes wrote:

Hi, do you mean midi timing clock (start / stop / continue) or midi timecode (MTC)?

You could try:

[metro 10] | [251{ <--- message box | [midiout]

251 is the decimal value of 0xFB, the continue message. Start with 250 and stop with 248. 'midiout' sends plain midi data, there's no 'midiin' equivalent under Win...

But if it was, like on Linux, can I read MTC messages like this??

[select 251 248] | | [s continue] [s stop]

You might want to use 'pulse' from maxlib v0.3 instead of metro as it allows input in beats per minute. [pulse 120 1 96 0] should give the right clock for 120 bpm for example.

A very useful external, I didn't know yet. It has a small zero-division bug, a quick fix is this change in line 34:

if (x->p_tempo * x->p_durdenom != 0) x->p_mspbdenom = x->p_tempo * x->p_durdenom;

ciao,

Frank Barknecht _ _______footils__

Frank Barknecht schrieb:

Olaf Matthes hat gesagt: // Olaf Matthes wrote:

...

You might want to use 'pulse' from maxlib v0.3 instead of metro as it allows input in beats per minute. [pulse 120 1 96 0] should give the right clock for 120 bpm for example.

A very useful external, I didn't know yet. It has a small zero-division bug, a quick fix is this change in line 34:

if (x->p_tempo * x->p_durdenom != 0) x->p_mspbdenom = x->p_tempo * x->p_durdenom;

Thanks for the bug fix, I've added this and uploaded maxlib as version 0.3b to the usual place:

http://www.akustische-kunst.de/puredata/maxlib/

Compared to the 0.2 release there are two new buffer (fifo and lifo) objects, the pulse object mentioned above and the minus / plus / divide / multi now take up to 32 arguments...

Olaf