[CLOSED] Cakewalk 2022.06 Early Access [Updated to Build 22]

[Morten Saether]

We're pleased to announce Early Access for 2022.06! This release introduces Mackie control surface improvements, loop and punch record enhancements, key binding to render Region FX, support for local help, in-app update improvements, plus various enhancements and bug fixes for user reported issues.

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 2022.06 Early Access build, you must be on the latest public release of 2022.02. 

Download Cakewalk 2022.06 EA installer

Download Cakewalk Offline Help installer

Should you need to revert to the 2022.02 release, you can download the Cakewalk 2022.02 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

 

Updated to 28.06.0.022

This build contains the following additional improvements:

• In-app update improvements:
  • Cakewalk now supports in-app download of optional content that was previously only available from either BandLab Assistant or the Cakewalk Web installer (Studio Instruments Suite, Drum Replacer, Melodyne trial, Theme Editor, and demo projects). To see all available updates, select Help > Check for Updates. If any optional content has not been installed yet, or an update is available, Cakewalk presents a toast notification to download and install the content.
  •  Add file name to the download progress toast notification so users know what is being downloaded.
  • Display error message when attempting to download multiple updates or checking for updates while one is in progress.
• Hang when trying to sign in to BandLab.
• Guard against crashes with toast notifications.
• Cakewalk should disable the options for Audio to MIDI conversion if Melodyne is not installed.
• Muting Melodyne clip in take lanes causes clip to disappear.
• Move To Folder context menu command moves tracks in incorrect order.
• Track Folder echo button status incorrect when active track is an audio track.

 

Updated to 28.06.0.013

This build contains the following additional improvements:

• Render Region FX key binding not available in English version.
• Cubase mode not being recalled in Mackie Control surface dialog.
• Shelf tool does not work with multiple clips in the same lane.
• Null pointer when trying to drag move range selection in project.
• Tempo track wiped after drag copy section in user project.
• Incorrect tempo at beginning of committed arrangement in user project.
• Unable to enter "+" character for markers when using non-US keyboard.

 

Mackie control surface improvements

The Mackie Control surface includes several new enhancements.

New compatibility modes

In addition to the recommended Cakewalk/SONAR mode, the Mackie Control surface now supports two extra emulation modes that can be used if your control surface does not provide a dedicated Cakewalk/SONAR mode:

• Mackie Control Universal (Universal Mode). Emulates Mackie’s default button layout.
• Mackie Control Universal (Cubase Mode). Emulates Mackie’s Cubase/Nuendo button layout.

It is important that both Cakewalk and your control surface are configured to use the same mode in order to ensure that buttons on the control surface map to the correct functions in Cakewalk.

Note: If your control surface provides a Cakewalk/SONAR mode, we recommend using this mode to provide maximum compatibility.

 

Disable Handshake now checked by default

Earlier versions of the Mackie Control protocol required a handshake during the initialization of the control surface. Mackie removed this requirement in later versions.

To reflect this change, the Disable Handshake option is now checked by default to bypass the handshake process.

Note: You may have to uncheck Disable Handshake on older devices when using the Cakewalk/SONAR mode.

 

Performance enhancement

Routing and track/bus ordering are now cached internally in order to avoid unnecessary repeated calculations during the control surface refresh process. This results in improved UI performance when using a very fast refresh rate.

The cache is reset every time the routing or track ordering changes, and then rebuilt again on the next query from the control surface.

 

Automatically extend final take when loop recording in Comping mode

When loop recording in Comping mode , the last take now automatically extends to the loop end time if more than one loop iteration was recorded. This prevents previous takes from being split at the transport stop time, and makes comping much easier because each take is a complete clip.

Note: If you loop record in Comping mode and also have auto punch Extend Takes to Punch Out Time enabled, then the last take will be extended to whichever occurs first: loop end or punch out time.

Old behavior (incomplete last take and split clips):

New behavior (complete last take and no split clips):

 

Option to automatically extend final take when punch recording

When Auto Punch recording, Cakewalk automatically splits all takes at the position where you stop recording. This happens if the transport is stopped before the punch out time.

This behavior may not be desirable in some cases, such as when speed comping, where you want each take to be a complete clip.

To prevent this behavior, Cakewalk now provides an option to extend the final take to the Auto Punch end. Right-click the Record  button  to open the Preferences dialog box, then enable Extend Takes to Punch Out Time.

Note: The Extend Takes to Punch Out Time option also requires that Auto Punch is enabled.

 

Option to open parent track folder when changing track focus

The Track view Options menu contains a new Expand Track Folder on Track Focus option, which automatically opens the focused track’s parent folder if it’s currently closed. This behavior may be desirable when using control surfaces or changing track focus via the Console view.

 

Key binding to render Region FX

A new key binding named Render Region FX allows you to render any Region FX for any active Region FX in the current clip selection. You can assign the key binding in Edit > Preferences > Customization - Keyboard Shortcuts (under Area: Global Bindings).

 

Support for local help

Cakewalk provides optional local help. To enable local help, go to Edit > Preferences > File - Advanced and select Always Use Local Help.

When you enable local help for the first time, Cakewalk presents a toast notification to download and install the local help, and whenever updated local help is available.

If your computer is not connected to the internet, Cakewalk will default to showing local help until an internet connection becomes available.

Note: Offline help is only available in English.

Tip: If you would like to use local help on a computer that is never connected to the internet, first download the local help from another computer that is connected to the internet, then copy the CakewalkHelp_Documentation_1.0.0.n.exe installer (found in \Downloads\Cakewalk) to removable media that you can transfer to your offline Cakewalk computer. Alternatively, copy the installed Cakewalk.chm file from the Cakewalk root folder (default is \Program Files\Cakewalk\Cakewalk Core).

 

Issues resolved in Cakewalk 2022.06 EA (build 28.06.0.008)

• Cakewalk will now install to ARM64 PCs running Windows 11 for ARM
• WarnSilentBuses config setting should default to off
• Flushing during bounce occurs with plugins on buses that are not part of the signal chain
• Export Arranger sections not working properly when project has locked clips
• Resizing Arranger sections should be able to snap to other sections
• Committed arrangement off by 1 tick / losing first note
• Corrupt tempo map when CTRL+drag copy section with only one tempo present
• Cakewalk External Controller API problem causing Cakewalk GUI to freeze
• External encoder presets not being picked up / stored properly

 

[Keni]

Problem immediate....

 

The Global Binding for Render Region FX is not in the Global Bindings. I will begin to search elsewhere to see if it's either in wrong list or not present at all...

 

Nope. Nowhere in key bindings. The word render finds nothing.

 

I verified that I do have 2022.06 installed....

 

Preferences windiw acting strangely. Taking much longet than normal to be ready to accept commands.

Using Locate Key option doesn't accept ctrl option. Remains unchanged and returns the regular M command when I attempt ctrl-m

 

 

Edited May 27, 2022 by Keni

[Morten Saether]

7 minutes ago, Keni said:

The Global Binding for Render Region FX is not in the Global Bindings.

Will be in the public release.

[Keni]

1 minute ago, Morten Saether said:

Will be in the public release.

OK... Some other little issues in the shortcuts. It seems that it names Ctrl-M for create region fx, but the list does not show the binding in the list itself. It shows as the command is unbound. Some stuff seems to be going on in the shortcuts box.... Sad that it must wait for public release. I guess it's believed it doesn't require testing?

 

Something is already "wrong" in the shortcut options box so it appears some kind of testing is needed in preparation of this new command...?

I guess there's nothing for me to test in this update. I don't use the other features being addressed...

[Olaf]

Like the "automatically extend last take" feature. Automatically splitting all previous takes at the stop point was really annoying. I'm glad that's solved.

[Lord Tim]

2 hours ago, Keni said:

Preferences windiw acting strangely. Taking much longet than normal to be ready to accept commands.

I don't think this is new to this EA. I've noticed that when you leave the Prefs window on the Keybinding page, it takes a while to open. If you change to any other category and press ok, it'll open instantly for me.

[Tom B]

Regarding the new control surface compatibility modes:  Does this allow a controller, such as the SSL UF8 which has a Cubase MCU profile available, to work reasonably well with Cakewalk?  Currently, the SSL FAQ says the UF8 does not support Cakewalk.  

Edited May 28, 2022 by Tom B

[user 905133]

Looking forward to trying the Comp/Take Lanes repair.  I stopped using Comp Mode to try out ideas and preserve them in lanes because the splits were trouble some.

[Keni]

3 hours ago, Lord Tim said:

I don't think this is new to this EA. I've noticed that when you leave the Prefs window on the Keybinding page, it takes a while to open. If you change to any other category and press ok, it'll open instantly for me.

This is the first time I’ve noticed it. I guess I haven’t made any changes in a long while.

It opened normally and sludged only when I selected the shortcuts tab. It also prevented Cake closing correctly and I was forced to task manager out of it. That was first time running after the update. That  hasn’t happened again since.

 

My shortcuts seem to be behaving normally, but the ctrl-m shows correctly in left window, but in the right pane the command appears unassigned? It works though. I don’t know if this is new with the update as I haven’t changed any shortcuts in quite some time.

[msmcleod]

9 hours ago, Tom B said:

Regarding the new control surface compatibility modes:  Does this allow a controller, such as the SSL UF8 which has a Cubase MCU profile available, to work reasonably well with Cakewalk?  Currently, the SSL FAQ says the UF8 does not support Cakewalk.  

That's the intention. Obviously without testing each individual device, we can't be 100% sure it will work, as anything other than a true MCU is simply emulating one.

Testing was done with a real MCU, a Yamaha 01X in Cubase/Nuendo mode, and a Korg nanoKONTROL 2 in Cubase mode.

Unfortunately we don't have an SLL UF8 to test with, but hopefully someone with an SSL UF8 can try this out and report back.

[Kyle Davis]

This release is a bit of a disappointment. Waited so long just for this? Well, I hope it wont crash this time. 

[msmcleod]

13 hours ago, Keni said:

OK... Some other little issues in the shortcuts. It seems that it names Ctrl-M for create region fx, but the list does not show the binding in the list itself. It shows as the command is unbound. Some stuff seems to be going on in the shortcuts box.... Sad that it must wait for public release. I guess it's believed it doesn't require testing?

 

Something is already "wrong" in the shortcut options box so it appears some kind of testing is needed in preparation of this new command...?

I guess there's nothing for me to test in this update. I don't use the other features being addressed...

The issue is down to a missing string definition in the English resource file.  The feature was working at the time it was implemented and tested, but it looks like a subsequent code merge went wrong at some point (merging resource files can be occasionally problematic).

This has now been fixed, and will be available in the main public release.

In the meantime, the entry is available in all other languages, so as a workaround you can switch to another language and make your binding there, e.g. for French:


 

[Lord Tim]

40 minutes ago, Kyle Davis said:

This release is a bit of a disappointment. Waited so long just for this? Well, I hope it wont crash this time. 

Looking at the other thread you made, it's not clear if you've reported any crash reports to the Devs.

Us users can't help you because you're unwilling to tell us anything about your problems or your system. 

If this crashing was as bad and as widespread as you're saying, the forum would be up in arms about it, which it's not, so it's clearly something that's either constrained to or exposed by your environment.

It could well be a CbB bug that your environment is exposing. If you don't report it, unless someone at Bandlab is a clairvoyant, nobody will know if there's a problem at all, let alone trying to solve it.

We *all* benefit from people reporting bugs that get fixed. These EA builds especially are here for us to give it a good test before the public release - this is the time to bring up problems, document them and report them.

[Keni]

1 hour ago, msmcleod said:

The issue is down to a missing string definition in the English resource file.  The feature was working at the time it was implemented and tested, but it looks like a subsequent code merge went wrong at some point (merging resource files can be occasionally problematic).

This has now been fixed, and will be available in the main public release.

In the meantime, the entry is available in all other languages, so as a workaround you can switch to another language and make your binding there, e.g. for French:


 

Thanks MS... interesting work around. I’ll give it a try after breakfast.

[Heinz Hupfer]

HI:)

 

Quote

The Track view Options menu contains a new Expand Track Folder on Track Focus option, which automatically opens the focused track’s parent folder if it’s currently closed. This behavior may be desirable when using control surfaces or changing track focus via the Console view.

Thanks for this, it's very helpful with Midi Controllers.

But now changing Tracks in the Track view with controller is slower than before.

It was very fast before.

Was slower when opening Multidock with Console, now with console it is VERY slow

But OK for working cause I don't need Console. (Very seldom)

 

Quote

Option to automatically extend final take when punch recording

Great, this is much better than before.

 

As far as I can see all Projects are opening and playing without any issues with this update.

Thanks for it Bakers;)

 

Bassman.

 

Edited May 28, 2022 by Heinz Hupfer

[Jacques Boileau]

3 hours ago, msmcleod said:

That's the intention. Obviously without testing each individual device, we can't be 100% sure it will work, as anything other than a true MCU is simply emulating one.

Testing was done with a real MCU, a Yamaha 01X in Cubase/Nuendo mode, and a Korg nanoKONTROL 2 in Cubase mode.

Unfortunately we don't have an SLL UF8 to test with, but hopefully someone with an SSL UF8 can try this out and report back.

I would be glad to test the new Cubase mode with my M-Audio Oxygen Pro 61 and report back. But since I have done quite a bit of work configuring it using AZ Controller (DAW control)  and ACT midi controller (plugin control), are there Cakewalk configuration file(s) I could backup so I can revert to my previous surface settings if need be?

[msmcleod]

Just now, Jacques Boileau said:

I would be glad to test the new Cubase mode with my M-Audio Oxygen Pro 61 and report back. But since I have done quite a bit of work configuring it using AZ Controller (DAW control)  and ACT midi controller (plugin control), are there Cakewalk configuration file(s) I could backup so I can revert to my previous surface settings if need be?

While Cakewalk isn't running, rename  ctrlsurface.dat  within %APPDATA%\Cakewalk\Cakewalk Core  to ctrlsurface.dat.bak

Then start Cakewalk.

Cakewalk will now have no control surfaces defined, so you can add the Mackie Control one for your Pro 61.  Once you've switched it over to Cubase mode within the Mackie Control surface dialog, remember to save it as a preset.

To switch back, quit cakewalk, delete ctrlsurface.dat  and rename ctrlsurface.dat.bak back to ctrlsurface.dat  - when you restart Cakewalk, it will be using AZ Controller again with your original settings.

[Jacques Boileau]

I started testing the surface Cubase mode with my Oxygen Pro. I wasn't able to get it working yet.

I selected Cubase as the DAW mode in my Oxygen Pro. Then I created an entry for it in control surfaces:

Next I configured it for Cubase and saved the preset:

But the protocol does not seem to be saved in the preset (or loaded when reopened). Every time I reopen this dialog, the protocol always reverts back to Cakewalk/SONAR mode.

Anything else I should do?

The configure layout and/or the ACT learn button  do not open anything. Shouldn't I be able to edit the control's in the ACT window? It has been a while since I have played with this but I remember another configuration window that I can't seem to get to now.

Presently, no control on my Oxygen Pro have any effect in Cakewalk. But I do see the WAI green bars beneath my tracks.

[msmcleod]

57 minutes ago, Jacques Boileau said:

I started testing the surface Cubase mode with my Oxygen Pro. I wasn't able to get it working yet.

I selected Cubase as the DAW mode in my Oxygen Pro. Then I created an entry for it in control surfaces:

Next I configured it for Cubase and saved the preset:

But the protocol does not seem to be saved in the preset (or loaded when reopened). Every time I reopen this dialog, the protocol always reverts back to Cakewalk/SONAR mode.

Anything else I should do?

The configure layout and/or the ACT learn button  do not open anything. Shouldn't I be able to edit the control's in the ACT window? It has been a while since I have played with this but I remember another configuration window that I can't seem to get to now.

Presently, no control on my Oxygen Pro have any effect in Cakewalk. But I do see the WAI green bars beneath my tracks.

The Oxygen Pro itself needs to be in Cubase DAW mode, and AFAIK you should be using the second Pro 61 MIDI ports - i.e. MIDIIN2 (Oxygen 61 MKV) /  MIDIOUT2 (Oxygen 61 MKV).  The primary ports are used for the keyboard itself.

You can't use ACT at the same time as the Mackie Control, as the Mackie Control integration takes full control over the MIDI ports.

We'll look into why the Cubase mode isn't being recalled.  [EDIT] - found the cause of this... it's been fixed for the main release.
 

[Keni]

5 hours ago, msmcleod said:

The issue is down to a missing string definition in the English resource file.  The feature was working at the time it was implemented and tested, but it looks like a subsequent code merge went wrong at some point (merging resource files can be occasionally problematic).

This has now been fixed, and will be available in the main public release.

In the meantime, the entry is available in all other languages, so as a workaround you can switch to another language and make your binding there, e.g. for French:


 

Thanks again MS...

 

Work around appears to have been successful. A bit daunting with my limited language knowledge, but it appears to be working. This should prove a major relief as I do a lot of such work. I believe this is a much desired command.

 

A note though. Am I doing something wrong, something changed, or a bug?

In preferences|shortcuts, the key search isn't accepting a click on the ctrl/shift/alt buttons and will only search for the final key strike. I am also continuing to investigate the right pane (of this dialog) display for actual setup. As I mentioned earlier. The ctrl-M command shows bound to the create melodyne clip command, the right pane shows the command with no bindings at all.