Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by MediaGary

  1. Truly, it's wonderful that you got to the bottom of this issue. I wish I had seen this thread earlier, as I could have saved you some heartache. Back in 2015, I had a plan to add two more SSHD's (a reasonable term for a hybrid HDD) to the two that I already had in order to build a very interesting RAID array. Things went badly *very* quickly, and that flavor of the project was abandoned. It's documented in the 2nd article of a 5-article series on my website. [ https://www.tedlandstudio.com/torpedo-at-the-dock ] The additional SSD cache in the HDD of a hybrid drive isn't especially effective because its small size makes it inherently slow, and it's not especially well-matched to media-based workloads that audio and video creates. Since then, I've made quite a few combinations of hybrid hard drives, and finally, at this time, I use a limited-horizon approach to this by using PrimoCache. You can read my summary description of PrimoCache, and the way that I use it in two posts that I did on another forum: [ https://www.gearslutz.com/board/showpost.php?p=15353007&postcount=13648 ] [ https://www.gearslutz.com/board/showpost.php?p=15354350&postcount=13655 ] Thanks OP for closing the loop and updating us with the solution!
  2. About the curve... I had the 55-inch (diagonal) LG OLED C6 curved screen on my DAWs for about two years. The curve for that one peaks at about 1.5-inches deep across its 48-inch width. If it was two flat panels in a 'V' arrangement, it calculates out to about a 3.4-degree angle. One advantage of curved screens is that it reduces the color/contrast falloff that's typical of IPS and VA technology panels when viewed an oblique angles. OLED panels don't have that falloff issue, so curves are wasted in that respect. I specifically chose the Samsung Q80T QLED for its contrast consistency at oblique angle views. I still would rather have kept the flat LG CX were it not for its too-aggressive brightness limiter. I have since learned that there is a way to overcome the CX ABL by delving into the service menus. Oh well... Once I went back from curved to flat, my brain had to re-adjust! My eyes/brain had developed habit of making the curved top edges of app windows of the apps to look 'normal' to me. When I went flat, it looked *wrong* for two days until I re-adjusted. In terms of sound, there was no difference to me in the interaction between the speakers and the screen. That's not surprising, considering how mild the curvature is.
  3. Watch out for people who get lazy with terminology in the world of computers! It's deadly. The Intel Hyperthreading and AMD Symmetrical Multithreading are both technologies that provide two threads per physical computer core; hence the 6/12 or 8/16, etc. terminology.
  4. This has come up before on this forum. I'm providing two links (below) to my posts on the topic. I used a curved 55-inch LG OLED display for about two years, and have since gone back to a flat LED display of the same size, even after testing the new LG CX OLED. I found that the auto-dimming, ABL (Automatic Brightness Limiter) and self-protection algorithms were bugging me. https://discuss.cakewalk.com/index.php?/topic/8458-new-34-monitor-age-old-questionproblem/&do=findComment&comment=77226 https://discuss.cakewalk.com/index.php?/topic/24049-how-is-cakewalk-on-a-4k-monitor/&do=findComment&comment=198593
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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
  13. 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.
  14. 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?
  15. 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/
  16. I volunteer my machine for running testing projects if that would help the cause.
  17. Is the Firewire PCIe board built with a XIO2213B chip? Are you using the Default or Legacy 1394 OHCI driver?
  18. 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.
  19. Thanks to @msmcleod and to @Will_Kaydo for your interest in this topic. I may have to draw a proper picture of my network connectivity, but the Echo Pre8 and the RME 9652 are in separate machines across a 10GbE network, so I don't get the benefit of a loopback/in-computer timing. RME 9652 PCI-----Computer1-----10GbitEthernet-----Computer2-----FireWire----Echo Pre8 The 10Gbit cards are Solarflare 5122F's that have fiber optic links through a MikroTik [CRS309-1G-8S+IN] LAN switch. Solarflare cards have sophisticated drivers with TCP/IP Offload capabilities. That may or may not contribute to what I'm seeing here. Computer1 and Computer2 are both HP Z220 workstation computers. Comp1 has an 8GB i5-3470 and its primary job is as a server. Comp2 is a 16GB i7-3770 whose primary job is as an Administration machine. Those two machines are participating and showing the 12-millisecond arrival difference between the Firewire and ASIO Link network signals. The picture attached below is the topology of the two studio computers when the MADI and ADAT connections were merged via the RME driver in the AMD/Win10 computer that's in the lower left side of the diagram. This combination achieved a 0.4-millisecond difference. The computer in the lower right is a 2010 Mac Pro now running Catalina. Since that diagram, I'm temporarily running the M32 via good old USB 2.0. The fact that ASIO Link Pro works at all may be enough, since the network-sourced audio inputs at best would be supplemental for experimental. However, if The function of ASIO Link Pro and AudioGridder ever showed up within the same product, like a poor-man's point-to-point Dante with the added sophistication of horizontal/remote VST processing, that would be a game-changing event in audio studio solutions. [hint, hint]
  20. Wow, thanks for that tip! Because my test machine had been used for *many* tests along the way, I had to un-install the ASIO drivers for the Klark-Teknik KT-USB, Midas MR18, Dante Via, and the Echo Pre8 before starting to get some forward momentum. The initial testing over the network was ... uninspiring. I managed a best case of a 12-millisecond difference (~576 samples) between the networked audio and the 'native' Echo Pre8 audio arriving in Cakewalk. In comparison, when I had the Audient ADAT coming in the Cakewalk along with the MADI audio from the Midas M32, merged via the RME HDSP 9632 and RME MADI drivers, the difference was around 0.4-milliseconds (~20 samples) Since this is just an exercise in what is possible in networking with free products like AudioGridder, it's no big deal, but certainly reveals how much it'll take to eventually make this a production-friendly solution.
  21. Thanks for showing us the way on this. I'm stumped right now: I have ASIO Link Pro running in two Win 10 (Home and Pro) computers in my "Test Lab" before I migrate to the Production Studio... Computer-A = ASIO Echo Audio Firewire (Echo Pre8) with ASIO Link Pro and CbB Computer-B = ASIO RME HDSP 9652 clock source ADAT with ADAT-1 /ADAT-2 from two different Audient ASP800's. AES/EBU master clock is from a Midas M32 to an Aardvark Sync DA that uses 3x BNC 75-ohm coax word-clock connections (2x ASP800 1x Echo Pre8) Network is 10GbE Ethernet ; Computer-A= Computer-B= I have verified that I have 'Received Audio Data' on 'Network In' coming from Comp-B to Comp-A. Network in a Comp-A is patched to 'ASIO Driver Out Mix' Signals from both the ASP800's and the Echo Pre8 show up as expected. When I start CbB the first error message is that 'Analog Out 1-2' is in use by another application. The next error/problem message is that all of the 16 outputs of the Echo Pre8 are unavailable and muted. Another problem is that within CbB 'Preferences>>Devices' all the of Echo Pre8 check boxes work normally, but all the ASIO Link Pro check boxes for 'Input Drivers' and 'Output Drivers' are greyed out and inoperable. I can't shake that feeling that I've missed something obvious, so I'm appealing here for ideas and diagnostic directions to take.
  22. I did an experiment a couple months ago that may be relevant to this discussion: The tested device was a 500GB Gen4 NVMe drive running the ATTO Benchmark in both a direct-to-CPU PCIe slot, and a switched PCIe slot. The result was a ~1-percent difference in the throughput. Link is below: https://www.gearslutz.com/board/showpost.php?p=14878090&postcount=1827 Also, outside of the space requirements for the audio, it's important to keep both the overall speed capability and the user experience in view. There was a pretty careful test done to compare the sample loading performance of an NVMe drive versus a conventional SATA SSD. The differences in the loading/usage experience is far smaller than the speed difference between the two technologies. I'd like to see other tests of this kind, particularly in the context of CbB. Link is below: https://docs.google.com/document/d/1wL8XYGgd_O9fomMrK1EpSnZJeQwhVOAn91e82byj8s4/edit Lastly, keep in mind that 50 mono tracks at 192kHz needs less than 40MBytes/sec to playback.
  23. Yes, I heartily recommend that you watch the Task Manager to see how your RAM usage goes. While I was in "go-big-or-go-home" mode, I built my new AMD machine with 128GB RAM because I have ambitions of running my Vienna Ensemble Pro and some other very impressive libraries that I've purchased. Along with that, I have the intent to run AudioGridder in the AMD machine as a VST/VSTi server to my venerable 2010 Mac Pro. So far, the high water mark for my RAM usage has been when I had DaVinci Resolve and CbB open concurrently. Even that was a total of less than 12GB. The biggest usage of the RAM is the 24GB that it's using for PrimoCache. I gained experience with PrimoCache running in the Win10 partition of the Mac and was very pleased. Even though the boot drive in the new machine is a Gen4 NVMe, and my Picture Cache for CbB lives there, on a whim I ran the Primo Cache trial and was amazed at this one thing: I opened a CbB project that had not been touched since Feb 2020, so the Picture Cache would need to be completely regenerated. The project is 34 mono tracks, 2 hours long. Because of PrimoCache, the Picture Cache was generated within 15 seconds. It was truly impressive to see all those CPU cores lit up, and to get of sense of what had to be some high-rate data movement. You can't directly observe the data rate of disk I/O in PrimoCache, but a benchmark like ATTO shows peak speeds over 22GBytes/sec. That's not a typo...it's 22,000MBytes/sec writing, and around 17GBytes/sec peak reading. That's the benefit of the 'L1' RAM cache in PrimoCache. The latency of RAM is about 20-50 nanoseconds, so it's 1/1000-th the wait time of even an NVMe which has latency numbers in the 20-100 microsecond range. The other lovely benefit of the PrimoCache implementation is that the 'L2' cache essentially makes the 'L1' RAM cache non-volatile, because it replicates the L1 RAM cache during operation, and restores it during reboot. I have 200GB of L2 cache apportioned on a Gen3 NVMe. Unfortunately, that's the *only* circus trick that makes all that RAM worthwhile if I'm not yet building an orchestral soundtrack for the next blockbuster. (Will we ever go to the movies again?) So, back to my original premise, spend some time watching the telemetry of the tools within Win10 so you don't over-invest. I think half of the RAM I have may wind up in the new machine that I will soon build for my son.
  • Create New...