IgoRr

Here is:

Yes, both he and I have the latest release 02.2022, the full installer 28.02.0.029 was installed. I just checked again, but I copied only 1 MIDI track, and the operation went successful. Maybe the question is that it's not possible to paste multiple copied tracks into 1 because there is only a field for 1 "new track" in the paste options? I send you a mini dump file here: Untitled_02212022_135753.dmp

A friend of mine just wrote to me, he was trying to copy some MIDI tracks (clips) from one project to another (empty), when doing a Paste Special in a new project, and when specifying the destination "new track", the Cakewalk instantly crashes. I checked the same thing on my computer - everything is happening. If I perform the same Paste Special operation on existing tracks, everything works fine. He has Windows 10 installed, I have Windows 8.1 Pro x64. I have a mini dump file about this crash, I can send it if necessary. Please check if this is happening to anyone else.

Now I specifically tried it - everything works flawlessly, I have version SSL Native FlexVerb 6.5.0 VST3. I checked all the presets, inserted them on different tracks and BUSes, even tried to insert 2 instances in series - everything works without failures. I have the latest update build 027, Windows 8.1 Pro x64 installed.

I work on Windows 8.1 and Melodyne 5.1.1 works for me without the slightest complaint. Also, it's best to copy clips with Melodyne after you "bounce to clip" on the original clip, this turns it into a "monolithic" file and is almost guaranteed to eliminate copying problems.

I just checked - everything works completely normally, there are no anomalies, after applie Melodyne, it opens in the format "Region FX"

This problem looks very strange, given that the MIDI system itself is universal, and is not tied to any specific engines of specific companies, it seems to me that this Thomas is a little disingenuous, announcing the "end of support for Cakewalk". But even if we assume that this is the reason, we can only hope that the developers from Bandlab will try to fix this problem themselves in the near future. Although, in the last few years, the leading competitors have clearly seen the displacement of Cakewalk from the media space by all available means, including the failure to provide support for Cakewalk by leading plug-in and other instruments manufacturers.

@Noel Borthwick Is it normal that the "Assistant" cannot be moved anywhere from the center of the screen? I remember that before a certain version, its window was completely controllable, and now it's not very convenient. I have windows 8.1 pro x64. Thanks!

A little different: Cakewalk was shelved not because of its instability, but because of the sluggishness of the guys from Boston, who, at a key point, could not (or did not want to) agree with Steinberg in terms of using ASIO. And while Cakewalk was looking for its analogue of this driver for 10 years (!!!), most of the dedicated Cakewalk users and some professional studios switched to MAC. Sometimes this is how you can literally break the course of History.

@Lord Tim In today's world, where literally everything is based on profit, the number of users has little effect. And the examples I have given above confirm the tendency to squeeze out Cakewalk from this media environment. I partly agree that Bandlab does not introduce amenities for beatmakers and hip-hop lovers, but Steinberg or Logic Pro do not do this either, nevertheless, their popularity and authority in the professional environment is only growing. I'm not exaggerating, I remember very well that 6-8 years ago, Cubase or Logic Pro were first of all compared only with Sonar, and now Cakewalk is practically not mentioned, except by individual enthusiasts. But from every iron you hear about Studio One or Reaper. And I repeat once again: now Cakewalk is in the best shape for all the years of its existence, it has much more creative tools, it has become much more convenient, but it is less and less in a professional environment, as long as it rests on the pure enthusiasm of users.

@Asato Maa Not a bad idea... in theory! Although, looking at what is happening in the music production environment, it seems to me that it will not be possible to save Cakewalk. The reason is very simple - at the present time, the fate and popularity of any program depends not on the number of subscribers in social media, and not even on the number of users, but on the commercial position for this program on the part of plug-in manufacturers or tools for it. And in this matter, from the moment, when Bandlab decided to make Cakewalk free, it began to be openly squeezed out of the market by its main competitors. The most important examples are - Audiobro, Cinematic Studio, Native Instruments and some others, which fundamentally do not apply "integration into DAW" in relation to Cakewalk. Over the past 3 years, our beloved DAW has completely disappeared from the list of "best music production software", while Cakewalk remains in the spotlight only thanks to private enthusiasts who dedicate their reviews to it. I already know quite a few professionals who, after 20 years of working with Cakewalk, are now switching to Cubase or Logic Pro, although right now Cakewalk is in the best shape ever. Unfortunately, the commercial policy of Bandlab does not depend on our opinions and will not change, which will inevitably lead to a complete drop in user interest and Bandlab's refusal to continue working on it.

@Jason Halogen This has never happened to me and never happens, although my keyboard is different. But I'm pretty sure your problem is that you've set the wrong MIDI input parameters on the tracks. You need to select for ALL tracks "Oxygen 88 Omni", almost completely sure that your problem will be solved. In addition, you should definitely arrange the outputs in all MIDI channels on each track by ascending numbers, because of this, confusion can also occur.

How can you work with individual notes/fragments of a track using a primitive quantize block in Inspector? Besides the fact that the Inspector contains only INPUT quantize, it can also be applied only to the selected clip as a whole. I specifically explained: it would be much more convenient to have such an open (NOT a drop-down menu) module in the Piano Roll, so that you can select the desired notes or fragments, and be able to control the quantize parameters when PLAYING the project.

This is what I checked first, the result is exactly the same. The fact is that this is the first time it happens with this plugin, in the previous release (november build) the same plugin of the same version worked completely fine.

Today, when opening a project with HOFA IQ-Reverb v2.0.5, Cakewalk build 27.12.0.102 completely crashes. I checked it several times on different projects, specially created an absolutely empty project without any other processing, added this plug-in to the tracks, to the BUS, save the project, reopen it - the result always crashes. The project normally opens in safe mode when this plugin fails to load, but it always crashes with it. I have already sent a report to the Bandlab support center, but just in case, I'll post the same here. I am attaching a error screen and mini-dump file, I hope for some clarification. ШАБЛОН '21''_01112022_004008.dmp

In general, yes, but the most convenient and logical place for such a block - is the Piano roll, where you can select the necessary notes or fragments, it seems to me. And precisely not in the form of some additional plug-in or plug-in module, but as a part of Cakewalk itself.

For many years I have been working at DAW from the Cakewalk company, and all these years I think that our program is missing a small Quantize pane in the Piano Roll. This could have been the controls for coantise and swing right during the playback of the fragment. It might look like a panel from Logic Pro X, although there is something similar in Cubase. Personally, I like the Logic Pro X version more and it seems convenient, although the Cakewalk team can certainly make their version no worse. Thanks in advance! I attach the screen.

The issue of working with a computer (in general) is not limited only to the speed of system loading, but also to the amount of free space on the system disk after installing the System (Windows) and all (!!!) programs that you use. This is important for the system to create a RAM-based virtual memory buffer. You can, of course, somehow work on a 128 GB disk, but practice has shown that this is enough only for the correct operation of Windows itself, and a set of utility programs that are not very heavy. To work with heavy and advanced multimedia programs, the manufacturers themselves indicate the minimum and recommended requisits, you yourself brought them. And this is done on the basis of their own measurements and checks. In my experience, the minimum sufficient storage capacity of the SSD for stable reliable work with music programs should be at least 250 GB. I have a system and the first "working" volume - type NVMe, this is generally the best solution for this type of work. But for portable programs, or for libraries from virtual instruments (Kontakt etc.), for folders with projects and audio-video material, any other disk or the creation of sim-links is quite suitable.

No, I didn't mean changing the values of the clip itself in the project, but the settings of the Windows audio system. Until you set 96 K in the "System Sound - Play" section, and then in the settings of the Cakewalk itself, it will not work correctly for you.

@EnglandBross I would venture to suggest that you change the resolution to 96 K only in the Cakewalk itself? For everything to work stably and reliably, first, it is in the system (Windows) sound settings that you need to change the discreteness (and the required bit rate) to 96 K, and then in Cakewalk. I have several examples of my friends who, on certain sound cards, with a discrepancy between the settings of Windows audio and Cakewalk, also had DAW crashes.

@murat k. I do not insist on my opinion, but personally it seems to me that you are over complicating the task of structuring plugins. There is no need to sort them on two levels (subfolders), if it can be organized much faster at one level in the Browser, and it will be no less intuitive and convenient. Human perception reacts much faster to objects accessible to the eye, than to those closed in folders, which directly affects the speed of searching and choosing plug-ins, this has been verified by many years of working with different programs. Quite a long time ago, a tendency has appeared for most software manufacturers to put everything in subfolders, which noticeably lengthened the search for objects, compared to the open list. And according to your method, at first a lot of time is spent on organizing, and then time is again wasted on searching and opening subfolders. Of course, this is a matter of habit, but from a rational point of view, this is not justified in practice.

@Mark MoreThan-Shaw Now I tried it - I have absolutely the same thing with folders and the "plus" sign, thanks for the noticed bug!

@murat k. You have nothing to answer? I have more than two plugins selected on the right-most side (layouts), so what exactly " it's not"?

@murat k. What exactly "it's not"?

@Daniel Russell You definitely have something wrong in your system, on my right side of the Plugin Manager you can select at least all the plugins from the first to the last. And it has always been that way, even in older versions of Sonar. Look for the reason in your system, the Plug-in Manager itself is working completely normally.