AB99

Thank you for clarifying that your comment was "tongue in cheek." There is something about posts on the internet as compared to in -person conversations that seem to exaggerate positions. I am just trying to explain my viewpoint on the "not finished" aspect and why I highly value the Sonar release, and I do not have any negative aspersions about you personally. While I have my own opinions, I try to value the opinion of others, including those that disagree with me. If two people think exactly alike, one of them is not thinking. I wish all the best for you, sincerely.

It is finished in that one can do professional and artistic work with it. Just because there is more that they want to do should not hold us all up for the other benefits like the reduced latency. And it is likely that after they create more graphic options that there will be other things that are not "bug" related. By the way, I just recorded a great session drummer today who works with many DAWs of many producers and he was impressed with Sonar. I hope you have great success with whatever DAW you use.

Almost no complex software is finished! MsWord by at one time the richest guy in the world! People complained a lot when Gibson dropped the prior version of this software. Meng saved it and made it free for years. If we pay $$, it helps fund the staff, this board and more. It helps with sustainability. I operate a small board and it is a lot of work! Cheers!

Sonar went to vector graphics. There are several reasons for vector graphics. So some patience will be required while they work on more color editing possibilities. Meanwhile, clips can be selected and colors can be chosen - both for foreground and background. Perhaps not ideal but it works.

First, I am very happy with Sonar. Everything important thing I need is there and the ability to record with very low latency is outstanding. I did notice an issue recently that is not critical, but still an issue. When I save to one hard drive I get a progress graphic of the saving. That is great. But then when I go to save it again to another hard drive, the progress graphic is not there. It appears that it does save it though. And any other hard drive after that, the same issue. I try to save every project to at least 3 hard drives. Any thoughts as to what may be causing the loss of the progress graphic on additional saves? Is it a Sonar issue, Windoes issue, something else? Anyone else noticing this? Thank you!

I think they said they are working on a theme editor. Hopefully, we can get some more information on that.

I assume they are working on the GUI. Iirc, the bakers indicated that there was a major GUi overhaul to go to the new Sonar for some modern reasons and that this was something they were going to address. Meanwhile, Sonar is working great for me. Is it perfect? No. But where it really counts for audio quality - like latency, it is great. It is minor issues like the markers being small and having a small font that bother me. We are dealing with very good people and they listen and make enhancements. Take for example, the free version of Sonar.

What are you worries about might happen 3 years from now? Is it that Bandlab will no longer offer Sonar or Bandlab folds or something like that? If that is the concern, maybe Bandlab could provide a written guarantee that if Sonar were to no longer be available that subscribers would be offered a reasonable purchase option at that time. Thoughts?

Can you set the background colors for all clips across a track without having to do so one at a time?

I would love it if I could make the fonts large in the markers on top. It is really hard to read what I write what the marker it about there. Maybe they could make it so if I hover the cursor over the marker - then a window temporarily opens up with large letters. Thank you!

I am curious. When would someone not want plugin load balancing checked?

I would go with the new Sonar. The latency specifications are better, at least for me, and that is important. Apparently, they have a new free version of Sonar that you might like, if you do not want to go with the subscription. By the way, I was also a user since the 1990s.

I like the horizonal meters better than the vertical. Is there a way to save the option of horizonal in the workspace or something else? The default seems to be vertical. I would also like the 90db range to be my standard setting. Thanks!

Love Sonar - but would love this feature. I can change the foreground color of the track but not the background color.

Congrats on getting a new computer. Keep us posted!

That is good info. Thank you. But if there is no need to move automation or other data other than the clips, it seems quicker to drag the clip or use the slide function.

Slide does not move some of the automation data and I think tempo map, but it does move the entire clip that you have selected. So select the clip that you want to slide, then go to process - slide, and then in the slide window insert the number of measures you want to move. I am not sure what you mean by "3 times." Also, you can select a clip and drag it to the measure you want to move it to. I would set snap to grid to "whole" so it moves snaps in at the beginning of a measure.

I do not have the program open now, but based on memory - it is under process - then select the slide option. In the slide option select measures and then enter the number of measures (under a - sign for sliding backward! ) Good luck! Nice avatar by the way!

You can select all the clips you want to move - go to "slide" and slide the number of measures that you want. It is easy to do. By the way, you can slide backwards or forwards.

I had a problem template last year. It happens. You just have to start from scratch. Please report back. One of the great things about Cakewalk, is there is a community here that tries to help!

Paul - I do not think you are rude at all. And you can be 1000 percent correct! I noticed that there are some keyboards being made with this high resolution and I was curious if Cakewalk was doing something about it. Perhaps the velocity aspect is beyond human comprehension. But I also do not think it is all about whether someone can repeat the velocity again and again at such fine points, but whether there is any added realism to the result. If there is truly no added realism in the result, then I would think that such would eventually not be a selling point for those keyboards, at least on the velocity issue. May be that there is another benefit to the advanced midi that goes beyond just the velocity issue. (I think you wrote about this!) Thank you for chiming in on this!

Mercury Classic Bright seems to work best for me.

Will - I can see where you got that idea in the beginning of the article, but then the article gets more specific. Here is some quotes from the article, including when to dither: https://www.izotope.com/en/learn/what-is-dithering-in-audio.html#:~:text=Dithering should always be off,bit to 16-bit). When to dither audio Dithering should always be off unless you're bouncing audio to lower bit depths. Ideally, you should only dither audio once during the final stage of audio mastering when exporting a file to a lower bit depth (e.g. from 32-bit to 24-bit, or 24-bit to 16-bit). However, almost all modern digital audio workstations operate at 32-bit floating point or higher internally, so if you’re exporting a 24-bit WAV file for mastering, you should also dither. Generally, you should only dither audio when bouncing down to 24-bits or less. You don’t have to worry about dithering if you’re exporting a 32-bit floating-point file or higher because it’s a high enough resolution that produces no audible quantization distortion. . . . Start using dithering in your digital audio Hopefully this helps you understand why dither is so crucial to digital audio, how and why it works, and when it should be applied. Now, you’ll never have to dither about dithering again. If you’re reducing bit depth, whether from 64 or 32-bit floating-point to 24-bit fixed point, or from 24-bit down to any lower fixed-point value, add dither! It will always do more good than harm. (Emphasis added.)

I am not finding what you are writing, in the article. Maybe I missed it. Here it states that one should dither when changing bit depth and almost no other time. https://www.izotope.com/en/learn/what-is-dithering-in-audio.html#:~:text=Dithering should always be off,bit to 16-bit). I do not see how recording is changing the bit depth. Maybe I am missing something here.

Did you try opening your Cwb projects in Sonar in safe mode? You might want to try that. Then add the plugins you want. I am just curious if that works.