Device Details

What exactly makes you believe that sending messages via M4L-Send/Receive has zero latency?

Sorry it isn't explained well.

The sender device sends the exact transport time with the midi note event.

The receiver device has a defined latency of 512 samples which means it receives the events 512 samples before they need to be sent out. It then just delays them by the necessary amount of time.

I have tried several other MIDI routers as well and this is the only one with zero latency. Also the MIDI through is a great addition. Good job with this one!

I have one request, would it be possible to add more IN / OUT channels?

I am having an issue with this device. When the device is ON, it does not send the sustain midi signal. Any recommendation?

does this make any difference if you're playing in midi notes live with a keyboard, as opposed to using a midi hardware sequencer or something?

Looks very very close to me, but when I'm routing midi from 1 channel to another, then outputting that midi to another channel to record/check it, there **does** seem to be a slight bit of latency. The source and recorded midi notes don't quite line up.

Agree with latest post, there is a slight latency I have not been able to get rid of. The thing is that when transport is sampled, there still are some actions to be done before outputting the note, and we have no control on these actions whatsoever.
Replaced transport par plugsync~ that is supposed to be very accurate and revamped the architecture to have it occur exactly on time, but I still have around 0.5ms of latency no matter what. Does not happen when using Live's builtin arpeggiator sending out midi to another channel. I've ended up quantizing record to 1/32nd on target track which is accurate enough for my needs.
Maybe there is somewhere a m4l function to bang at a specific time the midi out message ?

Wondering btw if the remaining latency is not linked to vector size, not sure as there is some jitter on it anyway. I guess that's one of the limitations of M4L to be a hassle when it comes to latency compensation.

Hey! I haven't checked these devices for a long time. Can you send me a message to thomas@voodoohop.com if you have any specific features/questions/bugs?

Hi, really a nice concept and it works great when the Ableton buffer size is set to 512, but as soon as I change it to a higher like 1024, the MIDI gets latency. So I was wondering if this could be made to be set dynamically. Thanks!

Hi, I really like the device, is there any chance to also send pitch bend information as well?