Jonathan Sasor

This is a known issue with Windows 7. Please use the web installer here instead:

Melodyne 5 is significantly more stable than v4, so if you have the option to upgrade... it's well worth it. I haven't seen any issues with Melodyne clips recently, and I've been doing a lot of testing with various project with a bunch of Melodyne clips. Printing FX is not a bad idea to future-proof backups for your projects, but shouldn't be necessary on a day-to-day basis for projects.

Can you capture a dump file when this happens?

Notice on the upper right side- you have the Workspace set to "Basic". It's doing this by design. Set this to "None" instead.

The Overloud plugins are installed with the full Cakewalk by BandLab installer versions, but if you use the updater from update to update, they shouldn't get touched as they're not changed on a regular basis.

Sent you a PM earlier to troubleshoot this further.

It does now! 😀

Go to Help | About Cakewalk, and double-check that you're on build 120. If so, close the app, then hold CTRL when launching Cakewalk. This will force copy the new presets.

This is expected. Going to Advanced in the Export Module menu brings up the new dialog

Usually crashes where the app just disappears as described are plugin-related. These types of crashes are why we implemented "ExceptionHandlingSeverity" as an option you can enable in the Initialization File section of the Preferences. Default value is 1, you can increase this to 7 if you're experiencing a crash, and it should then be able to get a dump file if it crashes again. At that point we can take a look at the dump file and if there's anything actionable on our end. In the meantime, normal saving of the project should work fine even if it subsequently crashes (the project just might not appear in the recent project list as that is populated on normal project close).

Please try this link for the rollback

Hi Olaf, Unfortunately we don't have ready access to many of the plugins in your project currently, so we're unable to get a repro as described currently, but we're still investigating. This issue is already logged on our end. Are you using a Workspace? I'm unable to reproduce this normally, but your description sounds like it may be reapplying a workspace on project load which would change those types of things in the UI. Is there a version of this plugin that's still available to test? It appears to be removed from their website. Also just because a plugin behaves one way in a particular DAW does not mean that the bug is not in the plugin. The things that @Noel Borthwick has seen... If you can provide details on this we'll investigate. I haven't heard of other reports of this. Are you changing the metering options that frequently? It might be easier to save a template with these configured as desired so you don't need to access the menu options as often. The issue with doing a redesign to implement a separate options page for this is it diverts resources from other features/fixes. We'll take it under consideration.

The only way you wouldn't see an option to manually set the install paths would be if you already had an existing Cakewalk/SONAR install, in which case it inherits a path that you would have set previously. Not that you can't manually reconfigure paths after installation either. The OP's issue was with getting the download to run via BandLab Assistant. Other users linked them to a new installer that worked successfully for them.

Nothing with our installers write anything to your router's internal memory. Sounds like you might have some sort of other system issue.

Hello Christopher, Are you sure the input port for your surfaces is set correctly in the Preferences? It's possible that this might have changed, thus causing it to receive data from the app, but not send. I just tested that automation does work correctly with a FP8 on my end, so nothing should have changed within the app to affect this in general.

The release notes are pointing to the main current release link, that hasn't changed since this build is in initial Early Access.

The rollback link has been replaced with Rebuild 4 which should work, apologies for the inconvenience.

We're pleased to announce Early Access for 2021.06 Update 2! This release fixes a few reported issues from the main 2021.06 release and adds some improvements. We'd love for you to check it out before we drop the official public version. Please note that Early Access installers are update installers, which only update from a specific version. To install the 2021.06 Update 2 Early Access build, you must be on the latest public release of 2021.04 or newer. Download Cakewalk 2021.06 EA installer Should you need to revert to the initial 2021.06 release, you can download the Cakewalk 2021.06 Rollback installer. If you haven't already done so, please read about the Early Access Program before participating. Please keep responses specific to problems or comments on this release. Unrelated bugs or feature requests should be posted in other threads or the feature request channel. Thanks again for your participation! The Bakers 2021.06 Highlights "Modern Standby" support and improved Power Management Added support for "Modern Standby" a new power management feature introduced in Windows 10 build 2004. Modern Standby mode is supported by some PC's (typically modern laptops). Modern standby is different from the traditional sleep modes and has to be specially handled by the application in order to suspend and resume hardware properly. Improved handling for resuming from a sleep state in Windows. Cakewalk will additionally reload the driver if necessary, if the driver requests a restart or it stops responding. Suspend and resume are properly handled when a dialog box is open. Handle VST instruments that change output counts If a VST instrument changes its output count, ports in projects previously saved with the instrument could become offset by the change in outputs. This could cause projects to stop playing through other virtual instruments until their instrument track inputs were reassigned. Cakewalk will now detect change in outputs on opening a project and automatically reassign ports appropriately with no user intervention required. Bug fixes Fixed crash when exporting single track with "-" in track name and filename Wedge Force Matcha plugin hangs on changing presets in 2021.06 release Projects saved with older versions of Omnisphere open with input ports assigned to incorrect instruments Space bar does not start playback when using Vienna Ensemble Pro Shift + Right Click toggle for Inline PRV causes unexpected lasso selection New projects flagged as modified in 2021.06 Extra Synth Instances inserted when adding all synth audio outputs for Split Instrument Track F2 to rename arranger section immediately after drag draw Alt + T in TV View Menu cut off slightly

If the crash is caught, it should prompt you about it, but they should go to C:\Users\YOUR_USER_NAME\AppData\Roaming\cakewalk\cakewalk core\MiniDumps.

That's always how it goes. A further quick note for the exception handling, just bear in mind that you'll ultimately want to remove that once you've captured your dump because it can also catch some other things that are benign. It's very handy for when you're trying to troubleshoot a particular scenario to get more details on a problem, but you'll want to turn that off when you don't need it.

Also, if you're not getting a crash dump initially, try increasing the exception handling severity in the preferences to capture a dump to send to us. Just go to the Initialization File section and add this option/value:

@dubdisciple sent you a PM to look into your Start Screen issue.

Note: The installer in the original post has been updated to version 1.0.0.015. This version now allows for the install of add-ons on top of an existing up-to-date Cakewalk installation. It also runs the full installer in silent mode when updating an existing Cakewalk installation prior to the previous update.

Because for years people have asked us for a system where they were confused by inconsistent third party driver names and how they were labeled only as left, right, and stereo. The port numbers actually will show you input port 1 on your device. It's beyond our control that Roland wrote a driver that put "mic/line 1" as input 5. Obviously it's not perfect for everyone at the moment, but the amount of work required to renumber the driver ports exceeded the scope of this update. @Noel Borthwick can give you more specifics.

The VS-700 system is a bit less common in that it has those extra ports that are listed before mic/line inputs 1-8 as you mentioned. As the driver goes, they are technically starting at ports 5 and 6. I get what you're saying though, but the new system is clearer for most other devices that have the analog 1-8 inputs listed first. The other driver names or friendly names are still there though, so aside from getting acclimated to the prefixes you're not losing anything.