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

Asio Devices not supporting 44100 Hz will throw exception on initialization and won't work... #166

Open
microdee opened this issue Feb 7, 2018 · 1 comment

Comments

@microdee
Copy link

microdee commented Feb 7, 2018

image

Also there's a workaround where

  1. one device (Device B) is selected which supports both 44100 Hz and the sampling rate of the "faulty" device (Device A)
  2. set the desired sampling rate while using Device B
  3. switch back to Device A while you keep the sampling rate enum intact
  4. now Device A initializes correctly

My suspicion is that the node is not getting the proper enum entry before it is asking to open the device with the unsupported (44100 Hz) sampling rate so instead it gets the default enum entry which I guess is 44100 Hz. It freaks out and throws an exception before it can update the enum with the actual supported sampling rates.

I know it might be an edge case but there are drivers not exposing lower sampling rates if the hardware is set to 48000 Hz or higher and makes them unusable with VAudio (like Voicemeeter virtual asio drivers or Jack)

@sunep
Copy link
Collaborator

sunep commented Sep 9, 2020

Sounds related to issue #173 and #165

Working with things like Dante, default sample rate is very often 48000Hz and can not be changed as all audio devices on the network need to be at the same sample rate. That is also why I suggest the default sample rate to be set to 48000Hz as suggested in issue #164

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

No branches or pull requests

2 participants