Ableton Forum

http://www.mediafire.com/?6uw4fl3u39n250w

here is a video of the demonstration of it missing the first note.

over %50 of the time it misses it and does not record it.

does anyone know what the issue is here?

how to fix it?

Sorry if the link doesn't work but I updated firmware and thought the problem went away but it still exists.

same problem here. first note also missed off when using note repeat..

Have you tried holding a pad down and then hitting the record button? It is a little tricky I will admit but if you just hold the pad down once it cycles through (if overdubbing or in fixed length recording) it places the missing note on the second run..

yeah it can record but seems to have an aversion. This must be a bug? Try this..no swing. hit repeat on 16ths and record in.. doesn't record on first step..?

Having the same problem here in repeat mode, absolutely refuses to catch the first note even on the next time round the loop.
it will only record the first note using repeat if you hold down your note before you start recording a new clip.
It behaves this way in drum racks and instruments.
anyone had any ideas yet?

What do you have your global quantize set to? It wasn't set to a bar from what I can see?

Not sure if we are having the same problem: When my first note in Repeat Mode was left away, I saw that all MIDI events were also recorded a tiny little bit too early. The latency compensation must have done something wrong.

In a very basic setup, everything worked fine. When I added an instance of U-He's DIVA, the Repeat Mode got unusable due to the wrong MIDI timing.

I spoke to Ableton's technical support today. They didn't know what was causing this problem but recommended to turn off Reduced Latency When Monitoring. This solved the problem. MIDI events recorded in Push's Repeat Mode are perfectly on the grid now. The first note gets recorded every time. Give it a try and see if it helps in your case too.

You sir are a genius!! That solved the problem instantly although not quite sure why.
Must be a bug due to the latency compensation settings.
hopefully ableton will get this sorted soon, but this is great as a temporary work around.