Ableton Forum

jonljacobi wrote: ↑

Tue Feb 11, 2020 2:29 pm

“Or”, or “and”?

True

If the controller is Red in preferences, it means something else grabbed the port.
If another app that supports MIDI is running, you need to disable the Live port in that app.
If no other MIDI Apps are running, make sure all Chromium browsers are closed. WebMIDI can also grab MIDI ports.

It's because of the MIDI Routing panel in Audio/MIDI. It remembers every device, but you can just make a new profile or remove devices from the default one.

Freiin wrote: ↑

Sat Jan 18, 2020 5:32 pm

But i have read something about midi 2.0 and someone said it doesn't makes sense Ableton improve piano roll with no midi 2.0

The vote on the final spec is tomorrow!
https://sonicstate.com/news/2020/01/18/ ... s-midi-20/

If you're using it with an instrument on a MIDI Track, it doesn't matter if the input is set to Ch1, Ch16 or All.
Like Darren said, Live sees everything as Channel 1 AFTER it passed though the MIDI Input.

- Set MIDI Track input to Ch 16 of your keyboard
- Load an External Instrument
- Set the output to the preferred Port and Ch 1

Maybe I'm missing something, but wouldn't External Instrument do the trick?

Things you can try to rule out hardware defect: - Put Push on a different surface than it is now. I suggest the foam it came in or on the cardboard box. - If you have an anti-static bracelet, it might help prevent static charges jumping to knobs. The knob-caps conduct when touched. - Trigger the ped...

Near the bottom of this page in the Control Surfaces section: https://docs.cycling74.com/max8/vignettes/live_object_model Live offers a special MaxForLive control surface that has a register_midi_control function. Using this, Max for Live developers can set up entirely custom control surfaces by add...

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! Just watch out so you don't create a Sysex feedback loop. If you send a Sysex Request and that Sysex Response...

Works here. Which device are you sending from? I tested with Push 1.
Everything up to date? Sysex/CC fixes are very recent.

Gotcha. I have no idea what ALC is supposed to be Ableton Live Clip. Which is the .alc file format. @Flange Several things to check: - Is the correct MIDI Input Selected? It might have taken over the settings from the Live Clip. (for example: None or Computer Keyboard) - Are there any Pads lighting...

I think this is the result of Live now supporting Sysex. Apart from the Sysex commands, there's no way to create a feedback loop. Switching modes sends a confirmation message, which is also the trigger message. Not in the studio atm, but there's something that might work: - Add a MIDI Effect Rack - ...

Keep in mind that you can configure individual pads to be more or less responsive. And you can determine the threshold of where Aftertouch kicks in. Its documented in the Push 2 development guide. Basically requires some Sysex. You can also get the current values. By default, the Aftertouch kicks in...

Its mentioned in 10.1b12, so it should work in the current release version. But later beta's also improve things like better timing with smaller buffers.