Will.

? I dont mean treat your room. Turn it from a square room, into a rectangar room side to side.

Your room is also dead square! It is not an ideal room shape to mix in, especially with it being untreated too. This means that there is a far greater amplitude that your ears receive causing you to make negative decisions in your mix. Try trimming down some inches behind you by hanging some drapes/curtains. This does not have to be wall to wall just two in the middle down. You can also just make some panels and place them behind you to get a more rectangular shape side-to-side in width. You could even use what you have at home. An old rug or some old blankets you dont use anymore.

Well, there you answer your own question to why you cant for the life of it workout why your sample rate of your interface in windows need to be the same as your asio sample rate within CbB to run Autotune live for recording without any issues. When you set your device as the default audio card in windows - windows automatically reverts its drivers to use with your interface. Within windows i only get 44k at 24bit and 48k at 24bit with my 2i2. So that tells me that windows uses my interface as the primary audio card by converting its drivers to be used with the device. Once this is not match I get dropout during recording with Autotune enabled. If i match the Asio with the drivers windows use with my interface, GUESS WHAT . . . NOMORE DROPOUTS WITH AUTOTUNE! Its that simple and straight foward.

Right click the icon on the taskbar and go to speaker properties. You need to match this with your DAW so that windows dont get confused with its conversions.

Well, In that case: Good luck with you problem. ??

Yeah . . . Windows 10 sucks! Im still running it though. ? Windows Defender: Disable it completely. Make sure you have the latest VCredist installed. Theres something in this update that is of magic everytime it is installed. Check for new updates, if the issue persist - uninstall previous windows updates and remove automatic updates. If all fails: Do a clean install and only install you VCredist updates.

. . . . and that is the answer. What I have been saying the whole time.

Mine does. ? My focusrite 2i2 is my only device on my system as my main soundcard, there for, I have access to my Asio Drivers. So whatever I change in the DAW affects my Asio Drivers for my interface (aka system drivers.)

Thats strange seeing that its compatible with hi speed USB too.

Your Asio needs to match that of your DAW which than goes in to Autotune. So, your buffer size needs to match. You Asio buffer size, You DAW buffer size and your buffer size in Autotune. This mean: If your Asio driver is the only driver selected in Windows as the primary drivers - set that sample rate according to your DAW which would than go into Autotune. What you're running in your DAW needs to match that in your O.S. From there you can adjust and match the buffer size in both your Asio drviers and in Autotune - depending on your Audio Insterface drivers these can be set independently. For instance with Focusrite Asio drivers whatever you change in the DAW change in windows too and also true the other way around. RTM of autotune. Try to disble that annoying Windows Defender too. Mine is permanently disabled. PS: I have no issue in regard with recording live vocals with Autotune with these settings.

Well . . . that is why you route the input echo channel to another audio track to record it with the effect. Most rappers an even singers prefer this way of recording. My system handles this with absolutely no issue if you do your setting correctly as i have said above.

I sometimes record rappers in CbB. Make sure your sample rates are in sync'd. Recording bit deph should match that of your Asio>Daw>Autotune.

It is extremely important to have your sample rate in windows exactly the same as in your audio application with SSD (also in general.) Then of course theres the obvious noticable setting: Which ever sample setting you had per project that was aaved needs to meet the exact same rate as your asio driver. Theres also that annoying Windows Defender. Disable it entire, by Enabling the setting in Local Group Policy Editor - you can do some research on this or watch youtube videos on how to do it. Last resort: Reinstall the M-Audio Asio drivers and make sure it is the only driver selected in Windows 10 and your DAW(s)

Say what?

They are old. We need a new historical one to talk about for eons. ? Call if you need help.

No, Nein, Ingen, Nej, Não, Nee. This topic has been touch on throughout this thread since page 1. Management have made everything crystal clear already. Further information on the pricing will be announced in future announcements.

? This is a polite way to tell everyone to move on ? "Next."

True. But you dont need a plugins though. The plugin will be faster, but its not needed. ?

Another one? ?

Edit: So is varispeed. Tape type Varispeed. Users just need to learn how to use it. I wont say its a hidden feature, more like one that is forgotten. I've been using it since i got my first copy of Cakewalk X1 LE.

From a personal point of view: For a very long time CbB felt clunky to me. This also depends on what you take as "Clunky." Clunky to me was - it felt overly "Cluttered" too many modules for a long time and I had a good reason to have felt that way. So this depends on what others see "Clunky" as. A few months ago all that changed in a day when I bought a 27inch 1920x1080 resolution monitor. All that "Clunkiness" disappeared. Cakewalk looked different. Theres enough real estate available. I can expand all my modules and still have enough space open. It doesnt look heavy or like theres too many things on a display - you know . . . look and feel "clunky." I was running a 20inch before. Instead, it looks sexy since i got the monitor.

I feel Netflix is busy planning to negotiate a movie deal about this topic alone. ??

? There goes my coffee.

Where can one signup for some panic? ?

Read the previous posts earlier in the topic on this matter. Just scroll to the beginning.