Ableton Forum

For a Reaktor-based live set, I'm considering remote-controlling Ableton - so Reaktor can remain a kind of 'one-stop-shop' for everything I need, while Ableton becomes a VST host / sampler. With this in mind, I want to build a simple MIDI mixer in Reaktor, which remote-controls the Ableton mixer via...

This is amazing, thanks so much dataf1ow! Works like a dream..

I'd like to make a really simple version of something like this, that would allow for CC control of just sends on the current track. Anyone seen something like this? Or could you gimme a hint on what selector I need?

I just checked my task manager and surprisingly I discovered that PUSH-2 drains 10-13% CPU just being idle. There is NOTHING on the screen. Blank....but pulling 13% CPU :roll: Lenovo X-220 laptop. That is somewhat alarming...I don't think it does that on my regular PC, which has a dedicated (budget...

JAMM wrote:How much % of the CPU of a MBP does a Push2 uses in comparison to a push1 ?

20 - 30%, on my 2015 MBP

Not sure the best course of action to raise this as a group with Ableton. They got a bug-fix ticket thing people can vote on?

My usual experience with hardware manufacturers is "they have no fucks to give", but it would be nice if Ableton could prove me wrong on this one.

Plenty of new Macs will have this problem!

Stromkraft wrote:

jomtones wrote: Be a lot cheaper than buying a 15" MBP.

I got my 2011 for $400. Running 24/7.

On Push 1...

JAMM wrote: And thats exactly what Ableton should mention on the website under hardware requirements.

Think you're totally right on this. Ableton's support response was completely insipid.

Push 2 still eats up 20% of CPU here and prevents getting any serious work done with it... Sounds like I may have to buy a quad-core Windows laptop for music and gigs then if it solves the issue. Be a lot cheaper than buying a 15" MBP anyway, I suspect. I really like this MBP, but I use it for ...

Interesting! Are you using a soundcard with it? Plugins? What buffer setting are you on?

It's nice, but as soon as I start throwing in a few plugins, audio stutters at low latencies.

This is on a 2013 i5 MacBook pro, 16gb RAM. Even loading for example Mad Zach's 64 lab renders it unusable. You have to head up to 512 buffer size just to clear the crackles.

Makes sense. I don't get a lot of value out of the display so far anyway :/

Current plan is to get an upgraded desktop PC and keep Push 2 for home studio use only. Bit daft really!

It's really weird. 20% of a modern CPU to drive a basic resolution little screen?

Does Push 1 suffer from any of this?

Totally agree. I'm really not impressed! I'm using a pretty powerful laptop but yeah, couldn't consider taking my set on the road with Push 2. I thought that was the whole point?

Any Ableton folks care to comment? Or care at all? I'm mystified.