|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#11
|
|||
|
|||
Re: HD Native vs Thunderbolt direct
Quote:
When running digilink, third-party hardware has to emulate the latency numbers of Avid hardware. Obviously that can only be equal to or greater latency than the device's actual latency. In fact, before the MTRX device profile was implemented into Pro Tools, even the MTRX had to run at a greater latency because it was emulating other Avid hardware (my first two years of the MTRX IIRC.) So you might get better latency numbers.
__________________
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 |
#12
|
|||
|
|||
Re: HD Native vs Thunderbolt direct
^^ almost certainly, Lynx have pointed out before the Thunderbolt is basically their PCIe hardware reimplemented for Thunderbolt and has similar latency to that. Without the padding to slow it down to HD IO latency.
|
#13
|
|||
|
|||
Re: HD Native vs Thunderbolt direct
Great news! TB it is for me!!
|
#14
|
|||
|
|||
Re: HD Native vs Thunderbolt direct
Quote:
Through all the talking I feel they did go more into HDX and not enough into the HD Native. They did mention that the Native card handled the I/O for Protools and a few things about lower latency with Avid hardware. I'm in a similar situation as you. Over the last few months I compared getting an HDX card or Carbon or just going UA Apollo(direct TB) now that computers are getting more powerful. I have the new computer so I need to narrow things down.
__________________
. System info https://duc.avid.com/member.php?u=57185 "please stop OVER-complicating simple things" |
#15
|
|||
|
|||
Re: HD Native vs Thunderbolt direct
I tried using an aurora n via thunderbolt instead of hd native thunderbolt last year. I was trying to avoid having to relaunch pro tools each time I changed the playback engine to/from the Dolby audio bridge. While it worked just fine, if you’re one that often has cpu overload messages while pushing your system, you will probably run into issues with garbled audio after a cpu error. To get back to work you have to open up the playback engine settings, change the buffer to a different setting, click ok, and then open playback engine settings back up to set the buffer back to your desired setting. It’s not the end of the world, but I went back to hd native because of it. Maybe/hopefully it’s been fixed over the last year with a pt or os update? I hope so, because I’m looking at the new DAD ax64 for my next interface.
|
#16
|
|||
|
|||
Re: HD Native vs Thunderbolt direct
Well, I just tried this with another Lynx. I'm doing a project for a client that uses abelton and they've asked me to try mixing there to make things easier on them. HD Native drivers were disconnecting non stop, so I grabbed another Lynx Aurora N connected via Thunderbolt. It works much better with Abelton, and it's also maybe working better with pro tools? No garbled audio like with previous Pro Tools versions and CPU usage on my studio Ultra seems to have gone down a little somehow.
Last edited by thebeatless; 05-12-2022 at 08:59 AM. |
#17
|
|||
|
|||
Re: HD Native vs Thunderbolt direct
The video helps me clarify the purpose of two FPGAs on the HDX card, versus one on the HD interface. It seems the HD Native FPGA offers some increased channel count in Pro Tools, automatic latency compensation for the interface (versus manual if occasionally needed), and a digilink port for my Omni if I choose to get it working on a planned Mac Studio.
I have believed that Omni HD is fast because it sits on the PCIe bus. This would echo the GearSpace low-latency database showing RME and Lynx PCIe interfaces at the top. But RME's well-written USB2 drivers are not far behind, and better than many interfaces with supposedly faster connections. TB3 is potentially faster but it comes down to drivers. If I owned a Lynx or Focusrite interface with both digilink and TB3 available, I would start with TB3 and enable digilink access only if and when needed for Pro Tools. Sky
__________________
(Opinions are my own, etc.) Mac Studio M2 Max 12/30/64GB/4TB, RME UFX III, Pro Tools Ultimate, MacOS Ventura. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Thunderbolt via HD Native box vs. Strictly Thunderbolt | TheGrobinson | Pro Tools HDX & HD Native Systems (Mac) | 3 | 09-29-2022 04:30 AM |
FS: HD Native PCIe card & HD Native Thunderbolt Interface | LDS | Buy & Sell | 0 | 05-20-2021 03:52 PM |
Avid HD Native Thunderbolt and Thunderbolt Cables. | SoundEng1 | Buy & Sell | 0 | 10-30-2018 10:24 PM |
HD native thunderbolt with thunderbolt card on desktop PC? | martthie_08 | Pro Tools HDX & HD Native Systems (Win) | 9 | 10-12-2016 10:26 PM |
HD native thunderbolt through Echo Express SE Thunderbolt Chassis | hkj1 | Pro Tools HDX & HD Native Systems (Mac) | 1 | 11-06-2013 05:49 PM |