Your opinion is valid from your perspective and for your use case. However Mixxx is designed as a DJ tool for life performance. In this regards we want low latency and never play any system sound like an Email notification sound or such. This would be embarrassing in a live situation.
While the described main use case works good, it is no reason that the other two common use cases are that hard. It is:
* Use Mixxx as media player
* Mix output of streaming players into your mix
The recently released Pipewire sound server seems to be a good foundation for such a solution. However Mixxx cannot unlash the full power because of the long Audio Stack: Portaudio -> Jack -> Pipewire -> ALSA
Your opinion is valid from your perspective and for your use case. However Mixxx is designed as a DJ tool for life performance. In this regards we want low latency and never play any system sound like an Email notification sound or such. This would be embarrassing in a live situation.
While the described main use case works good, it is no reason that the other two common use cases are that hard. It is:
* Use Mixxx as media player
* Mix output of streaming players into your mix
The recently released Pipewire sound server seems to be a good foundation for such a solution. However Mixxx cannot unlash the full power because of the long Audio Stack: Portaudio -> Jack -> Pipewire -> ALSA
For this Mixxx may access Pipewire directly using the Jack or Pulse API /bugs.launchpad .net/mixxx/ +bug/1172299
https:/
Do you have interest to help here?