Ableton Forum

taking CPU measurements on beta software is retarded. that's why the call it BETA FFS, it's not done, it sucks, and needs to be beaten severely.

the last thing people need to hear are rumors of plug ins being unusable bloated failures.

I can't even use some of the presets without major drop outs, that might change, that might not. I'm also only testing at 192kHz to really abuse the bitch.

stfu and go break it!!

Tone Deft wrote:taking CPU measurements on beta software is retarded. that's why the call it BETA FFS, it's not done, it sucks, and needs to be beaten severely.

the last thing people need to hear are rumors of plug ins being unusable bloated failures.

I can't even use some of the presets without major drop outs, that might change, that might not. I'm also only testing at 192kHz to really abuse the bitch.

stfu and go break it!!

surely beta is fixing small bugs, not recoding an entire plugin. I'm not dissing it, it sounds great and the beta hasnt crashed once yet. i'll be one of the first to puke up my money to ableton when the time comes.

Tone Deft wrote:taking CPU measurements on beta software is retarded. that's why the call it BETA FFS, it's not done, it sucks, and needs to be beaten severely.

the last thing people need to hear are rumors of plug ins being unusable bloated failures.

I can't even use some of the presets without major drop outs, that might change, that might not. I'm also only testing at 192kHz to really abuse the bitch.

stfu and go break it!!

How can you beta test and break something that doesn't work in the first place?

I'd agree its stupid to write it off based solely on performance whilst its still in beta, though all the signs are that it is very cpu intensive.

Emissary, just squashing the rumor mill with my own $0.02.

I've crashed it many times. most nights after work are waiting for the new download, launching it, crashing it in a short amount of time. writing the bug report, writing the e-mail, waiting for the e-mail to upload and passing out asleep 15 minutes later.

jonny72 wrote:How can you beta test and break something that doesn't work in the first place?

seriously? is there a typo in your question?

I'd agree its stupid to write it off based solely on performance whilst its still in beta, though all the signs are that it is very cpu intensive.

yeah...

Already sent in 3 bug reports Some with crashes and some without. All this in a few hours. Do I fucking qualify or not?

8 definitely seems to have more of a hunger for CPU than 7. Doesn't mean that you can't use Live in efficient ways, but if you want to dig into the content and instruments, it's going to want to dig into your processors.

That said, whether the CPU drain is weeded out in beta testing or not, this is one magnificent piece of software that is going to be bought by me as soon as I can get it.

I'm not noticing any tangible difference between Live 7 and 8 CPU wise, except for some of the new stuff, such as Corpus, which is documented as being a drain on CPU for windows currently. Collision is only similar to Tension and also if you derack some of the FX it works more efficiently - still, I tend to use track freeze for both Tension and Collison (I find them similar actually but am liking the collision sounds, esp. with corpus).

I have had 9 crashes so far, for 5 different problems. I'm with TD in that the more we push it, the more quickly we can get a stable version and Amaury told me not to hold back and be reticent on sending bug reports, even if they appear to be isolated. Overall, I'd say it's doing pretty good so far in terms of stability, I definately had knocked Live 7 over more times at the same stage of beta last year.

I don't have a super fast system so Collision is definitely cpu hungry on mine. Corpus Isn't really that bad on mine, it does have some cpu spikes sometimes but I think it just a bug cuz playing with the XY pad (decay to 0) rectifies it for me. I even put it back to the way it was and there's no cpu drain.

Anyway it sounds amazing, it can be some sort of reverb or just adding some big bottom to a kick.

corpus has a bug where the wet dry control set to 0% is really eating CPU, this bug is on the windows platform only AFAIK.

Yes I just tried, on one preset I made, it doesn't do much difference but I tried with another preset and the cpu really goes up when ya bring it down to 0%.

Oh shit, missed it again.

Been too busy cleaning up my place cause of the recent bushfire activity in our area.
Didn't have the computer on all day.


Could be worse.

Tried Beta here and there, really liked it.
Collision Corpus are CPU eaters but with nowadays machine shouldn't be a problem. Remember that Beta Software has to be compiled with the Debug option anyway so this takes away a lot of CPU cycles that could have been used for other stuff instead.
No crashes, simply some glitched but they were already reported.
What I like the most is the new operator and the effort they took in creating a pool of usable patches & sounds. They are still 'Abletonian' but this is the mark of the company... Moreover the Multi Dynamic Band effect, Freq Shifter, Vocoder and Collision/Corpus extend sonic possibilities to a point that was unthinkable before.
Time to sell my Zebra2? I do not think so. Zebra has a distinguishable character I still need. I'll wait when L8 will be available.

- Best
- Pasha

Tone Deft wrote:

jonny72 wrote:How can you beta test and break something that doesn't work in the first place?

seriously? is there a typo in your question?

I'd agree its stupid to write it off based solely on performance whilst its still in beta, though all the signs are that it is very cpu intensive.

yeah...

My point was that you can't really test something that causes audio to break up and the cpu to max out.

I've played with some more of the presets and its not as bad as I made out originally but its still pretty much unusable for me. On a lot of the presets playing 2 or 3 notes can hit 75% on the Live cpu meter, and thats with nothing else playing.

Any analog modelling synth is going to use a lot of cpu so I've not got any complaints - I don't tend to use the instruments much anyway. They might need to update the system requirements though so people know before buying, if someone with the minimum requirements bought Live Suite they probably wouldn't be very impressed with it.