Forums > Max For Live

live.remote~ HUGE latency, Beware!

July 15, 2012 | 2:58 pm

Just to let you know the latency of live.remote~ object is way bigger than specified in the manual.

According to the manual:
"Integer or float values are send into left inlet of live.remote~, as messages or as an audio signal. The values are applied sample-precise (if sent by the audio thread of Max) with a constant latency of a single audio buffer. " < - It's a lie!

According to my measurements the real latency = audiobuffer*2+2
for a 5 ms output buffer you have 12ms of a delay on a live.remote~
for a 10ms output buffer you have 22ms of a delay, an so on…

I wanted to make a precise envelope generator but with that huge delay it’s pointless.


July 15, 2012 | 6:42 pm

I can confirm your measurements and would appreciate some official comment on this.


July 15, 2012 | 8:20 pm

We’ll need to see how you are measuring this.

-A


July 15, 2012 | 9:17 pm

To see this issue you will need the following setup in Ableton:

1st channel square mono(or any other LFO) waveform panned to right
+ Max audio plugin routing the right channel: plugin~ –> live.object~ –> mixer volume of 2ch
2nd channel constant mono waveform with max value (1) panned to left
3rd channel record from the master (you will see a delay between left 1st and right 2nd channel)

Just press record, play and zoomin on the recorded waveform so you will see the delay is way longer than expected.

If you need me to send you my ableton project file just PM me with your email address.


July 15, 2012 | 10:18 pm

I’ve measured by transferring a message between numboxes and print cpuclock on each side.


July 16, 2012 | 12:12 am

@oomek sounds to me like you are measuring MFL device latency.You’ll need to find a way to rule that out of your test.

@broc tests like these have to stay in the audio domain to be accurate.

If you wish to report a bug, please include example projects with devices, full details and system information to

support @ cycling74 dot com

Thanks

-Andrew


July 16, 2012 | 8:56 am

Andrew,

can you please explain the M4L device latency in more detail.
It seems not mentioned anywhere in the documentation.


July 16, 2012 | 9:43 am

Yeah, what exactly is M4L device latency :/ ? and why it affects live.param~ so badly ?


July 16, 2012 | 10:11 am

I’ve sent the project files.


July 16, 2012 | 11:19 am

It appears the latency is inconsistent and not depending strictly on the audio buffer.
i.e. for an audio buffer of 50 ms the overal live.param~ latency is only 94.5ms


Viewing 10 posts - 1 through 10 (of 10 total)