Dubstepforum.com

Looking for a new PC, this old horse can't handle more than 10 instances of Massive running.

Anyone have any suggestions on where to start?

Aleksandr wrote:Looking for a new PC, this old horse can't handle more than 10 instances of Massive running.

Anyone have any suggestions on where to start?

How many do you need Bounce some shit down!

Anywho.

VirtualMark's Audio PC Guide
http://www.dubstepforum.com/viewtopic.p ... o+pc+guide


A few other threads
http://www.dubstepforum.com/first-time- ... 59583.html
http://www.dubstepforum.com/viewtopic.p ... &p=2392656
http://www.dubstepforum.com/viewtopic.p ... 7&p=661592

Some people will suggest building your own. Any new corei3/i5 processor laptop or desktop should be good enough though unless you have specific requirements.

Well, you can have quite a few running on just the bass itself.

Add that to the melody, pads, etc, and you can easily get 20+30

JT7 wrote:

Aleksandr wrote:Looking for a new PC, this old horse can't handle more than 10 instances of Massive running.

Anyone have any suggestions on where to start?

How many do you need Bounce some shit down!

I know most people LOL at having that many Massives open in a project or say other condescending things, but honestly I do it just out of simplicity. Most of my patches have way too much movement that then gets fucked to pieces when I try to use it in a sampler using any other notes than the root I bounced it in. I'm guessing there's a way of adjusting this (FL 8 ) but I don't know it, so I just use multiple Massives and be done with it. No tome of .wavs either Plus my laptop can handle it, so why not.

On topic, I've thought about upgrading many a time too but only if it was for reasonable prices, so I'd be interested in this as well.

http://www.se7ensins.com/forums/topic/4 ... ild-guide/

also: LOL at 10 instances of massive running.
even if you decide you need so many of them, why don't you just freeze the tracks after you're done with them?
or bounce them in place.

Yeah freezing tracks is the way to go. I annoyingly found the limits of my laptop cpu the other day. ONE instance of Massive, intel 2.5ghz t9300. I had the quality set on ultra, and the sample rate set at 96khz, as i was bouncing stuff down and processing for an experiment. I made a supersaw patch, I'd set the voice maximum to 64, and had about 12 voices per osc, 3 oscs spread over different octaves and i had put some chords down in midi. When i changed the adsr i noticed a crackling, and my cpu had spiked. Whad had happened was that the longer release was causing the notes to overlap - 3 oscs at 12 voices per core was 36 voices anyhow, but it was spiking up to the maximum of 64 voices at the end of the notes. Massive said 'over' on the cpu load, even tho windows was only showing about 60%. Its because massive was using one of the two cpu cores to the max.

I thought there was something up with my pc at first, as i've had loads more synths open in the past before encountering problems. But i've tried it on my i7 4.5ghz and ran into the same problem. What i've found is that any pc will struggle with massive on ultra quality, with tons of voices and notes and at a high sample rate. But if you have lots of cores you can open extra instances no problem, it's just that one instance with loads of voices will utilize one core to the max and cause dropouts. I froze the tracks with the high cpu load, and it dropped back to 0%. Or if you want to play it still, you could bounce a long note then load it into a sampler and play it there.

I've also experimented with a more basic patch on massive, and an overclocked i7 can run over 120 instances at 44.1khz with no dropouts. Just for the record.