ReverbX Crash?

  • Thread starter Thread starter bdemenil
  • Start date Start date
B

bdemenil

New member
Thanks to Tubedude's recomendations, I've been playing around with Timeworks ReverbX. I got it working fine on Win ME, but on win2K and winXP, it crashes whenever I choose Auditorium, Large Room, or Bright Hall algorithms.

I emailed their tech support about ten days ago, but am still waiting to hear back.

Ben
 
Here is a copy of an email I just posted to the Timeworks tech support guy who finally answered after about 3 weeks.

I have just finished running numerous tests to try to determine the root of the problem. What I have found is that ReverbX runs fine on all my systems, under either win2K or Win98, if the sample rate is set to 44.1KHz. If I set the sample rate is raised to 48KHz or higher, the more complex algorithms - Hall, Room, and Chamber - cease to work - crashing the program if selected. This happens whether the OS is win98 or win2K, so my initial belief that the problem is OS related, is wrong.

I have tested on the following systems :
#1
Win 98 + win2K
AMD 1.2 GB Tunderbird
256MB PC133 RAM
Epox motherboard w/ via chipset
Both MAudio Delta 66, and onboard sound.

#2
Win98 + win2K
P3 733
256MB PC133 RAM
Asus Motherboard
MAudio Delta 66

#3
Win2K and WinXP
Dual AMD MP 1600
Tyan Motherboard
512MB 2400 DDR
MAudio Delta 1010

Mixing software on all - Cakewalk Sonar, Ntrack 2.3 + 3.0

I suppose a common element here is the MAudio delta series soundcard. However, I did get the same result with the Epox onboard sound. My previous belief that the problem was OS related was due to the fact that in win98 I was always using the 44.1K sample rate.

Considering the diversity of systems on which I have encountered this problem, I cannot believe that I am the only one experiencing it.

Ben
 
Well,

Timeworks have now posted a fix to this problem. ReverbX now works correctly at any sample rate. Their customer support never took the time to get back to me though.
 
The fix is to download and install version 2.3 - which Timeworks put up on their website 2 weeks ago. There's a link to it from http://www.sonictimeworks.com/home.html .

What pisses me off is that they saw they had the problem, but still never bothered to get back to me about it. I also wonder how they could release a high-end audio plug-in without testing it at samplerates above 44.1K . And if the plugin came out in July - with a first fix released in August - why did it take them so long to notice?
 
You must log in or register to reply here.
Back
Top