m theo

I've looked in the forums but quite haven't quite found my answer to this, and between being both crazy sleep-deprived and ignorant of the finer points of scheduling, I could be missing something obvious...

I have a patch with two different components. The first is driving three Arduinos connected to three serial ports (through a hub). That part of the patch wants to use metro with overdrive (motors run smoothest, good sensor values, etc).

The second part of the patch is controlling lights via DMX, and uses jitter matrices extensively for fading between colors, etc. That part of the patch wants to use qmetro with overdrive off (smoothest behavior).

I could extract the relevant parts and post them (super time-pressed, or I would have done that already), but the above pretty much sums it up. I could trigger everything from one central metro, if only the two components of the patch played nicely together.

Is there some way for me to send bangs from a vanilla metro over to the jitter heavy side of the patch, but have that part of the patch behave as if it is running under a qmetro with overdrive off (even though it is in fact on)?

The second part of the patch is controlling lights via DMX, and uses  jitter matrices extensively for fading between colors, etc. That part of the patch wants to use qmetro with overdrive off (smoothest behavior).

jitter-qmetro-overdrive-redux

thanks, Rob...I had tried that, but it didn't solve the overdrive issue for that component of the patch...I realize that this is pretty much impossible to weigh in on without me posting the relevant parts of the patch—I'll repost when I'm less in the thick of it and have a chance to break things out more...

jitter / qmetro / overdrive /redux