If you find multiple clients accessing a device cause a problem.
#Avid hdx driver#
The writing is on the wall, besides HDX the Pro Tools world is going CoreAudio/ASIO.Īny Core Audio driver should support multiple-clients, not doing so would be a major mistake. OTOH there can be disadvantage in Avid lock-in, requiring DigiLink interfaces, etc., and now HD Native is discontinued. There just is no automatic benefit from operating a HD native system vs. RME also provides better customer and engineering support than Avid does.
#Avid hdx drivers#
I'd sure argue that say RME (what I use) CoreAudio drivers can provide a more reliable, lower latency environment for Pro Tools than HD Native systems.
#Avid hdx software#
to extremely well build driver products shipped by companies with sophisticated internal software engineering teams with deep knowledge of macOS and CoreAudio. From utter crap, vendors shipping not much better than chip vendors sample drivers, drivers done by dodgy contractors and third party teams, etc. It would make much more sense for Avid to release a next gen HDX card, and even then I'm just not sure if Avid has resources to do much.Īny issues with Core Audio are less just the idea that others apps can access the device but rather that the base quality of CoreAudio drivers varies greatly between vendors. The only reasons for funky driver stuff would be if needed to support DSP processing in the box, but I just don't see that coming. I expect/really hope Avid just ships the DAD standard drivers, Avid messing with the drivers would be the last thing I'd want. And here regardless of whatever Avid wants these boxes are build by DAD and DAD are pretty dammed smart. I would be very surprised if any sane engineering organization would produce a non-CoreAudio interface over Thunderbolt.
So I'm wondering if the Thunderbolt 3 will also give the same increase in stability as HD Native did?ĭAD's Thunderbolt products are CoreAudio. We changed the playback engine to HD Native Thunderbolt, and noticed a marked improvement in stability. There were definite minor performance issues, and occasional audible clicks with this setup.
I mainly bring this up because I recently had a system that was using Dante Virtual Soundcard as their main playback engine, and using it to connect to the MTRX STUDIO. (And before anyone mentions it, I know you can use HDX and HD Native as CoreAudio devices in Pro Tools, simultaneously sharing them with other applications, but then you lose that exclusive operational stability and it's a (B) type interface regardless of what processing is on the card).
Will the Thunderbolt 3 interface for the MTXR Studio act like (A) and give Pro Tools exclusive access to it, or will it just be another CoreAudio device that can be accessessed by multiple applications at once? (B) is all other CoreAudio devices, which work just fine, but sometimes have problems because other applications on the computer can access the same driver simultaneously causing a hiccup or crash. (A) is HDX and HD Native, which I would say are "direct" connections with Pro Tools and tend to have very stable operation since they take exclusive ownership of the drivers when used. Does anyone know how the new Thunderbolt 3 interface for the MTRX STUDIO will act with Pro Tools and CoreAudio?Ĭurrently there are two "classes" of playback engine,
0 kommentar(er)
