Noel Borthwick

We only write premium highest quality unleaded code. Its child and pet safe.

Thanks. Touch support for arranger is not yet available.

If the last time you used cakewalk was 20 years ago then you should be prepared to have a bit of a learning experience. Have you used any current generation music software? Everyone has installers with optional components although some integrate it directly into the program (which is a good thing) Prior to BandLab acquiring Cakewalk we had an installer called command center which was similar in principle to bandlab assistant though more sophisticated. It also allowed to install optional components (many more than what we do now) Bandlab is the company that owns Cakewalk. To use the software the requirement is to create an account that established you as a user. Bandlab is also a powerful cloud platform for recording and sharing music using mobile devices it the web. It has over 20 million users. There is no requirement to use that if you don't need it but it's free and available to any Cakewalk user. In short by default we install the bare minimum for Cakewalk to run to save bandwidth. There is zero bloatware.

@Hillmy as I explained before this will not happen with new users. That is the whole point of this change.

Correct since we have no idea whether this is a user edited preset or not, we can't remove them. Only a fresh install will have the new presets. The other alternative is to manually delete the presets from the registry and rerun CbB while holding CTRL key down, then tell it to personalize. That should recopy the factory presets. I've not tested this mechanism. That said many of the previous presets should work now since we added several plugins that were utilized by them.

Not related to update. Something environmental caused the plugin to lose it's authorization.

The changes we made affects new installs. If you previously had the preset it won't get automatically removed since the installer never removes existing presets.

A big can exist forever if it's not reported. Things don't get fixed automatically. I have never heard of this one. Please write up a proper description and recipe for it as a separate post and we can look at it for a future release.

@Variousartist this should be fixed in the final release. Several testers have already confirmed that its ok now. I've optimized the code so that it will throttle back and consume less UI bandwidth freeing up processing of input messages.

This wouldn't be a Cakewalk problem. All fast bounce does is render audio faster than realtime. If the plugin isn't handling this it would be something the plugin vendor needs to investigate on their end.

Got it thanks. Mark will take a look at it tomorrow.

@sreams check your PM. I'd like you to do a test with a build that should address this issue. If anyone else had this same issue reproducibly and would like to test a build, PM me.

@Kevin Walsh who did you send it to?

@Kevin Walsh use any service like dropbox or google to upload your file and share a link with us via PM.

I looked at the freeze issue and it was actually introduced a few releases ago when we added support for multiple instrument tracks. Its now been fixed for the final release so thanks for reporting it - although it would have been better in the previous release thread

As I said these thread is to report issues with the Early Access release so it should be used to report issues that are NEW to this release or its features rather than preexisting issues. We are of course interested in knowing about those as well but post them in the other more general forum. The external insert issue is not a bug - its a feature request and will be handled in due course. We have a backlog of many items so its normal for some things to take many months to be considered or addressed.

Thanks for the reports. BTW please keep in mind that this thread is primarily to discuss any issues or regressions directly related to the 2020.07 early access and not to make feature requests or post general bug reports. Please use a different thread to report other issues.

@sreamsInteresting. I wonder if it is so busy redrawing that it's not getting a chance to process the stop request. Can you reproduce this or was it a one off issue?

This has been addressed for the next update.

@mgustavo there is no change on our end AFIK so I have no idea why it was a problem for you in the first place

@Stxx There are no changes to ara in this release. Please provide a crash dump file so we can see the source. Crashes in melodyne 4 won't be fixed by celemony since melodyne 5 us the latest version. I suggest you upgrade.

@Michael Heavner we asked you for a project file to forward to waves but did not hear back. they need that for further investigation. Can you please supply us a link to the project file?

If you are able to capture a dump we can normally tell what operation is hanging.

Because they work just fine in Cakewalk and that's the only consideration for now. The framework for a plugin doesn't change its capabilities or sound in any way just its compatibility. While its something we may consider in the future, we have more pressing things to do with our time than stuff like this at the moment.

This is precisely the reason why we are very careful to change established operations in major editing views. While I may not like some operations personally (right click delete for one) there are many user for whom this is an important time saving operation. These were implemented decades ago at the request of power users to speed up editing. Windows conventions are good but not the solution to all problems.