Ableton reads midi signals but doesnt send them to tracks.

[Yehia Fahim]

Hey guys! Please help me!!

So I encountered an unusual behaviour from Ableton midi signals. I have my midis plugged in as always.. And they're sending signals to Ableton and the small yellow box on the right top corner is flashing normaly. But somehow my midi tracks are not receiving any midi signals. I have my I/O on all ins.. All channels... Monitor is set to auto... Midi to: no output. I can see the line of dots (signal velocity) on the (all ins) flashing yellow.. But the main big line dotted bar is the one not receiving any signals! Therefore I can not record any midi notes.

* the midi/key mapping tools are working fine and I can use my midi knobs to record automations but the note keys are not working. Even my computer midi keyboard has the same problem. Help me please I can't record any midi lines!

Thank you for your time!
help help help

[Pitch Black]

In Live's MIDI preferences, make sure you have "Track" enabled for your MIDI controller.

[Yehia Fahim]

It's already enabled. All "tracks" are highlighted with yellow. And I've restarted Ableton several times.

[S4racen]

Arm your tracks?

Cheers
D

[Yehia Fahim]

They're armed... I also tried arming more than one track but no luck :/
Thnks

[scheffkoch]

...is a clip playing in the same track while you're trying to play this instrument?...and this while arrangement recording is enabled?...

[S4racen]

Nothing sounds correct so delete your installation of Live and reinstall....

Then if still the same check the MIDI signals of the controller with a MIDI Monitor application...

Cheers
D

[kingbhudo]

I'm having the same issue and I while I haven't solved it yet myself, I've did notice the following that I thought might be useful;

When using my Alesis drum module, I experience the same issues as OP, the kit will send MIDI input messages and trigger notes in Ableton, but when recording, no MIDI data writes to the track.

However, when I use my Arturia Keylab 49 with otherwise identical Input / Output / Routing options, it works perfectly.

I confirmed this on a separate install on a different machine, so a reinstall didn't help me either.
It's very odd!

[57R34K]

When all else fails, I change monitor to in instead of auto. That fixes it for me every time

[mcavoym]

When using my Alesis drum module, I experience the same issues as OP, the kit will send MIDI input messages and trigger notes in Ableton, but when recording, no MIDI data writes to the track.

This thread is a bit old but your comment is fairly recent and I've been having the same issue with my Alesis module so after some digging I found out that the problem seems to be related to note on and off events and Live needing at least 10ms between those. I found a fix - it's not ideal but it does work!

Create a MIDI track and choose your kit as the input signal. Change Monitor from "Auto" to "In". Put a "Note Length" MIDI effect on that track and leave it. Create a second MIDI track, choose your first MIDI track as your input signal and then you should be good to go. The MIDI notes will be long enough for Ableton to be happy and you'll be able to record whatever you want! This worked for me so hopefully it'll work for you and whoever else reads this!

[LaurentAs]

Got the same issue or a similar one under Live 11.2.7 (Monterey/Intel), trying to receive midi notes from my Virus TI2, processing them (like making an arp out of them) and sending these processed notes back to the Virus for playing.

It kinda works for a moment, but at any instant it just stops working, and then, though the orange square top right is blinking while I press notes on the keyboard, meaning that Live actually receives something, it just seem to ignore it as nothing happens on the listening track (I've added a midi monitor outside Live, that shows my notes are received), and a midi monitor on the track receives nuts. Makes the whole DAW unuseable in a Live (!) context to me.
To unlock the keyboard I need to get into midi preferences, deactivate the midi in / track for the Virus, wait a bit and activate it back.
If I change preset in the Virus, it instantly stops working.

Any clue or investigation would be welcome.

P.S BTW the exact same workflow works perfectly under Bitwig, with the same routing so it's NOT a HW configuration problem.

[elgeorge]

I am having the same issue with a push 2 and an arturia keylab 61. The tracks reproduce the sound for a few seconds and then it just stops working. To make it work again I have to change some setups, but it will only work for a few second.

Did anyone get a solution to this?

[Klangraum]

Same issue here with version 11.2.10. MIDI is received, but no connection to an instrument track. The solution was to switch off-on the MIDI driver output in preferences. It seems to fail a correct MIDI driver initialization at startup. However, latest version 11.2.11 seems to work fine.

[ekoraytascilar]

Having the same issue on Live 11.3.13 running on Windows 10 with a Roli Seaboard2. I already have a Studiologic SL88 and the Push2 connected and they work perfectly fine. In fact this also happens occasionally with the Studiologic. But with Roli it is most severe and frequent. In some sessions Roli runs for some time but than stops sending MIDI to the track, although I see midi Signal being received in the top right corner. I changed cables and USB ports to no avail. Unplugging and replugging ROLI temporarily fixes the issue but it comes back in a few minutes. When I use Roli with the Equator synth in the standalone mode (at the very time this problem occurs in Live) it works just fine. This looks certainly like a glitch with Live.

Hope someone looks into this issue!

[FreshHumanFish]

Hi, I don't know if this helps but have you tried setting "Control Surface" to None in the settings.

I had the same issue and doing this made the signal go through, although it is not what I want, because I want to be able to use the Control Surface script.