Wookiee

@Jan van Schalkwyk how are you saving them? Only files with the CWP Cakewalk project file extension show. If you save as MIDIO- 0 or 1 they will not appear.

Sorry Colin only just seen it.

Couple of points. 1. Go to talk to Gibson they still own Cakewalk Inc, and the products, SONAR Platinum, Professional and Studio, by Gibson. It was them, Gibson, that took your money not Bandlab Technologies. 2. Bandlab Technologies only purchased the intellectual property rights to the code. They did not buy the company or its debts, or its commitments. Consequently they owe you absolutely nothing whatsoever. 3. You are under no obligation to purchase a subscription to any product from any company. 4. As you have have had this account since January 2019 you know all this already, as it was discussed extensively from April 2018 when Bandlab released the first version of the free CbB. One can only conclude you just want to stir the brown sticky stuff. If that is so go talk to owners of the product you are making an issue about Gibson Inc.

No you are inaffect requiring them to do tests. I have a good idea why, you don't ask the creators of the plugins but my paws are tied.

You infer that it is the teams/Cakewalk responsibility to ensure someone else's product works with theirs. Why? There is nothing they can do if they don't, can they? They obviously make best efforts to ensure that their software is compliant with the standards of ASIO, current Direct X, VST 2/3, the current MIDI requirements, the currently supported OS's, the majority of Graphics standards. What I personally think you should be doing is asking the plugin creators what plugins work on the ARM architecture, that is the real first question to ask. Then, and only then, if they say they are ARM compatible, but fail in you chosen host product, do you ask that products creator to resolve the issue. You are inaffect asking Cakewalk to ensure that their product runs on all the permutations of potential PC hardware combinations, plus test all third party plugins. When we know full well that Cakewalk, applies the latest SDK libraries to their products, but frequently third party creators don't test their products on all other potential hosts. I know this for a fact because when I have approached a number of third party plugin producers with errors. Their response is "Oh we don't test on xwz hosts." The most interesting thing with those plugins is, the Cakewalk team have identified the issue in the plugins creators code, and supplied them with the fix, whilst building a workaround into Cakewalk's code just incase they don't fix it.

From reading that, it very much appears the responsibility for functionality of VST Plugins, on an ARM CPU lies with the plugin creaters not the DAW creators. Just as the DAW working on an ARM CPU is the DAW creators responsibility. Which is totally unsurprising, when VST plugins were first introduced, the DAW creators had modify their code to use VST plugins.

@Leander, Cakewalk uses the first Audio device that Windows initialises. It appears Windows does this in alphabetically, which is irritating. Don't blame Cakewalk it just uses what Windows gives it. Unless you have a really good reason, and does have to really good one, ASIO4all should not be installed on a DAW.

If you are using a Workspace other than None, you must save that Workspace after you rearrange the control bar. It is a "feature" of Workspaces that they hold the control bar layout.

Are you subscribed or free? The Control bar is dictated by the Workspace, unfortunately the number of Workspaces in the free tier are restricted to one, which I believe you can't change or save.

@Jan have you considered it could be the FX in the FX bin in conjuction with the Pro Channel. Have you tried it with the FX bin disabled and the PC enabled.

@SVSX nag screens are not uncommon on free software, nearly all the free software I have ever tried, that has paid versions, has had a nag screen. Some are more persistent than others.

Missing a few things/ versions/releases, SONAR 8.5, SONAR X1.5

The oversampling of third party plugins still works, it is a function of the plugin not Sonar. The oversampling built into Sonar, doesn't work in the free tier version of Sonar.

@Phil T I suggest you post this in the feature request forum. It would be useful for it to work as you suggest.

@Ricky_Wayne_Hunt what ate your Windows audio settings, they will dictate your sample rate wnd bit depth. Change them to what you want the default to be. Control Panel > Audio or Settings > Audio.