WASAPI and Video Engine Support

[TrevorMBaker]

Hello everyone! I am new to this forum and new to Pro Tools within the last one and a half years. I am starting my second Pro Tools class, 110, and am writing this thread out of curiosity and as part of an assignment. To be fair, I simply think video engine support will eventually arrive, but I am wondering what perceptions are surrounding ASIO and WASAPI.



The Knowledge Base makes it clear that ASIO hasn't been through the testing Avid would desire, while WASAPI support is their focus. What's the skinny on that situation? I noticed that WASAPI's lowest latency is 256 samples compared to ASIO4ALL's 32 or 64.


I'm glad to be using Pro Tools for post-production work and am looking forward to getting my certification. I hope you are all doing well!

[Darryl Ramm]

I have no idea what you are looking at or talking about. WASAPI is unreliable and a mess in many situations compared to a quality ASIO interface with a quality ASIO driver developers by the interface manufacturer. And there is no universe in which Avid has had more focus on WASAPI than ASIO. If anything Avid has begrudgingly added WASAPI support to cater to new low-end users with Avid's low-end products (a market space where they have struggled badly, but are hopefully doing better now with Pro Tools Intro).

If you are intending to work with Pro Tools. Get a quality interface from a vendor with proven/quality ASIO drivers and a good reputation for long term hardware and software support. RME is an example at top of my list. Other vendors to look at are UAD, Focusrite, Presonus, Motu, Lynx, and at the high end Prism, DaD (or the Avid rebadged products), etc.

The Focusrite 2i2 is the very frequently recommended beginner interface here, including because it has ASIO support and the recommendation is always to use it as an ASIO interface.

[sslechta]

I agree, ASIO is the way to go. I've been running Focusrite interfaces for years.

[The Weed]

Plus a gazillion for RME, not only for their quality interfaces, best-in-class drivers, both ASIO and USB, and very long support, but TotalMix. However, bring your money.

And WASAPI? Run, very fast, from WASAPI.

[TrevorMBaker]

Originally Posted by Darryl Ramm

I have no idea what you are looking at or talking about. WASAPI is unreliable and a mess in many situations compared to a quality ASIO interface with a quality ASIO driver developers by the interface manufacturer. And there is no universe in which Avid has had more focus on WASAPI than ASIO. If anything Avid has begrudgingly added WASAPI support to cater to new low-end users with Avid's low-end products (a market space where they have struggled badly, but are hopefully doing better now with Pro Tools Intro).

If you are intending to work with Pro Tools. Get a quality interface from a vendor with proven/quality ASIO drivers and a good reputation for long term hardware and software support. RME is an example at top of my list. Other vendors to look at are UAD, Focusrite, Presonus, Motu, Lynx, and at the high end Prism, DaD (or the Avid rebadged products), etc.

The Focusrite 2i2 is the very frequently recommended beginner interface here, including because it has ASIO support and the recommendation is always to use it as an ASIO interface.

So, this article on knowledge base is what I am referencing when I say Avid is allegedly leaning toward WASAPI. I have been using ASIO to work with Pro Tools from the beginning.


Read the first two paragraphs

"*Although this guide mentions using ASIO4ALL with Pro Tools, ASIO4ALL is not officially supported or qualified by Avid for use with Pro Tools. We have found this configuration to generally work successfully, but it has not gone through Avid's rigorous testing processes. For a list of officially supported audio interfaces, refer to the Pro Tools system requirements pages."

https://avid.secure.force.com/pkb/ar...-on-Windows-10

[Darryl Ramm]

You need to reread the KB article.

It is talking about ASIO4ALL, not ASIO. You posted claims about ASIO, making completely invalid extrapolations confusing real ASIO with ASIO4ALL. Who cares if ASIO4ALL might be more problematic that WASAPI. Both should be ignored and folks should be using ASIO interfaces.

[lesbrunn]

Originally Posted by TrevorMBaker

Hello everyone! I am new to this forum and new to Pro Tools within the last one and a half years. I am starting my second Pro Tools class, 110, and am writing this thread out of curiosity and as part of an assignment. To be fair, I simply think video engine support will eventually arrive, but I am wondering what perceptions are surrounding ASIO and WASAPI.



The Knowledge Base makes it clear that ASIO hasn't been through the testing Avid would desire, while WASAPI support is their focus. What's the skinny on that situation? I noticed that WASAPI's lowest latency is 256 samples compared to ASIO4ALL's 32 or 64.


I'm glad to be using Pro Tools for post-production work and am looking forward to getting my certification. I hope you are all doing well!

There was a time when my interface broke down and I was forced to mess with Asio4All and Wasapi for a couple of weeks. It wasn't a pleasant experience. As Darryl said, nothing beats a good interface with Asio drivers from the maker of the interface.

[Schottlandru]

I would very much recommend looking at Voicemeeter Banana!

Offers two virtual ASIO drivers, a third ASIO Insert.
I give lectures streaming surround from my laptop through HDMI from Pro Tools.
Back in studio, change playback engine back to RME Asio, done.

[The Weed]

Originally Posted by Schottlandru

Back in studio, change playback engine back to RME Asio, done.

If you have an RME interface, why not use the included TotalMix to do all your signal routing?

For video streaming, would www.vdo.ninja be useful? It's also now combined with the latest versions of www.sonobus.net.

And they're both free.