OutrageProductions

I concur. The 14900k should be liquid cooled only!

Don't even bother trying to hold your breath on this: vector driven graphics (resizable for resolution) of Sonar are a completely different animal from the old CbB Bitmap style... in both form, function, and coding complexity.

The MS <PC Health Checkup> application can be DL'd & installed to check your system entirely. I have done 3 machines here in my studios without any issues. I had to add a TPM module ($14) to one MOBO, and two machines were running MBR boot formats, one of which was a RAID1 array which made me nervous, but after complete backups, I used a 3rd party app from AEOMI (partition manager) to upgrade both to GPT and it was faster and smoother than I had feared. The same app also has a much more detailed version of the MS tool mentioned above. Proper preparation is everything. And my entire desktop organization came up intact on all of them. The only thing that still bugs me (and I'm working on recode) is that the Win Explorer always opens in a place where I don't want it (but I run 4 monitors) and can't yet change that. Not mission critical, but irritating. Also HIGHLY recommend creating a W11 boot recovery drive (and learn how to utilize it) on a thumbdrive ASAP after upgrade. Saved my butt twice when I made some creative hacks to the registry... 😁

This is generally how I mockup bending double-stops on string instruments before cutting real strings from the score. Works well.

You may lose some old 32bit VSTi or DXi instruments because of W11 security issues. It automatically removed my original installation of Dimension Pro, Rapture Pro (and a couple of others), but those instruments were cr#p sounding IMO anyway. On identical HW with similar services disabled, I actually benchmarked minor speed improvements in W11 (~4%) countered by about 900Mb increase in idle RAM consumption. And I had to do tons of tweaks to the GUI to be comfortable, but otherwise... very satisfied. I'm still running some (non-musical) software from the XP/Vista era without issues under W11.

If your MOBO/chipset/BIOS & boot drive format are fully compatible, it's very easy to do an in-place upgrade. MS has a tool that will answer all your questions about upgrading to W11.

Sounds like the DC coupling section in the input of your amp is kaput. Tube amps are especially susceptible to this kind of induced noise.

Benchmark tests on my workhorse studio machine show that W11 has a 4% increase in speed of opening & manipulation of most applications, however (with identical services disabled) it is using 900Mb more ram at idle over W10. Sort of a minor tradeoff.

Your GPU is incapable of doing the math.

As an aside: other than Mark @msmcleod, I haven't seen much presence from any of the Bakers since mid March. Either they are busy coding on the next update, or...

Either that, or judging from his paws and the grin, he just successfully played "Great Balls of Fire" at 320BPM.

You should probably start HERE.

This is true for their lower end I/O's from 2021 onwards. Prior to that... not so much. Hence the A4A issues.

Start HERE with an excellent series on the basics of the application.

Learn how to understand and use all of the options available in the Export Dialog.

Real ASIO drivers don't go through the audio profile dialog AFAIK. Only WDM & WASAPI. There isn't currently a true ASIO driver for MOBO audio (coming soon on next gen HW tho!), only for external audio interfaces. If you have a fake (ASIO4ALL/Realtek/Behringer, et al) driver that says it's ASIO, then you're asking for problems.

I love it so far.

@Tom Bednarz I run sessions that will eat up to 80-90 Gb of my 128 available, but after flushing back to just the basic OS requirements leaves me with about 4.2Gb actually in use. I've found that NI Kontakt (et al), Spitfire, and UVI have a tendency to hang around in the Standby ram waiting for cocktails or the after party for some reason, so... {Some folks have an issue with, and will argue about my method, but I've been using it for 25+ years with zero issues:} DL "Rammap(dot)exe" and unzip it somewhere convenient. Create a batch file to open a CMD window and (with echo on, and a 2 second delay between each command) run the <Empty Standby List> & <Empty Working Sets> commands to flush the ram. Store the batch file somewhere convenient like the desktop and name it "Flush Ram(dot)bat" or something. I do this after and/or between each session. Works like a charm. It has never failed. Not even once. [Here's the batch file:] ::@echo off echo cd\{YOUR EXACT LOCATION OF RAMMAP} START rammap -Et timeout/t 2 /nobreak START rammap -Ew timeout/t 2 /nobreak Exit

To convert an analog audio source to a digital (computer/DAW) data stream you MUST have an AD/DA audio interface. If you want to track (in real time) multiple sources (like a drum kit), said interface MUST have a discrete input channel for each microphone desired.

If the track you are viewing has been frozen, it will just show the latter. Unfreeze it and the keyboard comes back.

Not gonna happen. All DAWs that support VST3 are from 2018 or later. Deal with it as is, or upgrade.

Have you enabled Echo Input on the channel?

Have you used any MIDI monitor (Midi-OX for example) to confirm that your keyboard is still sending out data? You may have had a component level failure in your keyboard. If your MSK25 is BlueTooth [MkII], you may have lost the transmitter.

The latest version of Kontakt is 8. Session Percussionist requires v7.7 or later of either Kontakt Full or Player. Works here in that configuration in both CbB & Sonar. You might try posting this issue on the NI forum in the Kontakt sub.