Noel Borthwick

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!

Can you check if you have allow arm changes during recording enabled?

You can solve this by disabling the One drive automatic backup integration which redirects folders on the PC.

Hi @Neil We've been working on some major changes for BandLab integration that should greatly improve the workflow for sharing to BandLab. It will be more deeply integrated into Cakewalk and you shouldn't have issue like this going forward. I agree that the BandLab integration should work better. What we have is the first cut that was done some time ago. I can't say yet when the new features will be available but it should be fairly soon.

@Andres Medina thanks that is useful info. I've contacted Vienna for a license of the Synchron player but will also look into the templates steps and see if I can spot something wrong.

Cakewalk does have tech support it's posted right at the top of the FAQ.

You can manually run the installer by going to this folder: %appdata%\bandlab-assistant\Downloads

Cakewalk automatically adds all the standard VST paths. You don't need to manually add paths unless you install plugins in different locations. Following an internet tutorial that is not related to Cakewalk is probably not going to help you.

Focusrite doesnt expose the headphone out as an ASIO output. You have to route it through their mixer. Re playback vs recording there is no way to change outputs other than manually. Most people use sends to output to a headphone mix bus. So all thats needed is a single click to enable the send, or to mute/unmute the bus.

Hi @Andres Medina thanks for sending the dump. I looked at it and it does seem to be a crash in our code when destroying some automation parameters. However we'll probably need the plugin to try and reproduce the issue. Does this happen even when starting with a new project and simply inserting and deleting this plugin? If its project specific you may need to send us the project file to try and reproduce it. We'll investigate it further for next release.

@Andres Medina your file did not attach. Please PM the file to me.

This should be addressed in the latest release. Please let us know if you continue to have this issue.

Its not clear from your post if you have prior experience using a DAW. If not you can expect a learning curve. The way to start is to take a task oriented approach like what do you need to do and learn progressively. To minimize distractions I suggest setting the default Workspace to "Basic" which will hide a lot of the details that you may not be interested in yet. See attached screenshots for where to change this. Choosing Basic will give you a feature set somewhat compatible to what you might see in GarageBand or a simpler DAW. It doesn't get much simpler than what you see with Basic in any DAW. I've also included a screenshot of an even simpler workspace that can easily be set up. Anecdotally, I've been developing Cakewalk over 20 years and there are still things even I don't know deeply as a user. That said I'm interested in knowing what specifically you find incomprehensible or what you are attempting to do.

The master bus will be exported as a separate track in bandlab so you can choose to mute it in bandlab if you don't want to hear it. But the master bus will include exactly what audio was sent to it.

We'd have to work with Steinberg development to try and track down what is causing the sharing issue. Please pass on the contact person at Steinberg you were dealing with and we can follow up with them.

Ahh yes from the custom control bar. It doesnt work from there. Why are you using that anymore when there is a dedicated export control bar?

If you have a track that cant be unfrozen send us a zip of the project file with the audio so we can investigate.

It hasn't been updated in awhile but its @cakewalkinc

That wouldn't really help since today the parallel processing occurs at the track level, so knowing about contiguous clips wouldn't make it easier. One approach could be splitting each clip into a new track behind the scenes and then bouncing the whole split project splitting the track outputs to new files.

Unlike normal export or bounce to track, Bounce to clips can't easily be done in parallel - at least not easily. The bounce code essentially relies on the audio engine which is optimized to render independent tracks for contiguous sections in parallel. With bounce to clips you are rendering chunks of data at different points on the timeline. So its not as a simple process to do this in parallel since we'd need to have multiple instances of the engine render the discontiguous sections of audio in parallel. Additionally the radius rendering isn't currently optimized for multi processing and could have bugs handling this. In short this would be nice to have but it would take a lot of work to achieve.