Push2DisplayProcess

[soundklinik 33]

Still waiting........

[Mark Williams]

for?

[JAMM]

....the CPU snapshot from your lightning fast laptop

[Mark Williams]

See reply I did a while ago, and you will see why I cant, or perhaps you think a broken spiral fracture of your ankle heals fast. Had an open reduction internal fixation on the fibula (plated) op on it on Monday. I dont use laptop its desktop PC. Its hardly lightening fast, but I dont encounter some of these issues that others have...
If pain eases off over the folowing few days, I will try to get in there, as I expansion packs to install for my Lethal Audio vst. Here is my PC specs thou
http://h20564.www2.hp.com/hpsc/doc/publ ... =c04556684

Upgraded Ram to 16GB and now use 256gb SSD, the 2TB sata hard disk is now storage for projects etc.

[JAMM]

Don't rush it.

quote from Ableton support:
"The Push 2 Display Process does require some heavy CPU resources, so it's possible that if your sets have gotten a little more CPU intensive, this could push it over the limit"

[Stromkraft]

Don't rush it.

quote from Ableton support:
"The Push 2 Display Process does require some heavy CPU resources, so it's possible that if your sets have gotten a little more CPU intensive, this could push it over the limit"

I don't see any screen shots getting around that. No matter the size this is there.

I just discovered that Push2DisplayProcess is marked as vulnerable to Dylib Hijacking. Great.

[Mark Williams]

I managed to get my leg under my desk, so I did the screenshot, but havent uploaded, yet but push2 display process was hovering around 10-13%, how is that comparing to you? My studio pc isnt online, so maybe I take a photo of the screen with my phone and do it that way...

Not sure how to upload a screenshot of the Push2Display process I took a photo via my camera, as my studio pc is strictly offline from internet.

Have added screenshot to dropbox, here is link
https://www.dropbox.com/s/kendi806qxm79 ... t.JPG?dl=0

[fishmonkey]

the CPU usage of the Push2DisplayProcess varies depending on what you are Pushing. for example, if you hit the Browse button you will see a spike in CPU usage...

[JAMM]

MBP 2011, Taskmanager Push2 CPU:
Around 28% and 34% depending turning the encoders or do some live drumming on a drumrack or trigger clips or scenes.
This is a simple liveset....8 tracks, four returns and some FX on the return and master channels, not every tracks is playing at the same time.
A few reverbs in low or medium quality, clips not in HQ mode etc etc. Only third party plug-in...Sugar bytes Turnado.

[soundklinik 33]

MBP 2011, Taskmanager Push2 CPU:
Around 28% and 34% depending turning the encoders or do some live drumming on a drumrack or trigger clips or scenes.
This is a simple liveset....8 tracks, four returns and some FX on the return and master channels, not every tracks is playing at the same time.
A few reverbs in low or medium quality, clips not in HQ mode etc etc. Only third party plug-in...Sugar bytes Turnado.

Man, that is really a lot of CPU ....and how much just an empty default template 2 x midi and 2 x audio?

[Mark Williams]

The screenshot I took, mine was running at about 14% and that was using Slate Drums SSD, Lethal Audio VST. Maybe having WiFi helps mine, as my studio PC is strictly offline, only take it online once every 6 months to update any vst's etc that need direct updates.

[[jur]]

MBP 2011, Taskmanager Push2 CPU:
Around 28% and 34% depending turning the encoders or do some live drumming on a drumrack or trigger clips or scenes.
This is a simple liveset....8 tracks, four returns and some FX on the return and master channels, not every tracks is playing at the same time.
A few reverbs in low or medium quality, clips not in HQ mode etc etc. Only third party plug-in...Sugar bytes Turnado.

Man, that is really a lot of CPU ....and how much just an empty default template 2 x midi and 2 x audio?

Don't forget that it's 30% out of 400% (for a quad core, or 200% if it's a bi-core).
From my observations, the mixer mode is the more cpu hungry one.

[JAMM]

yep 200% on my MBP...but you can't go up to 200 or 400 %
Before reaching that maximum the problems start.
SSD drive, wifi off, deleted most third party plugins, etc etc just to save CPU

[YannickBisson]

Same problem here. Push2Display process around 10% on PC and 20% on MBP. Empty set in Ableton, no plugins running, no audio.

[Stromkraft]

Don't forget that it's 30% out of 400% (for a quad core, or 200% if it's a bi-core).
From my observations, the mixer mode is the more cpu hungry one.

30%, or whatever one might have, is still quite a bit more than the 0% I enjoy with the Push 1.