Jim Roseberry

The Roland audio interfaces have some nice features. Lowest possible round-trip latency just isn't their forte'. At a 48-sample ASIO buffer size 44.1k, round-trip latency is 7.4ms.

Rendering video makes even a large/dense audio project look light-weight. IME, The ASIO implementation in Premier, After-Effects, etc is not quite on-par with better audio applications.

A 64-sample ASIO buffer at 44.1k = 1.5ms (This is true no matter what audio interface you're using) While true (and I know you already know this), that's not telling the whole story. When you're monitoring in realtime thru software EFX/processing, you're dealing with round-trip latency: ASIO input buffer (1.5ms) ASIO output buffer (1.5ms) A/D D/A (~1ms) Driver's safety-buffer - this is the X-Factor when it comes to round-trip latency and it's often hidden (can vary radically) In this example, we're already at 4ms... without factoring in the safety-buffer. If the audio interface is one of the better makes, the safety-buffer will be small and round-trip latency will be ~5-6ms. If the safety-buffer is large, round-trip latency can be more than double.

In the case of playing soft-synths, you're dealing with one-way (playback) latency. Monitoring audio tracks in realtime thru software EFX/processing, you're dealing with full round-trip latency. The UR44 (IIRC) yields about 7ms total round-trip latency at a 32-sample ASIO buffer size 44.1k. Some of the absolute latest generation of AmpSim plugins are sounding pretty decent. Helix Native sound pretty good. The new version of TH-U (from Overloud) is going to have a feature similar to Kemper's ability to "profile" actual mic'd amps/cabs. PRS Super Models sounds good (IMO) if you use different Cab IRs Onboard DSP to process/route/mix/loop-back-record can be extremely useful (if you use it). If you're after lowest possible round-trip latency, onboard DSP will slightly increase it. Part of the reason Quantum can achieve such low round-trip latency; it has zero onboard DSP for routing/mixing/loop-back-recording. All monitoring has to be done via software. Why so fixated on lowest possible round-trip latency? In the case of Quantum, since all monitoring has to be done via software, it's critical. Lets say you're using a Kemper Profiling amp... or something like Helix or HeadRush (all hardware guitar amp sims). The Kemper itself can have up to 4ms round-trip latency. The whole point of an audio interface like Quantum is to keep round-trip latency as low as possible. If Quantum were yielding 4ms latency, add the Kemper's 4ms latency... and you're at 8ms total round-trip latency (while monitoring guitar). That's a significant step backward compared to hardware based monitoring (8ms vs. near zero). Since Quantum can actually get down to 1ms total round-trip latency, even with Kemper's worst case scenario, you're at 5ms total round-trip latency. At 1ms total round-trip latency, Quantum makes software based monitoring effectively on-par with hardware. Monitoring via software at 1ms round-trip latency hits the CPU hard. High CPU clock-speed is critical... as this isn't a process well-suited for multi-threading.

In today's economic world, few have the luxury of being 100% altruistic.

The 896mk3 Hybrid interface (and all the Hybrid series) was (round-trip latency wise) a step backward from the original 896HD. The original 896HD yielded 5ms round-trip latency at a 64-sample ASIO buffer size 44.1k The Hybrid series added onboard DSP processing/mixing... and that increased round-trip latency to ~6.5ms at those same settings. To get sub 4ms round-trip latency from MOTU USB, you have to be running one of the newer AVB models (or spin-offs). The newer MOTU USB drivers allow you to tweak the safety-buffer size. FWIW, Thunderbolt under Windows is not a crap-shoot. You just have to make sure you've covered all the details. MOTU was one of the first companies to have (release version - not beta) Thunderbolt drivers for Windows that support "PCIe via Thunderbolt" (allowing PCIe level performance).

The reason they gave you that advice... Echo cards never worked with bridged PCI slots on motherboards. Lynx cards also had major issues with bridged PCI slots. RME and M-Audio were much more forgiving... and worked with most bridged PCI slots.

Add an instance of Kontakt (and load the desired sound/s) Add an Audio Track Assign the Audio Track to receive audio from that Kontakt instance (Input drop-down list) Assign the MIDI track to output to the instance of Kontakt (Output drop-down list)

This doesn't answer the OP's question... but he might want to check out Melodyne (light version included with CbB). Melodyne is far more advanced (sounds better) for intonation adjustment.

Well placed overheads can capture the bulk of a good drum-kit sound. This is a great example of that... Well done

+1 scook Open the type 1 SMF... and immediately save it as a Cakewalk Project. Often times, there are unwanted Tempo, Patch Changes, and Volume/Pan MIDI events. I'd strip those out unless specifically desired. Then, assign the individual MIDI tracks to specific virtual or hardware instruments.

Delete CbB's "aud.ini" file. You'll have to reset your audio preferences. In similar cases, that often resolves the issue.

Hi Larry, I get it... When we play, we always hire commercial sound/lights. Makes the whole process easier and more enjoyable. Most of the local working bands here do the same. When 1am hits, we (old folks) want to load our gear and head home. The band has to charge more, but that's offset by a competent engineer actually mixing the show (both audio and lights). A great sound/light company helps fully maximize the band (which helps with draw/etc).

Was the original Standard MIDI File type 0 or type 1?

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.