Misha

David, Thank you for giving this a shot! I don't have a problem with audio at all or with mouse inside of Cakewalk. Mouse slows when I minimize Cakewalk (no audio playing). Just one weird "brand new" side effect with this particular plugin. Never seen this anomaly with any other plugins. It feels like it is conflicting with some particular resources that mouse needs. Who knows. Well, good thing it's isolated.

Hi everyone. I've used this plugin on at least 3 dozen of projects without the issue I am experiencing now. Last time (without issues) about 2 month ago. Before 24H2 update. Yesterday, while I had a project opened with this plugin, I've noticed that my mouse pointer got super slow. About half slower than what it should be. It took me a while to find the culprit. First I disabled all plugins, pointer returned to normal. Then I deleted plugins one by one, until I reached Lurssen. As soon as it was gone, life returned to normal. To re-test my find, I updated plugin to latest version, re-launched Cakewalk. Opened a new blank project and inserted Lurssen (VST3). Moused slowed down. Lurssen has zero effect on mouse when opened in Reaper. Nothing spiking in Task Manager. Plenty of resources. I've used plugin successfully on current machine for about a year. Only started acting up after Win update. Also, seems there is no delay inside the Cakewalk itself, but severely noticed if program is minimized and you just mouse around desktop. This pointer slowdown doesn't happen when using Reaper. Simple steps to reproduce: Pre-requisite Win11 24H2 Open Cakewalk > Blank project Load Lurssen (VST3) Minimize Cakewalk > Move mouse pointer around Desktop. Lag usually kicks in in about 10-15 seconds. Thanks.

Thanks Sock Monkey. I think you are right. It might of been Cubase that installed that Generic driver.

Yeah, but it works as it should now. Through USB. No significant latency. Same as I would get using interface Plus using headphone jack, will most likely bring different flavor to the soup as it will go through a different conversion / preamp process (interface)

Phew. I wish people would chose words a bit more carefully. I don't know the insights, but hope he is OK. ---------------- Again, thank you everyone for chipping in. Seems like completely removing ASIO4ALL solved the lagging issue and Cakewalk is using native ASIO driver of Yeti. P.S. While Yeti PRO has several downsides, after so many years, I still consider it one of the best 24bit USB Microphones ever made (and it has XLR!) that has dedicated ASIO driver written for it, not a shell. Recently AKG Lyra - USB mic which has similar, multi-polar features and excellent reviews went on deep sale, unfortunately it's WASAPI only. As Meatloaf said: "But I Won’t Do That". I do have a decent interface, but find Yeti very special using it as a USB mic. I think it has to do with circuitry that was designed specifically for those capsules. In my understanding, using XLR bypasses internal pre-amp.

"He is no longer with us" Ohh no. Sad...... He helped me so many times.

"this particular setting is just displayed confusing way. " I don't think it's just displaying, seems like it's referencing to whatever is selected . ASIO4ALL was at that specific place, the only reference in Cakewalk, while the native driver was selected elsewhere (in Cakewalk). The only way to get rid of it was full uninstall of ASIO4ALL. This semi-permanent solution works for now. Hopefully works till summer.

Sal might be on the right path. I was in somewhat similar situation yesterday. Seems ASIO4ALL was the culprit. This is not the driver I use, but for some reason Cakewalk decided to use it here: Preferences > Audio > Sync and Caching instead of a native ASIO driver. Only after I uninstalled ASIO4ALL things got back to the way they should be.

No they are not. Those some are Adobe audition? Who else? Most do offer plans to renters to monetize, offer a choice to those who can't afford or don't need it long term, but as soon as they switch to sub only "business" people start ditching them. Waves and Reason are vivid examples. Both reverted their shortsighted decisions. There are very good reasons for this, most mentioned above. It's really strange "market" strategy, especially concerning Sonar considering what AI is saying: "Cakewalk, which was once a paid DAW (previously known as SONAR), became free in 2018 after being acquired by BandLab. Despite this, it remains relatively less popular compared to other major DAWs. Cakewalk's market share is likely in the 2-4% range"

The least what they could of done is offer a permanent unlock for current Cakewalk by bandlab for full year subscribers of new Sonar. Like 99% of cars are sold with an emergency spare tire. By not offering perpetual license and holding hostage Cakewalk by disabling activations from time to time, my trust of this company diminished greatly. Also, because Specific wording of Cakewalk discontinuation was present in FAQ at Sonar release. A particular person working for BL promised to keep us updated on this issue never responded (it's somewhere in this forum section) They suppress such conversations, which is a bad karma.

Thanks for additional info. I've never seen a realtek installing Asio shell by itself... As I've mentioned, most likely it was installed by another DAW. Again, as long as it works, I don't want to touch anything, as I have no clue why Cakewalk keeps on switching to something else instead of Yeti specifically here : Preferences > Audio > Sync and Caching, while everywhere else in Cakewalk it is pointed to correct driver.

I think this IS the right approach. I removed ASIO4All. What I got now in Preferences > Audio > Sync and Caching are two choices #1 - Generic Low Latency ASIO Driver #2 - Yeti Pro ASIO Same deal with trying to replace #1 for #2- it switches by itself to #1 again... mystery. I think one of non-Bandlab's daws installed that Generic ASIO. Cubase? Reaper? I dunno. However, even with this Generic Low Latency Asio driver, it seems it solved the issue with ridiculous latency. The question is, should I investigate further, or follow the golden rule of not touching c#ap if it doesn't stink? My wild guess is something is up with compatibility between (ancient, but special) Yeti driver and Cakewalk and my fear is that if I try to remove that strange Generic driver, mic might not want to work at all. Could it be that Cakewalk is avoiding problematic driver in such way that it just falls back to the next available without reporting error? In any case, it is for the most part resolved, and I thank you all for giving this time!!!

Thanks for giving this a shot!! I am using official Blue ASIO driver. It's old, but seems installs & recognizes everything without the issues. I started with easiest solution and found something strange. I went into: Preferences > Audio > Sync and Caching and saw that it was syncing to ASIO4ALL.... I changed that to Yeti clicked OK, re-opened Preferences, it switched back to ASIO4ALL clicked OK (tried Apply too, same result). Could this be the issue? Is there a reason it silently switches back to ASIO4ALL? Here is a video clip of what's happening: https://www.youtube.com/watch?v=Dp1YCTMVdr4 ------- P.S. I have an Apogee one usb mic from about 5 years ago, works like a charm. Zero issues.

With this specific question it's almost inevitable that some will offer a suggestion of interface. Just want to be clear upfront. I do have a decent interface and studio mics. This is for a different purpose. About 15 years ago I experimented with USB mic. Particularly Blue Yeti Pro. (That was way before Logi bought them). This mic had amazing features at the time, especially 24 bit recording and the fact that you can use it as USB or XLR. I've made whole bunch of recordings with this mic using USB, but switched to standard studio mics about 7 years ago. A few computers, operating systems and Cakewalk versions... I decided to re-visit the mic, as it has a very particular sound. What I found is that using XLR through interface sounded differently. Probably because of pre-amps. However, when I plugged it in as a USB device, I got the sound I was after. The problem is latency. Clips come at about 1 seconds late. If I do low buffer of even 256, starts crackling. Yes, driver is ancient, but I was wondering if this clip placement can be set somewhere globally to compensate for certain time, so future recording with this mic will respect that, unless I change it back. Again, kindly no lectures on how bad USB mics are. This is for specific purpose. Please let me know if this is possible. Thank you! P.S. I do have a very different (much newer) USB mic, it doesn't have this issue. So I believe the only solution is to use some kind of manual offset for this particular mic.

I dunno. Could be related to newest massive win update? Last few days I've noticed a different anomaly with Cakewalk UI. GUI would suddenly shrink to 1/4 size (all of it, like zoom out on whole thing) for a few seconds, then released to normal size, and be OK for the rest of the time while opened. I wonder if Win update screwed something up in graphics. Never seen this before.