Trying to start qjackctl I get this:
On Sun, 6 Jul 2025 23:47:55 -0400, bad sector wrote:
Trying to start qjackctl I get this:
Yeah, I used to have trouble with that. In the end I would run jackd
directly from a terminal window.
If you’re running PipeWire, then JACK functionality is rolled into that anyway.
On 7/7/25 1:46 AM, Lawrence D'Oliveiro wrote:
On Sun, 6 Jul 2025 23:47:55 -0400, bad sector wrote:
Trying to start qjackctl I get this:
Yeah, I used to have trouble with that. In the end I would run jackd
directly from a terminal window.
If you’re running PipeWire, then JACK functionality is rolled into that
anyway.
One of a few reasons I like qjackctl is the GUI connections display,
makes it all very easy.
On Mon, 7 Jul 2025 07:39:45 -0400, bad sector wrote:
On 7/7/25 1:46 AM, Lawrence D'Oliveiro wrote:
On Sun, 6 Jul 2025 23:47:55 -0400, bad sector wrote:
Trying to start qjackctl I get this:
Yeah, I used to have trouble with that. In the end I would run jackd
directly from a terminal window.
If you’re running PipeWire, then JACK functionality is rolled into that >>> anyway.
One of a few reasons I like qjackctl is the GUI connections display,
makes it all very easy.
Yes, that used to work, once jackd was already running.
With PipeWire, I run qpwgraph, which gives an equivalent GUI. The
difference with PipeWire is it is supposed to handle video patching in the same way as audio and MIDI patching. So it replaces PulseAudio and JACK,
and adds more functionality.
...PipeWire doesn't seem ready for prime time (or it isn't
adequately integrated in Tumbleweed).
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 1,064 |
Nodes: | 10 (0 / 10) |
Uptime: | 150:53:35 |
Calls: | 13,691 |
Calls today: | 1 |
Files: | 186,936 |
D/L today: |
443 files (116M bytes) |
Messages: | 2,411,008 |