Skip to content

Do not quit Jamulus if no valid audio device was found #1338

@ann0see

Description

@ann0see

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:

  1. A clear error message that the current device is not supported in this state which doesn't disappear unless you fixed the issue.
  2. A clear hint how to fix this issue (but sometimes that's not easy)
  3. 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?

See: #305 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    WindowsWindows runtime issuebugSomething isn't working

    Type

    No type

    Projects

    Status

    Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions