Dubstepforum.com

im getting crackling sounds when i load up multiple instances of heavyweight vst's like Massive or Predator. If ive got one or two its normally ok before i start adding reverb etc. But the more i add, the more it crackles. Can someone help?

its 1.73ghz processor and gig of ram.

do i need a better soundcard or more memory?

You could probably do with more RAM. You don't say what your soundcard is.

try lowering the buffer offset (or whatever its called) on your soundcard. If you do not have a sufficient soundcard enough try Asio4all...

are you using fruity loops? if so go to options, aduio settings, and increase your buffer length until the noise goes away...

i think my sound card is realtek high definition audio, and yh im using Fl Studio so ill give it a try. nice one

Antics nice one bruva, that was the problem, its been killin me! will having it up more affect anything that i should know about?

Also ive only been producing since jan 09, so is it necessary to get a better sound card and ram yet?

keyz wrote:Antics nice one bruva, that was the problem, its been killin me! will having it up more affect anything that i should know about?

Also ive only been producing since jan 09, so is it necessary to get a better sound card and ram yet?

its an issue, if you want to solve it then yes maybe upgrading is necessary,

if there are more important issues to address i.e monitors then deal with them instead

leave it in for that crackley burial sound

-Dubson- wrote:leave it in for that crackley burial sound

its under runs so it will only be there on play back, when you render it wont be there so you wont sound like burial. sorry to be a geek.

Lowpass wrote:

keyz wrote:Antics nice one bruva, that was the problem, its been killin me! will having it up more affect anything that i should know about?

Also ive only been producing since jan 09, so is it necessary to get a better sound card and ram yet?

its an issue, if you want to solve it then yes maybe upgrading is necessary,

if there are more important issues to address i.e monitors then deal with them instead

nice one mate

The only issue with increasing it is that it'll make the program slightly more RAM/CPU intensive as it has to render and store more... but i had a similar problem and havent noticed any further omplications once i changed it...

They're called underruns

http://flstudio.image-line.com/help/htm ... derrun.htm
http://flstudio.image-line.com/help/htm ... s_wave.htm

The key point here is that increasing the buffer length will reduce the glitches, but will introduce a delay if you use a midi keyboard/controller, and the whole program will generally run slower.

A better solution would be to bounce down the plugin tracks to audio - most people would reccomend doing this anyway. Search the forum for 'resampling'

Monitors are more important than a good computer to make your tunes on these days!? I'm sorry but as long as your levels are fine in your mix the ME can do the rest of the work, i'd rather be able to handle more than a few VSTs than to hear my music on monitors - they just make you care about how the tune sounds to much and not about whats going on sonically!

Not to have a go but Monitors should come once you're satisfied in your music enough to take it one step further and start learning how to mix down..

Thought id post in here rather than make my own threa dand be bombarded with alpacas and told to use the search feature

Ive just bought a Focusrite Saffire LE and im using Cubase 5. When i get to a particulalrly busy moment it all goes to shit, crackling and awful bit crushed sounding noises galore and the track plays slower than it should. Ive tried to increase the values of the options the driver gives "ASIO buffer size" and "Firewire buffer size" and this helps but the crackling is still there. The maximum they can be increased to is 40ms and 20ms respectively so im fucked basically, i cant increase it any more. Is there anything else that could be causing the problem? Ive checked my CPU and RAM usage when playing busy parts but its not noticeably high really. Checking the VST performance thing in Cubase the ASIO meter is maxed out lol.

Thing is when i get rid of the interface all together and go back to using the PCs inbuilt sound card everything's fine but i paid about £250 for this interface so i wanna bloody use it and get my moneys worth! Any suggestions of how i can fix the problem but still use the interface? Would be appreciated so much!

get the ASIO4ALL driver for Fl studio... minimal delay and playback is smooth...

clean the potato chips off your floor fatty

OMM-0910 wrote:They're called underruns

http://flstudio.image-line.com/help/htm ... derrun.htm
http://flstudio.image-line.com/help/htm ... s_wave.htm

The key point here is that increasing the buffer length will reduce the glitches, but will introduce a delay if you use a midi keyboard/controller, and the whole program will generally run slower.

A better solution would be to bounce down the plugin tracks to audio - most people would reccomend doing this anyway. Search the forum for 'resampling'

yh? whats does that mean? i looked for resamplin but i cant find anything to do with my problem.

in fl7 the buffer length is set to max, but wen i got loads of vst's up in certain parts of my beats. cpu maxes out, do i need a better soundcard?

jduffy wrote:

3za wrote:

-Dubson- wrote:leave it in for that crackley burial sound

its under runs so it will only be there on play back, when you render it wont be there so you wont sound like burial. sorry to be a geek.

Yeah too much is trying to be proccessed at once, and its missing some data out when it plays back.

Increase buffer, and also your running your software on the built in soundcard? Make sure the settings refect what it can handle as built in soundcards are not made for production tbh.

yh the soundcard is the standard one, and i aint touched the settings in Fl Studio since i got it, what needs to be changed?

keyz wrote:

jduffy wrote:

3za wrote:

-Dubson- wrote:leave it in for that crackley burial sound

its under runs so it will only be there on play back, when you render it wont be there so you wont sound like burial. sorry to be a geek.

Yeah too much is trying to be proccessed at once, and its missing some data out when it plays back.

Increase buffer, and also your running your software on the built in soundcard? Make sure the settings refect what it can handle as built in soundcards are not made for production tbh.

yh the soundcard is the standard one, and i aint touched the settings in Fl Studio since i got it, what needs to be changed?

standard one could be ok just make sure you asio4all installed and being used as your driver
go option>audio settings>input/output
and make sure it is asio4all if it is not you need to change it, if its not there you need to download and install it
then you nee to turn the buffer up untill it is ok