Salvatore Sorice

OK, I got it... I usually delete the "Preview" and "Metronome" Buses from my Projects and Templates. I added a new "Preview" Bus and all is well. @mettelus - thanks for the heads-up. I already have LoudMax on my Master Bus, set to -1.0db, just in case... :^)

Thanks @Chaps - I'll give that a try when I'm back at my PC later today.

Not sure if there is a setting I'm missing but if I Browse and Audition any Shots/Loops in Bandlab Sounds they are incredibly loud. Sonar (latest build). Looks like the Sounds are routed to my Hardware Outs and there is no way to change it. To not blow my ears off I have to turn my Hardware Outs waaay down - but then everything else is too low in volume. Is there a way to route the Sounds to a "Preview" Bus so I can adjust the volume? Do I have something set wrong?

Thanks @Xoo! Under Preferences/File/VST Settings I unchecked "Hide Related Plug-Ins" and the Sonitus ones are now visible. I guess they are "related" to the new Core Plug-Ins...

Thanks all for the comments. I tried using @Noel Borthwick redistributable installer, tried regsvr32. No help. I know about the auto-replace feature, but that is not the issue. The issue is that the Sonitus plugins are installed and work (ie, if I load a project that has them they work fine). But I can't find them anymore in the FX Browser, etc. (see my screenshots above). Maybe @Noel Borthwick or @msmcleodcan let me know what I'm doing wrong. Thanks in advance!

I know about the new core plugins. Still want to access the old Sonitus ones…

Hmmm. I was working through a tutorial and wanted to use some Sonitus Plugins. Tried to browse for them but none appear except for the Sonitus SurroundComp. They are in the scan path. Tried rescanning, scan failed plugins, etc. Even tried copying one of the DLLs to another folder in the scan path, No luck. They are not disabled. If I load a project that includes them they are working fine! I must be missing something simple. Any ideas? Here are some screenshots:

I still think the easiest workaround is to just remove the “s” from the https in the URL. No?

More RAM may help but it probably mostly depends on the plugins you’re using. Some are way more resource intensive than others.

Remove the “s” from the https in the URL.

What impresses me is that the Bakers really seem to be listening and doing their best to add the most requested improvements as soon as feasibly possible for a small team!

@David Baay - enjoy Pianoteq 9 - my favorite piano synth! @msmcleod - I set everything to Peak+RMS and now the meters all agree. Must have missed some settings (thought they were all the same), as navigating those Meter Option menus involve a lot of clicks! Still getting the occasional low meter segment staying lit as David confirmed.

Thanks Mark. I thought I had them set to the same settings. Will check when back at my PC.

Using current Sonar Version: 2025.09 (Build 038). Maybe it's always been this way, but today I noticed that the Playback Meter in the Inspector view is oddly different than in the Track view. Not sure how to explain, but the meter in the Inspector does not visually "agree" with the one in the Track View. It's "missing" some of the bars that fill the meter as sound is played (only showing the peaks), sometimes it only shows one meter bar (in this video sometimes only the right bar is displayed at a lower volume), and sometimes a single bar remains when play is stopped. Is this normal behavior? Could I have some weird setting enabled?

Giving this a bump hoping that the Bakers can implement it soon. Not knowing if a screen set is locked or not (unless you drop down the menu) is soooo annoying.. 😠