A quick test shows it doesn't report it's tail time correctly so stopping a cue stops the reverb dead. It sounds quite good though.
It works fine in mono on a insert in the edit device page although something weird is going on (as it is with most reverbs applied like this.)
TEST Play audio through an output with effect inserted./Stop audio/ effect inexplicably stops dead/ play another audio cue/ reverb from original cue starts playing again from the point the reverb cut off. END TEST
As with most reverb plugins, its very difficult to use on the effects tab of a mic cue, as it is very difficult to predict how your interface is going to appear to the plugin in and whether it will process, pass or block any signal paths that do not match the IO configuration of the plug in.
I haven't found any consistent or reliable way to use reverb plugins in Qlab and I must have tried over a dozen plugs now. There is probably a reason why other programs attach effects to signal paths rather than individual bits of audio (unless pre-rendering them). Even when utilising them in Qlab signal paths as in the example above there are clearly fundamental problems with the Qlab plugin architecture which give rise to some unexpected things happening.
With reference to mic cues if someone can explain how a stereo i/o plugin maps to a microphone cue that (with my interface) matrixes 10 mic inputs to 10 Qlab outputs then I might begin to have an understanding of how this was meant to work.
Mic
On Wednesday, October 9, 2013 8:48:07 PM UTC+1, Andy Lang wrote:
.