newtfish

I'm a bit confused about the options for metro. For me, anything lower than 1ms seems to just stick to 1ms.

For instance, it's possible to have the option [metro @interval 1], which I'm guessing should be 1 sample? However, there seems to be no different to the speed of this and [metro 1] (which is 1 ms)

Same thing if I use [metro 0.01] (can I even use float in terms of ms?

Any thoughts would be gratefully received.

whats-the-fastest-speed-metro-can-handle

1ms is the minimum. You have to go with MSP objects to get signal rate and even then you're limited to to vectors. Gen is the way to get single sample resolution.

Thanks Stringtapper. Im wondering is there a way I can create something similar to a metro using other objects, but just making it faster? Would I use signal rate objects for this to get it down to 1 sample?

AS stringtapper said, even if you use signal rate objects, you're still limited by the vector size of Max.The only way to get sample accurate precision in Max is by using Gen.

https://cycling74.com/wiki/index.php?title=MSP_Sequencing_Tutorial_1:_Audio-Rate_Sequencing

I haven't seen anyone make a single sample resolution sequencer with Gen but I guess it could be done.

when you need 0.5 milliseconds you can also use 2 metros. :)

I'm wondering what the contraption is that needs to be banged at this rate, though?

Thanks to everyone for your helps on this.

For Wetterberg, here is the patch Im using it on. I think I found this in one of Broc's posts. It queues rapid iterations quite well (to slow them down). However, unfortunately, when it uses the metro it could be a little faster.

I wonder how using two metros together could work in this scenario? Surely you would have to start one 0.5 seconds after the other?

Is there a reason not to do [sel 1] instead there?

Hi Wetterberg, Thanks for the suggesting Sel 1, it is a little better than not queuing at all, but still the messages are coming out too fast and some are being dropped (this is not a limitation of max, but something else I have no control over). Metro does seem to work, but it would be great if I could speed it up just a little bit.

There's no need for uzi, since the patch forms a feedback loop that iterates through itself.

well, actually, one might not really need a steady metronome at a rate higher than 1 ms, but one might need 2 bangs witha given difference of a certain speed. however, both can always be done by using [del 0.5]

a simply delay also will be enough to create a steady rate at 1/n milliseconds:

button
|
del 0
|
metro 1
|    |
|    del 0.5
  |
[...]


What's the fastest speed metro can handle?