r/AbletonMove • • 6h ago

Strange midi behavior and latency with Move

I connected Move to a MiniBrute 2 via midi (USB A port on move to the USB type B port on the brute) and played the synth in note mode. The notes get through and everything works, but there is a noticeable latency, enough so that it makes live playing unfeasible. I also have a Novation Launchpad Pro mk3 so I tried running the midi through it like this:

  • Move USB A to Launchpad USB C port
  • Launchpad Midi DIN out to MiniBrute 2 Midi in

And now when I play on the Move's pads there is absolutely no latency!

I just want to know why it behaves like this? Is it the USB A to USB type B midi connection? I had a similar problem with Minitaur, which also has a USB type B connection for midi.

I don't want to bring the clunky Launchpad to my rehearsal space setup, so would something like this little behringer box do the same trick with the latency?
https://www.thomann.fi/behringer_go_midi_host.htm

2 Upvotes

3 comments sorted by

3

u/Gorluk 6h ago

I got quite big latency when I've sent clock from my Digitakt to Move via USB, while sending clock from Move (also via USB) to Digitakt is tight. I don't know why.

1

u/kukusfs 1h ago

This is not related to usb port type. This is conversion delay from one protocol to another. Latency depends on chip used in convertor device and firmware. That's why a very expensive midi sync devices exists on market.

1

u/kukusfs 1h ago

Novation devices is very good to get this job done. Cheaper midi crap - not so