Ableton Forum

OK, so I haven't changed anything obvious but now its working fine.
In fact better than fine because i can send and receive SYSEX using the same track, which Ableton claims is not possible!

ShelLuser wrote: ↑

Tue Dec 03, 2019 2:11 pm

Which brings me to: do you use Max embedded or as a separate setup?

See OP.
I should add, I have no problem sending SYSEX from a M4L device out of Live. Its just receiving it I can't get to work.

ShelLuser wrote: ↑

Mon Dec 02, 2019 6:54 pm

Live filters all those system messages. The amount of midi data which you can process is very limited in that regards.

not according to Ableton https://help.ableton.com/hc/en-us/artic ... in-Live-10

I'm sending a SYSEX message to Live, with only one MIDI track , and I can see the MIDI in indicator flash , but I can't detect any SYSEX using the sysexin object in a M4L device. I can receive these message okay in a max patch though. Any idea why I can't receive SYSEX? (I'm not sending any SYSEX ...

Fix the large latency (several hundred milliseconds) before the playhead moves when moving midi loop braces.

This problem has been around for years, but is highlighted by the loop brace moving features of Push. It needs to be brought into line with legato clip triggering, or overhauled so that you ...

The Ableton Push makes a feature of the ability to move loop braces on drumrack midi clips, which invites you to use loop changes musically.

Unfortunately loop braces changes only move the playhead with a fixed latency of up to 250ms, and the change is not quantised.

This means that to change a ...

When I enter data from the Push to a M4L interface object such as live.dial or live.number with a small number of steps, the object doesnt always display the same value as the Push. There is no problem with live.tab

I can't work out how to fix this - seems like some kind of rounding error. My ...

URL?

if you want to start a pattern with the first beat you have to hit the button between 4 and 1 (which works).

Since with a low tempo 1/16th play a role, it looks like the whole thing is dependent on the tempo.


If I want to start a new loop on the first beat I have to trigger it at least 250ms ...

Checked it again and if you set the tempo to 20 bpm it looks like it's quantized to 1/16th notes. Since global quantization hasn't an effect on the pattern selection, I guess that quantization is hard coded in the Push midi remote scripts.


Do it at a higher BPM and you'll see that interval is ...

Normal. Push warns you when you change it to -20 "WARNING: Low threshold may cause stuck pads"

OK, according to this post https://forum.ableton.com/viewtopic.php?f=35&t=146837&hilit=+loop+length+quantize
from 2010, there was a problem with controlling the play position from M4L, which appeared to be a problem on Live's end.
It was first described here http://cycling74.com/forums/topic/move ...

You can further mutate the response using the midi compression device

1. make sure Repeat is off
2. make sure Auto Select on the drum rack is off (see here for more infos: https://forum.ableton.com/viewtopic.php?f=55&t=197026, https://forum.ableton.com/viewtopic.php?f=55&t=197042)


No, that makes no difference at all to the latency in selecting a new pattern.

Its ...

I should add the patterns change near instantly if the transport is not running. When transport running the pattern takes 250-500ms to change. Any ideas?