Maxim Vasilyev

Video with the second problem with a click on a track with plugins on the master. 2. Click_2.mp4

Hello I want to tell you about two problems with clicks. I have long noticed that in some projects in Sonar, during playback or rendering, clicks appear on the Aux (occasionally on a track) that is not playing at the time. Watch the video, which shows the Aux (track 43), to which sound is sent from tracks 41, 42, and during project playback, when there should be silence on these tracks - several clicks appear. Note that there is silence on the indication of tracks 41, 42, and clicks on the Aux. In the video, these tracks are frozen, but clicks also occur when they are unfrozen and I do not understand what exactly can cause these clicks, because in theory at this time they are silent. This often happens on the Aux, which has a plugin from Native Instruments or Fabfilter. If these clicks appear, they appear in the project at approximately the same place, and to hear them, you need to start playing the project from the very beginning. They can also be after Export Audio in the rendered Wav file at the same place where there are clicks when playing the project in real time. But this project can also be played without clicks, i.e. their appearance is unpredictable. This problem exists on the new Sonar and was previously observed on Cakewalk by Bandlab, and on the previous Sonar. In my opinion, this arose when Auxes appeared in Sonar, although very rarely such clicks appeared on any track. Moreover, this happens in projects at 44.1 kHz, and at 192 (24 or 32 Bit), i.e. it does not matter what Sampling Rate is set at the moment. Of course, when such a problem occurs on an Aux or Track Bounce to Track(s) and muting the "broken" Auxes (Tracks) solves it, but understand me correctly - it is annoying when such crackles start at an unpredictable moment. The second problem is that the click can appear right before the start of the game on this track after its Bounce (or Export Audio), when the master has plugins from iZotope, Softube, Fabfilter, Slate Digital. In the second video, you can see that at the beginning of the file on the first track there is silence, and after Bounce, before the start, a click appears. I changed the bit depth, but this did not fix the problem. Has anyone ever had these same problems and how to solve them? Important! These problems I am talking about occur in projects that I did 8-10 years ago on the Sonar of those years and, perhaps, these problems arose when opening these old projects in the new Sonar, although the plugins that were in those projects were deleted (or they did not open) and replaced with other plugins, and the Auxes were also created in the new Sonar. I haven't created a track from scratch in the new Sonar yet and I'd like to believe that this problem only occurs when opening old projects. 1 Unpredictable clicks on track or aux.mp4

I have the same problem. Yesterday everything worked. Today I tried to log in to Cakewalk Product Center, but I get an error message, while when I activate it, two BandLab windows open in the browser, and in both cases I get an unsuccessful activation. Tried changing the default browser from Google to Edge, still an error. At the same time, Sonar itself works fine, and I successfully log into my account on the BandLab website, but Cakewalk Product Center for some unknown reason refuses to log in. Wrote to support@cakewalk.com.

Hello How to insert multiple audio files into one track in one step? If now I drag several audio files from the explorer to Cakewalk, they stand up each in a separate track, but I need them to be one after another on the same track and, preferably, there should be a pause of 1 or 2 seconds? My task is to make a preview for stock sound effects (one item can have up to 15 audio files), which are more than 1000. Now I manually transfer them to one track, but in the future I will have to repeat this operation 500 times and I would like to have a function that allows you to load several audio files on one track in one action.

A little explanation. The video shows when I stop at the place where I want to leave the clip, but when I release the mouse button, the clip itself moves to the left. If you increase the Horizontal Zoom Control parameter, then everything is fine.

Hello This is a long-standing problem that still existed in early versions of Sonar. With a certain Horizontal Zoom Control parameter (closer to the minimum values), with the grid on, if you advance (or copy) a clip by some measure (with sticking to the grid; audio or midi; forward or backward - no difference) it, a clip, bounces forward. Link to video (Cakewalk version 2021.09): https://drive.google.com/file/d/10NLu-s6r2Rge328Pve6VkUvnhn5vQfHH/view?usp=sharing This manifests itself only during work, not always, but it is impossible to deliberately cause this problem in a new project. Are you aware of this issue?

Great news, Noel! Yes, this problem has manifested itself since the version in which the AUXs appeared.

Before writing here, I carefully reviewed all the settings of all tracks for duplication. I myself started working in the 90s with Cakewalk 3, in which the Panic button was in the form of a face from the "Scream" painting ? - I understand what I am doing.? The fact of the matter is that it is not easy to catch this problem, it rarely appears and, as a rule, at an unnecessary moment when you need to quickly fix something in an old project, and as a result, I am not sure now that when opening of the previous project, somewhere the AUX track setting was knocked down and you have to carefully review and listen for this. Fundamentally, this problem is that when you have everything in your project configured as you need, and when you open it, say, after a month or more (sometimes the next day), the program itself "decides", to change something - it’s not should be. Sometimes this is solved by reloading the project. There was such a case - I opened the CWB of an old project, and there was some kind of AUX track louder, without touching anything, saved it in CWP, closed the project, opened it - and all the rules. Sometimes it happens that way. The next time, when I have this problem again, I can send a file with the project, because this project, which is on the video, I have already "fixed". Maybe someone will try to open their old projects and see if everything is okay in these projects with AUX tracks?

Hello again Well, no one has this problem, which I write about in the first post? To clarify, when I work with current projects, the problem of increasing the volume in the AUX Track for unknown reasons manifests itself, but not always, and not on the first or second day of the song creation. So today I opened a project that I opened for the last time in the spring of 2021 and again ... https://drive.google.com/file/d/1ULqsb_aRT0okxSDCTleO3xDUfMWzzW95/view?usp=sharing This is a link to a video (albeit without sound), where you can see the difference in sound volume in the AUX Track using the indicators on the tracks. The AUX Track "Drums" is the AUX Track that was in the project, and the AUX Track "Drums NEW" is the one I created now. All of these AUX Tracks have the same parameters, all plugins are turned off, etc. This happens at both 44 and 192 kHz without a difference. This does not depend on the audio card or version of Cakewalk and Windows 10. Most often it happens with CWB projects, but also with CWP, as in this example in the video. Question to the developers: Have you identified such problems in yourself? I could not specifically identify this problem in a new project, but it unexpectedly arises at the stage of creating a song. It often happens like this: song creation (3-7 days), mixing - everything is ok. The next day (or a few days later), when something needs to be tweaked in the project (and there are already about 10 AUX tracks and in total there are about 50 tracks), then some, as a rule, one of the AUX Track will "shoot" + 6db! I understand that you can create a new AUX Track and send the tracks from the "broken" AUX Track to a new one or lower the volume by 6db (which I do), but something tells me that it shouldn't be that way.

No, but I think this is a problem with all Harrison plugins and a problem with the interface of those plugins. If they find a solution to this problem, then their other plugins will solve this problem.

I wrote an email to the developer of Harrison AVA Vocal Flow.

Hello. At first I only installed the VST2 version of Harrison AVA Vocal Flow and successfully registered the plugin, but after that everything hung. Restarting the system did not solve the problem: the plugin is loaded, you can turn the knobs on its panel, but when you click any other window, Cakewalk stops working (for example, try to close the plugin window). Later I uninstalled the VST2 version and installed the VST3 version. When this version (VST3) of the plugin is called, Cakewalk is simply closed. Then I installed both versions (VST2 and VST3), as well as all versions of the plugin that the installer offers - crash. A colleague from another studio has the same situation on Cakewalk. This is observed on Win 7 and win 10x64 as well. Everything works on other DAWs (eg Cubase). Does anyone have the same problem?

Hello! I faced this problem too. I have Win 10 with the latest updates, Cakewalk version 2020.09. This problem occurs in all projects using plugins protected by eLicenser. Installing eLicenser Control Center update 6.12.4.1276 and eLicenser Control Center update 6.12.4.1275 did not resolve the issue. For some reason, eLicenser starts the second process (this can be seen in the Task Manager), if you force it to close, then you can save the project without problems. But I solved this problem by installing an earlier version of eLicenser Control Center 6.11.10.2272. Looking forward to future eLicenser updates.

Sometimes I need to split a single audio recording in order to change the gain on several fragments. I understand that this can be done using the volume envelope, but I want to do it with the help of Gain, because there is such an opportunity in Sonar, but it is broken and this is a program bug. Hopefully this will be fixed in the next update.

Yes, for me this also happens with drums often, but also with vocal tracks. Perhaps some mono channel at the next opening becomes stereo in the channel properties?