Fly Studio wrote:Hmm, are you sure the VST3 VTM is still not rendering? I just used it on several clips in a montage and it seemed to work.
Fly Studio wrote:On the other hand, the VST3 VBC has several problems: metering will fail but processing will continue, or both will fail on render.
Fly Studio wrote:Slate told me something similar regarding the 'threading model' of Steinberg products. I don't know all the coding details you guys talked about; it's enough to keep up with the work.
Fly Studio wrote:
Hmm, are you sure the VST3 VTM is still not rendering? I just used it on several clips in a montage and it seemed to work.
It might be a bit different in the montage, but the main usage for me (Master Slots), it isn't rendering. Recently tested the most current version (public beta for AAX, with the shrinkable GUI, v1.1.3.x). I'm about to get in touch with the Steinberg support about this bug.
What's happening (currently), is that the plugins do work in realtime. But after rendering in WL (no matter which SRC!), the settings are being ignored (i.e. Compressor settings). The only thing that is happening, is some sort of slight volume and phase shift. So the signal can't be nulled anymore. Which confirms, that "something" is happening - it's just that the major settings are being ignored, and the signal is not being processed.
Not good maybe but 100% compliant with the vst3 spec. Moreover this behavior is very necessary for plugins with strong link between GUI and process like an fft realtime analyzer. Many vst3 plugins from many companies behave like this.
And still without FX automation available, the time-saving features that I DO like about Wavelab have quickly been rendered useless by all of this other fussing around. If I can't trust my software to do the most basic things properly, then I suppose it's time for a change.
Fly Studio wrote:And don't dare assign a high latency plug-in (like linear phase EQ) to a montage clip - it will create pops and dropouts in the next clip, at the point where the buffer ends (a 3/4 second latency will cause a disruption 3/4 seconds after the clip ends)
gkephart wrote:Yes, this is a real time killer, especially when trying to get real work done. Nugen audio VST3's also do not render, even when in a track slot, as well as Slate and Klanghelm. Now I've got to waste time testing my other VST3's for proper operation: all Brainworx, Voxengo, and Waves.
Jperkinski wrote:Does this Slate bug still exist in WL 8.5?
PLUG-INS: Rendering certain VST 3 effects used within the Master Section now works as expected.
Jperkinski wrote:Slate seems extremely slow to update anything and it seems like they have too much other stuff going on to address this issue.
Jperkinski wrote:What exactly was the main problem again? Do files render without Slate all together? or just some plugins and just some settings?
Jperkinski wrote:Is it just related to rendering before saving the montage?
Jperkinski wrote:Is VST-2 ok to use for now?
Users browsing this forum: panatrope and 2 guests