Wave Destination Module problems

Cj n' Malto · Post by **Cj n' Malto** » Wed Sep 05, 2007 7:46 pm

Hi there !
I'm Cj from France.
I' have these problems as well since I changed my configuration...
Before asus P4G8Xdeluxe, P4B, AGP with ATI, 2mram, I had no buzz.
Now I ugrated my computer in order to play with powerfull plugs in cubase.
Asus Commando, C2D e6600, 2mo ram, GPU Nvidia.

I use 1 pulsar 1 plus and 1 plulsar 2 classic.
And i don't want to change !!!!

I won power in cubase ! But I lost this : Impossible to use the pulsar wave driver to get my mix into wavelab

I got some audio clics, clips, buzz, etc... so first I try to change the wavelab preferences "buffer waves" but it was wronger and wronger

I reeinstalled my system several time, but nothing has changed.

Maybe I'm going to change my graphic card for a GPU ATI after seeing this :

http://www.kvraudio.com/forum/viewtopic ... d7207c4f5e

I use the same plug in Plugsound Pro and have the same problem !

Maybe I wonder if pulsar and PSPro accept else GPU than ATI ????

Malascope · Post by **Malascope** » Thu Sep 06, 2007 3:06 am

I have pretty much exactly the same problem that Smiley is having & have tried to solve in similar ways also to no avail.

I have a Pulsar 1 card (4 DSPs) & I can record into Cubase no problem but cannot record via wave module into Wavelab 4 or 5 either in 16 bit or 24 bit. I have tried similar things like putting the Pulsar into a different slot, reduced my video demands to basic, juggled the buffers in Wavelab etc etc.

I have the Pulsar installed in my brand new computer:
Intel Core 2 E6600
Motherboard: Asus P5B-E 965
2 x 1 GB DDR2 RAM
2 x 320G HD aaKS 7200rpm
Video Gigabyte X1650Pro
Win XP Home

I ran the Pulasr in my ancient P3 with Win 98 for years without this problem. It happened as soon as I installed it in the new computer.

Any further clues anyone?

Cj n' Malto · Post by **Cj n' Malto** » Thu Sep 06, 2007 3:13 am

Hi Malascope

Video Gigabyte X1650Pro

So you have got a GPU ATI
The Problem seems not to come from there ....

Smiley · Post by **Smiley** » Thu Sep 06, 2007 7:32 am

Hi folks, thank you all for your suggestions, its much appreciated here.
Now for the bad news

Ralph supplied me with a new Scope pro 14dsp beast....and guess what...the problem is still there!!!!!

Having just punted over 500 Euros I am not quite as happy as I could be

The card is great, and I am enjoying the added power of course, but I find this problem really irritating even though there are workarounds like recording the mix back in to cubase.

I havent contacted Ralph as my guess is all they can do is ask me to return the card for checks leaving me with no card for a month with no guarantee of fixing the problem.

It seems that there was no problem with my original card and right now I am just grateful that Ralph did me such a great deal on a new Scope Pro.

Ah well, nothing in life is perfect..but scope comes close

Cj n' Malto · Post by **Cj n' Malto** » Thu Sep 06, 2007 9:26 am

Ok this is no good !
But I'am using a "little trick" to do my mixes :

Shot at 2007-09-06[/img]

I reinject all the mix into Cubase SX3 to a new stereo track (of course take care this new track is going to a bus which is not going to the mix, if not WOOOOOOAOUH

larsen )

Malascope · Post by **Malascope** » Fri Sep 07, 2007 12:24 am

Thanks for the tip Cj & I have been mixing back into Cubase & that works fine but it's really annoying that I can't get get things to work smoothly as they should. I even get splutter & distortion just playing back wav files in Wavelab thru the wav module when I have Cubase loaded. They play fine when Cubase isn't loaded.

Like I say it all worked well on my old P3

Cj n' Malto · Post by **Cj n' Malto** » Fri Sep 07, 2007 11:56 am

Yep anyway I'm going to buy another graphic card (a sapphire radeon x1950pro)
I don't know if this will solve the Pulsar problem, but I hope this resolve the plugsound pro problem...

I think for this Creamware d'better to write some new drivers
When Creamware will upgrade their drivers ????
And if yes, I hope it will working with 64bit !!!!
Creamware wake up !!!

Post by **garyb** » Fri Sep 07, 2007 12:36 pm

have you tried setting wavelab's priority to "above normal" and scope to "low"?

there are no driver problems here, although a Vista driver would be nice for the platform's future...

dbmac · Post by **dbmac** » Sat Sep 08, 2007 4:55 am

Try increasing your ULLI (latency) setting - Wavelab doesn't like "ultra low" latency. It's not needed in a mastering environment anyway.

/dave

Malascope · Post by **Malascope** » Sat Sep 08, 2007 3:48 pm

Thanks for the the continuing interest everyone.

Yes the latency is set to max Dave.

I'm not sure how to change Wavelab's or Scope's priority garyb. Can you tell me? Plse forgive my ignorance.

Cheers

Post by **garyb** » Sat Sep 08, 2007 3:57 pm

to set priority, press cntrl/alt/del.
choose the "processes" tab.
find the application, i.e. wavelab, it may be abbreviated.
right click on the app.
choose "set priority" and highlight your priority setting choice.
you'll get a warning, choose "yes".
done.

Malascope · Post by **Malascope** » Sun Sep 09, 2007 6:27 am

Thanks for that gary. I tried your suggestion + a few variations....unfortunately that didn't work either

derdahli · Post by **derdahli** » Sun Sep 09, 2007 7:31 am

Hi!

Since I changed my system from P4 with and without HT on i865PE to an Amd X2 3800+ ( Dualcore Optimiser alreay used) on a nforce 550 chipset (Gigabyte GA-M55S-S3) I have similar and even worse problems.

On the first day I realised some clicks and dropouts recording via wave destination into Wavelab5.

But when I listen to webradio via Winamp or watch a movie with VLC it takes about 15 minutes until I get really strong distortion and a kind of slow tremoloeffect and it seem to get stronger by time. Sounds like a kind of sync problem.

Okay when this also happens to new, replaced cards I know now that it is not broken, that's good.

But perfective maintenance is the main reason not to use Creamware

Regards,
Christian

Cj n' Malto · Post by **Cj n' Malto** » Sun Sep 09, 2007 7:36 am

to set priority, press cntrl/alt/del.
choose the "processes" tab.
find the application, i.e. wavelab, it may be abbreviated.
right click on the app.
choose "set priority" and highlight your priority setting choice.
you'll get a warning, choose "yes".

I had already tried this

before.
It's a little better but still have some clips

Otherwise I bought another video card (with ATI this time) I increased my perfomances with Plugsound pro !

good news but not for this topic...
But nothing has changed with "Pulsar to Wave driver to wavelab"

Lima · Post by **Lima** » Sun Sep 09, 2007 11:04 am

Smiley, do you have any IRQ conflicts?

Smiley · Post by **Smiley** » Sun Sep 09, 2007 11:48 am

Hi Lima

No, all IRQ's fine, no conflicts with card.

It does seem to be at a hardware level....but where.... I have tried 2 different systems AMD and Intel (chipset and chip) and am currently using a brand new 14dsp scope pro..with no change.

Thanks for your suggestion though.

derdahli · Post by **derdahli** » Sun Sep 09, 2007 1:11 pm

Okay, it looks like my Wave Out tremolodistorsion problem only happens, when i put a cable( a very cheap one) into the SP Dif in/Out without connecting it to anything. So maybe its a different problem. Even when Scope is set as master.

But the clicking Wave In problem happened before i have used the SP Dif in.

Malascope · Post by **Malascope** » Wed Sep 12, 2007 3:01 am

Smiley if you ever solve your problem I'd be very interested how. My problem sounds identical to yours & it's driving me nuts!

I loved my Pulsar card when it ran on my old P3. I had been thinking about buying an additional Pulsar card but I really don't want to go down that track with things the way they are on my dual core system.

I have other problems as well like not being able to load more than one instance of MasterVerb without getting the "PCI Master Overflow" msg. (I can't even load a MasterVerb + a Masterverb Classic.) I could do this no problem on my P3. Does this happen to you as well?

Smiley · Post by **Smiley** » Wed Sep 12, 2007 4:20 am

Hi Malascope, thankfully I don't get your pci overflow errors..that sounds like an IRQ conflict, PCI bus drivers or other PCI card issue to me. Have you checked your IRQ's are not conflicting? Do you have any other bandwidth hungry PCI cards, are you using the latest drivers for the chipset? Sorry for asking this, but, did you install the chipset drivers when you built the new machine? Let me know dude, im happy to help if I can. As for the original wave dest problem....no luck so far, but to be honest it has taken a back seat in the priority stakes...I'm busy tryin to sell my house

I'll surely let you know if I find the solution though.

bassdude · Post by **bassdude** » Wed Sep 12, 2007 3:24 pm

Smiley, can you post up a sample of the "distorted audio".
Also, I've read thru the whole thread but did not see if you tried recording to another wav editor (like cooledit) to see if the problem exists there as well.
When you installed the scope pro did you format hardrive and do a clean install?