Jim Roseberry

You need to disable CPU Core-Parking all together. If it's enabled and you're running at low-latency, it will cause audio glitches. In my experience, the new Thread Director in Win11 (12th Gen CPUs and up) doesn't make a huge difference in performance. I wouldn't migrate to Win11 expecting a major performance increase (or decrease for that matter). If a machine is having DPC Latency issues, ASIO (Native or current) isn't going to resolve the issue. Windows 11 is a fine DAW platform... but being a general-purpose OS, there's a fair bit that needs tweaked. Native ASIO isn't a bad thing... but it alone isn't isn't going to change (negate) the need to tweak the OS.

Read the article... and it basically stated exactly what I thought it would. Class-compliant ASIO driver Arm CPU support I'm coming from the perspective of looking for ultimate performance. I'm using an Antelope Orion Studio Synergy Core (main DAW) and a Presonus Quantum (secondary machine)... which are both Thunderbolt audio interfaces. I chose those specifically because they're pushing the limits of ultra low-latency performance (sub 1ms RTL). The Orion Studio Synergy Core has great fidelity, onboard DSP, flexible routing, etc. IMO, All the best features rolled into a single audio interface. I don't think native ASIO is a bad thing. I'm certainly not against it. For me, it isn't bringing anything new/improved to the table. Same with ARM CPUs... When it comes to CPUs, I want the fastest "workstation" CPU I can get. Don't care if it's Intel, AMD, etc... (whatever offers highest performance at a given point in time). Right now, I'm running AMD's 9950x. Certainly Laptops have their purpose... and I see why some folks are interested in ARM CPU development (lower TDP, lower power demand, etc). Power-management and performance-management typically don't equate to top-performance. Thus, my lack of enthusiasm.

FWIW, I don't get the excitement. Windows 11 x64 is already a great DAW platform. Laptop users can currently run ASIO drivers. The only "advantage" of native ASIO is that the motherboard's onboard audio interface can be used via ASIO. Most DAW users are running a dedicated audio interface... for a multitude of reasons (higher quality A/D D/A, lower noise-floor, balanced I/O, etc). Some current audio interfaces can run sub 1ms total round-trip latency. Native ASIO isn't going to improve upon this. Apple has had "Core Audio" for years (akin to Native ASIO). Core Audio doesn't outperform current ASIO drivers on a PC.

Finding the right pointing device can really help those with RSI issues. Many folks love a trackball. For whatever reason, they really inflame my Tendonitis. Right now, I'm using a Logitech G703 Lightspeed. Buttons and wheel don't have a lot of resistance... and that seems to keep things comfortable (for my situation). Have never tried the Lift.

Yes, If there's any processing delay from the DI signal, that too would need to be compensated. That's exactly why I wanted you to record two separate passes of essentially the same reamp. I was thinking they'd likely not be 100% identical (thus won't 100% phase-cancel). The waveforms are aligned... and they're (obviously) pretty similar.

If I understand correctly, you're having issues with the reamped (originally DI) signal... and the original Kemper processed signals not aligning. As a quick test, if you do two separate passes reamping the DI signal thru the Kemper, do those two tracks align perfectly (phase cancel)? I would also measure the time offset between the Kemper's DI output and it's processed output. Now that you know that the audio interface itself is recording properly time-aligned, what happens when you do a short test recording (both DI and Kemper processed)... then try reamping that DI signal thru the Kemper? If the Kemper's DI is slightly latent, you just need to figure out the amount. If that's the case, for the future... use a quality DI box prior to the Kemper. An all analog path would be zero latency. If the DI is post A/D, it's definitely going to have some amount of latency.

First, you need to make sure your audio interface is perfectly aligning audio tracks (when recording). Most ASIO drivers don't report the actual latency accurately... causing a "record offset". Measure the record offset: Take a really short spike type signal (snare hit, impulse-response, or similar)... and re-record that to a second track via analog output to analog input (physically patch it). Now, zoom way in... and you're most likely going to see the tracks aren't perfectly aligned. Measure the time difference between the two spikes (measure this in samples. This is the actual record offset. In Cakewalk/Sonar: Preferences>Audio>Sync And Caching>Record Latency Adjustment (samples), enter the amount of of the record offset. Verify the record offset is working: Record the original spike onto a third track (same procedure as above). Zoom way in... and you should see the first and third tracks (spikes) line up perfectly. NOTE: You should do this for any audio interface (regardless of cost/quality). You only need do it once. Once you've verified all tracks are now properly record aligned, recreate your Kemper External Insert effect (measure the latency). Kemper re-amps should them line up precisely.

IIRC, Kemper has ~2-4ms of latency (input to output). There's no way for any DAW software to automatically compensate. However, if you take the time to configure an External Insert for the Kemper (within Cakewalk/Sonar), Cakewalk/Sonar can measure the latency and compensate for it. Note this only works if configured as an External Insert. Otherwise, you have to manually align to the original track. This is true with any DAW application (not just Cakewalk/Sonar).

Core Ultra 9 285K (not currently in-stock) 8 Performance cores 16 Efficient cores 24 Processing Threads 5.7GHz Max Turbo Core Ultra 7 265K 8 Performance cores 12 Efficient cores 20 Processing Threads 5.5GHz Max Turbo Core Ultra 5 245K 6 Performance cores 8 Efficient cores 14 Processing Threads 5.2GHz Max Turbo Performance gain vs 14th Gen is ~13%... but TDP is lower. AMD's 9950x is ~4% faster than the Core Ultra 9 285K. Some mid-tier Z890 motherboards come with useful additional features. Four M.2 slots Integrated Thunderbolt-4 port Nothing mind-blowing... but definitely a step in the right direction. With removal of Hyper-Threading, I was wondering if performance would decline (vs 14th Gen). Glad to say that's not the case.

I've got a pair of WA273-EQ preamps (four channels). One of the two developed an intermittent noise issue (early on... so Sweetwater swapped that out). Haven't had a single issue since. For the cost, they're hard to beat.

Heard about it yesterday. Insane world we live in. One local guitar player friend plays the mini Friedman JEL head.

Hi Keni, I never had any issue with Codemeter.

Hi Keni, Codemeter is a hardware dongle (similar to iLok or e-Licenser). For a good while, Codemeter was used by Samplitude. Magix moved away from using Codemeter... and it's not been used by many other developers.

With a laptop, you're dealing with a lot of performance throttling and power-management. Neither are good for a high-performance DAW scenario. First thing I'd do is check DPC Latency.

Ultra low latency performance of NuSonar (I like that name ) is significantly better that prior versions.