OutrageProductions

At this point, maybe a complete clean install of CW is in order. Noel has a sticky about how to do this near the top of the forum categories.

You can rename the Aud.ini to aud.OLD and it will get rebuilt on next open of the DAW. In the registry under (IIRC) HKLM a section for ASIO (just search the reg for ASIO) and make sure that any "ASIO" named drivers for ASIO4ALL, Realtek, Nvidia HDMI etc. are deleted, reboot & restart CW. Make sure that you have the ASIO drivers for your I/F installed (Presonus or Scarlett) and try again. Interesting that you can only get 44.1SR. My 18 year old Audiobox has always been set at 48k/24b and works perfectly.

As @57Gregy started on; completely delete anything that is ASIO4ALL related on your system and in the registry. You may need to do the same with the Realtek driver system, but it causes lesser issues in about half of all systems, and may reinstall if it is on your MOBO. The Audiobox should only use the Presonus ASIO drivers that were either supplied or can be DL'd from their support pages. I've used one for 18 years with RT latency as low as 5.3ms and no other issues. Any time you see anything relating to "wave profile" (or derivations thereof,) you are using the Win OS WDM/Wasapi style driver set, which have far inferior response specifications.

You do realize that the onboard staff module is to proper notation as 'notepad' is to word processing, right?

Have you tried to completely quit the DAW before editing the metadata header of the wave file, or is it still running in the background? CW/Sonar have always had a tendency to hold flags on files & folders of a project even after they are closed in the DAW, and only releases the most recent after the entire application is shut down. My other DAWs don't have this issue.

Delete Asio4All from your system... it only causes problems. It's not real ASIO, but a wrapper for the Windows WDM driver. This subject has been covered a thousand times in this forum.

Because of the inherent delay of the attack in most VSL string & choir libraries, I've developed the habit of entering a negative offset on the whole track, which will also compensate for the articulation map keystrokes, as they get sent with priority within the DAW. You can then continue to edit to the grid or quantize without any other intervention. Delay (IME) can be between 15 and 180 ticks, depending on the library voice timbres & tempo of the composition. Similar delay compensation with EastWest libraries. Interestingly enough, I haven't seen much issue with Spitfire or 8Dio though.

It is actually a fully balanced switching matrix capable of anything from 2.1 to 22.2.6 Atmos, so no... not really. I use it for 3 stereo pairs, 2 HP cue feeds, and a 7.1.4 playback system. I used to have a Dangerous Designs system, but outgrew it when I went from 5.1 to 7.1.4.

I use a Grace Designs m908 and it is absolutely transparent and ultra quiet. Probably not in your budget tho... $7k.

Have you tried Antiques Roadshow?

Are you actually using an 'audio interface' or the OS/MOBO built-in audio device? If the latter, then your Windows audio has to be set to the correct SR as well as CW.

It's not "automatic"... you had to type the "K" key at some point. The clue when using "clip mute" is that the subject will change to a 'greyed-out' appearance. To avoid that issue you can change the default keybinding to something else that takes more deliberate forethought.

Also helps to clear the cache in your browser before using the in-app login. If your credentials & cookies are stale, this can be a problem with activation.

You obviously have never read the EULA. You never 'own' any software, you just get granted the convenience of basically leasing it. Unless you write your own applications. Thank you for playing though.

I doubt this is the proper forum, as is seems highly unlikely to be related to audio I/O and software. You likely have a failing hardware issue on the MOBO. Ram is a good place to start by reseating and R/W tests from a shell.