Posted: Sat May 26, 2007 9:47 am
Is that Princess Superstar?spiral wrote:where are the other teats?knotkranky wrote:wow, that made me have a pull.nebulae wrote: How many of these piggies could a quad-core handle?
Is that Princess Superstar?spiral wrote:where are the other teats?knotkranky wrote:wow, that made me have a pull.nebulae wrote: How many of these piggies could a quad-core handle?
is there any reason they couldn't run operator and sampler in demo mode for the test? or would that give different performance results?nebulae wrote:The issue with this is that not everyone has all of the plugs, so a large portion would miss out on a true benchmark. I'd say Simpler and Impulse for sure.Johnisfaster wrote:if I were making a test I'd definetly put at least 1 of each of lives plugs including all fx and all instruments (operator, simpler, sampler, impulse) as well as a bunch of audio tracks. alot of reverbs and alot of delays and even some clever track routing. basically, use all of the features available including midi effects and track routing and the works.nebulae wrote:Anyone have other suggestions to give it a good baseline test that would be a good indicator of modern processors?
The other issue is that true trackcount has always been hard because I can't put out a 1gb project that streams 50 tracks...
Yeah, I suppose you're right.Johnisfaster wrote:is there any reason they couldn't run operator and sampler in demo mode for the test? or would that give different performance results?nebulae wrote:The issue with this is that not everyone has all of the plugs, so a large portion would miss out on a true benchmark. I'd say Simpler and Impulse for sure.Johnisfaster wrote: if I were making a test I'd definetly put at least 1 of each of lives plugs including all fx and all instruments (operator, simpler, sampler, impulse) as well as a bunch of audio tracks. alot of reverbs and alot of delays and even some clever track routing. basically, use all of the features available including midi effects and track routing and the works.
The other issue is that true trackcount has always been hard because I can't put out a 1gb project that streams 50 tracks...
I don't know if I am or not, maybe demo mode performs differently.. I don't know either way.nebulae wrote:Yeah, I suppose you're right.Johnisfaster wrote:is there any reason they couldn't run operator and sampler in demo mode for the test? or would that give different performance results?nebulae wrote: The issue with this is that not everyone has all of the plugs, so a large portion would miss out on a true benchmark. I'd say Simpler and Impulse for sure.
The other issue is that true trackcount has always been hard because I can't put out a 1gb project that streams 50 tracks...
The only disadvantage with the demo is that it disables saving the project, so I think there's some benefit to using Operator and Sampler. I'll put it in. Will get to work tomorrow - just got back from a deathmatch.Johnisfaster wrote:I don't know if I am or not, maybe demo mode performs differently.. I don't know either way.nebulae wrote:Yeah, I suppose you're right.Johnisfaster wrote: is there any reason they couldn't run operator and sampler in demo mode for the test? or would that give different performance results?
The fanboys are desperate to see this test perform better on such a mega machine. It doesnt matter HOW MANY FUCKING TIMES they are told live is the most hungy CPU mo fucker in the known universe they still claim this softwares engine as sleek and fast. Like fuck it is, add a few audio tracks and ditch some of those abletons plugins replacing with vsts and you will see that CPU go up to 40% in no time at all.RobertX wrote:I got the RAM [8 GIG] and drives [150GB 10k] in this morning and repeated the test...
Same results as before.
i find myself still agreeing with you more and more these days...mercyplease wrote:The fanboys are desperate to see this test perform better on such a mega machine. It doesnt matter HOW MANY FUCKING TIMES they are told live is the most hungy CPU mo fucker in the known universe they still claim this softwares engine as sleek and fast. Like fuck it is, add a few audio tracks and ditch some of those abletons plugins replacing with vsts and you will see that CPU go up to 40% in no time at all.RobertX wrote:I got the RAM [8 GIG] and drives [150GB 10k] in this morning and repeated the test...
Same results as before.
OvertoneZero wrote:This is not an accurate test, because as everyone knows, the CPU Meter on 8-Core Mac goes to 111%
JACKAL & HYDE wrote:OvertoneZero wrote:This is not an accurate test, because as everyone knows, the CPU Meter on 8-Core Mac goes to 111%
Wow, I've seen both the Mac & PC "meters" go up to 200% during the Live stress test.. Whats your point here? Your telling me that within Ableton, on an 8 core Mac, that the cpu meter defaults to 111%? C'mon
The test was done using Lives Benchmark/Stress test. PC/XP won -> 5% usage over time, end of story.
And with that, lets keep in mind whats on the box when you buy Ableton...
MADE for M.A.C.!!!!!! and..................p.......c
RobertX wrote:So far the test has been going for almost 5 hours and the temp is still at 35°. The fans are barely moving and the computer is making no noise at all.tacvbo83 wrote:although 35C is too hot, gonna wait for a cooler Mac Pro
I have a Core 2 Duo rig at home and that damn thing sounds like a leaf-blower.
When the new 45nm Intel chips [Penryn, Wolfdale & Yorkfield] come out they should run quite a bit cooler than present models.
yeah I was going to saylongjohns wrote:RobertX -
If you have the EIC, I'd be curious if you are successful in doing a Simpler -> Sampler conversion and loading the entire Grand Piano patch into RAM