Noel Borthwick

2022.09 has been released. Thanks for your help testing it!

Thanks for the heads up, we’ll sign them.

Which dlls in particular are you having warnings with?

Thanks everyone for checking out the latest EA. We plan to release this officially tomorrow. We just updated the build to 28.09.0.027 which includes a couple of important fixes. If you see this, we'd appreciate it if you tried it out before we release tomorrow.

No not at all. More like our (small) team has been working on some other equally important things. CbB is a pretty mature application and it's not always necessary to add new features but rather refine what we have.

If the internet is gone permanently, I think you will have far worse problems than not being able to use your DAW You can authorize cakewalk via the offline auth mechanism but yes that requires at least a remote internet connection somewhere. Pretty much most software today is tied to some sort of activation mechanism, its just how the industry has evolved.

For me any product its actually more than the sum of its features, but its workflow. If a product has a million features but the workflow doesn't suit me, I don't use it. Time is too short to waste on things that aren't intuitive to you.

Thanks for using Cakewalk software. It has grown by leaps and bounds over the last 4 years and is more stable and performant than it has ever been. In general, if any DAW meets your workflow and needs there is no need to keep endlessly looking elsewhere because you will waste more time learning new tools. And believe me when I say this - every product has flaws and bugs despite what you might hear from anyone else We're also working on something exciting that will be announced relatively soon so at minimum hold out until then 😛

Thanks to some tests from @David Baay I have isolated the issue that causes the UI to be unresponsive after stopping when there are hundreds of tracks with certain prochannel modules. It is fixed it for the upcoming release. The issue is easily reproducible if you have 200 tracks containing the console emulator. The reason for the delay on stop is because the console emulator ends up blocking the user interface under certain conditions. I have worked around the plugin issue in our code.

@Antre I realize that it's frustrating when you have a problem that apparently doesn't occur elsewhere, but the truth of the matter with troubleshooting is ALL DAW's are vastly different and that a symptom that appears in one and not another doesn't necessarily shed much light on why this happens. As others have indicated there are a ton of moving parts that can lead to something like this. The proper way to troubleshoot is through a process of elimination: - Start by deleting tracks - you may be surprised to find that the problem occurs with one of the tracks. If so go further to look at the content. - Bypass or remove all plugins from the project. Does the transport still take time to start? - When you press play there are many things that happen as a part of the preroll process. One is opening and prereading to cache audio data for all the tracks. If you have many tracks (many hundreds) and there is a disk fragmentation or slow read issue this process can take a couple of seconds. Try playing with the settings in Audio | Sync and Caching. Setting a very large playback buffer can cause preroll to take longer. - Check if you have one or more plugins with huge delay buffers. If there is a large delay buffer, again preroll before playback starts will take longer because the engine cannot start playback until all plugins process initial audio. - Check if always open all device is enabled. If you have many I/Os enabled in preferences and the audio driver is slow it can take long to open the devices. - Check if Allow arm changes during playback and record is enabled. If its on depending on the number of inputs and the driver this can slow the preroll process down The above settings are the most typical reasons for lag starting playback.

Next update will include masking tape 😉

Thanks for your support, guys. It is great that we are able to offer Cakewalk free to our users. As long as we are able to do so, enjoy it....

We can consider reducing the minimum loop size below 8th notes. A single tick resolution is too low. A DAW needs to do a lot more setup for looping than an audio editor or sampler so looping tiny region on the timeline is not as simple as it might look. Please move threads like this out of the release thread because its more suited to the feature request section.

Um you can do as much surgical editing as you need. Looping is not intended to be an editing tool. Use normal snap and zoom with the sample ruler to do surgical edits. Please move this to a different thread since its not related to this release.

There is nothing to fix because it isnt a bug. It is intentional that the loop length cannot be made smaller because there are problems rendering tiny loops. In any case there is no musical value in setting loops that small.