Major MAJOR clipping issue using Push

[mozzatron]

So i noticed this the other day very slightly after having a little play around and it gets progressively worse every time i add another track.....

But it's that bad even with 4 tracks added that i can't use it.

I have literally got a drum rack open (from the Ableton library) and 3 instrument racks (all containing Analog), so only 4 tracks in total (and no fx) and the clipping is absolutely terrible, to the point where the track almost won't play. It sounds like my CPU is completely maxing out but it only really spikes at around 25%, which is not enough for it to sound as bad as it does. Although the CPU meter is jumping all over the place so something is obviously not right.

I have never had this problem before, it is definitely something to do with Push as it's only just started happening

Anyone having a similar issue or know what the problem may be?

Need to get this sorted asap, as there is no way i can continue using it like this.

Cheers

[Asymmetricalmusic]

Sounds like a CPU thing........Could be Push but IDK what it could be, I'd bet it's have three instances of Analog.

I use a Mac OSX10.8.3 4 gigs of ram
L9 32-bit

I run about 20 tracks (Including tracks routing and such), two drum racks about 37 samples per. I run a Kaoscilator Pro and a Microkorg thru Live and run master fx's and tempo sync to them, I use a bunch of MIDI controllers including Push, APC40, 25 keyboard and a few trigger fingers.....My biggest gripe is the Arm Exclusive bug, BUT I never experienced even the slightest slow down.

What's your computer specks ?

You should contact support

Let us know what they say.......

[lo.key]

ive found i can get about 10-12 midi tracks (with complex midi programming) before things are really unusable.

[mozzatron]

It's definitely not a normal CPU issue, i have an iMac with a 2.8GHz i5 processor and 16GB of ram

I've released a few tracks and got plenty of others that have had over 30-40 tracks running, shit loads of Waves plugs ins, Ozone 5 (which is a CPU guzzler), and more synths than you can shake a shitty stick at....and the CPU didn't even break a sweat

Ableton have got back to me and requested a status report from Live...will let you know what they say once i hear back from them.

Will

[SuburbanThug]

I've found that Live doesn't like Push adding tracks. I hope they get this sorted out. Adding the tracks in Live from the laptop before starting is a workaround for now.

[mozzatron]

I've found that Live doesn't like Push adding tracks. I hope they get this sorted out. Adding the tracks in Live from the laptop before starting is a workaround for now.

Yeah major ball ache. What's the point of having a dedicated controller if you can't add tracks with it? What issues do you have?

[SuburbanThug]

Distortion while adding tracks. So I figure I'll add as many tracks as I could possibly need if I want to improvise live.

[SilverNeedle]

haven't got push (reserved one) but this sounds kind of odd... hopefully it's an easy software solution, can't understand why a MIDI controller would affect CPU usage?

[lo.key]

its not about the midi, its about the api 'add track' integration. But to be fair, adding tracks manually also stutters my cpu when im playing back a bunch of tracks already. I think the whole 'add tracks on the fly' option is fine for production, where a bit of distortion doesnt matter, but for live playback? Just get your set together first, is my advice.

[mozzatron]

Well i've been chatting to Ableton and they requested that i disable Airplay as this has been known to cause issues in the past, and also go through all my Live folders (For every single version on my computer) and delete the Template file, Undo File and preferences file in order to completely re-set Ableton. I then had to set everything up from scratch again (Midi routing, re-scan plug ins, add templates etc).

I haven't had chance to properly test to see if it's worked, but so far so good.

Will let you know if the problem persists and where we go from there.