AB9

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.

I assume you checked your spam folder?

Thank you. Does Sonar then have the current capability of taking advantage of the the possible values of the Vidal example?

Here is an example of a piano controller that uses high resolution midi: https://playvidal.com/products/vidal Here is quote from it: "Our electronics capture hi-res MIDI, with over 16,000 velocity values where most keyboards only support 127." And my underrstanding is that Cubase allows for high resolution midi. This is from AI about Cubase: High-Resolution MIDI Velocity (MIDI 2.0): While standard MIDI 1.0 uses a 7-bit velocity value (0-127), MIDI 2.0 introduces a 16-bit velocity value, offering much finer control over dynamic expression. This means you can have 16,384 possible velocity values instead of 128, providing a much wider range for dynamic expression. Cubase 13 supports MIDI 2.0, allowing you to take advantage of this higher resolution velocity. NOTE: This seems like it would be a pain in the editing process. But maybe it is better in the capturing process.

Does Sonar do high resolution midi? (Such as velocity) If not yet, are there plans for it? Thank you!

Thank you IgoRr. The Shift did not work. But the deleting the aud.ini worked!!! Problem solved thanks to you!