Sonar 2024.09 Feedback

[Noel Borthwick]

@noynekker I've tracked down and fixed the issue with BFD3. This problem is actually not new to this release but happened in the August release. You likely never tried it until now in Sonar.

The issue only happens in the old VST2 version of BFD3. When I first tested it in the new free BFD player groove playback it worked fine. We had to track down the old BFD3 and could then repro it.

The issue is caused due to a very obscure reason - we optimized time reporting to VST plugins in July and one of the changes was incorrectly reporting the transport changed state. This seems to confuse that specific plugin and preview returns a repeating buffer leading to the distortion.

The fix will be in the next release. However, for now a simple workaround is to run the Sonar transport. While the transport is playing, groove playback will work correctly in BFD3.
Thanks for reporting this.

[noynekker]

7 minutes ago, Noel Borthwick said:

@noynekker I've tracked down and fixed the issue with BFD3. This problem is actually not new to this release but happened in the August release. You likely never tried it until now in Sonar.

The issue only happens in the old VST2 version of BFD3. When I first tested it in the new free BFD player groove playback it worked fine. We had to track down the old BFD3 and could then repro it.

The issue is caused due to a very obscure reason - we optimized time reporting to VST plugins in July and one of the changes was incorrectly reporting the transport changed state. This seems to confuse that specific plugin and preview returns a repeating buffer leading to the distortion.

The fix will be in the next release. However, for now a simple workaround is to run the Sonar transport. While the transport is playing, groove playback will work correctly in BFD3.
Thanks for reporting this.

@Noel Borthwick . . . Thanks so much for taking the time to look into it deeper Noel ! Always appreciate your hands on input here on the forum, and glad I could report it here. I never noticed it until I started working on a new project, as you mention. I tried your workaround, and yes . . . if I drag out a midi note and play the transport, the groove editor in BFD3 does indeed work as expected. Looking forward to the fix😁 

[crazy sniffable]

On 10/27/2024 at 10:40 PM, msmcleod said:

This has been fixed for the next update.

Great news, thanks!

I must say you guys are knocking it out of the park working with people to find and fix issues. Glad I subscribed.

[Dam102]

Hello everyone, 

For some reason the Paid version of Sonar does not have the arranger options working. I installed to try the latest update and immediately encountered this.

What I mean is that I can even create from scratch while opening a new project but after a few minutes it won't let me edit, rename, alter in any way whatever is on the arranger lane and also on the left arranger window, I can't move them to rearrange or anything of the sort. 

On the free version all is well and working fine.

Anyone else experienced this behavior?

TYIA

[Wookiee]

47 minutes ago, Nuno Aguiar de Loureiro said:

Hello everyone, 

For some reason the Paid version of Sonar does not have the arranger options working. I installed to try the latest update and immediately encountered this.

What I mean is that I can even create from scratch while opening a new project but after a few minutes it won't let me edit, rename, alter in any way whatever is on the arranger lane and also on the left arranger window, I can't move them to rearrange or anything of the sort. 

On the free version all is well and working fine.

Anyone else experienced this behavior?

TYIA

Have you paid a subscription? 

[Dam102]

13 minutes ago, Wookiee said:

Have you paid a subscription? 

No, instaled to try first and check what the benefits at this time could be. Is it a trial limitation?

[Wookiee]

52 minutes ago, Dam102 said:

No, instaled to try first and check what the benefits at this time could be. Is it a trial limitation?

Probably limited functionality, most trials are.

[Andi Rock]

Just got the new software setup and loving it!  The tungsten theme is perfect, not the legacy one.  

[呂聖斐]

Hi, I found "audio to MIDI" doesn't work, 

I drag audio into midi track, but nothing happened,

 

But same project and same procedure, worked in Cakewalk Band lab latest Version
Am I doning anything wrong?

[Glenn Stanton]

is Melodyne installed? is it showing up in the Sonar list of plugins? it may be a licensed for CbB only version or running without a license?

[pwallie]

27 minutes ago, Glenn Stanton said:

is Melodyne installed? is it showing up in the Sonar list of plugins? it may be a licensed for CbB only version or running without a license?

is the basic version of melodyne still included?

[IgoRr]

4 hours ago, pwallie said:

is the basic version of melodyne still included?

No, but the basic version can be downloaded and installed for free using the "Check for updates" option in the "Help" menu, you will have all available free add. elements, among which there will be Melodyne. But it is best to have the "Pro" (studio) version installed, it works better and can be used in standalone format (Standalone).

[Kurre]

I think that a working Melodyne plugin only can be found in older CbB versions. Newer CbB versions only comes with Melodyne 5. That version only gives you a demo month.

However, if you never did a complete uninstall Melodyne kept working throughout later CbB versions.

A demo month is probably what goes for Sonar.

[IgoRr]

Good day!
A couple of days ago, I discovered a small and very strange bug - after some time of continuous work with the project, when opening ProChannel, the display of modules is shifted to the left by several centimeters, so that only a little more than half of all the content is visible vertically. No actions can restore the normal display, neither by minimizing the project/Sonar window itself, nor by closing/opening the "Inspector", nor by changing its location to the right, the normal display is restored only after completely closing Sonar and starting the project again. Unfortunately, I did not take screenshots of these incidents, but this is the first time this has happened in the entire time I have been using this version.
I have enough hardware for normal operation - Intel i3 8350K, all hard drives are SSD, two of them are Samsung 970 Evo Plus (NVMe 2.0), 32 GB RAM, Steinberg UR22C sound card, but there is no discrete graphics card, I work on the integrated Intel UHD 630 Graphics with the latests drivers, could this be the cause of such anomalies? Until this moment, nothing like this had ever happened before, which surprised me so much.

[Wookiee]

@IgoRr first question are all drivers up-to-date?

Have you performed all the standard Windows DAW tweaks?

The Pro Channel was in the main console view?

Did you try closing the console and redisplaying?

If you can recreate, get screen shots, then share the project less, any audio, with as much detail as possible, either on the Web report page or by email to support@cakewalk.com. 

[IgoRr]

1 hour ago, Wookiee said:

first question are all drivers up-to-date?

I specifically emphasized: the graphics driver is the latest version, as are ALL other drivers for all elements of the system (C++  too), I always monitoring this very strictly.  And my system is configured within the maximum possible limits, all (!) elements of antivirus and security programs and services, except for Firewall, have been completely removed from the system (Defender; Smartscreen). But these settings almost certainly cannot be the cause of such an anomaly, because I did not change anything in the settings, and such a failure appeared only in the latest version of Sonar. I opened ProChannel not in the console (mixer), but in the "Inspector" window in main project window, at that moment the thought did not occur to me to check the same thing in the console display. And such an incorrect display concerned any (!) audio or instrumental track, or buses when opened at the bottom of the main project window. But I have repeatedly tried to close/open the "Inspector", as I said above, and this does not solve the problem. If I have such an anomaly again, of course, I will immediately take screenshots and post them here.

Edited 12 hours ago by IgoRr

[Wookiee]

@IgoRr pretty much standard support question is check that drivers are up-to-date. 

I asked regarding console view just to check if it was only affecting the Inspector.

Are you using any display scaling? You didn't note the screen resolution you are using. 

How did you close the Inspector, you can collapse it, undock it and close it completely. 

[IgoRr]

2 hours ago, Wookiee said:

Используете ли вы какое-либо масштабирование дисплея? Вы не отметили используемое вами разрешение экрана. 

Как вы закрыли Инспектор? Его можно свернуть, открепить и полностью закрыть. 

Yes, I use screen scaling, but on the downside - I have a large 32-inch monitor with a resolution of 2560x1440 pixels (Samsung Space Monitor), so the scaling is currently set to 95%. Do you think this could be the reason? I just remembered that when the very first release of modern Sonar appeared, many modules were stopped displaying normally just in ProChannel when scaling, but when returning to 100%, everything was fixed, and then when scaling again, it was also displayed normally.
Today, for the whole evening, this anomaly did not return once, I can’t even imagine that such deviations could have happened yesterday.
I open and close the inspector with the "I" key, I also tried switching between different options in the ProChannel tabs, I tried to unpin it and change the location, but I already noted above that this did not eliminate the anomaly.

Thank you for your reply and attention!

[Wookiee]

@IgoRr it may well be, Windows, though it appears you can set custom values, only really supports scaling in 25% steps. Currently Sonar follows the same scaling rules as Windows in 25% steps. Try setting it to 75% and see how it goes.