I drive a couple of synths using an ancient usb 2 hub and an AMT8 plus some of those synths have usb-midi, everything works just fine.
How are you filtering out the MPE? Now that you mention it, I remember earlier on having a very similar issue with midi clock inconsistency, and I found it to be an issue with MPE (easily demonstrable by pressing my palm onto the pads while clocking a drum machine). Rather than disabling MPE entirely and using mono aftertouch (which does solve the issue), I ended up using an expression control device on every external instrument/midi track to convert MPE pressure to aftertouch and to disable pitchbend and slide. I have basically saved this device into every preset I use on standalone with external midi devices.
When I brought up this issue months ago, I was told on the Ableton forums that this should not be necessary, and that Push should filter that information by default. I don’t believe that to be the case in the current release version, but I do know that ensuring the disabling of Pressure, Slide, and PitchBend has solved my MIDI clock “hiccups” entirely.
Well the theory behind that comment would be that MPE is only MPE if its allowed to use multiple MIDI channels. So if you have a track or an external instrument device set to a single channel rather than the channel setting for that track being set to MPE, whats being output via MIDI for that track is certainly not MPE.
However with that theory in mind, if you still have clock issues with the above config, then there are probably two possible alternative explanations:
- When MPE messages from pads are prevented from being output as MPE due to the channel config for that track, poly aftertouch may be output instead, and maybe this is enough to cause the clock issues.
or
- Its not the actual output of MPE MIDI data to other devices that is causing the clock problem, its something happening at an earlier stage within Live itself which is causing things to get bogged down by the sheer amount of data, and so you still need to find some alternative techniques to reduce the amount of data at an earlier stage.
This is all theory, I havent tested it to see which parts of this theoretical stuff actually lines up with the experienced reality in practice.
1 Like
Isn’t there a setting on the gear setting page on push 3 that has an MPE enable / disable toggle ?
EDIT … My mistake, this is to do with MPE inputs
Thanx everybody for trying to help 
If by this, you mean turning off in the midi settings, yes I did. With the tr8s happens much more, also when I press the mpe pads, but on syntakt it mainly (only?) happens when I change screen, pad layout etc… when I press most of the squishy hard buttons , actually. I’ve tried everything except using the midi out from push, since I don’t have a cable. I’m guessing the use of o usb hub and a midi hub might be the problem.
Trying to work around this, realized that on the beta 6, if you have push to be slaved to another devices clock, it is disabled every time you change a project. Meaning you need to re-enable this every time. I’m trying to use a octatrack as a looper to help on the transition to a new project and it’s a bit annoying that I have to turn on midi sync every time I open a project on push.
Midi has to be the most annoying thing in Electronic music
Here is a visual explanation . You can see that the external sync is turned off when opening a project. Bummer
1 Like
What external midi controllers are you all using with the Push 3, if any? I have the controller version, so I can install user scripts, which is handy.
So far I have tried the Launchpad Pro mk3, which I use a a dedicated clip launcher, but also for quickly accessing FX sends, and mute/soloing tracks.
The Midi Fighter Twister is great. I have a script that uses the top half to control volume, rec enable, sends, etc of the current track, and the bottom half as a blue-hand controller.
I’ve also tried the Korg Nanokontrol2, a the Faderfox UC-4, but I’m not a fan of faders for track levels because they never seem to match, and neither takeover or absolute modes feel right. The LED rings on the MFT are better for this IMO.
I would prefer to use just the Push, but I find that switching modes just to access send levels or launch clips cn be jarring. I am trying to get used to using the new on-screen clip view, but that still switches tracks when you don’t want it to.
So far I like the MFT for the fact that its knobs always control the exact same thing, and the LP Pro because it’s so flexible, and allows for custom mappings.
1 Like
I use Intech Grid controllers in various configurations and I’m pretty happy, especially with the size and flexibility. And even at that I’m not really using the full potential of fully customising the controllers, at the moment I just map them in Live and go. One of the modules I have is kinda an equivalent to the midi fighter, I really must look into setting up a mapping like the one you’ve described.
Video manual for the performance pack just went up:
12 Likes
Been waiting for this 
Apologies for the interjection, but what script do you use for the MFT? A P3 controller is on its way to me, and I already have a MFT. Would love to get them working together. Your script sounds like it is just what I am looking for.
This one:
https://www.reddit.com/r/ableton/comments/isjroz/midi_remote_script_for_djtts_midi_fighter_twister/
It’s an old thread but it all still works perfectly, even in Live 12 beta
3 Likes
Seems like there finally is an easy way to create controllers to send midi cc (and even cv) to hardware instruments 
This will make integrating/automating midi controllable hardware in projects much easier! Love it.
Maybe I’m missing something so what better way to check then ask fellow nauts 
One thing during live performance that I find to be weird is that I cannot seem to find a setting that will simply select the actively playing clip when selecting a track. I’m running push in clip mode.
Say I’m on a track with a drum rack. I hit record and record sequences of various drums. Then I go to clop grid view and launch a flip on another track. Or I switch to another track to do something, then launch a clip for example.
Now when I go back to the drum rack track the just recorded clip that is playing is not automatically selected. In stead a clip is selected that was in the same scene as the previously launched clip.
While I do get when this can be useful; I don’t use scenes at all. I just want to be able to switch back and forth between tracks perform within currently playing clips. Currently every time I do this I have to scroll back down and hold select + the clip to go back to the playing clip and record more drums onto it or remove triggers etc.
Any ideas on how to improve this flow ?
2 Likes
Thanks!
Paging @Dataline…
1 Like
Ah yeah, I haven’t tried over USB but it seems like you might just need a different hub according to people on the ableton forums?
Yeah, it can be a pain. I’ve spent more time researching and troubleshooting midi problems than all my other audio gear problems combined.
1 Like
Asus just released their new NUC. Could be good news for Push 3 future upgrades:
4 Likes
I have ordered a long usbc extension cable. That way I can use push away from the computer (controller version) and focus on learning the unit
1 Like
I have found that not all USB-C cables will power the controller version from a MacBook. The power cable that comes with the Mac works for me, but a 2-meter Anker cable didn’t.