Noel Borthwick

Can you share the project and audio with us please? Upload it and send me a link.

We tested the VSL maps and the Vienna folks have had early access to this build of CbB for some time as well.

Cakewalk by default auto scans only newly added plugins and is typically very fast. Of course for shells like Waves it has to load the shell to check that. As scook mentioned you can disable the auto scan if you prefer to manage it manually.

Glad you like it. A lot of effort went into this feature and we wanted to get it right from the get go. @msmcleod did most of the articulation maps implementation so he can comment further. We plan on making a subforum for users to share articulation maps if there is interest but you are welcome to start a thread. Any Cubase compatible map should import into CbB. We already tested the Vienna Ensemble maps and they work fine.

@sreams glad you are seeing noticeable improvements. Curious in what specific area you saw this - is it larger projects or just something that previously had issues?

@Lynn WilsonIts normal for the project to close and the start screen to come up. I'm not sure what you mean by "The start menu appears, but the background (rest of the app) disappears. " I don't see anything abnormal here. What crash are you referring to? Are you still seeing a crash? If so please send me a link to the fresh dump file with this version and I'll look into it.

Please post some reviews as well if you are so inclined

PS. It will even batch import multiple maps at one time. Just multi-select in the import articulation dialog.

Error 13 has nothing to do with your system directly so you are troubleshooting the wrong area potentially. "ASIO subsystem signaled a dropout due to a state change." This means that the ASIO driver itself requested the application to stop. What should be investigated is what is causing the driver to signal the state change to the host. Typically this happens by changing sample rate or some property like that from the driver panel but it can also be caused by another application accessing the driver unexpectedly.

What is the dropout code you get? CbB has a mechanism for dropout diagnostics now.

>>System: Windows 10 1803 I may consider it just because of this lol.

I've reactivated the KVR page and updated some of the information. We'll post regular updates there going forward.

We'll consider allowing section export for a future release depending on how much of a can of worms it ends up being

Glad you were able to sort out the issue. Focusrite interfaces works fine with cbb. I have a 6i6 here that I use daily.

Have you reported this to the plugin vendor yet?

I am able to reproduce this and have been passing on information to Steinberg. It appears to be a problem with Syncrosoft copy protection. Interesting that an earlier version solves it for you. I will pass on this info.

Windows has built in Bluetooth MIDI support (no custom drivers supported) and Cbb supports it via the UWP MIDI driver mode. I don't know anything about this Yamaha device, but some vendors also release custom MME drivers that support bluetooth. You can talk to Yamaha support and ask about that. The bluetooth UWP MIDI stuff works pretty well, I used it in a very crowded space for a demo at the Microsoft build conference with Pete Brown (thousands of people with bluetooth on phones and other devices) and was surprised that it stood up even at a range of about 20 feet away. Let us know how it works out if you do get the Yamaha interface.

It looks like exporting from a surround bus (when category is set to buses) broke sometime in an early SONAR version. We'll fix it. For now export the "surround main" by setting source category to hardware outputs or entire mix. There is no requirement to actually have multiple hardware outputs.

@Max Arwood can you send me the project that was silent?

What is the dropout code being reported?

@Andres Medina I was finally able to get Syncron installed and have reproduced and fixed the crash issue. Thanks for reporting this! The problem is actually not related to Syncron at all and I am able to reproduce it with any VST3 plugin. (The issue occurs with any VST but is easier to reproduce with a VST3) The fix will be in our next release.

The OP is still working with Steinberg on this issue. It's something to do with the elicenser copy protection that causes it to lock the project file the moment you open it, thereby preventing the file from being saved. I have looked into it in our side and given Steinberg information about our process. The issue cannot be reproduced by anyone at Cakewalk or Steinberg which makes it harder for them to solve. Please contact Steinberg support if you are encountering this issue

Arrangement sections would probably be the most intuitive way to do this. You can also make multiple arrangement lanes for different instruments if you like.

@Max Arwood Send me a project that has an assigned aux which is silent and I will look at it.

Thanks for the kind words 😊 Often the quickest way to get to the bottom of a problem rather than sending endless messages, is to observe it and do tests directly on the users PC. In this case Greg had an issue that he had reported here and on facebook where he was getting crackling when moving his mouse only over the bus view. I had some other customers over the years report issues like this but since this was a more specific report I thought it was worth investigating further. He has a modern I9 and the project wasn't overly complex although he had a lot of cpu expensive plugins. I was unable to reproduce the issue even with his project file so I did some analysis of the code that is affected by mouse movement on buses and spotted some obvious inefficiencies. I did some optimizations to the hit test logic that makes it use a lot less CPU. After I sent a build to Greg it appeared to completely solve his problem and he is able to run the project at 128 samples now with no artifacts on mouse movement or scrolling. The strange thing to me is that despite having fixed it, I believe the original issue to be a system specific problem with one of his drivers. MOTU, UAD or the NVIDIA driver. Its hard to say which one caused it, but load on the UI should in general NOT affect audio streaming on a multi-core CPU since the audio engine runs on high priority threads that are not gated by the UI. IOW the UI can be 100% busy and you shouldn't hear artifacts. The only way the audio device would get blocked is if somehow this activity blocked the audio driver at the kernel level. Whatever the cause is, I'm happy that the improvements addressed his issue and the fixes should improve performance across the board as well!