I'm really really sad that is why I post the following here: I bet that is the solution to solve the issue with the vst3 - plugins of Softube.īecause - what I don't understand is, that the vst2 are working as intended, only the vst3 is doing it strange and wrong.
I haven't recognized that make mono plugin issue so far - bloddy Frankie -)
I just checked Neutron - it can at least handle 4 channels. That makes it a little clearer to me.Īt least they could provide up to 4 channels, couldn't they? iZotope essentially told me no way when I asked about getting Neutron working multichannel in Reaper, and I've since dropped using it (although already lost the money). I'd be curious to know whether they think this is even within the scope of the tool. FabFilter stuff doesn't, for example, which drives me nuts with regards to bus processing in surround mixes. Having the thing operate as a multichannel plugin would be ideal.īut not every plugin I own operates as multichannel. But if you're working with true multichannel content, or using it on a multichannel bus, that would obviously not work well. This actually kind of works well for me because, when I do multichannel tracks, I'm generally panning mono sources to surround. On a track with two channels, it operates in stereo. When inserting the VST3 version of the plugin on a track with greater than two channels, it appears to revert to a mono instance with a single mono sidechain input. When you don't touch em, the bug is not audible because then it's in the middle position and still balanced. I got aware of the bug not directly, but when I turned the amount knob far left or far right. You may want to try Drawmer outside of console. The issue is not that it ain't running smooth - the issue is, that the knobs are no longer doing what they do on tracks with only ONE stereo channel. Then check what the knobs for Amount and Gain are effecting. Please use console on ONE TRACK and raise the number of Channels to 4 on that track. Thank you for testing and the hint with the buffering.īut the issue has nothing to do with the number of instances - it's only a matter of the NUMBER OF CHANNELS within ONE TRACK. That's something which could affect the smooth playback as well, try to change the value. How is your Reaper preferences - audio - buffering - anticipative fx processing? There is 200 as default – but i changed it to higher amount earlier. I've just changed the compressor module of 4 instances/tracks to Drawmer and it runs smooth as well. It's now about 6 Months that I talked to the support team of Softube!! Acustica Audio had a similar issue and solved it in just a couple of weeks. with only 2 channels plugin works correctly. when I turn the amount knob all the way to the right only the left side gets louder and the Gain Knob in the output area also is just changing the left side.īut as I said - only when a track has more than 2 channels. I had really strange behaviour with knobs doing different things as supposed to when I tried to use the Drwawmer S73 as vst3.į**ck.i just installed the latest version and still the vst3 plugins are NOT WORKING CORRECTLY when the Track Channel Count is more than 2. Would you please check if the plugin is working correctly, too when the track channel count is more than 2? My test: i run 32 instances of Console 1 VST3 plugin within latest Reaper on OS X (all parts of C1 plugin are active) and everything sounds smooth and clean without any glitches – it made my day Softube and Cockos!!! I love you :-) :-( I'm not a reaper daw senior yet and it's possible there can be something wrong with my settings – so i'll be happy for any advice. The video (recorded with mobile for the cpu save purpose) is here:Īnd it contains 2 parts – the first one (time 0–0.35) is that behaviour already described earlier – it's a bit better than before i guess, but the behaviour changed after few minutes of playing and as you can see next, the dropouts became worse, longer, audibly distrorted and the CPU load of that instance increased rapidly (sometimes it takes even 40 % and whole daw becomes useless. You can also find every (i hope) technical specifications about the daw, my mac etc here: I've just tried to record my experiments with very simple reaper project (one stereo wav with VST3 Console 1 plugin – reaper is the only one running app, wi-fi, bluetooth, file sharing, most of services etc are disabled for that and i started the test right after system reboot.