Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New ASIO SDK available #1880

Closed
ann0see opened this issue Jun 16, 2021 · 9 comments · Fixed by #1981
Closed

New ASIO SDK available #1880

ann0see opened this issue Jun 16, 2021 · 9 comments · Fixed by #1981

Comments

@ann0see
Copy link
Member

ann0see commented Jun 16, 2021

Has this feature been discussed and generally agreed?

No.

Describe the solution you'd like

Download the latest ASIO SDK 2.3.3, and use it to compile the Windows build.

Maybe this fixes the build error in autobuild? no. It’s just a non behavioural change according to the change log.

Describe alternatives that have been considered

Move to portaudio (?)

@npostavs
Copy link
Contributor

Describe alternatives that have been considered

Move to portaudio (?)

It's not really an alternative, portaudio would use the ASIO SDK too.

@ann0see
Copy link
Member Author

ann0see commented Jun 16, 2021

Ok. So it also downloadeds the ASIO SDK?

@npostavs
Copy link
Contributor

No, you gotta download it yourself :)

(it is possible to use portaudio without ASIO, but would probably get much worse results for devices that have ASIO drivers)

@jujudusud
Copy link
Member

What about using Windows 10 new audio APIs (Audiograph or WASAPI) ?

@npostavs
Copy link
Contributor

What about using Windows 10 new audio APIs (Audiograph or WASAPI) ?

That only makes sense to avoid having to use ASIO4ALL (since ASIO4ALL itself uses WDM, as far as I know). If you have a device with a native ASIO driver then using ASIO will most likely give the best results.

@jujudusud
Copy link
Member

Using ASIO (if available with the hardware) is the only way on Windows to achieve a low latency without New APIs handled on the apps.
Using new Windows 10 APIs is, in my head, the best way to avoid having to use ASIO4ALL with a non ASIO device for Jamulus.

@henkdegroot
Copy link
Contributor

Maybe this fixes the build error in autobuild?

What error have you seen in the autobuild?

@ann0see
Copy link
Member Author

ann0see commented Jun 17, 2021

It’s gone. It seemed to be a temporary permission error while downloading the .zip file

@npostavs
Copy link
Contributor

Using new Windows 10 APIs is, in my head, the best way to avoid having to use ASIO4ALL with a non ASIO device for Jamulus.

Please check out #870 to try it out then :) (latest installer link is in the first post)

@gilgongo gilgongo linked a pull request Jul 9, 2021 that will close this issue
@ann0see ann0see mentioned this issue Aug 27, 2021
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants