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
Has this feature been discussed and generally agreed?
No. But a I assume many people are aware of it
Describe the solution you'd like
If you select devices with a wrong sample rate in e.g. ASIO4ALL or misconfigure devices, Jamulus currently handles this as fatal error (See soundbase.cpp SetDev). Users of ASIO4ALL might select a device which doesn't support 48kHz. This results in a warning and a fatal error. Jamulus will then ask you to close the app, even if the driver settings are open. Also you can't even open Jamulus if something is wrong with your audio devices since it quits with an error message. #305 fixed some parts of this issue, but in my opinion the current handling is not user friendly. I'd expect:
A clear error message that the current device is not supported in this state which doesn't disappear unless you fixed the issue.
A clear hint how to fix this issue (but sometimes that's not easy)
Jamulus not being quit. This confuses a lot of users. In my opinion it's not an error which should result in Jamulus being quit. Maybe we could even allow the user to change basic settings or connect to a server with chat only?
Same goes for automatically selecting another device if the configured device is not available (i.e. forgot to plug in.)
This should only give a warning. Do not change any settings automatically, since this confuses a lot of users.
Has this feature been discussed and generally agreed?
No. But a I assume many people are aware of it
Describe the solution you'd like
If you select devices with a wrong sample rate in e.g. ASIO4ALL or misconfigure devices, Jamulus currently handles this as fatal error (See soundbase.cpp SetDev). Users of ASIO4ALL might select a device which doesn't support 48kHz. This results in a warning and a fatal error. Jamulus will then ask you to close the app, even if the driver settings are open. Also you can't even open Jamulus if something is wrong with your audio devices since it quits with an error message. #305 fixed some parts of this issue, but in my opinion the current handling is not user friendly. I'd expect:
See: #305 (comment)
The text was updated successfully, but these errors were encountered: