Jump to content

Jim Roseberry

  • Content Count

  • Joined

  • Last visited

  • Days Won


Jim Roseberry last won the day on June 29 2020

Jim Roseberry had the most liked content!

Community Reputation

536 Excellent


Recent Profile Visitors

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

  1. Power profile is certainly part of the equation... but not all of it. CPU cooler has to be able to keep up (or course). Your audio interface determines the latency your DAW can achieve. The CPU has to be able to sustain the load (glitch-free)... but has no direct affect on the actual latency figure. 6.8ms total round-trip latency isn't bad. If you want lowest possible round-trip latency, Presonus Quantum can achieve sub 1ms (96k using a 16-sample ASIO buffer size). Right now, only the 10900k can sustain any type of load at those settings... and that's do to the super high clock-speed (5.3GHz). PCIe 4.0 SSDs have zero impact on audio latency. PCIe 3.0 SSDs sustain 3500MB/Sec. PCIe 4.0 SSD sustain about 4000-5000MB/Sec. You may be surprised to hear that the 5950x is currently performing slightly better with the B550 vs. X570 chipset. X570 is also active-cooled... which means small (annoying) high-RPM fan. Noisy! 5950x is an $800 CPU. If you're waiting for significant discount, it's going to be an extended wait. 😉
  2. Getting the new Vermeer AMD CPUs (like the 5950x) is currently almost like winning the lottery. When in-stock, they're gone within a few minutes. FWIW, I still feel the 10900k is a great balance of cost/performance. 10 cores 20 processing threads All ten cores can be locked at 5.3GHz That's a lot of CPU for $500.
  3. CPU speed is certainly an important factor... but there are numerous facets that affect performance. Just because you see "CPU headroom", that doesn't mean the machine is going to perform flawlessly (for DAW purposes). Threadripper's multi-threaded performance is off-the-chain good, but it's ultra low-latency performance is poor (even the 3970x). The new 5950x (Vermeer) is the first series of AMD CPUs where that's finally been resolved. The 5950x can run loads at a 32-sample ASIO buffer size... that the 3970x just can't sustain (glitch-free). That said, the new 10th Gen i9-10900k can run Helix Native (with a substantial patch using two 2048-sample Cab IRs) completely glitch-free at 96k using a 16-sample ASIO buffer size. The first CPU to be able to effectively do this (no glitches). Even with a 10900k or 5950x, if the machine's DPC Latency is high... you'll experience audio glitches/drop-outs. Lets say you want to run Helix Native at 44.1k using a 64-sample ASIO buffer size. That means the machine has 1.5ms to process the next audio buffer and get it in cue for playback. Anything that interrupts this process will cause an audio glitch/dropout. (ie: Poorly written drivers can monopolize the CPU.) Processes constantly running in the background (backup/sync, A/V, etc) can negatively affect performance. There's performance and power throttling: Say you have a typical song structure... where the song starts with maybe 8-16 tracks of drums, guitar, bass, keys, and lead vocal/melody. When the song reaches the bridge, let's say it breaks down to just the kick and a single bass part. At this point, CPU use (demand) is extremely low... so the system decides to throttle CPU clock-speed down to 1/4 speed... as well as parking several cores. When the stripped-down bridge ends, here comes the massive chorus-out-vamp. Huge stacks of backing vocals, synths, etc. That massive CPU load now falls on the CPU running at 1/4 clock-speed... with several cores that have been parked. Glitches at best... or a complete transport dropout. The harder you're pushing the machine (heavier loads, lower latency), the more important all the details. A general-purpose user wouldn't notice a few millisecond hiccup in data-flow. For someone wanting to run at a 64-sample ASIO buffer size, those few extra milliseconds can result in glitches/dropouts.
  4. With proliferation of (live) streaming, many companies don't feel the need to be bound to NAMM's schedule (especially when it's virtual). D.I. from Line-6 (owned by Yamaha) mentioned this recently on The Gear Page.
  5. Gibson was in financial trouble due to massive spending spree acquiring audio/music companies (many out of their realm of expertise). The whole while, Gibson was generating substantial sales revenue.
  6. The IR loading section was licensed from Two Notes. The reactive-load is not made by Two Notes. I have a pair of Captor-X boxes. They're great (especially for the cost). The reactive-load in the Badlander (to me) sounds slightly better than the one in Captor-X The IR loading in Captor-X as far more advanced: Can load/mix a pair of Cab IRs in realtime Can determine the length of the imported IR (which determines latency) Onboard Reverb, EQ, Enhancer, Tuner (which is erratic), Gate
  7. Just picked up a Badlander 50w head. The onboard reactive-load and CabClone IR sound excellent. Lots of features and versatility... and not over-the-top cost wise It's always a little sad to see a heritage company merge or get bought.
  8. Last time I was testing the 3950x and 3970x, I remember seeing a performance boost using the "Aggressive" Thread Scheduling Model. I also remember some issues when using the Aggressive Mode. I've been testing the new 5950x. AMD has ***finally*** solved their performance issue at ultra low latency settings. I'll revisit the Thread Scheduling Models... and give some details about performance.
  9. https://www.cakewalk.com/Support/Knowledge-Base/2007013271/EUCON-Control-Surface-Support-for-SONAR-X1
  10. There is a Eucon control surface plugin for Cakewalk. You need that, the Eucon installer from Avid, and Eucontrol for iPAD. I currently don't have Eucon installed on my machine. I had it installed/working just fine with CbB. It's a little more convoluted to configure (than native support for Eucon)... as you have to manually configure the various options in the Eucon control surface plugin. You can use Eucontrol to control any Eucon enabled application (ProTools, Cubase, Samplitude ProX, etc). Capabilities go far beyond a simple control surface. ie: You can directly access menu items via a single touch. Even setting up some basic things (undo, redo, quantize, Views, Process menu options, etc) can greatly enhance workflow.
  11. The new metering is certainly nice/welcome. Otherwise (to me)... not an overly exciting update. More than anything, I'd like to see Cubase improve on CPU efficiency. That's where they're lagging behind numerous other DAWs.
  12. Need to dig deeper... Not initially seeing a whole lot new vs. the Kronos II
  13. Unless you know a specific fix that your machine needs, your best coarse of action is to wait (for early issues to be resolved)... and then update.
  14. Unless those multiple audio interfaces are running via a single clock source, the aggregate device is all but useless. Audio tracks recorded/played via two separate audio clocks will drift apart over time (due to the small differences between the clocks). A more robust setup is two audio interfaces (same model/series) that were designed to operate (simultaneously) under the same driver (essentially adding more I/O). Those with multiple audio interfaces all running from a single clock-source (those who'd actually/practically benefit from aggregate devices) are a minuscule part of the overall DAW using community. The DAW using community is a tiny fraction of the overall number of computer users. This is why MS doesn't spend development time... to allow aggregate devices.
  15. We've got one client (scores Films) who's running a Cubase template with 2600 (that's not a typo) tracks. He's not running at a 64-sample ASIO buffer size.
  • Create New...