Difficult... It needs a mind...

 

it is working fine and, if i'm not wrong, it gives me less latency with the same buffer (a little bit more than 10 ms, when with the previous one it gave me about 20 ms)

 

Exactly!

 

That is why I was using the Magix ASIO driver for years. This version of ASIO4ALL is working perfectly with Pro Tools 12.5 from Startup to setup. Have launched Pro Tools 1/2 dozen times since install. No issues.

 

Seems to be on par with Magix ASIO driver now. Maybe better.

 

[/]

 

Last edited: Mar 22, 2021

Today I spent about 3 hours testing the new Asio4all and I confirm everything I said previously.
I have an RME system based on 34 physical Ins/Outs, but curiously Asio4all detects 46! (Wow I thought!). I installed the driver previously deleting the RME ones.
* Protools 12.5 HD (the audioutopia version). The biggest problem is that it makes a wrong reading of the Inputs and Outputs. It displays them in any order and cannot recognize whether an input is digital or analog. Some outputs don't even sound. I decided to only work with a stereo pair that works. After having routed an entire song to 2 outputs it remained fairly stable. But soon after he started throwing errors of the type "deactivate some plugins" (I have 64gb of RAM, I clarify and I think I do not know if there were 15 plugins in the project) and finally he nailed. Bye. It does not work.
I went to test it with Melodyne. I couldn't even get a stereo pair to sound.
I went to something much simpler: Band in a Box. Every time an output was set, whatever it was, the program crashed ...
Hope someone works better than me. I pass.

P.S. The GUI is worse than horrible

 

I don't know what to say, but my experience after installed this.. It introduced more latency to my setup. I used Voicemeeter Banana to stream media and sound from my DAW at the same time. I used to jam with a guitar, and all the amp sims in DAW not responded as quickly as it should like with 2.14 version. Latency reported seems to be low in the DAW but the sounds lag a bit , maybe +5 ms. playable but not suitable for fast riffs.

However rerouting directly through ASIO4All gave perfect response as expected

 

To replace it with A4A or because it was not satisfactory?
BTW, their gui (the old one at least) is really similar if not the same. Is it the same contraption under the hood?

I used it too, but eventually I found that latency was not negligible and I could even hear it, I can explain my experience if you like.

Same to me, but then I switched from Banana to Odeus Asio Link Pro, though a bit difficult to get into at first and it worked (latency reduced to a point I couldn't hear it no more) , and it's really more powerful in routing capabilities.
Never needed anymore to switch back to single exclusive ASIO driver.

 

I think I hear it too.Edit: nvm just googled it further and found it.

 

Last edited: Mar 23, 2021

Yeah, that covers it!!!

 

I though that his job description was being an ass4all, but that's only the title of this thread, my misread, me bad. How could I be so wrong?

edit: (I'm feeling snarky, Kid Charlemagne, just some snarky wordplay) .

 

Last edited: Mar 23, 2021

There's no shame in being wrong, just dont be an asiohole about it...

 

Has anyone had chance to test if this new beta version still works on Windows 7 yet?

Since, they appear to imply that it likely will still work, even though they no longer officially support OS' older than Windows 10.

 

Win 7, works fine

 

Just attempting to stay current as to avoid any possible issues with older driver. Most likely same UI from open source files.

If I get around to replacing my Edirol interface with a Thunder 3/4 or USB-C 4 unit, then the AISO4ALL driver would most likely not be needed any longer.

 

It works but changing the buffer size makes Studio one non responsive. Then I had to quit studio one from the task manager and restart again. If i didn't change the buffer, it had no problem.

 

My question is why would you use a driver not designed for your device when it comes with one explicitly designed that unit?

The ASIO4ALL driver is primarily designed to be used with internal sound devices for desktops/towers, laptops & basic USB audio devices.

 

Presonus should develop their own generic ASIO driver for Studio One IMHO.

 

2.15 (BETA 2)

CHANGES SINCE VERSION 2.15 (BETA 1):

• Fix: Sometimes, sample data was truncated to 16 bits on high resolution devices.
• Fix: “Internal Heap Overflow” – message with 32 bit applications on some systems. 64 bit programs were not affected.
• Fix: Sometimes a cryptic string was appearing as USB device channel name inside host ASIO settings.
• Changed AsioGetChannelInfo() to group channels by individual device.
• GUI now showing the audio data format currently used, instead of the capabilities, for any active item.
• Further GUI cleanup