Jim Roseberry

FWIW, I don't think the "Free" upgrade to Win10 was an altruistic move by Microsoft. They're trying to get Win7,/Win8.1/Win10 users on a single platform. Less to maintain/support

FWIW, If the machine is having issues such as high DPC Latency, it doesn't matter what DAW software/plugins you're running (all with be negatively affected). BTW, Unplugging the LAN port disconnects from the Internet... but it doesn't actually disable the LAN controller. ie: If the LAN controller's driver is causing high DPC Latency, simply unplugging the LAN port won't resolve it. You can update/roll-back the LAN driver... or disable it (Device Manager or motherboard's BIOS) while working with audio.

That combination works great. Used it myself for a good while...

If it doesn't bother you... it doesn't bother you Most guitar players I've seen are either using wedge monitor or IEMs (in addition to their amp). Our guitar player wants to hear the sound from his Amp (about 4' behind him)... plus in the wedge directly in front of him (doesn't use IEMs). Monitoring via wedge or especially IEMs eliminates higher latency of standing 15' from an amp. I like the tight timing from using IEMs, but I don't like the feeling of being isolated/separated from the audience.

With any reasonably current (Intel) build, you'll have Intel USB-2 or USB-3 integrated into the motherboard's chipset. That eliminates most compatibility problems. Prior to Z77 chipset motherboards, literally all USB-3 ports were third-party add-on controllers... as USB-3 had not yet been integrated into Intel chipsets. The CPU load from the USB controller is negligible on a reasonably current CPU. If you run a dense audio stress-test using a PCIe card vs. RME USB-2 audio interface, you'll find you can run the same amount of processing with each. Using the PCIe card doesn't result in more DSP processing power.

FWIW, The best USB-2 Audio interfaces *are* on par with the best PCI audio interfaces. M-Audio Delta and Audiophile series yields 5ms total round-trip latency at a 64-sample ASIO buffer size 44.1k RME USB-2 audio interfaces yield 4.9ms total round-trip latency at a 64-sample ASIO buffer size 44.1k A 64-sample ASIO buffer is 1.5ms at 44.1k (doesn't matter that audio interface you're using). Latency differences between various A/D D/A is negligible. When it comes to round-trip latency, the "X-Factor" is the driver's safety-buffer (which is often hidden). The best audio interfaces can use a smaller safety-buffer. Lesser audio interfaces use a larger safety-buffer (resulting in higher round-trip latency). Round-trip latency is the sum of the following: ASIO input buffer ASIO output buffer A/D D/A converter The driver's (often hidden) safety-buffer

Do any of you remember the DAL CardD+? The first "Pro" audio interface for the PC. ?

FWIW, With Thunderbolt-3 under Windows 10, you've just got to be aware of all the details (leave nothing to chance). You've got to have a motherboard with integrated Thunderbolt-3 controller... or one that specifically supports a Thunderbolt-3 controller AIC (add-in-card). You've got to be running Win10 Your audio interface needs drivers that support "PCIe via Thunderbolt" Most Thunderbolt audio interfaces are Thunderbolt-2, so you'll need a Thunderbolt-3 to Thunderbolt-2 adapter We've used motherboards from both Asus and Gigabyte... as well as custom laptop shells from Clevo. In all cases, whether the Thunderbolt-3 controller was integrated or AIC, performance was 100% reliable. Presonus recommends the StarTech Thunderbolt-3 to Thunderbolt-2 adapter. We've tested the Apple TB3>TB2 adapter under many different configurations (desktop and laptop)... and it's always worked fine. I moved from an Apollo-8 Quad/Satellite Quad setup... to Quantum... because it yields incredibly low round-trip latency. It's a gas to run Helix Native with 1ms total round-trip latency. I believe the hardware Helix has ~2ms round-trip latency. A note about USB-C audio interfaces: Though the units connect via USB-C port, all the models I've seen thus far are actually USB-2 (not USB-3.1 as you might expect).

USB audio interfaces with lowest round-trip latency are RME and MOTU (both sub 4ms). By comparison: The Apollo Thunderbolt series yields ~3.7ms total round-trip latency. Presonus Quantum yields ~1ms total round-trip latency. Note: Many audio interfaces don't allow selecting ASIO buffer size smaller than 64-samples when using higher sample-rates.

Blades, it'll get rid of the "quacky/smacky" piezo sound. Had an Alex Lifeson Les Paul with piezo... and running that thru an acoustic body resonance IR sounded *far* better than it should. It was close enough to be useful for recording (albeit not a substitute for a great acoustic mic'd extremely well).

Steev, Beating a dead horse here, but with the Pro version of Win10, you can shut down (disable) all automatic updates. Once configured, Win10 won't download any updates. If you've got the Home version of Win10, automatic updates can't be fully disabled.

Threadripper is great for heavily multi-threaded applications (video rendering in particular). What's not so great about Threadripper is the lower clock-speed. Not all processes in a DAW application can be multi-threaded, this is why highest clock-speed is still the most critical CPU spec. Right now, the Nvidia RTX video cards (2060, 2070, 2080, 2080ti) are causing high DPC Latency. That's not the case with Vega-64 (no DPC Latency issues). Speed wise, Vega-64 is comparable to a GTX-1080ti.

Steev, we can absolutely be friends. I think it's great that Bandlab bought Cakewalk! I've been a Cakewalk user since the CompuServ forums. ? Excited to see what the future brings... especially this being NAMM weekend.

Mr Roseberry is my dad! ? Call me Jim

Yes, the reverb decay was amplified to make it more obvious, but not by 60dB. At this point, I'm not often rendering to 16Bit audio. Years ago, after hearing the nasty sounding 16Bit reverb decay, I compared different forms of dither (UV22HR, Waves IDR, Pow-R1, Pow-R2, and Pow-R3). This was amplified to make the differences more obvious. Waves IDR was the quietest dither. For whatever reason, Pow-R algorithms 2 and 3 (using noise-shaped dither) kind of "irritated" my ears. Pow-R1 and UV-22HR produced to my ears the best sounding results. I'd give a slight nod to Pow-R1 I try to use Pow-R1 any time I'm reducing bit-depth.

If you've ever played a synth with distortion on the sound... and played in the higher registers, you've most likely heard aliasing. It's a very digital/grainy/phasey type sound... that doesn't sound like part of the rest of the audio. You can run a low-pass filter to reduce/eliminate aliasing, but that may impact the desired sound. On a guitar cab, there's not a whole lot above ~7.5kHz, so it's easier to filter out than on something that has more high-frequency content (like a saw-tooth synth).

I've owned/used all the top modelers. You can get good/great sounds out of all of them. HeadRush is really easy to use. No matter which one, I always run a high-pass filter prior to the Amp Block. This really helps tighten up the bottom end (clean/clear not flabby).

You can also use an acoustic body resonance IR to simulate an acoustic (from magnetic pickups) for live use. Can be done with Axe-FX, Helix, HeadRush, etc. It's not going to replace a great mic'd acoustic, but for live playing... it sounds close enough. Being able to switch immediately from acoustic to a distorted/crunch is super convenient.

Steev, you're great at comedy. I'm going to leave it at that.

I'm aware of not truncating from 24Bits down to 16Bits. The flip-phase example above would produce a result that's close to silence, but I don't think it can be absolute silence (dither noise is added to the 16Bit file - which is not present on the 24Bit file). I get the point. ?

If you do use a Thunderbolt to Firewire adapter (to connect a Firewire audio interface to a Thunderbolt controller), it will not achieve PCIe level performance. It's exactly the same as running a PCIe Firewire controller.

OK, I'll explain it for you. That adapter allows you to connected a FIREWIRE device to a Thunderbolt controller. I mentioned earlier that Thunderbolt is essentially external PCIe. This is similar to using a PCIe Firewire controller. Firewire does not (can not) provide access to the PCIe bus. That's what would be necessary to adapt/connect Quantum (or any other Thunderbolt audio interface).

? Read the fine print, Steev. Then come back and explain how it works.

Show the $29 Apple Firewire-to-Thunderbolt adapter that allows connecting a Thunderbolt audio interface to a Firewire controller... and explain how it works. Explain how you can connect ANY Thunderbolt audio interface (on PC) to a Thunderbolt-2 controller and achieve PCIe level performance. When you talk about your audio interface having 2ms record latency, you do realize that's meaningless, correct? That 2ms of latency is never heard (unless you're monitoring via software... and then it's much larger figure due to round-trip latency). The 2ms is compensated for upon playback. Some audio interfaces don't report their latency correctly; this is why all major DAW applications have a Record-Offset parameter. Regarding Quantum vs. Apollo: Quantum is by far the better low-latency performer.

I think it's sensible to use different sample-rates depending on circumstances. If I'm working with video, I'm using 48kHz. If I'm working with AmpSims, and especially if the project isn't too large, I'll work at 96kHz. If we're cutting a VO in the studio for my wife (Morning show on the local classic-rock station), we'll record that at 44.1kHz. IMO, There are many other aspects of a project that have a more profound effect on the final result than sample-rate. Song Arrangement Performance Mics/preamps/placement I don't believe any record has ever been bought (or not) solely because of the sample-rate. Craig mentioned that CbB has optional over-sampling. Aliasing noise can result from processing distortion (AmpSim, etc). Using a higher sample-rate (or over-sampling) puts the aliasing up above human hearing. When the HeadRush guitar processor was first released, it had audible aliasing noise. That issue has since been addressed (several firmware updates). Aliasing sounds unnatural/nasty (not as bad as digital-clipping... but a close second). It sticks out like a sore-thumb.