Greg Wynn

Hey thanks for looking into this. So I never ended up reverting to an earlier version and did some troubleshooting. 1. I thought it had something to do with ASIO buffer settings and swapped between 1024 and 128 and there was no change. 2. I took a good look at the plugins that I normally didn’t use in my template and saw I had a UAD reverb (Capital - next drum reverb ever ). I disabled it and then re-enable it. No change. 3. Puttered around for a bit before taking a break and rebooting - and then everything worked normally. Strange, eh ? I meant to update this thread and didn’t get to it but I thank you for looking into it !

Something is odd when I deselect and reselect a plugin. In my start template I have plugs I used for years each set up in tracks to give quick starting points with different choices. With this beta when I reselect a plug it sounds like audio gets all phasy. It only clears if I stop audio and restart the transport. That's never happened in 20+ years...but hey, it's what betas are for. EDIT - Yikes. I gotta roll this back as this issue is a show stopper for what I'm doing tonight. Anyone else ?

The assist feature is amazing for newish users. Well done !

Awesome ! Thank you.

Oh wow - I remember that ! It was a cool little program and actually taught me a lot about midi back in the day.

Thank you guys as always !

64 running at 6800 on an i9 14900. smokin’ !

Pretty sure that is true. Let me verify later on my own system and I’ll report here.

Yep. And it’s been like that forever. How do I know ? Because it used to drive me crazy until it became muscle memory to change it early in the project or use one of my templates that I’ve made.

Thank you for the plugin color changes for vst2 and vst3 !!

Backware compatibility. Recently I opened a project from 2009 and it opened fine (save for plugs that had long been deleted) and it opened fine with the vst2’s that were still installed. BTW - HUGE kudos to the Bakers making it so we can open files saved 15+ years ago. Try that, Pro Tools fans

this

It’s a thing that we used to have. Is it necessary ? Nope. But it was part of my workflow and made things 1% easier and sometimes just that 1% makes a difference. Why was it ever changed ?

Ugh. One of the updates made the colors as they are now. If I remember correctly the vst3’s were blue.

For old project compatibility I still have VST'2 that comingle fine with VST3's. However, can we get them to have different colors like they used to ? ?

Yep, for sure.

OUT FREAKING STANDING ! Thanks folks and thank you Meng !

I’m on Dark as well and also have the latest/greatest version. if I remember correctly all my VST3 were blue but as I said now they are the same color as my VST2’s - black. just odd….

Hi folks - I just noticed this so not sure when this changed but not that long ago in the menu where you select plugins it used to be that the VST3’s were (I think) blue and the VST2’s were black. Now they are all black ? Did I miss something ?

I recently opened a project that had been untouched since 2007. It opened flawlessly except for the plugins that had been jettisoned long ago.

I actually crank up Audiogridder sometimes because it catalogues all of the VST’s quite well and makes them quickly searchable.

Love the review but they REALLY need to get the name of it right !

The more recent updates have absolutely optimized Sonar - I remember using it the first time after the update and the difference was immediately discernible. And if there is even MORE optimizations then bring it on !

All the outputs go to “none”

Agreed , odd as I deleted the Fractal ASIO driver and yet the message comes up if Sonar is running and then I power up the Fractal, eh ? I I say to add it it then reverts Soner to 48k and completely remaps all my track and bus I/O’s. However now I can have the Fractal powered up before instantiating Sonar and it’s fine whereas previously Sonar would attempt to add it. EDIT - to answer the question - yes I was hoping to exclude the message. Thx for responding, @Noel Borthwick !