| Newsgroups |
gmane.comp.audio.jackit |
| Message-ID |
<[email protected]> |
Not my place to comment on this, but it will be very nice.
It is obviously what is needed.
I just have one Caveat though.
I would not pass everything to pulseaudio as pulse has its own silly
volume-facism.
In my humble opinion, get a robust way to let pulse send everything to
jack.
The pulse-jack-sync thing currently in use as an option doesnt really
work.
That way we can have all bluetooth and things desktop managed by pulse,
which it does very well but send the pulse result to jack.
On 2019-03-26 13:53, Thomas Brand wrote:
>
>
> I've thought about the same a few months ago.. mainly just because it
> could help the initial startup, making pulse a backend like alsa and
> others.
>
> It has some merit iff the workflow must use pulse (be it for
> Bluetooth).
>
> My conclusion is that at least 50% of success depends on the standard
> configuration on a distro. So even if jack had a pulse backend, it
> won't
> magically solve all issues but would allow for potentially easier
> startup.
>
> Also IIUC this would work without DBus negotiation etc, one could start
> jack like jackd -dpulse (and everything just works).
>
> Greetings
> Thomas
>
> _______________________________________________
> Jack-Devel mailing list
> [email protected]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org