Hello noeguer,

Thanks for commenting!

What you need to understand is that *any* two devices will eventually go out of sync. That is why midi has clock sync function, and why audio recorded separately from video almost always goes out of sync unless the timing is synched via some sort of protocol.

All hardware uses timing crystals to keep time and all have margins of error. It's often just a matter of how good the timing crystal is and how well its calibrated.

That "real hardware device" may have a cheap timing crystal or some programming errors. I once had a Dr Rhythm drum machine with hideous timing :) You may want to check both tempos against logic on a Mac which should be pretty accurate.

My algorithm makes the tempo as accurate as the processor clock, which is all one can do. you can't get anymore accurate on iOS without slaving to a MIDI clock sync from a master device.

Trust me, this algorithm is as accurate as any iOS metronome, and is more accurate than the algorithms many use.

Cheers,

Gary

You virus TI and the clock of every other device will all go out of sync by some fractional degree over time. It's just how electronics work.

I also looked into building a hardware version... and believe me the cost of the crystal goes up considerably with higher accuracy and yet still there is a margin of error, and calibration is required which will improve the error, but two hardware devices using different quartz crystals and different programming and calibration will go out of sync. That is why you often see video out of sync with audio even in broadcast situations.

What I can say is, you are quite welcome for the algorithm. I hope you do great things with it. There is no better way to get better timing on iOS, or any platform for that matter, without some kind of MIDI clock sync signal.