Ableton Forum

Hi,

Thanks, I'm too just getting crazy with this issue while recording midi ! I thought my controller was the issue too . Using Live 11.0.xx and Minilab MKII. Effectively if you disable "Chase Midi Notes" it's a bit better but seems not as effective as using monitor "In" instead of "Auto" ?

Waiting to see any fix by Ableton, I'll submit a ticket !
Best

Just received the following from Ableton support. Fixed in beta 11.1.x
Did not test yet.

Thanks for contacting Ableton Tech Support. This issue you have encountered has been addressed in the latest Live 11 beta version:
Strange MIDI monitoring double-triggering bug
More information about this release can be found in the Live 11 Beta Release Notes.
If you're interested in using the beta, you can sign up here. If not, no problem! In this case, simply wait for the next official version to be released and the fix will be included.

Please note:
If you plan to use the Live 11.1 beta and are currently running an Apple Silicon/ARM/M1 machine, please review the following message from our QA team. You will have to sign in/ sign up via Centercode to view this message.
In addition, as always, all Beta related issues should be reported in Centercode.

The dbl-trigger issue is still there in the latest 11.1b6, nothing to do with Chase MIDI. Maybe that was another issue, i dunno. This one's older than Chase MIDI feature.

Record-enable the track, set monitoring to Auto, disable Chase MIDI, enable Record Quantization at Quarter-note, and play a note into a recording clip, triggering it on the off-beats. As you do, you'll hear the quantized note and your own off-beat notes trigger.

Just uploaded this vid (unlisted) to show the issue:
https://www.youtube.com/watch?v=jtXtiI56wZA

garyboozy wrote: ↑

Mon Nov 08, 2021 11:20 am

The dbl-trigger issue is still there in the latest 11.1b6

And it's filled on Centercode, right?

it's an old prob, not specific to the beta, so nope.

Ah ok. So support is aware? Did you ever report this?

garyboozy wrote: ↑

Mon Nov 08, 2021 11:20 am

Just uploaded this vid (unlisted) to show the issue:
https://www.youtube.com/watch?v=jtXtiI56wZA

I watched the video. You played 1/8 Notes with a 1/4 Quantization. That will fail.
Maybe the bug is fixed after all?

Please explain

Been having this double-trigger issue for years, but I work around it with a M4L Device called Clip Quantize Mapper which lets you map a midi button or key to quantize specific tracks at specific values. Just drop the device on a channel before your instrument, turn off the Record Quantuzation in ableton, and you’re good to go. You have to have the channel selected in order for it to work (if you just recorded a drum rack loop, but then switched to another channel, you have to select the drums channel again. basically it will quantize the currently selected clip in whatever track you are on, provided there is a Clip Quantize Mapper device on that channel). What I do is have one on every channel, and it’s great because you can have different quantize values per track. I then map a single midi button to all of them.

Setting monitor to “In” does work too but then you have to manually change back to Auto to hear the midi clip you just recorded.

Turning off Midi Note Chase solved the double trigger problem for me.
Latest Live 11.0.12
Thanks for the tip (even when it don't solves the problem for everybody here...weird)

My question is, is there a version that does not have this problem or has it always existed and nobody knew about it?

Daniel.Pro-13 wrote: ↑

Fri Aug 19, 2022 12:37 am

My question is, is there a version that does not have this problem or has it always existed and nobody knew about it?

It's been fixed if I remember well. Which version are you using?

I see this happen with quarter and eighth note (record) quantization even with MIDI Chase disabled.

In fact, it happens with Monitor Off, as I play random crap, most notes are just recorded (not played), but once in a while some will actually play (I guess those are the ones people will hear as double notes), which should not happen AFAIK.

It is almost like they are moved to the "future", that is, to the right too much.

Windows 10 and Live 11.2b8 (happens in 11.1.6 too).

Oh, and I was using the Computer MIDI Keyboard to test, not an hardware controller.

[jur] wrote: ↑

Wed Aug 31, 2022 5:01 pm

Daniel.Pro-13 wrote: ↑

Fri Aug 19, 2022 12:37 am

My question is, is there a version that does not have this problem or has it always existed and nobody knew about it?

It's been fixed if I remember well. Which version are you using?

I had tried all the versions and in all the same problem. Maybe another problem was solved but unfortunately not this one.

I'm certainly a newbie, but this doesn't make sense to me.

When I make a MIDI recording with quantization, on the hits where I fail and the system quantizes me, I can hear the sound twice although only one note is actually recorded.

This may be acceptable for a studio recording, but if you wanted to do a live loop session, you would be hearing these "ghost notes." If I turn off quantization (or quantize to a figure higher than a 4th), this stops happening because The system does not "move" my notes and therefore I do not have "ghost notes"

Video with quantization
https://www.veed.io/view/0c73247e-404b- ... anel=share

Video with no quantization at all
https://www.veed.io/view/27ebec0f-b69a- ... anel=share