Problems with Massive VST :(

[MassAphekt]

I keep getting annoying crackling noises, I notice especially on my subbasses at the very end of each note I can hear a click or crackle noise every time.
It's not a pirated version, I bought it last year if anyone asks lol
my specs are

windows 64bit
fl studio 10
12gb ram
1tb harddrive
intel i7 2600 processor

I am not entirely sure what I should do, I always keep my buffer high in ASIO given the power of the processor and all, I notice if I bring it to the middle (buffer) my CPU use-age on fl studio accumulates high, I don't understand? My computer is only a month old with daily maintenance and all, is there any suggestions on fixing the crackling noises and also the unusual spike of cpu when I use many instances of massive (I use to be able to have roughly 40+ instances of fm8 and massive with fx and still be at like 50cpu, but now I can't even get to 20+ instances without getting to 60+cpu im frustrated

[sunny_b_uk]

that sucks, i built my pc 2 years ago & its half the power of yours yet i can load 35-40 massives till i start hitting 60% cpu in FL 10. try using asio4all, or underneath it go to "Mixer: Resampling" and set to 'linear' or '6-point hermite'. i dont know what else it could be.

[Sonika]

I'm thinking it's actually something you're doing withIN massive. Try raising the attack and the release. This is a really common problem, especially with subs. It's all about higher attack and higher release, that should fix the clicks

[sunny_b_uk]

hmmm hes said crackling not clicks. tbh it sounds more like a buffer problem in FL Studio since he said the crackling only comes when hes loaded 20 instances. try what i said in my other post & download asio4all, your most likely relying on an onboard soundcard from what i can tell.
i would probably have the same problem if i didnt use asio4all.

[Sonika]

Right, it's just the "clicks and crackles at the end of each note" that caught my attention, it seems like that exact problem, but I could be very wrong.

[wormcode]

Why would you need that many instances ever?? Or you just benchmarking?

Try reinstallling the drivers. What is your latency set at?

[nowaysj]

The cpu usage depends on the complexity of the patch. I can have a hundred massives open or just three.

Also go to options, audio. Get familiar with that page, use the help <f1>, as well, head over to IL's forum. I remember in 9 there was a setting that particularly helped with ni products. Think it was align ticks or something like that. May not be it, but a good place to start, also, I'd pay Sonika some heed.

Also change your avatar! That avatar has been used by a looong time forum member. Forum law.

[Sonika]

Yup. Forum law dictates that any forum member sporting the same signature quote or avatar as another is susceptible to instant execution.

[MassAphekt]

lmao okay thanks guys, but I think I already have asio4all? doesnt it get installed with fl studio 10 at the beginning?
Plus producing with dubstep 30+ instances is not enough imo, especially if you have to clone a few here and there
but yeah Ill try the toher soultions, I knew of the attack and release but I'd much rather rid of the entire problem then work around it ya smell me? thanks alot for the tips guys and i will change my avatar :p sorry I just found it randomly

[JTMMusicuk]

[quote="wormcode"]Why would you need that many instances ever?? quote]
yeah i was thinking this, i only ever need like 6 or 7 at most
you know that popular saying "too many synths spoils the broth" or something like that

[wormcode]

Yeah I still don't see a situation of needing over 30 of them. I always was a believer in "keep it simple". And resampling too. I suppose if there's some layering going on yeah.

ASIO4ALL does get installed I think, but not sure if it's enabled by default. Check it, and check its latency. 15-20ms is good, over 40-50 is bad but doable. More than that and it's time to start looking for a new audio interface, or at least bouncing to audio.

Also change Massive's quality settings in the interface from "ultra" or whatever to normal or low quality, then change back to best quality when it's time to render.

[Today]

holy shit i've never had 30 synths open.... probably like 6 tops... but i bounce my sounds to audio often
i didn't realize u could even do that.. i have 8G memory but i dunno if i could

[sunny_b_uk]

firstly do what wormcode said since asio4all isnt used at all by default.. & if you really have run out of ideas and your completely stuck, then the only other suggestion i have is to check your CPU's temperature by downloading Speedfan http://download.cnet.com/SpeedFan/3000- ... 67444.html
the problem could possibly be that your CPU might not have a sufficient heatsink fan installed and causing it to overheat. my cpu runs at 25-35 degrees celsius. reaching 50-60 degrees celsius would be way too much and would shorten the life of your computer completely (as well as slowing it down a lot)
ANOTHER good way in FL to save cpu with VSTs is to click Tools then Macros and click Switch smart disable for all plugins. keep doing this as u add more plugins, then obviously bounce to audio when you have your sound/sounds the way you want them.

[GuerrillaWarfare]

Hey man, this always happens to me in massive, especially with subs, raising the attack (if the clicking is at the start of the note) or the release (if it's at the end) usually fixes the problem. Sorry if my answer sounds really obvious :L

[VirtualMark]

The amount of instances you can run depends on a lot of things:

Sample rate - if you're running at 96khz it'll take up much more resources

ASIO buffer size - the smaller the buffer, the lower the latency, but its also more demanding and can crackle more if set too low

Amount of voices/unison - this makes loads of difference

Complexity of patch - obviously more stuff routed and modulating takes up more cpu

Quality setting on Massive - ultra takes the most cpu, sounds the best too

ADSR - yeah it can obviously cause a click. but also if the release is set high, when the keys overlap it plays double(i.e if unison is set to 3 and you play a chord, thats 9 voices. play another chord straight after, and its then playing 18 voices while the release from the last one stops)

Your tune - how many other effects, vst's etc

Your computer - background processes, antivirus, web browser, defragging, power settings, usb devices etc.


No 2 patches are the same. I can overload my 5ghz i7 with just one patch. Setting unison to 64/64, adsr with a long release, quality on ultra and sample rate on 96khz. It will crackle between notes like crazy as it drops voices.

Try freezing tracks - surely you don't need 40 instances active all at once. Freeze the ones you're not editing and it'll free up cpu.

[MassAphekt]

thanks for the awesome feedback guys
virtualmark, I like the extensive list you have there, It makes sense now as to why I can only load less now (complexity of the patches itself), I run in 48khz my buffer is 1024 asio
im already aware of the asdr fix and i always disconnect from the internet and shut off all background programs and services (that are unnecessary) when I produce. And I always haven't been a fan of resampling everything, I unno, I always find myself wanting to go back and change something lol but I'll def use that method more often if it means me saving cpu for the sake of the track, thanks guys