Clicks and pops since version 4.0

[mcneilis]

Hi,

I didn't add this on to the \"Clicks and Pops still in 4.0\" thread as my problem has only just started since upgrading to version 4.0. I have had my UAD-1 cards for over a year and this is the first time I've had clicks and pops. I have not changed any hardware or software since the upgrade. I'm getting the problems with Nuendo 3.11 and Wavelab 4.01b.

I don't know if this affects things but I don't have any hyper-threading switched on.

Here are my specs...

INTEL PENTIUM 4 3Ghz Processor
INTEL D865PE Motherboard
MICROSOFT WINDOWS XP SP2
ATI RADEON 7000 64M graphics card
4x DIMM DDR 400Mhz 512Mb RAM
RME HDSP 9632 Sound Interface
UAD-1 x 2

Any help appreciated.

Thanks,

Michael.

 

[.mr chris]

what is the PCI lantency of the ATI Radeon?

 

[mcneilis]

Hi,

I don't know how to find the latency for the graphics card?

My RME soundcard latency is is set to 256 samples as always in its settings window.

In Nuendo, (once i add plugins) the uad-1 Performance meter reads 256 samples as buffer size and current and new latency is 512 samples.

For Wavelab I have these at 2048 and 4096 as it's not so important in Wavelab for the lower latency.

I'm pretty much a novice at understanding latency so don't be afraid to say I'm talking crap.

Thanks,

Michael.

 

[franYo]

You need a tool such as this one:

http://downloads.guru3d.com/download.php?det=951

Franjo

 

[mcneilis]

Thanks Franjo.

My graphics card has a latency of 255 samples along with my soundcard too.

Thanks,

Michael.

 

[.mr chris]

... \"somehow\" I knew that

so-ho: 1st dont mix asio/ sample buffer latency with PCI latency, 2 different things.

use the PCI latency tool and set the PCI latency of the RME to 255/ leave it like it is. THIS IS HOW IT SHOULD BE.

Now, set the PCI latency of the ATI to 64 or even 32.

In other words, higher PCI LATENCY setting allows the device to \"hold\" the BUS longer, trying to \"increase\" overall performance.

The RME stuff is so \"intelligent\" to quickly release the PCI bus when it is \"done\".

The ATI gfx guys seem to set the PCI latency always to their favor, means on different systems I have seen and own, it is always set to 255... not true for e.g. Matrox Gfx cards... anyway

save the settings, apply at startup and check IF this helps you setup

HTH,
.chris

btw. latest version is 2.7: http://www.audiotrak.net/support_faq.htm

 

[mcneilis]

Hi,

I'll try that soon, Mr. Chris. The reason I cannot try right now is I'm having another problem with the playback of my audio in Nuendo and Wavelab now.

To save starting another thread in another forum, maybe you have an idea why my audio every now again plays at half speed even if I have it set to 44.1k at all times in Nuendo and Wavelab and the files I'm playing are 44.1k also.

Thanks a lot for all your help,

Michael.

 

[.mr chris]

hm, ... this sounds like some \"bad-clocking\".

- is your rme set as MASTER?
- did you try with a clean .npr with NO UAD plugs?
- how are your other UAD settings?(see UAD-1 config window)
- which RME hdsp 9632/ firmware are you running?

you also could try to UNINSTALL the UAD software complete, means after uninstall *check* the vstplugins directory if \"something\" is left also in your \"program files\" folder etc...
- then reboot
- then *fresh* install of the UAD 4.0 installer.
- then reboot again, then try with clean .npr to do some testings

HTH, .c

 

[philwal]

... "somehow" I knew that

so-ho: 1st dont mix asio/ sample buffer latency with PCI latency, 2 different things.

use the PCI latency tool and set the PCI latency of the RME to 255/ leave it like it is. THIS IS HOW IT SHOULD BE.

Now, set the PCI latency of the ATI to 64 or even 32.

In other words, higher PCI LATENCY setting allows the device to "hold" the BUS longer, trying to "increase" overall performance.

btw. latest version is 2.7: http://www.audiotrak.net/support_faq.htm

I just tried the latency tool. My ATI setting was at 255 and I reduced it to 32. I noticed that there were two ATI devices, the other was already at 32. The UAD cards are both at 64. I use a Tascam US 122 audio midi interface, so as far as sound card settings are concerned, the latency tool cant adjust anything on that. Should I adjust the latency of the UAD cards?

philwal

 

[Akis]

AFAIK, 64 is a good PCI latency value for UAD-1, Powercore etc.

 

[mcneilis]

Hi,


I tried switching my RME card back as the master (it was on autosync for 2 months with my Kurzweil KSP8 as master) and it worked for maybe 10 mins. I started typing a message on here to say it was working and then suddenly it went back to not working again. It's pretty random. The drivers for the RME are up to date by the way.

The following has been the case since I got the RME card last year but maybe it has something to do with it...

Everytime I click on my RME card settings page, the following settings change within a second...

System clock frequency goes from 44.1k to 32k..

and maybe less importantly... the autosync ref says input ADAT and frequency 48k but after a second goes to blank. I use ADAT to record from.

When I play back in Nuendo or Wavelab, the system clock frequency goes back to 44.1k.

As for the clicks and pops, I've changed the PCI latency of the API down to 32 and for the 10 mins I got playback working, one 16 bit track rendered with UAD-1 plugs and didn't have any pops but another did and all my 32 bit ones I tested did too.

I've tried rolling back to version 3.9 of the UAD-1 software (I don't have the Dimension D so I may as well go back to a version that worked for me) but I cannot check if it's working fully until I've got the playback working on my RME. Maybe I should post in RME forums too?

Thanks,

Michael.

 

[philwal]

AFAIK, 64 is a good PCI latency value for UAD-1, Powercore etc.

I tried altering the setting for UAD, and found that there was some improvement at 128. I figured that if there were two cards, why not double the latency? Still not perfect though. I didnt have this problem before version 4 and before adding the extra card. Perhaps there is a recommended setting for using two cards. I note in the manual that the experts at UAD can recommend different settings. I am waiting for a response to my query.

 

[mcneilis]

My UAD-1 cards were set to 128 so I've lowered them to 64 myself too. Thanks Akis.

Just following on from my past post slightly. The playback does seem like it's playing at 32k and not at half temp (22k from 44k) as I originally thought so maybe the 32k setting on my RME clock settings that it changes to is important?

Michael.

 

[Akis]

I remember having a similar issue with my RME and Windows Media Player a couple of years ago, where it would set the sample rate @ 32K randomly, but unfortunately, I don't remember what solved it. Sorry...

 

[mcneilis]

So my computer has randomly started playing at 44.1k in Wavelab again as I wanted, and using software version 3.9 I'm getting no clicks or pops, so I'm going to leave it as this version for now. I just hope it's randomly fixed in version 4.1 as I want to buy the multiband compressor.

As for the 32k playback, I still have no idea about that and it will probably randomly go back to not working soon enough, so any other suggestions are still welcome.

Edit: The 32k problem did come back but when I opened up Media Player and played some audio and went back to Wavelab, the system clock stayed at 44.1k as desired. I then had the problem again 10 minutes later, and did the same thing in Media Player and it has started working again. There's definitely something happening with the system clock and Media Player seems to be resetting it back to 44.1k for me.

I'll post on the RME forum to try and find a permanent solution.


Thanks,

Michael.

 

[philwal]

It seems I may have sorted my problem, though time will tell. I checked the system information in Accesories, and noticed that one of my cards was sharing an IRQ with the Radeon graphics card. I assumed it was the new card so I changed that to another slot. Checked the IRQ and found that I still had the conflict, so realised that the first card was the culprit, even though I only had the problem recently. I changed that to the slot vacated by the other one, and seems to run better now. Also I seem to be able to run my ES122 at 512, though not at the 256 I would prefer.

Perhaps it is worth you checking for IRQ conflicts as well?

Best of luck

philwal

 

[philwal]

I spoke too soon. The cliks pops or silences are still coming, maybe not as frequent. I have tascam us122 set at highest setting of 2048, the UAD latency is siiting at 192, which has given no clicks for over 3 minutes, the longest yet. It needs to be clean so I can master. The Expert setting in VST bay is for high audio. Internet connection is shut down as is all inyternet security software, so I am puzzled at what is wrong.

Does it matter which PCI slots the cards are in? They occupy IRQ 18 and 19.
Any suggestions, as this is starting to cause a lot of wasted time.

 

[philwal]

Further investigation, and I tried increasing the CPU limit to 100% in the Performance meter. This led to a click free performance. Two more performances of same project and still no clicks. 16 plugins were in operation but below the 98% limit that I had selected. The VST performance monitor showed a lot of activity, around 45-50%. On changing to a 100% ceiling the VST meter showed 30-35%. The increase in headroom seems to have removed the stress that caused the audio dropouts.

Able to get back to some creative work again.

 

[.mr chris]

Michael,

to me it looks like *you* should do some serious research/ re-reading of your RME manual and checking the basic \"tweaks\" for an Audio-PC/ DAW.

the sample rate switching is sure solved with tunig tip #9
http://www.musicxp.net/tuning_tips.php

HTH and I think you \"know what I mean\" :wink:
.chris

 

[MASSIVE Mastering]

Try something -

Switch over \"Generic ASIO Multimedia Driver\" when you're not actually tracking. With Cub/endo, this rarely fails. Of course, there can be other contributing factors, but at least give it a shot. It's worked for more people than I can count.