IgoRr

Try launching the Cakewalk, and from the already open program through the browser, run this project with the Shift key held down, this allows you to open projects in "safe mode". When loading a project, you can select the tools and plugins that you want or do not want to load, most often in this mode, even if you select ALL items to load, projects in most cases open normally.

? ✌️

I have been using this method for almost 5 years now, and not once has there been the slightest incident with any of the existing elements of the system or Cakewalk.

??✌️ Congratulations!

And what settings do you use in the "Audio Export" window? Maybe you unintentionally changed something in the settings, and now because of this, the frequency characteristics of the exported file have changed? Try to attach a screenshot of these settings here, someone will definitely tell you the solution, I have everything left as before when exporting, but I never changed any settings in this window. If you attach a screenshot, I will compare it with my settings, maybe everything will be solved easier than it seems.

By any logic, you need to look carefully at the plug-in settings on the Master Bus, because all other tracks or buses affect only something specific, and you, if I understand correctly, reduce the low-frequency component throughout the mix.

I have carefully checked all the plugins you mentioned and everything works without any anomalies. I specially conducted an experiment - I added all these plug-ins to one track with the instrument (Spectrasonics Keyscape), and everything works properly. Each of the plugins opens properly, only Native Instruments Replica opens with a delay, but this was the case in the previous two versions, I am completely sure that these are features of the latest version of the plugin itself. I want to emphasize that I do not have a discrete video card, I work on the Intel HD 630 Graphics integrated into the processor. I had a couple of times in all the time when, after installing the latest version on top of the previous one, some small anomalies appeared, but never such serious ones. Try to completely uninstall Cakewalk, clean out all folders and files, check the registry, and clean install this latest version, in 99.99% of cases, all problems are completely solved in this way.

For the future, you have one more option: go upstairs to "Utilities" - the last line is "Cakewalk Plug-in Manager". In the left window, select the line VST3. Scroll in the right window all the plugins to the letter "S", if there is no Shadow Hills, at the bottom left select the option "Show excluded(plugins)", it may turn out that for some reason Cakewalk sent it to this section. If it's there, click on it, and on the bottom left, the "Enable Plug-in" button. This happened to me a couple of times, although I have not found out the reason.

In principle, this new function is very convenient in itself, but if it could be "optimized" a little more: make it not in the form of a "point", but in the form of a link, in the same way as the "Add Plugin" function is designed to when hovering over this function, a list of plugins immediately opened, as in the "Add" section. This way it would be possible to "replace" the plugin in one click.

Yes, everything is working perfectly now, thank you very much!!! ?

+1 Yes, I confirm that this is exactly what happens. In addition, I repeated the experiment twice, and noticed that after removing the plugin, with several clicks on the inactive icon, the Cakewalk crashes completely, as in the example of F.J. Lamela. This can seriously damage the project in an unfortunate set of circumstances.

There is the simplest way to bypass the restrictions of the installers of old elements, if you want, write me a personal message, I will lay out the text for the .reg file here, which simply enters into the registry about the "installed Sonar" (Platinum). Sonar itself is not necessary to install, you can install it right away the latest version of Cakewalk with full access to old installers.

I'm sorry, I do not speak English well enough, and Google translate gives some strange translation, can you explain what you mean? ☹️

+1 I fully support the proposal of Xel Ohh! It would also be very nice to be able to add more than one instance of the same module to the Pro Channel, for example, two EQs, one - before the compressor (cut-off), and the second - after the compressor for fine EQ of the track. Or two identical compressors or limiters for sequential compression or limiting. I don't think this is a difficult task, and the payoff for users would be huge!

You understood correctly what I wanted to say and explain my idea. I watch a lot of tutorials from Jacob Collier, he works in Logic Pro X, and his YouTube videos in 4K fully match the aspect ratio of my monitor. And I saw several projects with him, where more than 100 closed tracks were displayed, and there was a feeling that in Logic you can compress (reduce) them even more. I don't know, maybe I'm asking too much, but it seems to me that changing the resolution of the UI is not too difficult for a team that is able to implement such complex and subtle improvements in Cakewalk, although I could be wrong.

Yes, it looks like the way it is now, 47 completely closed tracks or folders fit on my monitor. But I would like the vertical size to be reduced even more, in the Logic Pro X, more than 100 tracks fit in the same size and monitor resolution, while the display of track names is fully preserved, this is very convenient. I don't think it would be very difficult to do this in our Cakewalk, or am I mistaken?

Folders too. But I meant precisely the possibility of reducing the vertical size of tracks and folders, as implemented in Logic Pro X, where tracks and folders can be compressed in size almost to lines, but at the same time, track and clip names remain visible.

Hi! It would be great if to the Cakewalk was added the option to change (reduce) the vertical size of CLOSED tracks, similar to Logic Pro X, this would significantly optimize the main interface window when working with a large number of tracks. Even on my large 2560x1440 32" monitor, the number of closed tracks is very limited, and I have to spend a lot of time searching, batch processing, and moving vertically between tracks. Thanks in advance, continue to enjoy my favorite program from the development team, thank you so much for your work!

I just checked it myself, all submenus open, all functions are available. Try reinstalling Cakewalk directly over the current version, this error may be fixed.

I’m sorry, I can’t find a way to change the in the tempo track of the curvature types between several already created nodes, is there some way to do this in bulk, and not one at a time? For example, there is an already edited envelope tempo in the project, but all types of curves are set to "jump", how to massively change them to "linear"? I tried to do it in the "Inspector" of the track's tempo, highlighting all the events, tried on all the keys and their combinations, but I did not find a single way to change the curvature types in bulk. Also, nowhere did I find the settings to set this curvature type in advance "by default". Thank you in advance for any hint if there is such a way!

All this would make sense if ALL projects refused to save via CTRL-S, but the fact of the matter is that this happens extremely rarely, in the vast majority of cases, it works perfectly. I already wrote in the first post that I used both hotkeys and the file save menu, and none of the methods work. Saving in the "save as" mode does not make sense for me, because I have autosave activated, which saves copies every 5 minutes, and this mode works completely normally. Let's leave this discussion, I clearly see that such an anomaly occurs only with me, and the whole discussion boils down to the questions "have I tried" all the standard saving methods, of which there are only 2, and which I have already developed at the reflex level ?

Absolutely not, where did you get it? Simply, you repeated 2 times essentially the same thing, which is a bit different from what I spoke about at the very beginning in great detail.

You inattentively read my words, if all (!!!) my projects behaved with such deviations, then your assumptions could make sense. But I always save projects in the same way, and in 99% the saving happens properly without any additional actions or expectations. And in quite isolated cases, such an anomaly occurs, which I wrote about in great detail in the very first post.

Many years ago, I did this too, but then I just made my own "template" with fully configured options, a certain number of tracks, groups and buses, added "standard" plugins, customized display of meters, and now I always open it at the beginning so as not to deal with this every time again. And if I start a new project, I immediately rename this open "template" to what the next project will be called, and save it with this new name. And everything (99.9%) is perfectly preserved, without the slightest anomalies. But, in isolated cases (as I said earlier), an already finished project (without opening a "template") is not saved in any way by standard actions, the last changes are saved only when the project is closed by selecting "Save" in the save options window.

Hello! At the risk of asking one question: since the old versions of Sonar, very rarely in single projects, after saving (manually) a working project, when trying to close the Cakewalk, a window appears with the options "Save; NO (do not save) and Cancel". If you select " NO", then the last changes in the project are not saved, despite the fact that before that I saved the project by clicking the "Save" option. I specifically checked it many times - I save the working project, then I specially add a few tracks, or make any other changes, save again, then close the project, this window appears with save options, if I select "No", then the next time I open the project, the added changes will not are saved. I still have the "Autosave" option activated, and it works as expected, it's very strange. I do not consider this a serious "problem", but I would like to know at least the approximate reasons for this behavior of Cakewalk in single projects. Thanks in advance for any ideas and tips!