1 Topic by laszlozsolt82 (edited by laszlozsolt82 2011-09-05 18:29:35)

  • Registered: 2010-02-20
  • Posts: 8

Topic: Clicks and pops, asio meter spikes in Cubase 5 with FF 400

Hi !

I have a problem with my system, and i hope someone can help me here:
Got an RME FF400 soundcard, curently using Cubase 5 and in the VST Performance meter the ASIO meter it s going crazy when i run a couple of VST s, Even if i run at high buffer size like 1024 sample the same thing happens.....I can listen to music in Winamp with no problem, and record guitar DI tracks in Cubase, but when i apply a couple of vst effects the clicks starts....

Computer specs are the following:

Windows 7 64 bit
Gigabyte MA785GT UD3H  Motherboard with onboard TI FW chipset
AMD Phenom II X4 955     CPU
8 GB DDR3 RAM
Radeon X 1300
WD 7200 rpm 500 GB HDD

What should i do?
Suggestions?

  • From: Connecticut, USA
  • Registered: 2011-08-01
  • Posts: 376

Re: Clicks and pops, asio meter spikes in Cubase 5 with FF 400

Hi,
This link will help for optimizing Windows for audio.
http://www.rme-audio.de/forum/viewtopic.php?id=5462
Other than this it would be most likely power management settings in your BIOs. I'm not familiar enough with that AMD boards BIOs to get any tips on that.
Thanks Chris

Chris Ludwig
North East USA Sales | Synthax/RME
www.facebook.com/RMEAmericas
Twitter @RMEAmericas

ChrisLudwig's Website

  • Registered: 2010-02-20
  • Posts: 8

Re: Clicks and pops, asio meter spikes in Cubase 5 with FF 400

Thanks for your reply, i already optimized my windows 7 for audio aplications.

What about the power management settings in BIOS? What should i try in my BIOS?

  • Registered: 2010-02-20
  • Posts: 8

Re: Clicks and pops, asio meter spikes in Cubase 5 with FF 400

Downloaded the latest drivers for the Motherboard and the fireface to, but nothing changed.
Any suggestions?

  • Registered: 2010-02-20
  • Posts: 8

Re: Clicks and pops, asio meter spikes in Cubase 5 with FF 400

Just checked my BIOS settings and my C1E and SpeedStep (Cool and Quiet at AMD) where already disabled, so no luck until now....Any other suggestions?