|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
HDX Consensus
Hi Everyone,
I've done a lot of reading on the topic, but I'd love to hear a consensus on the strengths and weaknesses of the HDX card. I've heard about issues with ADC and latency, and I'd like to understand what the issues are and how people work around them before I invest in HDX. I have a MTRX Studio with TB3 now. I've considered Carbon for the HDX workflow, but I'd rather not have more than one actual interface if I can avoid it. I love the idea of the Hybrid Engine workflow for tracking, thus my reaching out regarding HDX. Worth it? Not worth it? What are your thoughts? Thank you!
__________________
Be safe and well, Shawn Honsberger Argyle Street on Apple Music System Details: Apple Mac Studio M2 Ultra 24 Core CPU, 60 Core GPU 192GB Unified Memory, 4 TB SSD Apple iPad Pro M2 (12.9-inch) (6th generation) I/O + Control Surfaces: AVID Pro Tools | MTRX Studio (TB3 Native) AVID Thunderbolt 3 Option Module RTL (96k): 1.2ms at 32 samples, 1.8ms at 64 samples RTL (48k): 2.3ms at 32 samples, 3.6ms at 64 samples AVID S1 EUCON Controller Elgato Stream Deck XL Software: Apple macOS 14.4.1 AVID Pro Tools Ultimate 2024.3.1 AVID EUCON 2023.11 AVID Control 2023.11 Dolby Atmos Renderer 5.2.0 SoundFlow 5.7.7 Scheps MOMDeck Apple Logic Pro X 10.8.1 Drivers: AVID MTRX Studio Firmware 1.1.3.1 AVID HD Driver 2024.3 AVID DADTBDriver CoreAudio 1.1 |
#2
|
|||
|
|||
Re: HDX Consensus
I doubt you will find much in terms of a consensus. Bugs and tech issues aside, is the hybrid workflow actually beneficial? Or was it really just a move Avid needed to make to try and keep 12 year old HDX DSP vaguely relevant in an age of rapidly advancing CPU technology?
It is worth taking the hybrid engine for a spin before you commit to dropping a fortune on a HDX card. Personally, I fall in the latter. The hybrid engine wasn't an improvement in workflow to me. It was the thing that caused me to ditch HDX entirely...
__________________
Pro Tools Ultimate 2024.3. OSX 13.6.5. Win 10. HD Native. Lynx AES16e. Lynx Aurora 16. i9-13900KF. ASRock Z690 Steel Legend. 64GB Ram. AMD Vega 64. BM Decklink. Dolby Atmos Renderer 5.2. Trinnov D-Mon. D-Command. |
#3
|
||||
|
||||
Re: HDX Consensus
Good morning!
I love my HDX system. I'm primarily a recording studio. I love being able to not worry about latency when tracking or overdubbing into a big mature mix. I haven't had any latency issues except some time ago when tracking with a session with a lot of complicated signal routing. Haven't had latency issues in years since that.
__________________
Will Russell Electric Wilburland Studio https://linktr.ee/wilburland M1MAX Mac Studio OS 14.4.1, PT2024.3, HDX, S1/Dock M1 PRO MacBook Pro OS 14.4.1, PT2024.3, BabyFacePro FS |
#4
|
|||
|
|||
Re: HDX Consensus
I find Hybrid useful to use your digilink hardware through the connection while having all the voices of native.
For tracking, I only use HDX (classic) mode. Tracking with Hybrid mode (DSP channels, lightning bolt on) I dislike immensely. Too many compromises and too much hassle. I'd rather switch to classic HDX mode. So I mix in hybrid and track in HDX classic.
__________________
Pro Tools Ult 2024.3.1, HDX 2, MTRX/SPQ, RME BBF Pro + MADIface Pro • S1 x 2, Fire Max11 x 2, Dock, iPad Air5 • Mac Mini 14,12, 12 core, macOS 13.6.6 • RAM 32GB, SSD 4TB, GPU 19 core • QNAP TVS-872XT 148TB TB3 |
#5
|
||||
|
||||
Re: HDX Consensus
Quote:
I trust your opinion having read your responses all over the DUC for years. What have your experiences been recording with hybrid to have made it not worth your time?
__________________
Will Russell Electric Wilburland Studio https://linktr.ee/wilburland M1MAX Mac Studio OS 14.4.1, PT2024.3, HDX, S1/Dock M1 PRO MacBook Pro OS 14.4.1, PT2024.3, BabyFacePro FS |
#6
|
|||
|
|||
Re: HDX Consensus
Quote:
Second there's the path to output. Every track on the way to output needs to be in DSP mode. I think Avid may have now made this "intelligent" and interrogates the path and flips them all now but it didn't used to. And then we loop back up to problem 1 above -- any plugins on that path non-DSP get disabled or if you hit a hybrid plugin, the whole session can crash. I have sat in with clients and an engineer where they were "let's put the artist in the booth to take a quick overdub", throw a channel into DSP and watch Pro Tools blink out of existence. None of those things are an issue with classic HDX (where you can also mix DSP and native plugins.)
__________________
Pro Tools Ult 2024.3.1, HDX 2, MTRX/SPQ, RME BBF Pro + MADIface Pro • S1 x 2, Fire Max11 x 2, Dock, iPad Air5 • Mac Mini 14,12, 12 core, macOS 13.6.6 • RAM 32GB, SSD 4TB, GPU 19 core • QNAP TVS-872XT 148TB TB3 |
#7
|
|||
|
|||
Re: HDX Consensus
__________________
Best, Sean Sean McDonald Red Medicine Recording LLC Sofa King Music Services http://www.seanmcdonald.com |
#8
|
|||
|
|||
Re: HDX Consensus
And workflows for fix-up/rerecoding/punch in if you need to do that? Can you pick up the mix in process you have that needs this and get stuff done OK staying in hybrid mode or are there problems?
|
#9
|
||||
|
||||
Re: HDX Consensus
Quote:
__________________
Will Russell Electric Wilburland Studio https://linktr.ee/wilburland M1MAX Mac Studio OS 14.4.1, PT2024.3, HDX, S1/Dock M1 PRO MacBook Pro OS 14.4.1, PT2024.3, BabyFacePro FS |
#10
|
|||
|
|||
Re: HDX Consensus
Another issue I always encountered with HDX in hybrid mode was totally cooked delay compensation. Mixing in Pro Tools with a coreaudio interface would give me beautifully synchronised two pips on printed audio in the session. HDX in classic mode would do the same with some blue mode use. The hybrid engine was a total mess, with two pips flamming all over the place.
All this stuff absolutely adheres to a laws of diminishing returns. I love using HDX in classic mode, but it also suffers from its own diminishing returns. 256 voices per HDX card, along with changes to how those voices are allocated. A native plugin on a 5.1 aux channel will chew up 2.5% of the available voices. Toss a Nugen DSP plugin on the aux instead, and there goes 2.5% of your available DSP. It's the weird conundrum that the Hybrid engine was meant to solve. 256 voices of HDX Classic processing is really a non-event for modern, powerful native systems running at 32 sample buffers. You should really try switching out HDX for a decent, low latency native interface to do some thorough testing. You will probably be shocked to see how limited HDX is. Probably even more so, now that the 2024.3 update allows Pro Tools to use both P & E cores in the system. The only place I have really found HDX to hold its own anymore is in sessions that both stretch the voice numbers towards 2048 of the hybrid engine, whilst also requiring low latency monitoring. It is just a shame it hasn't be executed very neatly.
__________________
Pro Tools Ultimate 2024.3. OSX 13.6.5. Win 10. HD Native. Lynx AES16e. Lynx Aurora 16. i9-13900KF. ASRock Z690 Steel Legend. 64GB Ram. AMD Vega 64. BM Decklink. Dolby Atmos Renderer 5.2. Trinnov D-Mon. D-Command. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Windows 10 Consensus? | seanmccoy | Pro Tools 12 | 9 | 07-15-2016 08:06 AM |
consensus on 10? | basslik | macOS | 39 | 03-07-2012 09:42 AM |
PT 8 on XP, where is it at, consensus? | dubrichie | Pro Tools TDM Systems (Win) | 12 | 03-15-2010 08:54 PM |
10.4.11 consensus | Phil Jeffers | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 2 | 11-26-2007 01:36 PM |