Dubstepforum.com

cpu hungry

Lowpass wrote:cpu hungry

+1


I can understand WHY people use it but personally I go for Reaktor / FM8.. NI do make beastly pieces of kit though.

Stupid names for the oscillators, I mean what happened to sine, square & sawtooth? Are they not good enough names!

Albino3, FM8 & Sculpture > Massive

Rendr wrote:Stupid names for the oscillators, I mean what happened to sine, square & sawtooth? Are they not good enough names!

Albino3, FM8 & Sculpture > Massive

I agree that FM8 is the shit, but Massive's waveforms are what makes it aweomse!

DJ Vision wrote:

Rendr wrote:Stupid names for the oscillators, I mean what happened to sine, square & sawtooth? Are they not good enough names!

Albino3, FM8 & Sculpture > Massive

I agree that FM8 is the shit, but Massive's waveforms are what makes it aweomse!

If only it came with some normal waveforms. ATM i'm fuckin loving the Sculpture synth on Logic, the sound quality is 10x better than any other synth i've tried yet.

My cpu can also handle massive fine, ive never had to bounce down a channel to wav to get back cpu.

Altered State wrote:My cpu can also handle massive fine, ive never had to bounce down a channel to wav to get back cpu.

Me either but its nice to keep below 50%.. issit not?

Massive's alright but LEAVE THE 'FILTHY ELECTRO' (or whatever it is called) PRESET ALONE PLEASE. Sick of it tbh.

massive does it for me, easy to use, quick modulation, great sounds. Didn't know there was such a big gap in terms of cpu usage between massive and albino. Matter of the fact is that Massive runs great on my system

Legendary wrote:

Altered State wrote:My cpu can also handle massive fine, ive never had to bounce down a channel to wav to get back cpu.

Me either but its nice to keep below 50%.. issit not?

in a tune im doing atm in ableton i have 5 instances of massive running at once and my cpu does not go above 25% with the whole tune being played back in ableton live 7

if you have problems with resource using massive then maybe you should "upgrade your current regradings with a free ringing 42 megabitings quicker"?

but tbh one thing that pisses me off is the lack of automation for synched LFO
it has to be macro'd in ratio mode or drawn
NI didnt think about that one

Blunt-DMO wrote:

Legendary wrote:

Altered State wrote:My cpu can also handle massive fine, ive never had to bounce down a channel to wav to get back cpu.

Me either but its nice to keep below 50%.. issit not?

in a tune im doing atm in ableton i have 5 instances of massive running at once and my cpu does not go above 25% with the whole tune being played back in ableton live 7

if you have problems with resource using massive then maybe you should "upgrade your current regradings with a free ringing 42 megabitings quicker"?

but tbh one thing that pisses me off is the lack of automation for synched LFO
it has to be macro'd in ratio mode or drawn
NI didnt think about that one

Hmm, i'm talking having multiple instances of massive, FM8 & a PSP nitro, with full up FX channels and buses, I have a good rig, just Reaktor, for one .. lets you re-create it without using half as much CPU..And often a better UI, not some beefy piece of crap what looks like its just ripped out of a mech from a sci-fi fantasy game

EDIT: & Like malstrom, you can tell if a tunes been made on massive, most of it the time cause it sounds like every other sound from it, TO good, theres no rawness to it, even the raw sounds like.. clean..

Then again this is just my opinion and thats why I bought FM8 instead, I love how imperfect it sounds and how nice the UI is..maybe mech sci-fi sounds are just not for me.

Legendary wrote:

Altered State wrote:My cpu can also handle massive fine, ive never had to bounce down a channel to wav to get back cpu.

Me either but its nice to keep below 50%.. issit not?

ive never came anywhere near 50% and i am normaly opperating with multiple massive's, FM8's, PsP Nitro (and other FX) etc etc.


What slows down my system more is the use of samples as the harddrive is the slowist componant in the computer - i remember i made a tune once where i mixed every channel down to wav and then it started getting a bit sketchy.

Altered State wrote:

Legendary wrote:

Altered State wrote:My cpu can also handle massive fine, ive never had to bounce down a channel to wav to get back cpu.

Me either but its nice to keep below 50%.. issit not?

ive never came anywhere near 50% and i am normaly opperating with multiple massive's, FM8's, PsP Nitro (and other FX) etc etc.

Thats bollocks tbh unless you're running a 3.something quad core .. Or you have you external unit what takes CPU stress away.. Or if you use Massive in that eco thing it has..Or Ableton is really good with CPU, despite its horrible lay out.

I run a 3.3ghz 5600+ dual core (over clocked from 2.9) and its not like it peaks over 50% unless shits stacked to shit but.. it does go over...I use Cubase4 and tbh it seems to be more CPU friendly than when I used to use FL8.

Wavs are buffered from the HDD, they shouldn't take up much / if any CPU power..Thats latency and your HDDs speed rate.

I run a 3.3ghz 5600+ dual core

AMD mate, the architecture is different and is not as well suited i find with multimedia.

im an amd fan, i have a dual core amd and core2duo intel

i find the intel works better for audio visual applications

i too run multiple instances of massive and fm8 never see it go above 25% on my core2duo e6600 on stock speeds and an x1950xtx graphics card.

ive noticed if the GC is dire then it increases the overhead of vsts if they have a high end graphical interface

all my instances run on high not eco

having said that though i use massive cos its the first one ive learned and i have to agree already im hearing sounds that are "familiar" i may well move to something else

Macc wrote:Massive's alright but LEAVE THE 'FILTHY ELECTRO' (or whatever it is called) PRESET ALONE PLEASE. Sick of it tbh.

LMAO yeah i know what you mean it's called brutal electro and it sticks out like a sore thumb

nowaysj wrote:Haters.

My cpu can handle it easily.

I don't care if the oscs are called aunt Jemima's Jambalaya 1 and 2. It sounds dope, is easy to work with, and inspires creativity.

Legendary wrote:

Altered State wrote:

Legendary wrote:

Altered State wrote:My cpu can also handle massive fine, ive never had to bounce down a channel to wav to get back cpu.

Me either but its nice to keep below 50%.. issit not?

ive never came anywhere near 50% and i am normaly opperating with multiple massive's, FM8's, PsP Nitro (and other FX) etc etc.

Thats bollocks tbh unless you're running a 3.something quad core .. Or you have you external unit what takes CPU stress away.. Or if you use Massive in that eco thing it has..Or Ableton is really good with CPU, despite its horrible lay out.

I run a 3.3ghz 5600+ dual core (over clocked from 2.9) and its not like it peaks over 50% unless shits stacked to shit but.. it does go over...I use Cubase4 and tbh it seems to be more CPU friendly than when I used to use FL8.

Wavs are buffered from the HDD, they shouldn't take up much / if any CPU power..Thats latency and your HDDs speed rate.

I run 3.6ghz dual core and I tell no lies.

Quad core doesn't actually make that much differnce at the moment, correct me if im wrong but FL8 isnt written to take advantage of multiple cores so in this instance my two cores are more than enough at 1.8ghz each.

On top of this I am running fast ram, and the timings are matched with the CPU speed perfectly and run at the 1:1 ratio - so if you are struggling i suggest looking into ram timings (if you know what you are doing with PCs)

As I said in another post:

The HDD is the slowist as it has to actually locate the wav's on the disk. Without going too much in depth I store my samples on the slowist partition of my disk so this might have somthing to do with it.

Also, the HDD cache is only 16mb? Maybe 32. I cant remember, but its tiny considering all the other things that have to be swapped in and out of the drive along with your .wavs.

more often than not i find myself creating waveforms in massive and sampling them to use in kontakt or reaktor