#Usb vs firewire audio interface latency 64 Bit#
#Usb vs firewire audio interface latency driver#
#Usb vs firewire audio interface latency 32 bit#
#Usb vs firewire audio interface latency upgrade#

MOTU's PCIe 424 controller can be used with the 2408mkIII. Lynx doesn't make a PCIe unit with 8 channels of analog I/O. Lynx, MOTU, and RME all make excellent PCIe audio interfaces. If that's the case, no audio interface will work well at lower ASIO buffer sizes. Have you measured the laptop's DPC Latency? My guess is it's pretty high. Lots of throttling going on to keep CPU temps in check with most laptops. That's 4.3ms total round-trip latency at that 48-sample ASIO buffer size 44.1k. I can run substantial loads glitch-free at a 48-sample ASIO buffer size. FWIW, I run a RME Fireface UFX (which is a USB2 unit with 30 channels of I/O).

Eight channels of I/O is nowhere near saturating the USB2 bus. Hi John, FWIW, I'm going to repeat what others have said. Any recommendations on a PCIex with 8 channels. Feel like hard wired PCIex slot is the way to go on a new computer. The fire power of the laptop is overshadowed by the bottleneck of the USB 2 connection. The thing sounds like a popcorn popper unless I increase the buffer to over 2 sec.

#Usb vs firewire audio interface latency 64 Bit#

Have a 64 bit win 7 i7 laptop 6G RAM connected via USB 2 to a Presonus 22VSL box. Have been beta testing a synth that is a real CPU hog but performs well on the XP rig.

#Usb vs firewire audio interface latency upgrade#

This performs well, 10 channels, but obsolescence has me up against a wall and will have to upgrade the system at some point.

#Usb vs firewire audio interface latency 32 bit#

Qualitative assessment is that I have an old quad core XP 32 bit rig with a PCI M-Audio 1010 LT sync'd to a 2 channel M-Audio 2496. Looks like vdd is dealing with the same issue. Never been on this part of the forum and was about to open a thread. JohnKenn Jim, Can you clarify a bit more since didn't understand some of the intention.

#Usb vs firewire audio interface latency driver#

3) the driver for the USB port(s) in your computer. If your driver works for you, great, but I think it highly likely that it is at least partly responsible for your snaps, crackles, pops and poor latency. In that case, a powered USB hub is required. There can be issues with it (and many other 2-input buss-powered i/f's) if you're using condenser mics and trying to supply phantom power to them. PreSonus have dropped support for the VSL interfaces and have just hung owners out to dry. I always had latency issues and ran into the occasional bug. I have a 44VSL and ran it on the hardware in my sig below. Three possibilities to consider: 1) the 22VSL driver (even the 'current' v1.3, which claims Win10 compatibility).

Granted, a CPU hog in the extreme, but the laptop has all the power necessary otherwise to carry the load if there were not a bottleneck somewhere between the motherboard and the USB box.

I can fire up a lean and clean Reaper session, one track only and overload the system with a single instance of Nitroflex. From a performance standpoint, you'd do well with anything RME, MOTU, or Lynx. ie: The RME UFX sounds great, it's rock-solid, and offers round-trip latency on par with the best units available. There's no reason to be put off by the best USB audio interfaces. and gets the A/D out of the PC (which results in a lower noise-floor). If your primary focus is recording audio tracks, I'd go with something that offers a little more flexibility. the RME AI/O is an excellent choice (very popular with composers). If your primary focus is working with virtual instruments. Your machine has to be able to sustain the load. This yields 2-4ms total round-trip latency. The best PCIe units (RME, MOTU, Lynx) allow you to go down to a 32-sample or even 16-sample ASIO buffer size. The best USB audio interfaces (RME) yield 4.3ms total round-trip latency at a 48-sample ASIO buffer size 44.1k.