OutrageProductions

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.

Open the Inspector; clip properties and you can type in the exact bar/beat starting point.

Ok folks; to clear up some confusion: as the writer, she held the copyrights to the songs, but her masters were owned by the record label (pretty common industry practice since the 1930's) as a rising artist. The controversy arose when Big Machine was usurped by a hostile takeover from someone who also represented Kanye West, and they enjoined Taylor's use of the "mechanical" rights to her performances on those masters; meaning she could not perform them identically and receive exclusive remuneration, in either live or documentary productions. Which is why she chose to recreate most of those recordings as "Taylor's Versions" and then retain the mechanical rights as well. Very few artists through history have managed to regain ownership of their masters once signed over or their catalog was sold.

Taylor Swift just bought back the rights to her first six albums released on Big Machine. If you create the art, you should own the art.

https://www.nytimes.com/2025/05/27/arts/music/rick-derringer-dead-hang-on-sloopy.html

I've been streaming several channels of SomaFM for years and love the variety!

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...