Next version of Push 3 they will provide a direct connection to your screen / monitor.
1 Like
I give it a couple days before somebody is running Doom on it
7 Likes
actually if m4l graphics will be a thing I imagine it would be pretty easy to do
You joke, but potentially possible over USB-C (I don’t think it would have much advantage vs running the DAW itself though at that point)
By the way, is it still possible to power the Push over USB like Push 2 did with dimmed LEDs? USB-C obviously can provide more power vs USB-B.
EDIT: I should RTFM. Nice. This is also a huge upgrade for me even for non-standalone.
1 Like
Yeh thanks, all-in-all it does seem like a solid progression. I’d be really interested to experience first hand the improved workflow with the inclusion of ADAT and also the immediacy and options with routing from RME Totalmix. The MPE keybed is a big feature alone (as mentioned numerous times in the thread) 
Yes it was a joke 
and so no need to wait for the next version to turn the Push 3 into a computer with monitor via USB C A crazy thought but not unreachable
EDIT: It would need a graphics card on board the Push 3 though!
1 Like
Lucky! Mine shipped yesterday, arrives on Tuesday. Maybe you’re close to Nashville? That seems like their warehouse/distro hub in the USA
You know, I completely assumed this was possible, but you’re right. From the Ableton website:
Types of limitations
Certain Max for Live devices are subject to the following types of limitations when used on Push (standalone):
^### Limited control:
- Certain parameters or modes of these devices can’t be mapped, automated or controlled.
- New mappings are not possible.
- Live Sets with existing parameter mappings should load and play back correctly.
All modulation devices are limited control, including:
- Envelope Follower
- LFO
- Shaper
- Shaper MIDI
- All CV Tools devices (see list below)
I must say that this is a huge omission and should have been implemented for sure. they are going to improve the integration with m4l devices I’m sure but they are not transparent in what way exactly. This seems like such a m obvious thing to implement from the get go.
Still interested in push 3 but it does make me a bit less enthousiastic as I was really seeing me go nuts with LFO’s and what not.
5 Likes
And that despite having four hands!
To me this doesn’t mean that you can’t map and modulate synth parameters with m4l lfos but that you can’t modulate the device itself (i.e. with another lfo).
It’s a limitation but less severe than it may seem at first. I’m pretty sure it will be solved given the m4l user base, but let’s see how it evolves.
Still you can at least modulate compared to let’s say an mpc where you can’t modulate anything
Below that it says ”new mappings are not possible “ Which to me says you can’t map destinations to an lfo. I could be wrong of course.
It’s not a deal breaker but it’s definitely a bit of a bummer if that is indeed the case.
My interpretation is that it isn’t possible to select new LFO destinations in standalone.
Are you sure? What about the 32-slot FM modulation matrix of the OPx4 synth?
1 Like
That’s not really the same as having a free assignable lfo. It’s still nice of course 
1 Like
THIS I didn‘t see either. Huge Showstopper. Even Natehorn was right then, that simpler is in fact limited to one LFO.
I mean why can I load those M4L Devices in the first place if I can‘t use them?
Shaper…of course one need shaper. This thing is the most fun.
I never said that It was just a response the claim that you can’t modulate anything.
It is.
I’m not 100% sure that “New mappings are not possible.” is referred to new mappings of synths parameters with m4l lfos… but it should be referred to the m4l device parameters that can be automated but can’t be mapped while working standalone.
No it’s not. You can still use lfos after mapping. Just can’t assign mapping a in the hardware yet. It’s a big omission sure
3 Likes
True. But I thought that is what we are about now. What is possible on push.
Nah it already states it can’t be mapped on the modulator devices themselves in the first bullet point. The second point definitely indicates that you can’t map an lfo to a parameter from the hardware.
Templates.
But again we are not sure that you can’t use m4l lfos to map synth parameters, to me that statement means you can’t map the m4l lfos to be modulate by other m4l lfos when using it standalone.