Igor

Of course, this is a typo, you are right, I wanted to write 384, thanks for the correction!

Thanks, Noel, for your reply! No (at all) changes in the system since yesterday morning, there were no changes in my computer, I did not install, uninstall, clean the registry, etc. I checked everything very carefully several times - in the complete absence of any other running programs, processes and services (I used the "Task Manager"), nothing changes in the behavior of Sonar - the audio engine load is noticeably higher than before in the same projects, I opened 5-6 different projects to check. I have several very heavy projects with 120+ tracks, including 10+ audio tracks, about a dozen different VSTI, and quite a lot of different processing, these projects slow down very much in this latest version, which was not observed in the penultimate one. And the same projects, in Cakewalk by Bandlab, work practically without anomalies, and with a noticeably lower audio engine load - about 15-20% down in peak values. Moreover, for the purpose of the experiment, I installed the previous version (build 109), and nothing like that happens in it. To completely exclude any coincidences, I again reduced the number of samples to 386, as it was before, and everything works without any problems. And when I reinstalled this latest version on top, a higher audio engine load is observed again. In principle, I can work with even higher sample buffer values (768, 1024, etc.), since I do not directly record audio or instruments, but the very fact of increased audio engine load forces me to ask these questions. I fully admit that the problem is in my computer, but I would like to understand what it is in order to try to fix it. And one more question: it seemed to me that in the previous release it was already stated that the initial screen with the counter was removed when Sonar was launched, but in both the previous version and this one, it continues to appear, did I misunderstand you?

Good day to all! Yesterday night I installed the latest version - build 08.004, opened my last project, which I worked with before, and immediately noticed an increase in the audio engine load. Sometimes the load indicator exceeds 280-300%. Artifacts and even slight slowdowns appeared during playback. I installed it over the previous version, the settings remained the same, but the audio engine load increased noticeably even in the idle mode of the project. For many years I have been working on the audio system settings of 48 kHz 24 bit 386 samples, and even in the most difficult projects the audio engine withstood such settings without problems. I opened the settings in the panel of my audio card - Steinberg UR22-C, and increased the buffer size to 512 samples, now it has become better, but sometimes, still, small artifacts in the sound are heard. This is very strange, because the project has very little processing - no more than 10-12 plugins in total (none particularly heavy), 5 activated ProChannel, one audio track, and 8 MIDI tracks with sending to Kontakt (strings groups). Can you check the loading status of the audio engine and the system as a whole, so that I can understand why Sonar's behavior during playback has changed so much? My system runs on an Intel QuadCore i3 8350K, 24GB RAM, and before this update, I did not experience any noticeable problems with projects in either Cakewalk by Bandlab or Sonar. I understand that for the new Sonar it is desirable to have an 8-core (or more) processor, but everything worked quite well on the same hardware before. Or maybe there are some tips on setting up Sonar itself or the audio system that can fix the situation. Thanks in advance!

The color for the header of tracks and buses is selected not with the right mouse button and not anywhere, but on a narrow strip to the left of the header of any track with the left mouse button, see the attached GIF file. In the same way, you can select a color for a group of tracks or buses selected together.

You need to go to this section of the screen settings and activate this checkbox (see screenshot), then the colors you choose for the tracks will be displayed not only on the content of the clips.

Hello everyone! I installed the latest update (build 097) today, and when I try to open a previously saved template, from which I start all new projects, a notification appears: "PC2A Leveler Amplifier - Error: Missing or corrupt resource file/s". Then the project opens, but when I try to open the "ProChannel" field in the "Inspector", Sonar crashes. I tried to create a new empty project from the factory templates, and everything happens the same way, but "ProChannel" opens, although it is still impossible to add "PC2A Leveler Amplifier" - this notification appears again and the "PC2A" interface is displayed simply with empty gray background. After trying to remove it from ProChannel and add it again, Sonar crashes again. Absolutely the same thing happens with the latest version of Cakewalk by Bandlab. Before installing the latest Sonar update, I uninstalled the previous version (build 094), maybe that's the reason? I've already tried reinstalling both Sonar and Cakewalk, but nothing has changed. Is there a way to restore this module, or will I have to completely uninstall and reinstall everything? Attached is the dump file and a screenshot of the error notification: Shablon Sonar '25_07192025_111930.dmp

Today I installed the latest version of Sonar, and I can say: I think this is the best version in the last year or two! After this update, I now have everything in order with the display of all texts in all windows and sections, the names of modules appeared in the "Style Dial FX" section, which was not there before this update. In addition, the text has now become more contrasting in the windows of the pop-up hint in all places where it appears - on the "Automation" line, in the Piano-roll, etc. And now the track numbers are displayed in the headers, which I also did not have before. And today I am happy - I have a perfectly installed and configured Windows 10 system, I have the best DAW for serious and productive work with music in any style, and the very first project opened today also loaded faster, and is played with less consumption of system resources! I thank with all my heart the entire team of developers and everyone involved in the "polishing" of my favorite program, happiness to you and good health to all!

In theory, synthrack is a one element of the "Browser", where there is also a section for plugins, notes, help, etc. And the "Browser" window is opened and closed by pressing the "B" key on the keyboard by default, if you pin "Synthrack" to the "Browser", you can open and close this section with one "B" key. And in the "Dock" at the bottom of the main window, plugins and the mixer console are pinned, you can open and close the "Dock" with the "D" key on the keyboard.

I have been using an excellent program for cleaning memory for many years - MZ Ram Booster. This is a free utility with very good settings for any actions to clean memory, including automatically, with settings for "minimum RAM", "Auto-cleaning when starting / shutting down Windows", "Cleaning every ...", etc. In the vast majority of cases, I use it to work with video editors that consume a lot of RAM, I have never needed to use this program to work with Cakewalk or Sonar, but if someone has such problems, then MZ Ram Booster can also be useful. https://mz-ram-booster.en.softonic.com/download

Also check the Tempo track, maybe you have some events after the last note in the project. In principle, literally any event recorded in any format on any track affects the stop of playback at the end of the project, you just need to find this event.

Try converting the effects added to the rack to "Convert FX Rack Effects to FX Chain", then holding down the "CTRL" key, you can copy the converted FX block to any other track the required number of times, and then extract the effects in other tracks to the standard format of separate effects using the "Extract FX Chain Plugins" function. This is also not done directly in one click, but it will still save you a lot of time and effort in such operations. Try to perform plugin extraction operations on new tracks by selecting several tracks and holding down the "CTRL" key, it is quite possible that it will work, and you will be able to save even more time.

If you don't need TTS-1 and never use it in your work, there is a guaranteed way to bypass assigning a MIDI output to it: you need to go to the tab at the top "Utilities" and select "Cakewalk Plug-in Manager - DirectX Instruments (DXI)", select TTS-1 in the right part, and click the button at the bottom left "Exclude Plug-in". After that, TTS-1 will no longer appear in the list of suggested outputs from MIDI tracks. If you need TTS-1 again at some point, you can connect it in the reverse order, I have attached an animated screenshot of the entire operation, it is very simple.

Does Cakewalk by Bandlab launch (open) itself for you? If so, you first need to configure the system audio - specifically in the system settings (Windows audio settings) select the driver from your sound card for "Playback" and mark it as "Set Default", then select the same driver in Cakewalk. If Cakewalk does not launch, then try deleting the "AUD.INI" file along the route: C:\Users\IGOR\AppData\Roaming\Cakewalk\Cakewalk Core -- The next time you launch Cakewalk, it will recreate this file, and you will be able to select any of the drivers available in the system.

I just checked it in my Sonar - this plugin works completely normally, I have a rather old version - 1.0.3.84 from the "Additional Content" from the SONAR X3 I bought back then. The most likely reason for your failure with this plugin, it seems to me, is either incorrect installation/activation, or the absence/outdated versions of dynamic C++ libraries, read the content of this post on this topic, here you can also download the necessary Visual C++ set: https://discuss.cakewalk.com/topic/80961-resolution-startup-crashes-with-latest-sonar-release/

Try to create a new empty folder for projects on any other disk, check all the details of this folder: "Read only; hidden; locked", remove all this, then create a shortcut for this folder and place it on the desktop. Then create a new empty project in Sonar (you can open the factory template), and save it to this folder. Close Sonar, and try to run this saved project again, if there is no scanning, then it is better to work with projects in this format. And in general, storing projects on the desktop is far from the best idea, in case of any problems with the system (virus, crash, startup failure, etc.), all your projects will simply disappear, because the desktop - is physically a system disk. You can, of course, make copies, but then why duplicate everything if you can initially store projects on another disk?