hwaavatar.blogg.se

Mad zach 64 pad lab clicking
Mad zach 64 pad lab clicking











mad zach 64 pad lab clicking

I'm sure this has made the problem go away in the past, but tonight as I retest and type, the problem remains.ĭoes anyone have any suggestions? I can't tell if this is a CPU problem of a SSD contention issue. If I turn off Push 2 at it's power switch, Push2DisplayProcess disappears from Activity Monitor. Anyway the audio problems remain, though perhaps a little less frequent. Of course at this level, I cannot use Live as I would like. ~60% for live and ~30% for Push2DisplayProcess). If I change the Buffer from 256 sample to 2048 samples, the CPU stays the same (i.e. If I switch back to Device, the CPU and glitches revert to as before. The audio glitches become slightly more frequent. On the same track, if I change the view on Push 2 from Device to Mix, Activity Monitor tells me Live CU is now ~100%, Push2DisplayProcessis now ~50%. The Live CPU monitor will bump up but sometimes hardly registers it.

mad zach 64 pad lab clicking mad zach 64 pad lab clicking

When I play my track it sounds fine, but every few seconds I hear a little glitch or stutter or distortion. On even a simple Live set, Activity Monitor tells me that Push2DisplayProcess is using 34% CPU. I have disconnected all other peripherals apart from a Magic Mouse and quit all other applications and disabled the WiFi. I am running Ableton Live 9.6.2 64bit and a Push 2. I have a Macbookpro, running OS X 10.9, 2.7GHz Intel Core I7, 16 GB 1600 MHz DDR3, with APPLE SSD SD512E drive.













Mad zach 64 pad lab clicking