Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
pops and clicks with new update
Last post Thu, Feb 28 2013 by gstew, 4 replies.
Options
Go to last post
Posted on Thu, Feb 21 2013 23:53
by gstew
Joined on Fri, Oct 19 2012, Posts 22
hey guys,

anyone know if I can just re install the 5.1.11947 update to get back to the last version,this one is giving clicks and pops like crazy,even with 4 buffers(only ever had to use 1 before).

thanks,

Grant
i7 3820 3.6ghz ,Asrock x79 Extreme6,64G G-skill Ares Series DDR3 1600 RAM,Corsair H80 cooler, Corsair Force Series 3 240G SSD,OCZ Vertex 120G SSD,Samsung 240GB SSD,Seagate Barracuda 2TB 7200 HD,EVGA GTX 460 GPU, Corsair TX 750 PSU
VEP5,Cubase 7,Hollywood Strings Diamond,Hollywood Wood Winds Diamond,HW Brass Diamond ,EWQLSO Platinum Plus,QL Spaces Reverb,Sibelius 7,M-audio Oxygen 88
Posted on Fri, Feb 22 2013 16:11
by Paul
Joined on Sat, Aug 03 2002, Vienna, Posts 13521

Hi Grant,

I have already answered your mail to

Yes, you can roll back without any troubles. Close all VSL software and install the older software from the VE PRO 5 archive, if you like.

Best,

Paul

Paul Kopf
Product Manager - Vienna Symphonic Library
Posted on Mon, Feb 25 2013 11:53
by crusoe
Joined on Sat, Dec 26 2009, Posts 141
Since I had the same problem and was able to resolve it, here's a short description of the steps I followed. Maybe this will be helpful to someone.

1) Observe the machine behavior. It's likely that you have nothing to observe - started playback, pops and clicks no matter what you try. But if you are lucky, there could be some hints that might help later. For example, in my case the playback was clean in the beginning, but after I'd start using the MIDI controller, switch to the other windows, etc., the sound artifacts would appear more and more often. This likely suggests a software problem, so I started digging in this direction.

2) Localize the source of the problem. The problem is fairly complex, that's why the first step above is important. The hardware could simply malfunction. There are common-sense methods to check this, so I won't add anything except for one note. If you have an USB self-powered audio-interface, there's a chance it doesn't get enough power from your machine. To check this, you can try using the double-end USB cable (check the image). On the software side one must put attention to the following: audio drivers, DPC latency (google this if you don't know what it is), any other running programs.

3) Eliminate the suspects one at a time, observing the result every time changes are made. The most complex here is the DPC latency. If you are on Windows Vista and later, I suggest that you use the ADK advice from this page, even though there exists an easier to use LatencyMon and such. ADK will give you better results. So if DPC is indeed an issue, you will identify it this way. Drivers: carefully search the Internet for the similar issues on the same hardware/software pair as yours. The newest audio drivers are not necessarily the best ones.

In my case there was a problem with the audio driver. I didn't suspect it though because didn't update it for a long time, and there were no hardware changes at the time pops and clicks started. At the same time, I did VE PRO update, no wonder I suspected it. I checked the DPC latency, and identified ndis.sys spikes caused by NLA service, exactly as in the link above, disabled it, and reduced the maximum DPC latency ever taking place to 256. The problem still persisted. I tried removing any extra VST from the project, and ended up with a single track, low CPU usage, and audio pops. Needless to say, the latency settings in ASIO control panel and in VE PRO connection wouldn't change anything. Finally, I downloaded the 1.21 beta driver from Presonus that I previously avoided because of the 'beta'. And voila, problems solved. Turns out the whole Presonus VSL line has (or had) this issue.

Posted on Thu, Feb 28 2013 07:26
by gstew
Joined on Fri, Oct 19 2012, Posts 22

hi,

I'm pretty sure at this point it's a driver issue with my m-audio audiofile 2496(it's PCI) . I had an online support session with Steinberg the other day and they were positive it's a sound card/driver issue. It's NOT THE VEP5 UPDATE (I should have posted that the other day).
I'm thinking of maybe trying an earlier driver version,what do you think of that idea? Otherwise I may swap it out for another sound card ,I can still return it.

thanks for your help,

G
i7 3820 3.6ghz ,Asrock x79 Extreme6,64G G-skill Ares Series DDR3 1600 RAM,Corsair H80 cooler, Corsair Force Series 3 240G SSD,OCZ Vertex 120G SSD,Samsung 240GB SSD,Seagate Barracuda 2TB 7200 HD,EVGA GTX 460 GPU, Corsair TX 750 PSU
VEP5,Cubase 7,Hollywood Strings Diamond,Hollywood Wood Winds Diamond,HW Brass Diamond ,EWQLSO Platinum Plus,QL Spaces Reverb,Sibelius 7,M-audio Oxygen 88
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.