Device Details


Overview

Name | Version: Latency Meter 1.0
Author: T0n1
Device Type: Audio Effect
Description: Latency Meter is a simple M4L Live Set for measuring the latency of external audio or midi plugin devices and audio interfaces. To use it, download the LatencyMeter Live Project from the download link, the combination of several devices is the actual meter software - MeterAudio.amxd here is only one of several devices.

For audio plugin latency measurement, replace the M4L example device chain in the Audio Test Route track, for MIDI plugin latency measurement, do the same with the Midi Test Route track.

For audio interface latency measurement, select one of its channels in the Audio Out and Audio In tracks and directly connect them with a cable. For stereo channels, one cable suffices.

Hit play to start the measurement. The M4L devices in the Audio Meter, Midi Meter, Audio Interface Meter tracks respectively display the measured latency in ms.

MIDI plugin latency is measured with two distinct notes, therefore make sure that the same notes are passed by a measured plugin. Audio plugin latency is measured with a click and the left/right difference, therefore it must not distort or even delay the input.

Details

Live Version Used: 8.4
Max Version Used: 5.1.9
Date Added: Apr 01 2013 04:41:35
Date Last Updated: No Updates
Downloads: 899
License: AttributionShareAlike
Average Rating (1)

Log in to rate this device

5

Files

Device File: MeterAudio.amxd
 


Comments

very useful!
thanks
Could you post an Instruction? I cant wrap my head around how this i supposed to work, it always shows 0ms.
The device itself is useless outside the context of the Live Set from the download URL with its Audio and MIDI Test Route. I developed it after experiencing unexpected latency with M4L device chains, as opposed to internal devices like Utility.
I'm still on Live 8, but if I remember correctly, the "Live Sets that contain Max for Live devices or third-party plug-ins now have lower latency" change introduced in Live 9.2 is said to have fixed that problem: buffer read/write cycles are no more performed sequentially on a single device-to-device basis for each cycle, but the whole chain is processed within one cycle, thus the latency for one device is the same as the latency for a multiple device chain - and the example Live Set contains exactly such a long chain.
But for measuring the internal latency of a plugin or the latency of external hardware, the tool should still be useful.
Thanks, still works like a charm!

Login to comment on this device.

Browse the full library