“However, it only supports VST2 plug-ins, not VST3” - that’s the problem with jBridge.
1 Like
Exactly. I have 3 different monitor speakers and headphones - when I change the monitor having the plugin in here - automatically with this change individual set-up SW SoundID plugin is activated with correct curve. When the SW plugin was as main insert - you have do manually change the correction profile inside SW plugin - whenever you change the monitor speaker.
@Highly-Controversial check out this video, round 7:00 min - Chris Selim is explaining this technique.
Great! Really glad it was helpful!
2 Likes
Yes there is that but you have no risk of knocking the volume control and SW peaking into distortion which could potentially cause harm to your monitors .
I have 3 pairs ABC and i only active by a button on the controller the SW’s i need , it means pressing two buttons but i’m for safety over convenience . That’s the thing with Cubase so many ways to work , it’s what ever you feel comfortable with
Not sure about what peaking you are writing? My Sonarworks plugin is not peaking. Only one monitor is active at the time and only that one receives signal, only one instance of Sonarworks is active at the time, and i have the option “safe headroom” activated in SW SoundID plugin - which prevents SW peaking/cliping due to correction curve adjustments. So I have no problem with peaking, distortion whatsoever. In my opinion both ways of using SW in control room are ok.
1 Like
I know how Sonarworks cheers, If you turn the control room volume up , is it possible to push the volume into Sonar works causing it to hard limit via the monitor inserts ?
thanks for this, I only have 3 tracks running, 1 X FF Twin 3 and Spitfire LABS Soft Piano and it clips and Spikes lots. On Mac Studio Max 64Gb Ram
Ok, it has never been an issue for me since I don’t use the control room volume knob (it is always in the same position). I use hardware volume control on my desk for monitors volume adjustment.
1 Like
Been using Bidule for ages. It’s quite the Swiss army knife of a plugin. Works in instrument or mixer slots. Synced in stream or discrete processing abilities. Can host, or be hosted as (make a solid multi plugin/platform bridger/chainer): stand alone/VST2/VST3/AU/CLAP/ReWire. Monitor and manipulate MIDI and Audio in real time. Play/Record/Loop audio/midi. Arp/Step/Stochastic sequencers. Link and manipulate VST parameters. Convert VST to CC and vice verse. OSC Server/Client.
Set up alternate mixers/gain-stages. Ability to automate it all from the DAW (VST), MIDI, or OSC.
One of the first and most basic uses I got from Bidule was the ability to load or kill various plugins while the transport is going and not suffer from terrible audio glitches and transport pauses. Would always keep an instance or two in project templates reserved for such purposes.
1 Like
Maybe nothing but here goes.
Cubase 13 empty project with ur22 plugged in but not assigned. The peak meter is spiking like crazy. Simple 1 track recordings popping an clicking constantly.
I stopped my usb 3 ports going to sleep in power manager and have massively reduced the spikes, with no audible noise on the next take.
hope this helps
Im afraid this is standard optimisation , make sure all services are set to NEVER sleep
I use oversampling quite a bit. This is alarming.
1 Like
Update :
And believe it or not , i think the pain and the heartache has been worth it .
i9 , total complete new install .
Bios Flash
Bios configured by Windows pro tech
Windows with ALL up todate drivers installed professionally
Windows fully optimised
Nvdia setup with the latest Steinberg recommended posted the other day .
Test
16 SSL X sats
4 Pro R2 reverbs
1 MF heavy bastard Steinberg Multitap delay on an outrageous Cpu heavy preset
Test drum loops
The new Plutec plugins
Imager
Dsm Limitless
3x Sonarworks
2 x Supervision
Results
Absolutely rock solid ASIO at the moment in a new project test . I’m not going to bother loading any projects made in C12 , nor am i loading bad on a couple of brands of Plugins .
To be honest , with the new plugin set and a few from C12 i have non need to install any other brands than the ones mentioned part from 2 more .
I’m really happy with the results At the moment , obviously time will tell once the project grows but , i haven’t even got any graphically glitches .
I haven’t tested the Halion7 midi issue yet but that will only make the Asio go down lol
Was it worth a completely annellation and rebuilt ? It may look like it was .
It’s been a loooooooooong week
Hopefully creative flow can now take priority , if get writers block i’ll Head for the nearly cliff 
3 Likes
So, in the end, it was in fact a configuration issue with your specific computer?
I also got a lot of spikes when I turned on over-sampling on a particular 3rd party plugin (Sonimus N-console).
1 Like
If I’m reading his initial configuration and new configuration correctly, he also went from an i7 to an i9, so a much more powerful CPU, and perhaps one that was benefited, instead of disadvantaged, in the Cubase 13 modifications mentioned that may relate to affinity in a recent post from Steinberg on this investigation.
I knew the Steinberg lynch mode would try this .
Might be , migt not be , could be something in the windows setup the NEW C13 did not like , could be anything , all i know is the problem has been recognised by Steinberg and Steinberg are working for a fix , i was told by a member of Staff that i MAY still encounter issues with the new install so , in light of your comment … I doubt it
I was told the i9 will perform a lot better due to the 16 threads BUT the problem may still persist . Straight from Staff
1 Like
If a project runs well on the same machine in CB12 and not on CB13 then the fault is with some change in Cubase , nothing else.
6 Likes
And if a VST plugin/instrument is running stably on the same system when hosted inside of a competing VST host at the same settings, or when hosted externally from Cubase, inside of AudioGridder, or Vienna Ensemble pro, locally, on the same system, but not in Cubase, then it is safe to conclude that Cubase is the issue here.
Throwing more money or processing power at the problem is not the solution. Optimizing the software is.
2 Likes
Exactamundo , reinstalling everything has just removed any underline issues