Martin Saleteg - the driving force behind Vienna Suite - just informed me that the problem is fixed already. An update will be released during the next few days.
Thanks for your patience!
/Dietz - Vienna Symphonic Library
194,603 users have contributed to 42,924 threads and 257,981 posts.
In the past 24 hours, we have 2 new thread(s), 8 new post(s) and 118 new user(s).
@denka said:
I hope that RTAS optimization will be included in this update.
It is.
One thing worth noting however, compared to previous versions of the Convolution Reverb, the new version will give much lower CPU usage with higher latency settings. Please do NOT use latency settings which are lower than your soundcard buffer size. In previous versions of the Convolution Reverb, high latency settings actually gave an increased CPU spike load. The setting is explained in the updated Suite manual.
@denka said:
I hope that RTAS optimization will be included in this update.
It is.
One thing worth noting however, compared to previous versions of the Convolution Reverb, the new version will give much lower CPU usage with higher latency settings. Please do NOT use latency settings which are lower than your soundcard buffer size. In previous versions of the Convolution Reverb, high latency settings actually gave an increased CPU spike load. The setting is explained in the updated Suite manual.
great news. tnx martin.
HI,
Yes, that´s the new version, 1.3.1589, changelog should be updated any time.
Here are the fixes:
• Hybrid Reverb: Fixed bug that could cause muted sound output
• Hybrid Reverb: Fixed bug that could cause loud noise
• Hybrid/Convolution Reverb: Fixed crash in trying to set sample rates lower than 44.1kHz or higher than 384kHz
• Hybrid Reverb: Was reporting too short tail time, now fixed
• Hybrid Reverb: Fixed missing resource for ProTools plugin on Windows
Best,
Paul
Yes, I've had the same problem when using Cubase 6 with Vienna Ensemble Pro and Hybrid Reverb. To solve the problem, I quit Cubase 6 and reload. This usually works until I turn the computer off.
I have an i Mac OS X 10.6.7
Derek Spedding
I am experiencing the same problem, esp the monitor explosion and heart attack. Love the reverb though. Hopefully a fix is coming soon.
I just installed the last version (1.3). But the problem seems to be same ...
Monitor explosion ... Logic 9.1.3 ... OSX 10.6.7 ... 64bit.
Yes, I've also installed the latest version of Hybrid, but the problem persists. I agree, it's great software - compare with altiverb!
I keep looking in the software download section, but there's no later version yet.
Thanks Paul,
that's good news.. had the "cause loud noise" problem on my mac pro, os x 10.6.7, Cubase 6.0.2 today..
even realoading the plug-in did not solve the issue.. however, i'm very optimistic that the coming release will fix this..
after all - vsl software is my favorite - for a reason ;)
thanks
gernot
Hi,
Just adding myself to the choir of people who STILL have this problem. Running Logic 9.1.4 64bit, VEP, Mac OSX 10.6.7 and the latest Vienna Suite build 1.3.1589 on a 2008 2.26 eight-core Mac Pro, w/28 gigs of ram. I am running a complex template with many instances of Kontakt 4, Trillian, Omnisphere, RMX, Amplitube 3, etc. plugins without issue otherwise. This is an extremely stable rig. And I have not had this problem happen due to any other plugin, including the other Vienna Suite plugins, EXCEPT Hybrid Reverb. Also, this is not related to Mac core overloads, at least as reported by the meters in Logic - playback was stopped and the cores were far below max when this latest monitor explosion occurred. There were several instances of Hybrid Reverb instantiated.
Just changed a preset in Hybrid Verb and whammo - Full code white noise @ over 100db [film music studio - high volume for dynamic mixing headroom] - think I may have just done real damage to my ears along with my rather expensive Quested Main Monitors.
This is an intermittent, but absolutely chronic and extremely dangerous problem. I have set the buffer to the same as the audiio card [256] [and also to the default 512] with no improvement.
I can verify that, contrary to what Dietz said, this is NOT yet fixed. Very bummed, because I love the sound of this reverb, but it will now be relegated to the "do not use until fixed" column. My ears are still ringing, and hurt enough to be giving me a headache :( :( :(
Will send to support email as well.
Thanks.