You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
one device (Device B) is selected which supports both 44100 Hz and the sampling rate of the "faulty" device (Device A)
set the desired sampling rate while using Device B
switch back to Device A while you keep the sampling rate enum intact
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)
The text was updated successfully, but these errors were encountered:
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
Also there's a workaround where
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)
The text was updated successfully, but these errors were encountered: