Jump to content

Jim Roseberry

Members
  • Content Count

    697
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by Jim Roseberry

  1. QC seems to be a nice "cherry-picked" feature set of Helix, Axe-FX, Kemper. I'll grab one from Sweetwater (when they're actually available). The Mooer G300 can also load "profiles/captures". You have to use an iPad to create the captures (a bit of a pain)... but it works. Our local SamAsh had one used for $550... so I grabbed it to test. Sounds a whole lot better than you'd expect (given cost and being MIC).
  2. AMD has finally gotten their ultra low latency performance together with the new Vermeer (5xxx) series. I've got a 5950x based DAW (I'm typing on it right now). The 10900kwill out-perform the 5950x when it comes to ultra low latency performance (example below). In heavily multi-threaded scenarios (video rendering), the 5950x will significantly best the 10900k. Lets say you want to run Helix Native (plugin version of the Line-6 Helix guitar processor)... at latency equal to or lower than the hardware version (which is 2ms). When it comes to ultra low round-trip latency, the Presonus Quantum is as good as it gets. Set Quantum to 96k using a 32-sample ASIO buffer size. This results in 1ms total round-trip latency. Load Helix Native and create a significant patch using two 2048-sample Cab IRs, delay, reverb, etc. The 5950x is the first AMD CPU to be able to sustain this ultra low latency scenario completely glitch-free. With the Threadripper 3970x, you'll experience glitches. Needless to say, this is excellent performance. With the 10900k, you can actually set the ASIO buffer size down to 16-samples (sub 1ms round-trip latency)... and it'll sustain the load glitch-free. It's the first CPU we've tested that could actually do this... The 10900k is a $500 CPU. The 5950x is a $800 CPU. Competition benefits all of us.
  3. Unless you're a beta-tester or "influencer", you don't have a Quad Cortex (haven't started shipping). Pete Thorn has done an excellent demonstration video...as has Rabea Massaad. The QC is going to be another great guitar modeler/profiler option (along with Helix, AxeFX, Kemper, etc).
  4. That's not what I'm saying in any way/shape/form. 😉 We deal with many Mac users who simply can't get the speed/configuration they need to run large scoring templates. The solution is a well-configured custom PC DAW. Exactly what they need... nothing more... nothing less Windows 10 is a fine DAW platform... once fully reined-in. If you watch any popular TV series, you're hearing scoring work that's using a PC. Danny Lux, Timothy Wynn, Fred Coury, etc... The top LA based composers meet once a month for dinner... to discuss all things technology and music.
  5. Performance is slightly better with B550 vs X570... and no additional noise. I'm not interested in lower-end Vermeer CPUs... as the clock-speed is slower.
  6. 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. 😉
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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
  12. 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.
  13. 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.
  14. https://www.cakewalk.com/Support/Knowledge-Base/2007013271/EUCON-Control-Surface-Support-for-SONAR-X1
  15. 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.
  16. 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.
  17. Need to dig deeper... Not initially seeing a whole lot new vs. the Kronos II
  18. 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.
  19. 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.
  20. 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.
  21. Here's hoping 2021 is a much better year!!!
  22. In nearly 30 years, I don't think I've ever been contacted by a client who wanted to work at high ASIO buffer sizes (higher latency)... or at lower CPU clock-speed (to conserve battery-life or power). 😁 Folks have different levels of needs/expectations.
  23. Live Nation recently publicized that they're going to ask performers to take a substantial pay cut. This (naturally) upsets performers... If the venue can only be 1/4 capacity, that means 1/4 the intake. Everyone loses... and ticket prices skyrocket even higher
  24. Fixed x2 😁 In Ohio: Gigs (only large clubs can afford full bands) start at 6-7pm... and end at 10:30-11pm Last-call is at 9:45pm. Alcohol sales end at 10pm. Bars have to be closed at 11pm. I don't mind the early gigs... but does the "Rona" only come out at 11:01pm? People are "loading up" at last call... leaving hammered... and/or going to private after-parties to continue.
  25. You'll need a MIDI Drum Map that changes the MIDI notes (recorded from the TD25)... into the MIDI notes that trigger the desired sounds from EZ Drummer. If one doesn't already exist, I'm sure you could create one in 30-60 minutes. Create a test project with the following: MIDI Drum performance (recorded from the TD25) - on a MIDI Track MIDI Drum Map (to map the TD25 pad notes to articulations in EZ Drummer) Instrument Track with EZ Drummer You could (also) change the MIDI notes the TD25 pads send... to match the desired sounds in EZ Drummer (thus eliminating the need to use a MIDI Drum Map). There are also MIDI Drum Maps in EZ Drummer (there is a "Roland" Map but not sure it matches the TD25). There's no right/wrong way to get to the proper MIDI notes (to trigger the desired EZ Drummer sounds). Pick what makes most sense to you. With the above test project: On the MIDI track with your MIDI drum performance, select the MIDI Drum Map (you created for the TD25) as the MIDI output If you use a MIDI Drum Map in Cakewalk, that Drum Map allows you to select the EZ Drummer instance for the MIDI output of each mapped MIDI note If you use EZ Drummer's MIDI Maps, skip this step. If you changed the MIDI notes sent by the Nitro pads (on the TD25 itself), skip this step. If not using MIDI Drum Maps in Cakewalk, set the MIDI Output (of the recorded MIDI Drum track) to EZ Drummer. The recorded MIDI drum performance should now be triggering EZ Drummer (with the desired articulations). When you insert EZ Drummer into your Cakewalk project, you have two options for the Instrument track. Simple Instrument Track - creates a single stereo output for EZ Drummer Instrument Track Per Output - creates a track for each audio output from EZ Drummer With the first option, you'd have to mix the drums within EZ Drummer. With the second option, you've got individual mic channels that can be mixed within Cakewalk (Kick, Snare, HiHat, Toms, Overheads, etc). There's no right/wrong... just how you prefer to work The Focusrite Scarlett series is OK when it comes to round-trip latency (~6ms at the smallest buffer size). It would be better for triggering EZ Drummer samples in realtime (than the TD25's onboard audio interface)... as it offers lower round-trip latency. Some drummers would find even 5-6ms round-trip latency too much lag to comfortably trigger EZ Drummer samples in realtime. Get that lag (round-trip latency) sub 3ms... and it feels a lot more immediate.
×
×
  • Create New...