Noel Borthwick

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.

No its not the same issue. If the app is closing with no crash its almost sure that the plugin is corrupting the application heap. That is the most common symptom.

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.

You must Ctrl drag by clicking on the envelope segment. If you click on the white space it won't work.

@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.

This is not a bug - all versions of Cakewalk have worked this way. Please refer to the documentation for the smart tool. In particular read the section on Using the Smart tool on automation When using the upper zone (B) it only works on SELECTED nodes or the selected region. If there is no time selection it will use the last selected node. When clicking on a line segment (D) if you hold down CTRL it will drag just that segment.

Nope. As has been explained many times there are reasons for authorization as present in every program free or not.

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.

Adding in-app install was the first step. We'll tackle in-app authorization in a future release.

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.

This has been discussed earlier. Just run the installer manually outside of BandLab assistant and it should launch and run properly. You will find the downloader at %appdata%\bandlab-assistant\downloads

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

An official 2020.08 hotfix will roll out very soon to all users, but if you are affected by any of the issues listed below you may download the 2020.08 hotfix now.

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.

@scook I don't think it ever worked. That bug has been there since 2005. I rarely want to change the audio folder so didnt notice it before.

This has nothing to do with Copy all audio or any esoteric design intent. It was a simple bug in the code that was wiping out the user settings when you OK'd the dialog. There is logic to change the audio folder paths based on changes to the file name (this is used when saving a new project). That was being unexpectedly executed causing the problem. Its been fixed for the next update.

You can use a drum map to set this up by assigning the entire note range to different instruments.

This is not a bug. Delay compensation is not supported for synths because synths are always rendered just in time. They wouldn't be much point having synths that have delay would there? All the Enable delay compensation flag does is allow turning off delay comp at an effects level. Its a leftover from years ago and not something most users will ever need to set. Turning it off will make things go out of sync. We already have a PDC override feature in CbB for the cases that delay comp needs to be overriden so this manual setting is obsolete.

I'm curious how many users are actively using Mix Recall. At some point we plan on improving the feature.