Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

42 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I got a mental cramp as I tried to translate your description into a topology diagram. If you'd draw one for me, I can be more helpful. Nevertheless, it seems to me that CbB can't see the reported latency of two "layers" of drivers, so its 'Recording Offset' setting needs to be changed to achieve alignment. Get an out-to-in jumper cable on the out-of-time recording input, and run a pre-recorded click track to it. Record the input click track coming through the loopback and adjust the Recording Offset value to make is all happy. That's the best I can offer without a more clear understanding of what's connected to what.
  2. No, I actually didn't think it through to check whether the LP EQ was standard or not. I just remember it being a 'heavy' plugin. My intent is for the test project to be based on an unadorned/vanilla version of CbB so that everyone can participate and we can have valid comparisons between machine configurations.
  3. Can you offer a standardized CbB project that we can all use for comparison? Perhaps a beastly combination of linear phase EQ's, synth/patterns, and other heavy stuff to stress performance the aspects that you'd like to explore.
  4. Seems to me your best first move is to install a AMD Radeon video card. Nothing exotic is required; it's just a way to get DPC latency-friendly behavior from the drivers, since the Nvidia card you have now is a major hindrance to *any* good audio experience. Don't get me wrong, I run an Nvidia card in my AMD-based rig right now, and everything runs great. However, something older/cheaper might be easier to find, and the AMD Radeon world is a good place to start.
  5. Latency of USB ports is *practically* unrelated to its speed in Gbit/sec. You will find that USB 2.0 and 3.1, 3.2 in all its flavors have latency figures that are all clustered around what the driver suite is able to accomplish. Each vendor has its own device driver implementation, and that is a strong predictor of what you'll experience/measure. Also, as you know, a USB 3.x port will 'downshift' to run at USB 2.0 speeds when presented with a USB 2.0 device. Also keep in mind that PCI is less than 1.1Gbit/sec, and that PCIe interfaces tend to be just one PCIe lane. Usually that's a PCIe 1.1 lane, so 250MByte/sec or a net of 2Gbit/sec (payload after decode) is a common performance metric. However, both PCIe and PCI have a vastly different and more efficient driver implementation, and therefore is able to achieve lower latency than USB. I've attached a chart I made a few weeks ago that summarizes the Round-Trip-Latency of all of the attachment methods that I've used with my Midas M32 and Behringer X32 mixers, both in Win10 and macOS. To helps with the nomenclature of the chart: DVS is Dante Virtual Soundcard, AES16e-50 is a Lynx PCIe card, the DN9630 is a USB 2.0-to-AES50 adapter, the MADI interface is an RME PCIe ExpressCard, the LoopBk was direct ADAT-out-to-ADAT-in of an RME HDSP 9652 connected through an external box to a PCIe slot. Lastly, X-ADAT is the way that RME 9652 card is connected through my Midas M32 that serves as the center of my studio.
  6. Hey, @GreenLight I have a 4k screen, and there's a screenshot capture of how I have it organized when I'm running Cakewalk. I run CbB at 100% so nothing is magnified. That requires a pretty large screen that allows all of the little numbers/icons in the Control Bar to be represented. Use a website called www.isthisretina.com to compare and calculate reasonable viewing distances. If your 4:3 screen is 1280x960, then it's about 84 pixels per inch with a "retina distance" of 41-inches. To maintain the same 84-PPI , a 52-inch diagonal screen would be required at 4k. To simply have a reasonable 35-inch viewing distance, my calculations show that a 45-inch diagonal screen would be required to run at 4k/100% . Pick the size that works for you.
  7. Just adding my testimony here: I have/use Nectar 2 Suite; always as an insert. It's super handy to have around because it's a very convenient way to keep a profile of a "plug-in chain" for individuals that send me vocal tracks. The EQ, compression, de-essing, saturation, etc. all in a single preset saved me a bunch of time yesterday when a church called me for an emergency edit/mix for some Christmas presentation content they needed. I find the manual pitch correction function to be clumsy, but the De-Breath works well. I only have used the Harmony Generator function twice in the past 6 years (also have Nectar 1) so I can't say much about those functions.
  8. I'm back with two questions: Did you happen to run the LatencyMon tool by Resplendence on your former 3900X? Can you run LatencyMon for 7 or 10 minutes on this new 5900X? https://www.resplendence.com/downloads
  9. This is hopefully helpful: I have an MR18 that is similar to the XR18 which is functionally similar to your X18 (whew!). First checking the hardware routing ... in the X-Edit app, the In/Out panel (pop-up window) there is a 2x11 grid where 'USB 1/2' column has a blue dot in the cell on the 'Main' row. That's what's needed to get CbB 1/2 out to go to the physical main outs of your X18. As for what you mean about "no audio going to the X18 via the USB lead", you should check the 'Meter' view in the main X-Edit app to see if something is coming from CbB or not. I'm not familiar with the tablet app that runs the X18, checking those two things should get you closer to a solution. Keep us posted.
  10. Please tell me a little more: What RAM speed and latency and motherboard (e.g. 3200-C16, X570) ? Are you using the Firewire or the USB of the MOTU 896 Mk3 ? Which release of Win10 are you using?
  11. You should run Xmeters in the taskbar of your computer. I have it configured to show operating system stuff in orange, and the other color for application work. You'll quickly see that a CPU logical core is never dedicated to one or the other, but *very* dynamically mixes the workload. Another thing is that it's quite interesting to see CbB go all out with Drum Replacement. It's actually quite beautiful to see how evenly loaded all 32 logical cores are during that process. https://entropy6.com/xmeters/
  12. I volunteer my machine for running testing projects if that would help the cause.
  13. Is the Firewire PCIe board built with a XIO2213B chip? Are you using the Default or Legacy 1394 OHCI driver?
  14. I have both, and work within both. The Win10 is the AMD 3950X in my signature, and the macOS machine is a 12-core 96GB 2010 Mac Pro (affectionately called the Millennium Falcon) that runs Catalina 10.15.6, has Alpine Ridge Thunderbolt, 10GbE, and will soon benefit from running insert plugins via AudioGridder hosted in the AMD machine. Both machines are concurrently connected to my Midas M32 mixer; the AMD via USB 2.0, and the Mac via a K-T DN9630 AES50-to-USB 2.0 adapter. My reason for this elaborate configuration is that I collaborate with musicians who have projects in Reaper, CbB (Win-only), Logic Pro X (Mac-only) Digital Performer, and Studio One. In pre-Covid days, they'd bring over the projects on a portable drive of some sort. These days, things are so slow, that I'm learning video editing and doing wild audio configuration experiments to keep myself entertained. As for preference, it's still a 50/50 thing after several years of having a foot in both camps. I like the backward-compatibility of Windows that preserves the investment in hardware, allows PCI (distinguished from PCIe) devices to still be used, and allows the re-use of technology orphaned from data centers. On the Mac side, I like the multicam features of Final Cut Pro (Mac-only) that have yet to be matched by DaVinci Resolve, and the soft-synths built into Logic Pro X. My eyes are happiest when using CbB. The other DAWs are less beautiful to me.
  • Create New...