Jump to content

2022.09 Feedback


Morten Saether

Recommended Posts

Hi all - please use this topic to post feedback specific to the 2022.09 release. Release-specific feedback is valuable to us, and consolidating it in a single topic is extremely helpful.

We request that  discussion in this thread be restricted to issues directly concerning this release, to make it easier for us to assist users. For other topics, kindly use the feature request section or create new posts.  Off topic messages will be deleted.

Thanks in advance!

2022.09 Release Notes

  • Like 4
Link to comment
Share on other sites

How do we access the full application installer as referenced in the 2022.09 release notes;

“Note: If you do an update install of the application, only the main application and its DLL files will be updated with the new digital signatures. To update all signed components, you will have to run the full application installer.“

  • Like 1
Link to comment
Share on other sites

3 minutes ago, Michael Vogel said:

How do we access the full application installer as referenced in the 2022.09 release notes;

“Note: If you do an update install of the application, only the main application and its DLL files will be updated with the new digital signatures. To update all signed components, you will have to run the full application installer.“

The easiest way might be to run the Cakewalk 2022.06 Rollback installer and check for updates again. It'll then download the latest 2022.09 installer.

Link to comment
Share on other sites

It would be nice if, in addition to the automatic update available in CW, the release posts would include a link to the update installer, just like the early access posts, and also a link to the full program installer updated to the latest release.

For instance, now, if you want to update all the dlls to the new signed versions - which are a good idea - there's no option provided to do it. The only option is to uninstall CW completely, and reinstall, with losing all the customizations and settings - and I'm not doing that.

Edited by Olaf
  • Like 1
Link to comment
Share on other sites

5 minutes ago, Olaf said:

For instance, now, if you want to update all the dlls to the new signed versions - which are a good idea - there's no option provided to do it. The only option is to uninstall CW completely, and reinstall, with losing all the customizations and settings - and I'm not doing that.

Instead on uninstall, try using the rollback installer provided in the product announcement.

FYI, a simple uninstall does not remove custom setting as the registry and user directory are left untouched by the uninstall process.

Link to comment
Share on other sites

4 minutes ago, Olaf said:

Doing that only replaces the dlls targeted by the update, doesn't it?

In this case, it will pick up the signed dlls.

Rolling back two versions (this requires rollback installers for the last 2 production announcements) will cause the update process to download and run the full CbB install instead of the update installer for the current release.

Link to comment
Share on other sites

4 minutes ago, scook said:

In this case, it will pick up the signed dlls.

It will, but, from what I understand, only those involved in the new/modified features.

5 minutes ago, scook said:

Rolling back two versions (this requires rollback installers for the last 2 production announcements) will cause the update process to download and run the full CbB install instead of the update installer for the current release.

So why not just get the full installer instead of all this process?

  • Like 1
Link to comment
Share on other sites

Just now, Olaf said:
7 minutes ago, scook said:

Rolling back two versions (this requires rollback installers for the last 2 production announcements) will cause the update process to download and run the full CbB install instead of the update installer for the current release.

So why not just get the full installer instead of all this process?

user preference and cost

 

For the longest time users requested an update only installer. After the initial install, update installers are adequate for most user needs.

Update installers are considerably smaller than the full installer so cost considerably less to distribute.

 

Link to comment
Share on other sites

15 minutes ago, scook said:

user preference and cost

It would be user preference if you had the choice. Otherwise it's more like a user must.

As for the cost, it's probably the exact same. Regardless of how you access the installers, the bandwidth involved is the same.

It's not about getting the full installer every time, instead of the update, it's about having both available, for when you need each. Like for now, when you would want to update all your dlls.

I like having automatic updates in CW, don't get me wrong, I like to be notified, having the update available at a single click, that's all good. Question is what do you do when you need the full installer, or need some extra options. It's not a question of either or, but rather having both, as needed. In the end, it's just a link to the resources.

  • Great Idea 1
Link to comment
Share on other sites

I still get a stereo signal when selecting only L or R input from a Patch Point:

"Mono inputs from Patch Points and Aux Tracks

Prior to this release, if a track or bus had an input assigned to a mono input (L/R) from an AUX track or Patch Point, the input would always and include both left and right channels from the patch point when playing back. Patch point inputs now correctly include just the channel specified as a track input."

 

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...